This repository has been archived by the owner on Jul 16, 2024. It is now read-only.
Bump Build Spec to 0.2 #6
Merged
Conversation
This file contains 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
The latest version of the Build Spec maintains state between commands rather than running all commands in a separate install of the shell. This allows us to set the tag as an environment variable rather than using temporary files. Note we're still generating a JSON file at the end of the build to pass along build details to CloudFormation in the next step in the pipeline.
curiousaksh
pushed a commit
to curiousaksh/ecs-refarch-continuous-deployment
that referenced
this pull request
Jan 23, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The latest version of the Build Spec maintains state between commands
rather than running all commands in a separate install of the shell.
This allows us to set the tag as an environment variable rather than
using temporary files.
Note we're still generating a JSON file at the end of the build to pass
along build details to CloudFormation in the next step in the pipeline.