When we want to release a new version that:
- Will be marked as release in GitHub
- Will have artifacts that include the content (i.e. cslang-cli-with-content.zip)
- Will test that the content matches the language version (only the default content test suite)
- Will run the CLI with a simple flow (sanity check)
To do so we use drone.io. (Contact one of the CloudSlang owners for credentials.)
It is also possible to build everything locally since all of the build scripts and flows are available under the /build folder of this repo.
In the build folder we have:
- An Ant file, that runs a CloudSlang flow, that builds and tests the CLI (we also use it in Travis, but without adding and testing the content).
- A shell script that uploads the artifacts to GitHub, and runs sanity checks.
-
Choose a release tag you want to build. (Every release of Jenkins creates a tag.)
-
Copy the tag name.
After you created a user and was added to the project:
- Enter the project.
-
Go to the Settings tab.
-
Click the arrow next to Build Now.
-
Click Choose Custom Branch.
-
Enter the tag you want to create a release for (the one copied from GitHub) in the Branch Name and press Build now.
- Check the log (if you wish).