Skip to content

[SVLS-9625] chore(ci): trigger a rebuild and re-sign of the CI image - #1322

Open
lym953 wants to merge 2 commits into
mainfrom
yiming.luo/resign-ci-image
Open

[SVLS-9625] chore(ci): trigger a rebuild and re-sign of the CI image#1322
lym953 wants to merge 2 commits into
mainfrom
yiming.luo/resign-ci-image

Conversation

@lym953

@lym953 lym953 commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Problem

CI jobs are failing to start because registry.ddbuild.io/ci/datadog-lambda-extension:latest is unsigned and image-integrity enforcement blocks the pull:

verifier containerd-image-verifier rejected image: signature manifest not found

ddsign signing was added to the ci image job in #1065 (2026-03-05), but the job only runs when a push to main changes .gitlab/Dockerfile — and the last such change was 2025-12-03. So the job has never run with signing enabled.

This PR

Deletes the trailing blank lines from .gitlab/Dockerfile: a no-op for the image content, but enough to make that rule match on merge and rebuild, sign, and push :latest.

Testing

Ran the ci image job against a throwaway tag to confirm signing works before relying on it (job 1939023452): the build pushed, and ddsign sign reported "signatureIsNew": true. So DDSIGN_ID_TOKEN and the signer allowlist are set up correctly — the job simply never ran.

The merge itself can't be rehearsed from a branch. After merge, confirm the ci image job ran and that integration-suite: [oom] / [lmi-oom] start cleanly.

Resources

Slack discussion: https://dd.slack.com/archives/C027P1CK07N/p1785767085015909

🤖 Generated with Claude Code

@datadog-prod-us1-3

datadog-prod-us1-3 Bot commented Aug 10, 2026

Copy link
Copy Markdown

Pipelines

⚠️ Warnings

🚦 2 Pipeline jobs failed

DataDog/datadog-lambda-extension | cargo fmt   View in Datadog   GitLab

DataDog/datadog-lambda-extension | integration-cleanup-layer   View in Datadog   GitLab

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: caede8b | Docs | Datadog PR Page | Give us feedback!

The ci image job only runs when a main push changes .gitlab/Dockerfile.
Removing the trailing blank lines is a no-op change that makes that rule
match, so the image is rebuilt, signed with ddsign, and pushed as :latest.
@lym953 lym953 changed the title chore(ci): allow rebuilding and re-signing the CI image on demand chore(ci): trigger a rebuild and re-sign of the CI image Aug 11, 2026
@lym953 lym953 changed the title chore(ci): trigger a rebuild and re-sign of the CI image [SVLS-9625] chore(ci): trigger a rebuild and re-sign of the CI image Aug 11, 2026
@lym953
lym953 marked this pull request as ready for review August 11, 2026 01:56
@lym953
lym953 requested a review from a team as a code owner August 11, 2026 01:56
@lym953
lym953 requested review from duncanista and a lite review from Copilot August 11, 2026 01:56

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

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 triggers a rebuild and re-sign of the registry.ddbuild.io/ci/datadog-lambda-extension:latest CI image by making a no-op change to .gitlab/Dockerfile, ensuring the ci image job runs on merge and produces a signed image compatible with image-integrity enforcement.

Changes:

  • Removed trailing blank lines from .gitlab/Dockerfile to force the CI image build rule to match.
  • No functional changes to the Docker build steps; change is intended solely to retrigger the pipeline behavior.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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.

2 participants