-
Notifications
You must be signed in to change notification settings - Fork 1
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
Buildkite plugin for shared SBC code #1
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This plugin supports pushing images and params to AWS accounts and pushing ruby gems to jfrog.
There are currently 4 actions it supports:
build
,push_image
,push_param
,publish_gem
.build
No settings required except for a
.buildkite/build.sh
file in the repository.If any custom functions need to be defined, define it in a
.buildkite/custom_functions.sh
file.push_image
settings for
environment
,landscape
, andaccount_id
need to be defined in the pipeline.For example
If the
qa
environment you push to takes advantage of a database image used for testing, then add the env ofHAS_DB_IMAGE: true
push_param
settings for
environment
,landscape
, andaccount_id
must be defined in the pipeline.For example
publish_gem
If the repository is used for a ruby gem, then no other settings are needed aside from the action. It does require the
APP
env to be passed into the container.This only supports gem pushing via a docker container that has the gem built and assumes the docker container will execute
.buildkite/releash.sh
as a command.It also had a dependency on the compose file or docker setting to mount the
.buildkite
folder in the container.The reason is because the
publish_gem
action simply copies therelease.sh
script from the plugin. The docker container needs to invoke the command.Here is an example usage:
Docker compose file
pipeline file