This repository has been archived by the owner on Apr 15, 2019. It is now read-only.
Use variable for job name instead of hardcoded string in Jenkinsfile - Closes #961 #962
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
slaweet
changed the title
fchavant
force-pushed
the
961-use-job-name
branch
from
6506cf8
to
1e3be3c
Compare
slaweet
approved these changes
Nov 8, 2017
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.
What was the problem?
"lisk-nano" was hardcoded in the
JenkinsfileHow did I fix it?
the
$JOB_BASE_NAMEvariable is now used insteadHow to test it?
make sure both the lisk-nano and lisk-wallet-private Jenkins jobs still work
Review checklist