9c35979e12
Most references are in documentation and comments. The main developer-visible behavior change is moving the downloaded artifact cache from ~/.gerritcodereview/buck-cache to bazel-cache, which will result in re-downloading dependencies on the next build; this had to happen sooner or later. Alternatives, which are not worth the effort, include teaching the scripts to accept both locations, or having it rearrange and/or symlink directories behind the scenes. There are just a few references remaining, all of which are intentional: $ git grep -Pi '\bbuck(lets?)?\b' HEAD HEAD:java/com/google/gerrit/httpd/raw/StaticModule.java: // https://gerrit-review.googlesource.com/#/c/57570/57/gerrit-httpd/BUCK@32 HEAD:resources/com/google/gerrit/server/mime/mime-types.properties:bucklet = text/x-python HEAD:resources/com/google/gerrit/server/mime/mime-types.properties:BUCK = text/x-python Change-Id: Idb93a483451ccf86ba96c379d38008a7894c3f95
95 lines
2.1 KiB
Plaintext
95 lines
2.1 KiB
Plaintext
= Making a Release of a Gerrit Subproject
|
|
|
|
[[make-snapshot]]
|
|
== Make a Snapshot
|
|
|
|
* Build the latest snapshot and install it into the local Maven
|
|
repository:
|
|
+
|
|
----
|
|
mvn clean install
|
|
----
|
|
|
|
* Test Gerrit with this snapshot locally
|
|
|
|
|
|
== Publish Snapshot
|
|
|
|
If a snapshot for a subproject was created that should be referenced by
|
|
Gerrit while current Gerrit development is ongoing, this snapshot needs
|
|
to be published.
|
|
|
|
* Make sure you have done the configuration needed for deployment:
|
|
** link:dev-release-deploy-config.html#deploy-configuration-settings-xml[
|
|
Configuration in Maven `settings.xml`]
|
|
** link:dev-release-deploy-config.html#deploy-configuration-subprojects[
|
|
Configuration for Subprojects in `pom.xml`]
|
|
|
|
* Deploy the new snapshot:
|
|
+
|
|
----
|
|
mvn deploy
|
|
----
|
|
|
|
* Change the `id`, `bin_sha1`, and `src_sha1` values in the `maven_jar`
|
|
for the subproject in `/WORKSPACE` to the `SNAPSHOT` version.
|
|
+
|
|
When Gerrit gets released, a release of the subproject has to be done
|
|
and Gerrit has to reference the released subproject version.
|
|
|
|
|
|
[[prepare-release]]
|
|
== Prepare the Release
|
|
|
|
* link:#make-snapshot[First create (and test) the latest snapshot for
|
|
the subproject]
|
|
|
|
* Update the top level `pom.xml` in the subproject to reflect
|
|
the new project version (the exact value of the tag you will create
|
|
below)
|
|
|
|
* Create the Release Tag
|
|
+
|
|
----
|
|
git tag -a -m "prolog-cafe 1.3" v1.3
|
|
----
|
|
|
|
* Build and install into local Maven repository:
|
|
+
|
|
----
|
|
mvn clean install
|
|
----
|
|
|
|
|
|
[[publish-release]]
|
|
== Publish the Release
|
|
|
|
* Make sure you have done the configuration needed for deployment:
|
|
** link:dev-release-deploy-config.html#deploy-configuration-settings-xml[
|
|
Configuration in Maven `settings.xml`]
|
|
** Configuration in `pom.xml` for
|
|
link:dev-release-deploy-config.html#deploy-configuration-subprojects[subprojects]
|
|
|
|
* Deploy the new release:
|
|
+
|
|
----
|
|
mvn deploy
|
|
----
|
|
|
|
* Push the pom change(s) to the project's repository
|
|
`refs/for/<master|stable>`
|
|
|
|
* Push the Release Tag
|
|
+
|
|
----
|
|
git push gerrit-review refs/tags/v1.3:refs/tags/v1.3
|
|
----
|
|
|
|
|
|
GERRIT
|
|
------
|
|
Part of link:index.html[Gerrit Code Review]
|
|
|
|
SEARCHBOX
|
|
---------
|