-
Notifications
You must be signed in to change notification settings - Fork 788
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
add Cloud Native Jenkins workloads #2312
Comments
we should roll these changes in too btw - so folks can easily enable feature branches & Previews using custom patterns: jenkins-x/draft-packs#84 |
we may want to introduce common build steps which are reused across |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
we want to use Jenkins X as the basis of Cloud Native Jenkins - i.e. a cloud native way of automating any CI or CI+CD pipelines for any workloads.
So rather than baking in Kubernetes workloads OOTB, we'd like to make it easy for folks to setup a Team and configure the team with either
Kubernetes Workloads
orRelease Workloads
(just do CI and release libraries/jars/npm modules/binaries but don't do deployment) and allow folks to create additional workloads as extensions.So when installing Jenkins X we should prompt for the workload kind to be used and default to Kubernetes workloads unless folks specify a CLI argument
--buildpack=jenkins-x-classic
etc.As part of this work it would be great to refactor our current build packs so that they are more modular and easy to reuse. e.g. the Kubernetes workload pipelines should reuse the Release workload pipelines (for doing things like setting up git, creating a new release version, tagging git, deploying the jars/npm modules etc) - then layer on top the helm/skaffold/promote/preview stuff.
So lets refactor the build packs into 2 repos here: https://github.com/jenkins-x-buildpacks and make it easier to use a single build pack for both Prow & serverless Jenkins or static Jenkins Servers etc
The text was updated successfully, but these errors were encountered: