1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
Steps to build junit:
- Must be manual
- Write release notes
- Not too tedious:
- Push to github (junit-team)
- Run the ./mvnw clean install
- If not done, update $M2_HOME/settings.xml
- If not done, copy GnuPG keys in to ${gpg.homedir}. See settings.xml.
- Perform Maven deployment of a snapshot or release version in Jenkins
Remember that the version specified in the pom.xml indicates the version
to be deployed, with -SNAPSHOT indicating that this is an unofficial
pre-release version towards the goal of the version without the -SNAPSHOT
- (to deploy gpg signed snapshot version)
$ ./mvnw -Pjunit-release clean deploy
- (to cut a release of the current targetted version)
$ ./mvnw -B release:prepare release:perform
This will result in the current pom.xml version having -SNAPSHOT removed
and the release cut from that version. The version will then be incremented
and -SNAPSHOT added back in anticipation of the next release version.
- (to cut a release of while changing the version from the current target)
$ ./mvnw -B -DreleaseVersion=5.0 release:prepare release:perform
This will ignore the current version in the pom.xml, set it to 5.0 and
the release cut from that 5.0 version. Then 5.0 will be incremented (to 5.1)
and -SNAPSHOT added back in anticipation of the next release version.
- (to deploy specified release version and next target release in non-interactive mode -B)
An example with the next development version and deploying release version:
$ ./mvnw -B -DreleaseVersion=4.12 -DdevelopmentVersion=4.13-SNAPSHOT release:prepare release:perform
- If you are not an official release manager, and you want to cut a release of
JUnit for use within your organization, use the following command
$ ./mvnw -DpushChanges=false -DlocalCheckout '-Darguments=-Dgpg.skip=true -DaltDeploymentRepository=my-company-repo-id::default::my-company-repo-url' -B -DreleaseVersion=4.12-mycompany-1 release:prepare release:perform
where
- my-company-repo-id is the <id> of your company's <server> entry in your
settings.xml with the credentials to deploy to your company's Maven repository
- my-company-repo-url is the deployment URL of your company's Maven repository
- 4.12-mycompany-1 is the version you are deploying, be sure to namespace
the version so that you don't conflict with others, hence why the text "mycompany"
is included in the example version number.
- Promote the maven artifacts and close staging repository if released successfully
- Tedious:
- Update SourceForge if major release
- Update javadocs on github site (and "latest" link)
- Update javadocs on junit.org
- Put release notes on github.
- Announce on blog, user list, dev list, announce list, junit.org, twitter
- Profit!
===================================================================================
== Internal template of Maven settings used by JUnit build machine. ==
== settings.xml ==
===================================================================================
<?xml version="1.0" encoding="UTF-8"?>
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
<servers>
<server>
<id>junit-snapshot-repo</id>
<username><!--a username registered with Sonatype for deployment--></username>
<password><!--corresponding password--></password>
</server>
<server>
<id>junit-releases-repo</id>
<username><!--a username registered with Sonatype for deployment--></username>
<password><!--corresponding password--></password>
</server>
</servers>
<profiles>
<profile>
<id>junit-release</id>
<properties>
<!-- NOTE: See keyname used by maven-gpg-plugin in pom.xml. -->
<gpg.passphrase>...</gpg.passphrase>
<gpg.defaultKeyring>false</gpg.defaultKeyring>
<gpg.useagent>true</gpg.useagent>
<gpg.homedir>/private/.../.gnupg</gpg.homedir>
<gpg.publicKeyring>/private/.../.gnupg/pubring.gpg</gpg.publicKeyring>
<gpg.secretKeyring>/private/.../.gnupg/secring.gpg</gpg.secretKeyring>
</properties>
</profile>
</profiles>
</settings>
===================================================================================
|
