- Notifications
You must be signed in to change notification settings - Fork385
Extension with multiple Environments support#3
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…o webmethods-sample-project-layout, so that these are project specific
…to reduce duplicate configuration entries
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
hardcoded currentDir
…roject-layout since this is a project specific parameter
…gger for quiesce tests
…de internal properties
commit 3 cutomers
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.