-
Notifications
You must be signed in to change notification settings - Fork 974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fork Upbound build submodule #1583
Fork Upbound build submodule #1583
Comments
https://crossplane.github.io/docs/master/release/release-process.html Note that Jenkins (somewhat) automates the above release process for Crossplane, and any proposal to change to a different CI/CD system will need to account for automating Crossplane releases (i.e. tagging, Cross compiling, and publishing artifacts). |
Not strictly related to CI/CD openness, but if we do move to Github actions it would be good to replace our previous configuration that added comments to PRs for linter violations per #1411. |
We're now using GitHub Actions which has made a big difference, but the Upbound build submodule being used internally still means it's hard for folks who don't work for Upbound to understand the blast radius of their changes to the build submodule. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm re-opening this issue for further consideration |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
/fresh |
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as |
/fresh I'm pretty sure Upbound decided to fork the Upbound build submodule. So internal Upbound projects are moving away from it (mostly to a fork, for now). I still think it would be worth forking it under the Crossplane org to clarify that it's a "Crossplane thing", that we could optimize for use only by Crossplane projects. |
See crossplane/crossplane#1583 for context. Signed-off-by: Nic Cope <nicc@rk0n.org>
See crossplane/crossplane#1583 for context. Signed-off-by: Nic Cope <nicc@rk0n.org>
See crossplane/crossplane#1583 for context. Signed-off-by: Nic Cope <nicc@rk0n.org>
See crossplane/crossplane#1583 for context. Signed-off-by: Nic Cope <nicc@rk0n.org>
What problem are you facing?
Edit: Upbound decided to fork the Upbound build submodule. So internal Upbound projects are moving away from it (mostly to a fork, for now). This means there's nothing blocking us from moving (or forking) the submodule to the Crossplane org, to make it clear that it's only used by Crossplane now.
In addition to moving/forking it, I'd like to do a pass over it and remove anything that we know we don't use.
Currently Crossplane relies on a CI/CD system that could be opaque to community members who do not work for Upbound.
How could Crossplane help solve your problem?
At a minimum we should ensure Crossplane's CI/CD system is associated with "Crossplane" rather than "Upbound". This would involve forking the build submodule to github.com/crossplane/build, and hosting Jenkins at https://jenkins.crossplane.io.
We may consider taking this a step further and replacing Jenkins with GitHub Actions. This "GitHub native" CI/CD system may be less opaque to community members, and integrate more tightly with GitHub's native permissions model.
The text was updated successfully, but these errors were encountered: