-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore: update the way the LTS images are built #8953
chore: update the way the LTS images are built #8953
Conversation
FYI, proposing this on |
Codecov Report
@@ Coverage Diff @@
## release/v2.6 #8953 +/- ##
===============================================
Coverage ? 63.62%
===============================================
Files ? 624
Lines ? 31925
Branches ? 0
===============================================
Hits ? 20311
Misses ? 10087
Partials ? 1527 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe test it with a person project by connecting gcb with your fork ?
args: | ||
- 'build' | ||
- '--cache-from' | ||
- 'gcr.io/$PROJECT_ID/skaffold-builder:latest' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to add
- '--build-arg'
- 'SKAFFOLD_VERSION=$TAG_NAME'
to inject version to the build context
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, sorry, I was testing this with a modified version of this file (mostly because I didn't want to push to AR too) and then I forgot to copy my fixes back into this file. Fixed!
deploy/cloudbuild-release-lts.yaml
Outdated
- 'gcr.io/$PROJECT_ID/skaffold-builder:latest' | ||
- 'gcr.io/$PROJECT_ID/skaffold:$_SCANNING_MARKER-lts' | ||
- '-t' | ||
- 'us-east1-docker.pkg.dev/$PROJECT_ID/scanning/skaffold:$TAG_NAME-lts' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This means, artifact registry scanner will scan all binary deps, probably we want to do it anyway. Just double check this is intended behavior?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh.. seems that our internal scanner is already doing this may be we don't need to push the image to ar anymore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I removed AR. I wasn't sure why that was there but didn't want to change it...
I testing it by doing this: Do you think that's good enough or should I wire up a trigger? |
…8953) * chore: update the way the LTS images are built * Add the --build-arg and remove the Artifact Registry copy.
…8953) * chore: update the way the LTS images are built * Add the --build-arg and remove the Artifact Registry copy.
…8953) * chore: update the way the LTS images are built * Add the --build-arg and remove the Artifact Registry copy.
I moved everything from
Dockerfile.deps.lts
intoDockerfile.lts
directly. Unforunately, this makes this diff pretty useless, but basically the only changes were thedownload-skaffold
section at the top and the removal of the Go installation (the last two lines).