aboutsummaryrefslogtreecommitdiffhomepage
path: root/scripts/release
Commit message (Collapse)AuthorAge
* Fix usage command of release scriptGravatar Yannic Bonenberger2018-08-10
| | | | | | Closes #5679. PiperOrigin-RevId: 208194222
* Simplify the release scripts in preparation of rewriting them in PythonGravatar Philipp Wollermann2018-03-27
| | | | | | | | These are the scripts I'm currently using for the Bazel 0.12.0 release. Closes #4908. PiperOrigin-RevId: 190598268
* Various Shell Script Fixes and Improvements - Part OneGravatar Androbin2017-11-29
| | | | | | | | see #4023 Closes #4051. PiperOrigin-RevId: 177279457
* Release notes: correctly strip out none, n/a, noGravatar Damien Martin-Guillerez2017-10-18
| | | | | | | | | | | | | | The previous regex was only matching lines and was not even correctly doing so. We no match everything that is starting with none, n/a or no as a sentence or as a full line. We also match empty string and '.' as a full line. RELNOTES: . RELNOTES: None. RELNOTES: No. Change-Id: I6e85627170ce35e652c90a37e735b7db93c88b4e PiperOrigin-RevId: 172452278
* Ensure that the release notes are not empty if there is no rollbackGravatar Damien Martin-Guillerez2017-10-16
| | | | | | | | | | Because the empty list was returned for the list of hashes to ignore, we matching all the lines in the following grep. By adding a dummy hashes, it ensure that list is never empty and we thus never give a match all pattern. Change-Id: Ic5446c16b56633805e61b24ad71b67029a7b01e3 PiperOrigin-RevId: 172321625
* Release notes test small fixesGravatar Damien Martin-Guillerez2017-10-16
| | | | | | | | - Avoid trap being called when grep is not matching (|| true) - Ensure we always start in master branch Change-Id: I7a71abbdfae7dc2b9680e769ed0322a6a12221dc PiperOrigin-RevId: 172316454
* Release notes: exclude no.Gravatar dmarting2017-10-11
| | | | | RELNOTES: No. (test) PiperOrigin-RevId: 171673073
* Release script: remove non-needed `xargs echo`Gravatar dmarting2017-07-28
| | | | | | They are the root cause of #3459. PiperOrigin-RevId: 163392890
* Force fetch when fetching remote release notesGravatar dmarting2017-07-26
| | | | | | | | If the release note locally are totally different, they will failed to fetch and we want to consider the remote as the source of truth rather than the local. Fixes #3447. PiperOrigin-RevId: 163202815
* 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
* Fix typo: s/exists/exist/ where needed.Gravatar philwo2017-05-31
| | | | | RELNOTES: None. PiperOrigin-RevId: 157572063
* Do not put PiperOrigin-RevId tag into relnotesGravatar Marcel Hlopko2017-05-04
| | | | | Change-Id: If79da71d2939517724d92cbe470173b5d68e3019 PiperOrigin-RevId: 155075510
* 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 release scripts by using full hash everywhereGravatar Damien Martin-Guillerez2017-01-26
| | | | | | | | | | | | | Previously we were using short hash for rendering to the user but our repository as grown and on some configuration of git the short hash size has increased. To be future-proof, just remove all usage of short hash and use full hash instead. Fixes #2429. -- PiperOrigin-RevId: 145667804 MOS_MIGRATED_REVID=145667804
* Rollback of commit 96297ed7a9ab3df0f45e93bae9d71833f4195334.Gravatar Damien Martin-Guillerez2017-01-26
| | | | | | | | | | | | | | | | | | | | | | | | *** Reason for rollback *** Roll-forward with fix *** Original change description *** Automated [] rollback of commit ffc0d2df0213123a4451bed5850827319afcdeee. *** Reason for rollback *** Grr I knew I shouldn't have done 2 changes in one tests are failing now Fixes #2429. *** Original change description *** Release scripts: factor out the push to notes and fix a typo -- PiperOrigin-RevId: 145662713 MOS_MIGRATED_REVID=145662713
* Rollback of commit ffc0d2df0213123a4451bed5850827319afcdeee.Gravatar Damien Martin-Guillerez2017-01-26
| | | | | | | | | | | | | | | | *** Reason for rollback *** Grr I knew I shouldn't have done 2 changes in one tests are failing now Fixes #2429. *** Original change description *** Release scripts: factor out the push to notes and fix a typo -- PiperOrigin-RevId: 145657489 MOS_MIGRATED_REVID=145657489
* Release scripts: factor out the push to notes and fix a typoGravatar Damien Martin-Guillerez2017-01-25
| | | | | | -- PiperOrigin-RevId: 145559628 MOS_MIGRATED_REVID=145559628
* 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 script: stays in the release branch after creating itGravatar Damien Martin-Guillerez2016-12-13
| | | | | | | | | | | Getting back to the previous branch was confusing for users and not really useful. -- Change-Id: Icc3d4b30ab7d75de73fcb5885a215a08b96dfeb3 Reviewed-on: https://cr.bazel.build/7593 PiperOrigin-RevId: 141892852 MOS_MIGRATED_REVID=141892852
* Release: add a generate-rc command to the release scriptGravatar Damien Martin-Guillerez2016-12-06
| | | | | | | | | | | | | | | | This generate-rc command allows people to use the git workflow, that is: $ git checkout -b release-name baseline $ git cherry-pick commit1 commit2 ... $ ./scripts/release/release.sh generate-rc Instead of $ ./scripts/release/release.sh create name baseline commit1 commit2 .... -- Change-Id: I4a00f7ab46590450ba7ee26c6509ed747f32d956 Reviewed-on: https://cr.bazel.build/7450 PiperOrigin-RevId: 141163272 MOS_MIGRATED_REVID=141163272
* 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: split up the create operationGravatar Damien Martin-Guillerez2016-12-02
| | | | | | | | | | | | | | Now the create operation is really two part: 1. Overwrite the branch with new cherry-picks 2. Create the commit from the history The second part will be provided as a command. -- Change-Id: Id527fa00c0d573825fcb5f324516cfdd4dcb9139 Reviewed-on: https://cr.bazel.build/7350 PiperOrigin-RevId: 140845679 MOS_MIGRATED_REVID=140845679
* 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
* Release script: add a --force_rc command to override the candidate numberGravatar Damien Martin-Guillerez2016-11-21
| | | | | | | -- Change-Id: I9eb4897dd65e1f63fb4a1ff59ba901f81cd2e6c0 Reviewed-on: https://cr.bazel.build/7336 MOS_MIGRATED_REVID=139580860
* Fix //script/release:release_testGravatar Kristina Chodorow2016-10-28
| | | | | | | Fixes #2003. -- MOS_MIGRATED_REVID=137545010
* Print a summary of what the create command didGravatar Kristina Chodorow2016-10-28
| | | | | | | | | | | | | Added an echo to print "Created 1.2.3RC4 on branch release-1.2.3." when `release.sh create` runs, to save people from the mistake I made (pushing the first RC as "RC3"). I also added a line to bounce the shell back to the original branch the user was on, since it's a bit weird to have the script exit and be on a different branch. -- MOS_MIGRATED_REVID=137512849
* Add all the sources to //:srcs filegroup and add a check to detectGravatar Damien Martin-Guillerez2016-07-01
| | | | | | | | | | | missing file to it. We need to activate this check on presubmits -- Change-Id: Ia95e92d3816ce92bb69bc0e2cf56e9c60b68d970 Reviewed-on: https://bazel-review.googlesource.com/#/c/3949/ MOS_MIGRATED_REVID=126404792
* 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
* Set Bazel's workspace nameGravatar Kristina Chodorow2016-04-27
| | | | | | | | | | RELNOTES: Bazel's workspace name is now io_bazel. If you are using Bazel's source as an external repository, then you may want to update the name you're referring to it as or you'll begin seeing warnings about name mismatches in your code. -- MOS_MIGRATED_REVID=120926179
* Fix release test after commit e7be839Gravatar Damien Martin-Guillerez2016-04-25
| | | | | | | | | Fixes #1187. -- Change-Id: I36e87d86926a38785dcd98c841db826c518cc575 Reviewed-on: https://bazel-review.googlesource.com/3463 MOS_MIGRATED_REVID=120710112
* Add a "Cherry picks" line to the release notesGravatar Kristina Chodorow2016-04-22
| | | | | | | | I was confused about the bulleted list on 0.2.2, so I figured it would be nice tell people what the commit list is. -- MOS_MIGRATED_REVID=120577721
* Fix the release tests after rollback of commit ↵Gravatar Damien Martin-Guillerez2016-04-22
| | | | | | | 9e4c78fb5752fa554db82815f7336255831a95ab -- MOS_MIGRATED_REVID=120540000
* Fix release test with repository issueGravatar Damien Martin-Guillerez2016-04-21
| | | | | | | I properly tested it this time. -- MOS_MIGRATED_REVID=120339101
* Add the repository name prefix to release test environmentGravatar Damien Martin-Guillerez2016-04-20
| | | | | | | This test is now failing on ci.bazel.io -- MOS_MIGRATED_REVID=120328587
* [release] Truncate git hash to 7 charactersGravatar Damien Martin-Guillerez2015-10-08
| | | | | | | | With that change, all the git hash will have the same length in the release notes, even when specifying the full commit hash. -- MOS_MIGRATED_REVID=104861463
* [release] Ignore commit hooksGravatar Damien Martin-Guillerez2015-10-07
| | | | | | | | | So this can be run in a git clone that has commit hooks (e.g., for adding Gerrit change id) without adding garbage to the commit log. -- MOS_MIGRATED_REVID=104761737
* [release] Add new line between releases in the changelogGravatar Damien Martin-Guillerez2015-10-05
| | | | | -- MOS_MIGRATED_REVID=104510412
* [release] Use SSH as the default way to speak to GitHubGravatar Damien Martin-Guillerez2015-10-02
| | | | | -- MOS_MIGRATED_REVID=104506836
* 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
* --Gravatar Damien Martin-Guillerez2015-09-09
| | | | MOS_MIGRATED_REVID=102637361
* Change URLs to bazelbuildGravatar Kristina Chodorow2015-09-01
| | | | | -- MOS_MIGRATED_REVID=102022958
* Fix word wrapping determinism on BSD / LinuxGravatar Damien Martin-Guillerez2015-08-27
| | | | | | | | | | fmt behaves totally differently depending on the version and on the OS, use fold instead that has a consistent behaviour accross platform. Tested with bazel test //scripts/release/... on OSX and Linux. -- MOS_MIGRATED_REVID=101567574
* Port to FreeBSD.Gravatar Doug Rabson2015-08-26
| | | | | | | -- Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7 Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840 MOS_MIGRATED_REVID=101462155
* Fix //scripts/release:release_testGravatar Damien Martin-Guillerez2015-07-30
| | | | | | | Fixes #341 -- MOS_MIGRATED_REVID=99458831
* Disable failing Bazel release test so that we can push.Gravatar Lukacs Berki2015-07-29
| | | | | -- MOS_MIGRATED_REVID=99383290
* 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
* Release note scripts: fix fmt usage under LinuxGravatar Damien Martin-Guillerez2015-07-27
| | | | | | | | | | | For some strange reason fmt do not try to fill the line by default under GNU/Linux. This is using a wrapper around fmt to fix //scripts/release:relnotes_test on Linux. Fixes #331. -- MOS_MIGRATED_REVID=99165254
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-18 16:08:07 +0000