Skip to content
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

Status of migration from Jenkins to GitHub Actions #16039

Open
AkihiroSuda opened this issue Jan 11, 2024 · 5 comments
Open

Status of migration from Jenkins to GitHub Actions #16039

AkihiroSuda opened this issue Jan 11, 2024 · 5 comments

Comments

@AkihiroSuda
Copy link

https://www.docker.com/blog/building-trusted-content-with-github-actions/

Docker has begun migrating its Docker Official Images (DOI) builds to the GitHub Actions platform.
[...]
As we increase the trust in the DOI catalog, we will spread out the work over three phases. In our first phase, only Linux/AMD64 and Linux/386 images will be built on GitHub Actions. For the second phase, we eagerly anticipate the availability of GitHub Actions Arm-based hosted runners next year to add support for additional Arm architectures. In our final phase, we will investigate using GitHub Actions self-hosted runners for the image architectures not supported by GitHub Actions hosted runners to cover any outstanding architectures.

Some questions:

  • What's the current status of this migration? Is there an ETA for the first batch of the images to be built on GHA?

  • Will the migration mean switching away from the classic builder too?

  • Will they be built using https://github.com/docker/build-push-action ? or bashbrew?

  • Is there anything that the community can help to facilitate this?

@whalelines
Copy link
Contributor

Thanks for your interest in DOI. I've answered your questions below.

What's the current status of this migration? Is there an ETA for the first batch of the images to be built on GHA?

Over 30 DOI have already been migrated to be built on GHA for amd64 and 386. The migrated DOI are listed in the build repository. You can track the progress there.

Will the migration mean switching away from the classic builder too?

Yes, the migrated images use BuildKit.

Will they be built using https://github.com/docker/build-push-action ? or bashbrew?

bashbrew is still used. The details of the build process can be found in the https://github.com/docker-library/meta and https://github.com/docker-library/meta-scripts repositories.

Is there anything that the community can help to facilitate this?

Feel free to peruse the build code, continue to use DOI, and let us know if you see any issues.

Thanks again for your interest and support!

@AkihiroSuda
Copy link
Author

Thank you!

(For the future reference, the images are built in https://github.com/docker-library/meta/blob/subset/.github/workflows/build.yml , and the logs are available in https://github.com/docker-library/meta/actions/workflows/build.yml)

@AkihiroSuda
Copy link
Author

Feature request: it would be nice to have links to GHA builds logs in the Web UI of Docker Hub, as it is hard to find the log for a specific image via https://github.com/docker-library/meta/actions/workflows/build.yml

@LaurentGoderre
Copy link
Member

@AkihiroSuda While I don't disagree, it's hard to find the builds sometimes.

@tianon
Copy link
Member

tianon commented Jan 18, 2024

I would love a way to store the build logs directly in the image metadata (especially for individual build steps, so even cached builds could still have useful logs).

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

4 participants