[infinispan-issues] [JBoss JIRA] (ISPN-1947) Automate staging repository step in release script
Sanne Grinovero (JIRA)
issues at jboss.org
Mon Dec 19 07:05:00 EST 2016
[ https://issues.jboss.org/browse/ISPN-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13340162#comment-13340162 ]
Sanne Grinovero commented on ISPN-1947:
---------------------------------------
Note that closing the repository doesn't imply releasing it. You should close the staging repo, so that it's "sealed" and no more artifacts are added.
Then you can test it, automatically or advertise to the community that a CR is available on the staging repo (there's actually an URL to a Maven repository associated).
Finally after (and only if) the tests are satisfactory, then you release it.
> Automate staging repository step in release script
> --------------------------------------------------
>
> Key: ISPN-1947
> URL: https://issues.jboss.org/browse/ISPN-1947
> Project: Infinispan
> Issue Type: Task
> Components: Build process
> Reporter: Sanne Grinovero
> Assignee: Sebastian Łaskawiec
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> The Nexus staging plugin can be used to control the staging repository from command line (including authenticating with your account as set in your settings file)
> https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the infinispan-issues
mailing list