[
https://issues.apache.org/jira/browse/JAMES-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17293778#comment-17293778
]
Juhan Aasaru commented on JAMES-3510:
-------------------------------------
We have set up publishing to Maven Central with a (non-apache) open source
project [https://github.com/SK-EID/smart-id-java-client] using Travis
This is how it works
https://github.com/SK-EID/smart-id-java-client/blob/master/.travis.yml keeps an
encrypted private key (secret #1) that is encrypted with a password (secret #2)
Travis decrypts the PGP private key using these two secrets.
And starts
[https://github.com/SK-EID/smart-id-java-client/blob/master/travis.sh]
This script detects if the build was triggered because someone just created a
new tag for the repository (tag = version number) and if this was the case
starts publishing script:
[https://github.com/SK-EID/smart-id-java-client/blob/master/publish.sh]
This script PGP signs the artifacts, bundles them and uploads to Maven Central
staging repo.
After that one has to log in to sonatype staging repository, click "close",
perfor any tests and publish the new version.
> Automate release procedure to speed up releases
> -----------------------------------------------
>
> Key: JAMES-3510
> URL: https://issues.apache.org/jira/browse/JAMES-3510
> Project: James Server
> Issue Type: Improvement
> Reporter: Juhan Aasaru
> Priority: Major
>
> Could we collect here the steps that could be automated to fasten the process
> of creating a new release.
> Me (or my colleague Andreas) would be willing to work on some of the
> automation tasks.
> I propose automating publishing to Maven Central (building artifacts and PGP
> signing them)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
