| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Closes #5679.
PiperOrigin-RevId: 208194222
|
|
|
|
|
|
|
|
| |
These are the scripts I'm currently using for the Bazel 0.12.0 release.
Closes #4908.
PiperOrigin-RevId: 190598268
|
|
|
|
|
|
|
|
| |
see #4023
Closes #4051.
PiperOrigin-RevId: 177279457
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 157572063
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 145559628
MOS_MIGRATED_REVID=145559628
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
--
Change-Id: I9eb4897dd65e1f63fb4a1ff59ba901f81cd2e6c0
Reviewed-on: https://cr.bazel.build/7336
MOS_MIGRATED_REVID=139580860
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104510412
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104506836
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
MOS_MIGRATED_REVID=102637361
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102022958
|
|
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
|