Building your own branch of ci jenkins pipelines or temurin build

You can now run a build pipeline using your own branch of either ci-jenkins-pipelines or temurin-build, simply by setting parameters appropriately, as follows:

Some things to "note" is as follows:

• The "defaultsJson" are the "User" defaults for various parameters, and is relevant when "useAdoptBashScripts" is set to false.
• The "adoptDefaultsJson" are the "Adopt" defaults for various parameters, and is relevant when "useAdoptBashScripts" is set to true.
• The downstream build jobs now get passed the "USER_REMOTE_CONFIGS" (if useAdoptBashScripts==false, constructed from the defaultsJson pipeline branch & url), DEFAULTS_JSON and ADOPT_DEFAULTS_JSON from the openjdkNN-pipeline job.

Note: If you are changing ci-jenkins-pipelines in an area that affects the top level openjdkNN-pipeline script (pipelines/build/common/build_base_file.groovy), you will likely need to update the Jenkins openjdkNN-pipeline job SCM to point directly at your repo and branch, as at that level it is not always possible to dynamically load everything.

To build using your own branch of temurin-build or ci-jenkins-pipelines:

1. Select the https://ci.adoptopenjdk.net/job/build-scripts/openjdkNN-pipeline and select "Build with parameters"
2. Set "useAdoptBashScripts" to false
3. Within "defaultsJson" "repository" section, change the values of "build_branch" and "build_url" to be your fork and branch of temurin-build.
4. Within "defaultsJson" "repository" section, change the values of "pipeline_branch" and "pipeline_url" to be your fork and branch of ci-jenkins-pipelines.
5. "Build"