Skip to content

Bumb CI to 24.04 #5244

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.

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

Open
1 of 4 tasks
Nils-ChristianIseke opened this issue Apr 19, 2025 · 7 comments
Open
1 of 4 tasks

Bumb CI to 24.04 #5244

Nils-ChristianIseke opened this issue Apr 19, 2025 · 7 comments
Assignees

Comments

@Nils-ChristianIseke
Copy link
Contributor

Nils-ChristianIseke commented Apr 19, 2025

Issue Type

  • 🐛 Bug / Problem
  • ✏️ Typo / Grammar
  • 📖 Outdated Content
  • 🚀 Enhancement

Distribution

Migration from Ubuntu 22.04 to 24.04

Description

We currently pin dependencies to Ubuntu 22.04 system packages (like python3-stevedore 3.5.0). Upgrading to 24.04 requires updating all dependencies and CI infrastructure.

Affected Pages/Sections

None

Screenshots or Examples (if applicable)

None

Suggested Fix

Bump to Ubuntu 22.04

Additional Context

None

@Nils-ChristianIseke
Copy link
Contributor Author

I can do that, but I won't start working on this before may. So if anyone wants to do it now, go ahead

@fujitatomoya
Copy link
Collaborator

@Nils-ChristianIseke thanks for creating issue.

I do not we are in rush on this, so i will go ahead to assign this to you as offered.

@christophebedard
Copy link
Member

Yeah, we're in no rush!

Before actually changing anything, I'd recommend figuring out what needs to be changed (versions of dependencies, Dockerfile, GitHub Actions, documentation about how to build the docs, etc.) and then figuring out what the concrete changes should be, especially the versions (based on the system package on Ubuntu 24.04).

Like I mentioned in #5241 (comment), we'll also have to coordinate to update the nightly CI job that builds the docs, since that's separate from this repo. That might take some time since this isn't really a priority. I will ask about this at the next Infrastructure PMC meeting.

@christophebedard
Copy link
Member

Interesting, looks like the nightly CI job simply uses the Dockerfile from this repo.

@christophebedard
Copy link
Member

We just talked about this in the Infrastructure PMC meeting. In summary:

The job is currently on build.ros.org, but there are plans to move it to build.ros2.org. Therefore, we can do both that and the bump to Noble at once. We'll set up the job on build.test.ros2.org, which will allow us to test the bump to Noble for the docs generation (because there is apparently no way for non-admins to trigger the docs job on build.ros.org, and this way we can test without using prod). Then we can move the job to build.ros2.org.

Once we have a branch with the Dockerfile bumped to Noble and the new test job on build.test.ros2.org, we can try it out.

@christophebedard
Copy link
Member

FYI @Nils-ChristianIseke I can now trigger test builds for the docs (https://build.test.ros2.org/job/doc_ros2-documentation/), so I'm ready once you've updated the Dockerfile

@Nils-ChristianIseke
Copy link
Contributor Author

Working on this in #5595

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants