Extension with multiple Environments support #3
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
…o webmethods-sample-project-layout, so that these are project specific
…to reduce duplicate configuration entries
AngelSAG
suggested changes
Apr 26, 2017
There was a problem hiding this comment.
Don't import the .bak files in the repo.
In the jenkinsfile.unix there is a harcoded path to your machine.
Why are the eclipse .classpath and .project important here? Is there a reason for this?
If you deploy on multiple environments split this into stages - deploy to Test- > run test -> deploy to QA-> deploy to preProd-> deploy to Prod ->. You might add test phases for every environment.
…roject-layout since this is a project specific parameter
…gger for quiesce tests
…de internal properties
maam1
added a commit
to krishnajc/AssetRepo
that referenced
this pull request
Jun 21, 2019
commit 3 cutomers
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.
The major change here is the introduction of the ENV.groovy file for configurable environments. Other than that I adjusted and unified the naming of targets and properties. I also extended the Jenkinsfile to show how deployment to multiple environments (here TEST and QA) could be realized.