Build dist is bionic even though jammy is specified in config

Travis CI Discussions & Feedback
, ,
1

This just started happening recently, in the last couple of days.

Conf:

language: clojure
dist: jammy
services:
- docker
addons:
  chrome: stable
lein: 2.9.8
before_script:
- echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
- docker-compose up -d
- nvm install
- nvm use
- npm install
if: commit_message !~ /Version \d+/
script:
- lein eftest
- npx shadow-cljs compile karma-test
- npx karma start --single-run
jdk:
- openjdk24
cache:
  directories:
  - "$HOME/.m2"
branches:
  only:
  - master
env:
  global:
  - LEIN_JVM_OPTS="-Dmaven.wagon.rto=1800000"

Job log

Worker information
hostname: 9ed22019-df69-4fe0-a4bb-418fcf569a34@1.worker-com-bd65588d-rkpwq.gce-production-2
version: deploy_2025.08.20.CI.1 https://github.com/travis-ci/worker/tree/70d52e32e4e4cfdcfeda8e5e475406670be2589f
instance: travis-job-aeba863e-7c05-4864-8cfe-281246daca97 travis-ci-ubuntu-1804-1745853968-72b9825f (via amqp)
startup: 5.914101815s
0.20s0.00s0.01s0.00s0.01s
system_info

Build system information
Build language: clojure
Build dist: jammy
Build id: 276453150
Job id: 635668145
Runtime kernel version: 5.4.0-1106-gcp
VM: default
travis-build version: fc2910e8
Build image provisioning date and time
Mon Apr 28 15:58:55 UTC 2025
Operating System Details
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic
Systemd Version
systemd 237
Cookbooks Version
d0e65ab https://github.com/travis-ci/travis-cookbooks/tree/d0e65ab
git version
git version 2.43.0
bash version
GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)
...
2

Hello,

Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic

This is a known bug currently being worked on, where the dist specification is being ignored, and builds are defaulting to older images.

Since your build is running on Bionic (not Jammy as requested), add this to handle the dpl version issue:

language: clojure
dist: jammy
services:
  - docker
addons:
  chrome: stable
lein: 2.9.8

before_script:
  - echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
  - docker-compose up -d
  - nvm install
  - nvm use
  - npm install

# fix dpl installation
before_deploy:
  - gem install dpl -v 1.10.16

deploy:
  edge:
    branch: dpl-v1

if: commit_message !~ /Version \d+/

script:
  - lein eftest
  - npx shadow-cljs compile karma-test
  - npx karma start --single-run

jdk:
  - openjdk24

cache:
  directories:
    - "$HOME/.m2"

branches:
  only:
    - master

env:
  global:
    - LEIN_JVM_OPTS="-Dmaven.wagon.rto=1800000"

This should fix the problem.

3

Thank you for the reply, is there a way to track the underlying issue where the specified dist is being ignored?

4

@Montana Is there a work-around for using openjdk21?

I’m seeing this error due to using outdated source list:

Err:11 ``https://apt.bell-sw.com`` stable Release
Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification. [IP: 104.18.1.179 443]

Which results in Java 21 failing to download, and thus build fails.

5

Hi @nickdos,

Try adding this in your before_install:

before_install:
  - wget -O - https://packages.adoptium.net/artifactory/api/gpg/key/public | sudo apt-key add -
  - echo "deb https://packages.adoptium.net/artifactory/deb $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/adoptium.list
  - sudo apt-get update
  - sudo apt-get install -y temurin-21-jdk
  - export JAVA_HOME=/usr/lib/jvm/temurin-21-jdk-amd64
  - export PATH=$JAVA_HOME/bin:$PATH
  - java -version
6

Thanks @Montana , that code got close but it needed an additional sed command to remove Bellsoft entry. See final yaml:

before_install:
- echo "Removing BellSoft URL from /etc/apt/sources.list..."
- sudo sed -i '/apt\.bell-sw\.com/d' /etc/apt/sources.list
- sudo apt-get update
- wget -O - https://packages.adoptium.net/artifactory/api/gpg/key/public | sudo apt-key add -
- echo "deb https://packages.adoptium.net/artifactory/deb $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/adoptium.list
- sudo apt-get update
- sudo apt-get install -y temurin-21-jdk
- export JAVA_HOME=/usr/lib/jvm/temurin-21-jdk-amd64
- export PATH=$JAVA_HOME/bin:$PATH
- java -version
7

Hey @nickdos,

From looking at the logs, Gradle can’t resolve jakarta.servlet:jakarta.servlet-api:6.2.0 (there is no final 6.2.0 on Maven Central, only 6.1.0 stable and 6.2.0-M1 milestone). Hence the “Could not find 6.2.0”error.”

If I were you, I’d change any place that declares jakarta.servlet-api:6.2.0 to 6.1.0 (recommended) or 6.0.0. Do not use 6.2.0 unless you explicitly choose the 6.2.0-M1 milestone. (6.1.0 is latest stable; 6.2 is “under development”.)

Here’s an example build.gradle:

subprojects {
  repositories {
    mavenCentral()
    maven { url "https://nexus.ala.org.au/content/groups/public" }
  }
  configurations.all {
    resolutionStrategy {
      force 'jakarta.servlet:jakarta.servlet-api:6.1.0'
    }
  }
}

This should hopefully get you building.

8

Thanks @Montana - yes, now that Java 21 is installing, I’m aware of that issue which is due to a Java 21 upgrade process I’m working through. So not the fault of Travis but rather self-inflicted :wink:

1 Like