CloudBees Jenkins X Distribution Release #7: February Release
This product/service is no longer being offered by CloudBees. Visit https://jenkins-x.io/ to learn more about the community offering.
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.
This month the team has been focusing on two things: continue to improve Jenkins X overall and plan for the future. This has resulted in 30 issues and enhancements being fixed or added and a full audit of the jx codebase to identify which areas we should focus on next.
On the planning side, we’re still exploring a few different options, but we’re taking a very close look at how jx boot is structured and how we can improve it.
The first milestone is to try and separate the cluster creation from the installation and upgrading of Jenkins X. More details will be available shortly in the form of a proposal posted to https://github.com/jenkins-x/enhancements - this is following the new project praxis of publishing proposals for larger initiatives and soliciting community feedback before embarking on the actual implementation. If you are interested in the future of Jenkins X, keep an eye on the enhancement repo and join in on the discussions.
The second milestone is to replace Prow (which handles ChatOps and the communication with GitHub ) with Lighthouse , which has wider git server support (including future support for Bitbucket and Gitlab) and a smaller footprint. We hope to have this switch completed in the April release.
In terms of bug fixes and improvements, the most notable fix is 6568 which was caused by a change we made in the January release that resulted in mismatched permissions. The manual fix was straight forward, but now it’s fixed in the code as well. Otherwise, there’s been a few fixes to Github Enterprise and Bitbucket support, in anticipation of the Lighthouse migration, as well as a couple of critical git-related issues.
You’ll find the full list below, which is also available as part of the release notes :
Document and share development steps required to support Jenkins X on Kubernetes providers
Pass the repo owner into jx step git credentials --credential-helper
rename jx step create install values to something more accurate
Review command deprecation proposal and generate issues accordingly
Knowing how many resources exist for CRD’s is useful when maintaining cluster, a command to list these counts would be helpful
BitBucket Server with boot/gitops/vault gets error for \No git service found\"
Change in googleapis/gnostic breaks \make generate-openapi\"
controllerbuild can’t list config maps and so can’t get git credentials
When jx-auth-config map logic is added, the build controller does not have permission to list configuration maps, which prevents receiving git credentials (jx step git credentials).
CreateTestJxHomeDir only creates tmp JX_HOME in case gitAuth.yaml exists
Dev pipeline fails on fresh jx boot install using bitbucketserver
Diagnose and fix sporadic hangs on environment promotes in boot-vault and boot-local versions BDD tests
jx boot failing on GHE with latest CLI due to failing GET request
jx boot STEP: verify-jenkins-x-environment failing. Returning 401 Unauthorized, Body
jx boot upgrade replaces OWNERS with OWNERS from jenkins-x-boot-config
jx create pullrequest with Gitlab somehow ends up with a \-/\" in URL"
PipelineRuns rerun by Lighthouse due to Tekton race condition won’t be handled by build controller
REPLACE_ME placeholders in buildpacks using modern syntax aren’t replaced
Unable to re-run 'jx boot' from the initial boot config directory
As always, you can download the latest distribution here , and if you have any feedback please email me at email@example.com
Stay up to date
We'll never share your email address and you can opt out at any time, we promise.