This is an automated email from the ASF dual-hosted git repository. vatamane pushed a commit to branch jenkins-upgrade-erlang in repository https://gitbox.apache.org/repos/asf/couchdb.git
commit 63f3e4eff76b5d6ca0e34ae8a6bdf6cb1740a1b8 Author: Nick Vatamaniuc <[email protected]> AuthorDate: Thu Jun 19 23:19:08 2025 -0400 Upgrade Erlang for CI --- build-aux/Jenkinsfile.full | 4 ++-- build-aux/Jenkinsfile.pr | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/build-aux/Jenkinsfile.full b/build-aux/Jenkinsfile.full index 9c8b5565b..b3196d68a 100644 --- a/build-aux/Jenkinsfile.full +++ b/build-aux/Jenkinsfile.full @@ -14,11 +14,11 @@ // the License. // Erlang version embedded in binary packages -ERLANG_VERSION = '26.2.5.11' +ERLANG_VERSION = '26.2.5.13' // Erlang version used for rebar in release process. CouchDB will not build from // the release tarball on Erlang versions older than this -MINIMUM_ERLANG_VERSION = '26.2.5.11' +MINIMUM_ERLANG_VERSION = '26.2.5.13' // We create parallel build / test / package stages for each OS using the metadata // in this map. Adding a new OS should ideally only involve adding a new entry here. diff --git a/build-aux/Jenkinsfile.pr b/build-aux/Jenkinsfile.pr index b7c1036c5..fcd3a8a79 100644 --- a/build-aux/Jenkinsfile.pr +++ b/build-aux/Jenkinsfile.pr @@ -50,7 +50,7 @@ pipeline { // Search for ERLANG_VERSION // see https://issues.jenkins.io/browse/JENKINS-61047 for why this cannot // be done parametrically - LOW_ERLANG_VER = '26.2.5.11' + LOW_ERLANG_VER = '26.2.5.13' } options { @@ -247,7 +247,7 @@ pipeline { axes { axis { name 'ERLANG_VERSION' - values '26.2.5.11', '27.3.3', '28.0' + values '26.2.5.13', '27.3.4.1', '28.0.1' } axis { name 'SM_VSN'
