Support for custom environment, prepare, test, deploy and cleanup phases in Strider
Using configuration information in your script
You can access any information relating to the current job, by using EJS syntax in your script.
A common example would be retrieving the name of the branch that is currently being built:
echo Deploying <%= ref.branch %>….scripts/deploy.sh <%= ref.branch %>
This plugin also supports being configured using the
strider.json file in your project.
It can have the following properties, but you can pick and choose which you want to use.
A more complete example of a
strider.json would be: