-
Notifications
You must be signed in to change notification settings - Fork 57
feat: allow specifying Kaniko targets for multi-stage dockerfiles #436
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
hamishc
wants to merge
6
commits into
coder:main
Choose a base branch
from
hamishc:kaniko-skip-unused
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
497d803
Added the ability to specify build targets for kaniko build and an op…
d09ed90
Fixed linting issues
9bf8257
Missed a linter error
a77ad2f
Merge branch 'main' into kaniko-skip-unused
johnstcn 8781126
Merge branch 'main' into kaniko-skip-unused
hamishc 8c7eee7
Added tests for building with a target specified
hamishc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -100,6 +100,10 @@ type Options struct { | |
| // This value can always be set to true - even if the container is being | ||
| // started for the first time. | ||
| SkipRebuild bool | ||
| // SkipUnusedStages builds only used stages if defined to true. Otherwise, | ||
| // it builds by default all stages, even the unnecessary ones until it | ||
| // reaches the target stage / end of Dockerfile | ||
| SkipUnusedStages bool | ||
| // GitURL is the URL of the Git repository to clone. This is optional. | ||
| GitURL string | ||
| // GitCloneDepth is the depth to use when cloning the Git repository. | ||
|
|
@@ -359,6 +363,14 @@ func (o *Options) CLI() serpent.OptionSet { | |
| "docker start This value can always be set to true - even if the " + | ||
| "container is being started for the first time.", | ||
| }, | ||
| { | ||
| Flag: "skip-unused-stages", | ||
| Env: WithEnvPrefix("SKIP_UNUSED_STAGES"), | ||
| Value: serpent.BoolOf(&o.SkipUnusedStages), | ||
| Description: "Skip building all unused docker stages. Otherwise it builds by " + | ||
| "default all stages, even the unnecessary ones until it reaches the " + | ||
| "target stage / end of Dockerfile.", | ||
| }, | ||
|
Comment on lines
+366
to
+373
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Where is this actually used? |
||
| { | ||
| Flag: "git-url", | ||
| Env: WithEnvPrefix("GIT_URL"), | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Do we want to also add a second target and then assert that we only go up as far as
my-target?e.g.
and then assert
params.Useror similar?Similarly, what is the expected behaviour for
--skip-unused-stages?