Our release process is non-standard and undocumented. Let's automate it. This MR will create a script that builds front-end assets, cuts a tag, and provides instructions for manual steps needed to complete a release.
The script works like this:
$ ./scripts/release.sh -h Usage: ./scripts/release.sh [-h | --help] [-H | --head <branch>] [--dry-run] [-f | --force] <tag_name> -h, --help Show this help message and exit. -H, --head <branch> (Optional) The branch to return to after release. Defaults to current branch. --dry-run Print the operations that would be performed, but do not execute them. -f, --force Ignore precondition checks (for testing/debugging only). <tag_name> The name of the release tag to create.
Attached is an example of output it produces.
| Comment | File | Size | Author |
|---|---|---|---|
| example-output.txt | 2.81 KB | traviscarden |
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
traviscarden commented@balsama, do you think we should add this to our CI job?
Comment #4
balsamaThis is great. And I see you cleaned up the cruft that had inadvertently been committed too.
I don't think we need this to be a part of CI. Thanks.
Comment #6
traviscarden commented