Stewart X Addison
Stewart X Addison
Assuming modifying generated-configure.sh is valid, this will fix the fact that AIX currently claims it's output directory is not on a local filesystem when it really is. Alternative solution 1:...
If you try to run the openjdk builds (default or OpenJ9) on RHEL7/ppc64le the builds fail due to a missing symbol GLIBC_2.22 in the `lib/server/libjvm.so` or `lib/compressedrefs/libj9jit29.so` shared libraries. We...
Intermittent failure showing up in (at least) x64 jobs ``` BLIC Listen address[1] = localhost:30050 listening on port 30050:...... at Sep 15, 2017 4:39:50 PM BLIC Listen address[0] = localhost:30060...
We seem to have lost the jobs in the pipeline that verified the `hotspot` variant builds. Looks at the triggered builds it seems to have a default `BUILD_CONFIG_URL` of https://raw.githubusercontent.com/adoptium/ci-jenkins-pipelines/master/pipelines/jobs/configurations...
**Please describe what you want to be able to do that isn't documented and/or what you'd like to see in the documentation** We now have a large number of build...
The Groovy checks on PRs are failing as they can no longer download test-ng 7.2.0 from jenkins-ci.org. Passing log: https://github.com/adoptium/ci-jenkins-pipelines/actions/runs/7213899246/job/19654797971?pr=836 (Seemed to pull correctly: `Downloading https://repo.jenkins-ci.org/public/org/testng/testng/7.2.0/testng-7.2.0.jar to /tmp/gradle_download7089325946772859694bin` Failing log:...
If a non-authorized user looks at https://ci.adoptium.net/job/build-scripts/ they cannot see the non-weekly pipelines such as [openjdk21-pipeline](https://ci.adoptium.net/job/build-scripts/job/openjdk21-pipeline/) or the [evaluation equivalent](https://ci.adoptium.net/job/build-scripts/job/evaluation-openjdk21-pipeline/). This makes it harder for the casual user to be...
**What are you trying to do?** Test PRs in this reposoitory **Expected behaviour:** Tests things that we build **Observed behaviour:** PR test tests JDK20, not 21 or the upcoming 21...
**What are you trying to do?** Run the PR tester on a PR via the `run tests` directive **Expected behaviour:** Builds run as they would in the production buid jobs...
Part of providing a solution to https://github.com/adoptium/temurin-build/issues/3355 This changes the format of the "nightlies" from: `yyyy-HH-dd-HH-mm` to `ea.21+23` which will be reflected in the filename and also in the published...