[cle-release-team] Hoe to release an indie

[Matthew Jones]

Yea, presently jenkins has the credentials stored to deploy it to sonatype.

To actually release something tagged to maven central, you actually have to
login to the interface, verify that all of the files are there and the poms
are correct. Close the deployment and release the deployment. This is
mentioned in the pre-release step under "obtaining credentials" on how to
do this (have to create a jira entry and have it approved).

I wouldn't say this is a huge deal because already Sam, Chris and myself
can do this, and it takes around 4-6 hours anyway for the artifacts to make
it into maven central. But if you (or someone else) is actually going to be
active in this process, you can obtain this account.

Jenkins deploys it as a special account we setup, but we still login and
close/release as our personal accounts.

On Mon, Apr 23, 2012 at 2:14 AM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> Ok that all sounds fine, thanks for the info.
>
> In the past, whenever I've released a tool I go in and update master for
> that branch as well, so the next full release picks it up, so that's all
> good.
>
> What I am really interested in is this:
>
> #3 - The final step (actually closing it and releasing the artifacts to
> sonatype) are currently limited to a select group. Maybe this group should
> be more limited than the people actually doing the actions on Jenkins?
> Maybe not? I'm not sure how complex we want it
>
>
> So that sounds like we DO need to go to sonatype and push it through?
>
> cheers,
> Steve
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20120423/3a879d66/attachment-0006.html