Skip to content

chore: Add Debian Trixie targets across archs and release variable #1036

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

chore: Add Debian Trixie targets across archs and release variable #1036

wants to merge 6 commits into from

Conversation

gounthar
Copy link
Contributor

@gounthar gounthar commented Aug 19, 2025 •
edited
Loading

Implemented Debian “trixie” alongside existing Debian builds.

Testing done

make list
agent_alpine_jdk17
agent_alpine_jdk21
agent_debian_jdk17
agent_debian_jdk21
agent_rhel_ubi9_jdk17
agent_rhel_ubi9_jdk21
inbound-agent_alpine_jdk17
inbound-agent_alpine_jdk21
inbound-agent_debian_jdk17
inbound-agent_debian_jdk21
inbound-agent_rhel_ubi9_jdk17
inbound-agent_rhel_ubi9_jdk21
make build-agent_debian_jdk21
[...]

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed

@gounthar
Add Debian Trixie targets across archs and release variable
e0f7b49 
- Add debian_trixie target using debian/Dockerfile and DEBIAN_TRIXIE_RELEASE
- Include Trixie in linux, linux-arm64, linux-arm32 (jdk17), s390x (jdk21), and ppc64le groups
- Tag images with "trixie" and reuse Debian platforms/JDK matrix
- Enables building Jenkins agent images for Debian Trixie across architectures
@gounthar gounthar requested a review from a team as a code owner August 19, 2025 07:12
timja
timja reviewed Aug 20, 2025
View reviewed changes
docker-bake.hcl Outdated
targets = [
"alpine",
"debian",
"debian_trixie",
Copy link
Member

@timja timja Aug 20, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to maintain two debian lines? or just maintain one?

Given additional build times and infra cost?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a great question. 🤔 Unfortunately, I'm not the right person to answer it. If it were up to me, I'd opt for one release with both Debian flavors, and then continue with only Trixie if no issues arise.

Copy link
Contributor

@MarkEWaite MarkEWaite Aug 20, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that we want only one Debian flavor and I think it should be based on Trixie.

I think that we should write a blog post and announce that we're switching the default container images from Debian Bookworm to Debian Trixie. We'll need to switch the container images for:

  • Jenkins core
  • Inbound agents
  • SSH agents

That aligns with our pattern of only supporting 1 operating system version for each operating system variant. The examples are:

  • Alpine - 3.22
  • Debian - 12 (Bookworm)
  • UBI - 9

I'm open to other opinions, but I think a transition from Bookworm to Trixie is the same type of transition that we did on the last Debian release when we transitioned from Bullseye to Bookworm:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your insights, everyone. 🙏

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 for just switching tags to trixie

I've open the PR for the core : jenkinsci/docker#2063

@gounthar gounthar mentioned this pull request Aug 21, 2025
Merged
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@MarkEWaite MarkEWaite MarkEWaite left review comments

@timja timja timja left review comments

+1 more reviewer

@jonesbusy jonesbusy jonesbusy left review comments

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@gounthar @MarkEWaite @jonesbusy @timja