add exit injection via env for Go app #8
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
for our e2e tests we want a deplo.io app that exits with a certain code so we can test some of the status handling. So e.g. when setting the env var DEBUG_EXIT=2, the go app will exit with code 2.
ctrox
force-pushed
the
go-inject-error
branch
5 times, most recently
from
56392d1
to
e120b74
Compare
for now this is just for use in e2e tests but eventually we could also verify the apps will build with our build packs.
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.
for our e2e tests we want a deplo.io app that exits with a certain code
so we can test some of the status handling. So e.g. when setting the env
var DEBUG_EXIT=2, the go app will exit with code 2.
The second commit adds an action to build the go app and upload the image so we can use it in our e2e tests.