Release Notes


Table of Contents

CloudBees Jenkins X Distribution version 2

RELEASED 4 September 2019

Components

Software Component Version

chartmuseum

exposecontroller

2.3.111

external-dns

2.5.4

heapster

jenkins-x-platform

2.0.1012

jenkins-x/jenkins-x-builders

0.1.686

jx

2.0.643

nexus

prow

0.0.1079

tekton

0.0.42

Resolved Issues

Hook and Tide pods failing with credentials error

A problem with users running jx upgrade platform or jx upgrade addon prow on clusters configured with GitOps has been fixed.

Preview environments not getting GC’d

An issue with clusterrole creation for gcpreviews has been addressed fixed.

jx get build logs doesn’t scrub (all) secrets

An issue has been fixed with jx get build logs where API tokens were displayed in clear text rather than masked with asterisks.

Support parallel stages for tekton builds

The mechanism to run the steps of pipeline stages in parallel has been fixed.

Port jx step create pr versions to use new step create pr code to provide consistent messages

jx step create pr versions was updated with more consistent pull request output messaging.

jx import does not respect --git-username and --git-api-token

jx import has been fixed to register the user input for --git-username and --git-api-token.

updatebot making tons of commits to an existing PR in rapid succession causes pipelinerunner to fall over

updatebot has been fixed to allow multiple chart commits in a single pull request.

master sometimes builds twice on merge

A bug was fixed where two builds are triggered simultaneously when jx step create pr is updating an existing pull request.

Preview dead code

A bug was fixed where the correct status code is not displayed when a preview application is unsuccessful.

jx boot fails to create storage

An issue was addressed where storage creation was failing using jx boot when zone is a region instead of a zone.

jx root command contains flags which are specific to only a few commands

A bug was fixed where jx options displays flags that are specific to only specific commands and are not universal flags.

jx boot not installing with vault

An issue was addressed where Vault was not installed when running jx boot with exposecontroller.

Memory limit for pipelinerunner (256Mi) is too low

An issue was addressed where running jx controller pipelinerunner was failing due to low default memory limits.

jx boot is no longer reentrant

A bug was fixed where jx boot can not be run repeatedly due to old versions of the ingress chart.

jx version always fails

A bug was fixed where jx version returns an error unless using a specific jx release.

Release notes missing?

An issue was address where release notes were missing due to a bug in changelog display.

Upgrade add on prow fails on GitOps cluster

A bug was fixed where jx upgrade add on prow fails on a cluster with GitOps enabled due to outdated prow and tekton versions.

gcloud.go appends \"-zone\" to existing DNS zones

A bug was fixed where running jx install --ng --external-dns appends the --zone option by default to existing DNS zones created in GCP.

Creating a long term storage fails if the generated name ends with \"-\"

A bug was fixed when creating a boot cluster and allowing the command-line interface to automatically name the storage bucket, which can cause failure if the name is above 60 characters and leaves a dash (-) at the end.

Support creating private repositories using boot

When running jx boot, it is now possible to create private repositories during the installation process.

jx step helm build fails when using boot

A bug was fixed where running jx step helm build fails due to missing versions, which is addressed using version resolver.

Jx get apps fails on a fresh boot install

A bug was fixed where jx get apps fails due to a missing app.yaml file after a new installation using jx boot.

PipelineResources duplicated for the same branch

A bug was fixed in PipelineResources where a new pipeline resource is created when a pipeline is triggered rather than reusing existing resources for project and branch.

Allow ref of boot config to be overridden on boot CLI

An issue was addressed where Git commit references can now be overwritten during jx boot configuration.

jx add app fails with conflict

A bug was fixed where jx add app fails due to installing the environment in the wrong place using a jx boot installation.

Error finding a tag when creating the dev environment on a fresh boot install

A bug was fixed where a finding a tag returns an error when creating a new cluster using jx boot.

jx boot verify-env step fails to create correct PR for dev environment

A bug was fixed where jx boot is run against a customized jx-requirements.yaml file, and jx step verify env fails to create the correct pull request to merge the customized jx-requirements.yaml back to Master.

Environment PR fails on step helm build when installing an app on jx boot

A bug was fixed where a pull request on a dev environment fails when installing an app on a new jx boot installation.

The step Validate Git fails on the master build of a fresh jx boot dev environment

A bug was fixed where creating a cluster with GitOps using jx boot and subsequently executing the Master branch build of the dev environment results in a failure in Validate Git.

add an alternative to exposecontroller that is more like boot?

An issue was addressed where a jx step expose command was added to simplify any jx boot installation when creating an Ingress for exposed services using a template file.

Improve jx uninstall

jx uninstall has been updated to add confirmation, warnings and details about what resources and components it will delete.

GC Previews not working in vault cluster

A bug was fixed where Garbage Collection (GC) previews fail in clusters with Vault enabled.

verify-generation-complete rule in Makefile.codegen does not fail for untracked files

A bug in the verify-generation-complete rule in Makefile.codegen where it tries to detect changes that have not been committed by running git ls-files --modified, which only captures modified exsiting files but not new files.

Error when running the dev environment master pipeline on a fresh boot cluster

A bug was fixed where the master pipeline of the dev environment on a new jx boot installation with GitOps failed during the kube-system step.

jx upgrade addons downgrades vault-operator

A bug was fixed where jx upgrade addons was downgrading vault-operator from version 0.4.16 to version 0.2.1, which is not available.

allow the parameters.schema.json to be templated for different git providers

The parameters.schema.json boot parameter is now templated for jx boot to allow improved support for kubernetes and/or Git providers.

Pipeline Scheduler trustedOrg is hardcoded in boot config

An issue was addressed where the trustedOrg in the pipeline schedulers of the Jenkins X Boot configuration were hard-coded, rather than specified in the jx-requreiments.yaml file.

Add flag to automatically attempt to distribute parallel stages across nodes

An issue was resolved where kaniko can cause problems with the container garbage collection of the kubernetes node, especially when multiple kaniko pods are running on the node simultaneously.

Error auto cloning jx boot config

A bug was fixed where running jx boot outside of a configuration directory prompts the command line interface to clone it from the CloudBees Git repository, but instead caused an error due to a boot configuration error.

boot: register by default the webhooks over HTTP instead of HTTPS

An issue was addressed where the jx boot command creates webhook endpoints in HTTP and registers them as well as setting the shared secret with the Git provider, which is insecure and users should be forewarned to configure TLS for HTTPS transfer.

Ensure users are aware that Vault does not have a secure (https) connection

Users are now aware via warning and confirmation that Vault does not have a secure HTTPS connection and alllows users to opt out of using Vault.

Broken cloudbees profile

An issue was addressed where the CloudBees profile overrides cloning functionality.

Can’t use latest release for version stream

An issue was addressed where jx boot now uses specified version streams rather than always using the latest release for the version stream.

Previews are not including changes from the PR

A bug was fixed where pull request changes made in branches were not included in previews because pull request builds were cloning Master rather than the branch with the changes.

Certain versions don’t seem to be created by new jx step create pr

A bug was fixed where pipelines was not included when running jx step create pr.

JX boot - running boot twice on a vault cluster overwrites secrets

A bug was fixed where an incorrect value was stored in Vault when switching from local storage to Vault storage in a jx boot installation with local storage enabled

jx boot outputs numerous WARNING messages when templating

A bug was fixed where jx boot installation issues numerous WARNING messages even though the command line interface appears to install successfully.

jx boot step verify-env panics when invalid secrets are used

A bug was fixed where the jx boot command line interface panics with an error when the verify env step is run on invalid secrets.

jx delete application error pulling environment repo

A bug was fixed where jx delete fails to remove created applications and causes an error.

step-verify-env failing when running jx boot in cluster for the dev environment pipeline

A bug was fixed where an error occurs in jx boot when running a master pipeline build in the dev environment.

Change the jx boot order install external-dns before vault

Changes in the installation order during jx boot installation have been made where external-dns is prioritized before Vault installation.

vault ingress doesn’t always get discovered during jx boot

An issue was addressed where Vault service URL can now be discovered via Ingress.

vault name is never saved to requirements

A bug was fixed where the specified Vault name was not saved in jx-requirements.yaml

Exclude build pods from jx step verify pods

An issue was addressed where clusters will hang if build pods are not excluded from jx step verify pods.

jx step helm apply fails to replace vault URLs

A bug in jx ste helm apply that failed to replace the URLs for Vaults has been fixed.

pipelineRun selector wasn’t looking for labels properly

A bug has been fixed in pipelineRun selector where it was not looking for Prow job labels properly.

jx step verify git assumes only pipeline user is configured

An issue was fixed where jx step verify git now validates Git users and verifies the validity of pipelineUser.

jx step create pr versions --excludes stops looking for charts once it finds an exclude

A bug was fixed where there is a break where a continue should be when running jx step create pr versions with the --excludes option.

clientFactory.cloneVersionStream does not work for shas

A bug was fixed where the clientFactory meta-pipeline could not clone the version repository if the version stream branch is in secure hash algorithm (SHA) format.

jx get build logs (and other things using logs) doesn’t order stages properly

A bug was fixed where jx get build logs was not ordering metapipeline logs properly.

jx step create PR should not create empty commits

A bug was fixed where jx step create pr was creating pull requests with empty file commits.

jx step create pr versions should have a fixed order for sources in the matrix.md

A bug was fixed where jx step create pr does not sort the order of the dependency matrix.

jx step create pr is changing versions and then back again

A bug in jx step create pr was fixed where it was changing versions and causing conflicting updates during pull requests.

Executing jx boot with local changes in jenkins-x-boot-config fails

A bug was fixed where jx boot would fail with changes made to the jx-requirements.yaml file in jenkins-x-boot-config.

jx boot pipleine run in a pipeline without tls enabled will fail

A bug was fixed where jx step verify preinstall verification would fail if TLS is not enabled.