Skip to content

Add step to print labels in build workflow#51

Merged
ahanafy merged 57 commits intomainfrom
ah-container-build-clarity
Apr 23, 2025
Merged

Add step to print labels in build workflow#51
ahanafy merged 57 commits intomainfrom
ah-container-build-clarity

Conversation

@ahanafy
Copy link
Copy Markdown
Contributor

@ahanafy ahanafy commented Apr 8, 2025

This pull request enhances the GitHub Actions workflow for building and publishing Docker images by introducing shared tags, improving metadata management, and adding detailed summaries for build outputs. Additionally, it updates the base Python image in the Dockerfile.

Workflow Enhancements:

  • Shared Tags Job: Introduced a new shared-tags job to generate reusable outputs for branch names, timestamps (ISO 8601 and legacy formats), and a summary of generated tags. These outputs are used across other jobs for consistency. (.github/workflows/build.yml, .github/workflows/build.ymlR20-R56)
  • Improved Metadata and Annotations: Updated the docker/metadata-action configuration to use the shared tags for generating Docker image tags and annotations. This includes adding descriptions and timestamps in the image annotations. (.github/workflows/build.yml, [1] [2]
  • Container Registry Links: Added a step to generate and include direct links to the container registry in the job summary, enhancing traceability for published images. (.github/workflows/build.yml, [1] [2]

Codebase Updates:

  • Python Base Image Update: Updated the base Python image in the api-implementation/Dockerfile from python:3.13 to python:3.13.2 to ensure the latest patch version is used. (api-implementation/Dockerfile, api-implementation/DockerfileL2-R2)

@ahanafy ahanafy marked this pull request as draft April 8, 2025 22:22
Comment thread .github/workflows/build.yml Outdated
Comment thread .github/workflows/build.yml Outdated
@birgelee
Copy link
Copy Markdown
Member

@ahanafy is this ready for review? I am generally in favor of this idea.

@ahanafy
Copy link
Copy Markdown
Contributor Author

ahanafy commented Apr 14, 2025

@ahanafy is this ready for review? I am generally in favor of this idea.

Still fighting with the build. Although in principle the idea works. I'm having issues with setting the description as a multiline string

…ed readability and URL-encoded newlines in build workflow
@ahanafy ahanafy force-pushed the ah-container-build-clarity branch from d77104f to 3158339 Compare April 22, 2025 02:01
@ahanafy ahanafy marked this pull request as ready for review April 22, 2025 02:10
@ahanafy ahanafy requested review from birgelee, Copilot and sciros April 22, 2025 02:11
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds a new step to the build workflow that prints generated image labels and enhances tag generation with a shared output for branch names and timestamps. Key changes include:

  • The introduction of the "shared-tags" job that generates and outputs branch names and timestamp values.
  • Integration of the shared tag outputs into subsequent jobs for metadata extraction, image tagging, and summary generation.
  • Updates to the unbound image build process with specific adjustments to image references and registry links.
Files not reviewed (1)
  • api-implementation/Dockerfile: Language not supported
Comments suppressed due to low confidence (1)

.github/workflows/build.yml:304

  • The change in subject-name replaces the dynamic matrix-service variable with a hardcoded 'unbound' value. If this is intentional, consider adding a comment to clarify the rationale to avoid confusion for future maintainers.
subject-name: ${{ env.REGISTRY }}/${{ github.repository_owner }}/unbound

Comment thread .github/workflows/build.yml Outdated
Comment thread .github/workflows/build.yml
@ahanafy ahanafy merged commit bbf1bf1 into main Apr 23, 2025
6 checks passed
@ahanafy ahanafy deleted the ah-container-build-clarity branch April 23, 2025 15:07
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

Successfully merging this pull request may close these issues.

5 participants