CloudBees Jenkins X Distribution provides a stable, predictable release line for teams building cloud native Kubernetes-based applications with Jenkins X. It comes battle tested and ready for production workloads with support and documentation vetted by CloudBees. As Jenkins X rapidly evolves, so will CloudBees Jenkins X Distribution with stability and reliability in the forefront.
March has been a strange month for all of us. COVID-19 has affected everyone in one way or another; some more closely than others. Despite everything going on in the world, we have continued to make progress on three fronts: continuing to improve Jenkins X overall, moving Lighthouse towards a stable state, and rethinking how clusters should be created.
As mentioned with last month’s release, our first milestone for Jenkins X’s future is to carve out the cluster creation from boot, which we’re still working on. Today you would usually use jx boot to first create a cluster and then install Jenkins X on that cluster. Unfortunately, this means that the configuration and setup of your cluster is not stored in a centralized repository. It can be tricky to do maintain or recover your setup without going back and figuring out how you set it up in the first place. Using boot to create clusters also makes it a more complex component to maintain. So to solve both issues, we’ve decided to offer default terraform scripts that will help you more easily set up clusters on AWS and Google Cloud (with support for Azure coming soon) so that you have all your configuration as code; even for your infrastructure. The next phase of this will be to remove the code from jx boot that is now used to create your infrastructure and update the documentation to help you use and customize the Terraform scripts.
We expect the Terraform first scripts and accompanying documentation to be ready soon for OSS Jenkins X. We’ll include official support for them in the April CJXD release.
You’ll find the full list of features and bugs which are part of this release below. The list is also available as part ofthe release notes:
Improve documentation for EKS support using JX Boot
add request-memory option for devpod
Allow to debug/trace GitHub API calls
Boot fails with Helm 3
Jenkins fail to create a service account on google cloud if the cluster is two character name
Booting from a Dev environment's repository after it failed to generate the update PR skips its creation
`cannot parse k8s as path:key` when bootstrapping cluster using `jx boot`
Docker registry repository name error
env variables in overridden step are ignored
Failure to access asset after performing a release and then updating downstream dependencies
Instructions are incomplete and does not work
`jx add app jx-app-jenkins` w/ Bitbucket uses user as dev env owner, not organization
jx boot errors when GitHub owner name contains capital letters
jx boot fails at step to create vault
`jx boot` fails to write version stream information into `jx-requirements.yml`
jx boot fails when using helm3 due to jx trying to run helm init
jx boot fails with --dir flag
jx boot incorrectly changes environment ingress tls secret name
jx step credentials gets the secrets always from a k8s secret when vault is enabled
jx upgrade ingress --cluster not working on EKS (http -> https)
Missing link to preview environment URL
nginx-ingress controller v1.29.0 and later doesn't add address to ingresses
non-boot clusters nil pointer on `jx step helm apply`
PipelineActivity has wrong/insufficient data for batch builds
Release tagging cannot be disabled using noReleasePrepare config flag
signal SIGSEGV: segmentation violation on jx boot command in AKS
Step helm apply does not load team settings
The release pipeline is triggered for a branch named `all-in-master`
Unable to execute 'jx boot' from outside a boot repo
Upper limit for Helm binary to restrictive in jenkins-x-versions
We are creating webhooks before the pipelinerunner service is active on a boot installation
jx boot resets staging urltemplate to default
“Unable to get the Jenkins X Version" error when executing "jx diagnose" command on Windows
Feature: Migrate jx-app-fossa to jenkins-x-apps org
Review of Jenkins X docs to make consistent use of the \application\" term"
Dependency updates fail if a release asset cannot be located
fix repositoryResouce httpCloneURL when using git with ssh
jx diagnose can't handle windows git version
jx import could not determine organisation and repository name
jx step create pr regex' fails to parse upstream dependency asset
As always, you can download the latest distribution here , and if you have any feedback please email me at email@example.com .