Cargo

Migrate to the new Nexus instance at Codehaus (maven repo for deploy)

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.2, 1.0.3
  • Fix Version/s: 1.0.4
  • Component/s: Build
  • Labels:
    None
  • Environment:
    n/a
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

We should deploy to the maven repo on the new Nexus instance at Codehaus (https://nexus.codehaus.org), instead of the old maven repo that we use for deploy today.

This will get us benefits like:

  • Staging support when cutting a release
  • Validation of release (according to requirements of central)
  • Faster replication to central (every 2 hours)

Documentation about this:
https://docs.codehaus.org/display/HAUSMATES/Codehaus+Maven+Repository+Usage+Guide

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Anders Hammar added a comment -

The validation rules of the staging repo will require some changes to our build procedure, like adding signatures. There is some info in this blog post:http://www.sonatype.com/people/2010/01/nexus-oss-ecosystem/

I'll try to dig up the exact requirements today. Any changes should be added as sub-tasks I think.

Show
Anders Hammar added a comment - The validation rules of the staging repo will require some changes to our build procedure, like adding signatures. There is some info in this blog post: http://www.sonatype.com/people/2010/01/nexus-oss-ecosystem/ I'll try to dig up the exact requirements today. Any changes should be added as sub-tasks I think.
Hide
Permalink
Anders Hammar added a comment -

I've mailed the Codehaus support regarding this.

Show
Anders Hammar added a comment - I've mailed the Codehaus support regarding this.
Hide
Permalink
Anders Hammar added a comment -

Ticket HAUS-1991 created.

Show
Anders Hammar added a comment - Ticket HAUS-1991 created.
Hide
Permalink
Anders Hammar added a comment -

The migration has started. We are now beyond the point of no return...

Show
Anders Hammar added a comment - The migration has started. We are now beyond the point of no return...
Hide
Permalink
Savas Ali Tokmen added a comment -

Yesterday I've tried deploying on the repo (the snapshot, mvn deploy -Drelease=true -DperformRelease=true), the major change is that you now need gpg as the release process will sign the JARs. File exchange is also much more stable compared to the old WebDAV.

This ticket can be closed as soon as the following redirection are in place:

Show
Savas Ali Tokmen added a comment - Yesterday I've tried deploying on the repo (the snapshot, mvn deploy -Drelease=true -DperformRelease=true), the major change is that you now need gpg as the release process will sign the JARs. File exchange is also much more stable compared to the old WebDAV. This ticket can be closed as soon as the following redirection are in place: http://repository.codehaus.org/org/codehaus/cargo/ to http://nexus.codehaus.org/content/repositories/releases/org/codehaus/cargo/ http://snapshots.repository.codehaus.org/org/codehaus/cargo to http://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/cargo/
Hide
Permalink
Anders Hammar added a comment -

I suggest we keep this ticket open until the release of 1.0.3 is complete. When we know everything regarding the migration is ok we close it.

Show
Anders Hammar added a comment - I suggest we keep this ticket open until the release of 1.0.3 is complete. When we know everything regarding the migration is ok we close it.
Hide
Permalink
Savas Ali Tokmen added a comment -

OK working

For the next version, in order to enable staging, we would perhaps need to move the Maven2 submodules resources, core and extensions into one.

Show
Savas Ali Tokmen added a comment - OK working For the next version, in order to enable staging, we would perhaps need to move the Maven2 submodules resources, core and extensions into one.
Hide
Permalink
Anders Hammar added a comment -

Nope, that shouldn't be necessary. You can do several releases into one staging repo.

Show
Anders Hammar added a comment - Nope, that shouldn't be necessary. You can do several releases into one staging repo.
Hide
Permalink
Anders Hammar added a comment -

Re-opening as we aren't finished I think. The redirects have caused issues (see CARGO-840) for example. Also, the release process needs to be tuned. I'll add a separate task for that.

Show
Anders Hammar added a comment - Re-opening as we aren't finished I think. The redirects have caused issues (see CARGO-840 ) for example. Also, the release process needs to be tuned. I'll add a separate task for that.
Hide
Permalink
Savas Ali Tokmen added a comment -

CARGO 1.0.3 has been finished without fully implementing a staging strategy. This needs to be done better for 1.0.4.

Show
Savas Ali Tokmen added a comment - CARGO 1.0.3 has been finished without fully implementing a staging strategy. This needs to be done better for 1.0.4.
Hide
Permalink
Savas Ali Tokmen added a comment -

Finished

Show
Savas Ali Tokmen added a comment - Finished
Hide
Permalink
Anders Hammar added a comment -

Ali,

this ticket was assigned to me. Please don't close other people's tickets! At least not without asking first.

Show
Anders Hammar added a comment - Ali, this ticket was assigned to me. Please don't close other people's tickets! At least not without asking first.
Hide
Permalink
Savas Ali Tokmen added a comment -

Oops sorry about that

Show
Savas Ali Tokmen added a comment - Oops sorry about that
Hide
Permalink
Savas Ali Tokmen added a comment -

Are we going to close this for 1.0.4 or postpone?

Show
Savas Ali Tokmen added a comment - Are we going to close this for 1.0.4 or postpone?
Hide
Permalink
Anders Hammar added a comment -

We'll close when the staging is done. You may re-assign this ticket to you and close it when you close the vote for 1.0.4. SO, yes, it should be closed for 1.0.4.

Show
Anders Hammar added a comment - We'll close when the staging is done. You may re-assign this ticket to you and close it when you close the vote for 1.0.4. SO, yes, it should be closed for 1.0.4.

People

  • Assignee:
    Anders Hammar
    Reporter:
    Anders Hammar
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: