On Wed, Jun 16, 2010 at 9:14 PM, Michael O'Cleirigh < michael.ocleir...@rivulet.ca> wrote:
> Hello, > > I've attached the patches for the 1.4.x pom.xml and the trunk 1.5 pom.xml > to the issue: (https://issues.apache.org/jira/browse/WICKET-2918) > > I added the apache parent pom and then created a copy of the bamboo profile > minus the dependencyManagement section to let the definition contained in > the apache parent pom to be used. > > I'm not totally clear at this point how the access credentials will work > but I think it should be the existing committer username/password > > Essentially one username/password will have to be placed into a > settings.xml file that can be located relative to the workspace directory > within the hudson job that builds each version. > > With the oss.sonatype.org repository I created a set of CI credentials > that were then granted permission to deploy a specific groupID > (org.wicketstuff) then I used a custom settings.xml file with those > credentials to line up with the <id/>tag of the snapshot repository which > allowed hudson to deploy the snapshots. In my hudson instance I needed to > use shell access to place the settings.xml file in the right location. > > The release repository is configured to use staging so when a release is > cut the deploy will upload into a temporary space within nexus. > > The nexus username/password is used to authenticate and 'close' (a right > click menu option) the repository which makes the uploaded artifacts > available for download by those knowing the link. If the vote to release is > passed there is an option to 'promote' (another right click menu item) the > staged release which will then within an hour sync it up with the central > repository. > I think testing the nexus release mechanism should be doable before the > next release because it can be staged and if successful it can be dropped. > Great! Thanks for all the help. I'll get a ticket going with infra asap. -- Jeremy Thomerson http://www.wickettraining.com
