aboutsummaryrefslogtreecommitdiffhomepage
path: root/scripts/release/common.sh
Commit message (Collapse)AuthorAge
* Release script: remove non-needed `xargs echo`Gravatar dmarting2017-07-28
| | | | | | They are the root cause of #3459. PiperOrigin-RevId: 163392890
* Minor Bash improvementsGravatar Androbin2017-06-27
| | | | | | | | | | | | | | | | | Based on output of static analysis tool. https://github.com/koalaman/shellcheck/wiki/SC2166 https://github.com/koalaman/shellcheck/wiki/SC2207 https://github.com/koalaman/shellcheck/wiki/SC2145 https://github.com/koalaman/shellcheck/wiki/SC2001 https://github.com/koalaman/shellcheck/wiki/SC2129 https://github.com/koalaman/shellcheck/wiki/SC2128 https://github.com/koalaman/shellcheck/wiki/SC2004 https://github.com/koalaman/shellcheck/wiki/SC2048 Closes #3162. PiperOrigin-RevId: 160261247
* Follow-up of commit dbdaf83fe5480179bf65b86421168a5dba0e2198: common.sh was ↵Gravatar Damien Martin-Guillerez2017-01-26
| | | | | | | | | | not exported This also make sure we list cherry-picks with long hash. -- PiperOrigin-RevId: 145724726 MOS_MIGRATED_REVID=145724726
* Fix formatting of the release CHANGELOG file Gravatar Damien Martin-Guillerez2017-01-10
| | | | | | | | | | | | | | - Add backquotes around the changelog - Add empty line at the end of the changelog - Enforce the use of the master changelog prior to release Fixes #2281. -- Change-Id: I449f5209a6b05e65411a64ce82ea1d89d60ee4d3 Reviewed-on: https://cr.bazel.build/8044 PiperOrigin-RevId: 144080940 MOS_MIGRATED_REVID=144080940
* Release scripts: add a git note with the cherrypick origin Gravatar Damien Martin-Guillerez2017-01-10
| | | | | | | | | | | | | | | | | | | If the patch-id differ because of merge conflict or subtle adjacent change, the cherrypick origin was missing, resulting in non existent cherrypick lines in the changelog. If the cherrypicks are done by the script, adds the cherrypick origin to a git note and use that origin when generating the release note. Also fallback to the commit hash of the resulting commit if the cherrypick origin cannot be found. Fixes #2272. -- Change-Id: I311bbe777ea82be05f9fba0a658bab075ed1bd97 Reviewed-on: https://cr.bazel.build/8042 PiperOrigin-RevId: 144075867 MOS_MIGRATED_REVID=144075867
* Release script: if master branch does not exist, fall back on origin/masterGravatar Damien Martin-Guillerez2016-12-20
| | | | | | | | | | | | | | | On ci.bazel.io local branch names are not set, so the release script was not finding information about the master branch. If the master ref does not exist, this change fall backs to looking at origin/master instead. Fixes #2263. To be cherry-picked for #2246. -- Change-Id: Ibe4f3533e529d79917233d89951f88cb58d14ce3 Reviewed-on: https://cr.bazel.build/8033 PiperOrigin-RevId: 142524954 MOS_MIGRATED_REVID=142524954
* Release: merge release notes with previousGravatar Damien Martin-Guillerez2016-12-05
| | | | | | | | | | This change does a three way merge with previous release notes if it exists. -- Change-Id: Idac7905e1550a8e00f96c7034b61603678ff59a6 Reviewed-on: https://cr.bazel.build/7355 PiperOrigin-RevId: 141031870 MOS_MIGRATED_REVID=141031870
* Release: refactor the way we keep track of release notesGravatar Damien Martin-Guillerez2016-12-02
| | | | | | | | | | | | | | | | | | | Now the release branch does not contains the release commit anymore. Instead, we regenerate the full release notes each time we have to (release candidate creation and final release). Two side effects: - The date is now showing the date of the operation and no longer the date of the release candidate (so release will be correctly dated) - The release notes show the release candidate number :) Tested: bazel test //scripts/release/... + build README.md -- Change-Id: Ia249bbdc0d6ed240bd969f24aa013f709f9a0a74 Reviewed-on: https://cr.bazel.build/7338 PiperOrigin-RevId: 140841432 MOS_MIGRATED_REVID=140841432
* Release script: add release notes to the git notesGravatar Damien Martin-Guillerez2016-11-22
| | | | | | | | | | | This is a first change to get rid of the release commit on release branch. Doing so will 1/ allows for git workflow (git cherry-pick), 2/ allows to use merge feature from git notes. -- Change-Id: Id6a93f0dc70b9efe8ff705f1dd2a16489989f281 Reviewed-on: https://cr.bazel.build/7337 MOS_MIGRATED_REVID=139904935
* Replace #!/bin/bash -eu with #!/bin/bash and "set -eu". Otherwise, the "-eu" ↵Gravatar Philipp Wollermann2016-06-21
| | | | | | | | | is not picked up when you run the scripts manually using "bash script.sh". This is also in our shell style guide: "Executables must start with #!/bin/bash and a minimum number of flags. Use set to set shell options so that calling your script as bash <script_name> does not break its functionality." -- MOS_MIGRATED_REVID=125450962
* Rationalize copyright headersGravatar Damien Martin-Guillerez2015-09-25
| | | | | | | | | | | The headers were modified with `find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'` And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan. The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand. -- MOS_MIGRATED_REVID=103938715
* Bazel release process scriptsGravatar Damien Martin-Guillerez2015-07-29
Those scripts are made to handle the soon to be Bazel release process. It is still missing the CI part that deploys built artifacts and sends announcement mails. It uses the RELNOTES: tag (RELNOTES for a simple change, RELNOTES[NEW] for a new feature, RELNOTES[INC] for an incompatible change) to create the CHANGELOG.md file. The main entry point is scripts/release/release.sh and should be the only script called directly. -- Change-Id: I6e066fda4d862ce793cc03dc8bdf0b8cb34f7c2c Reviewed-on: https://bazel-review.googlesource.com/#/c/1580/ MOS_MIGRATED_REVID=99282250
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-29 14:39:26 +0000