Thanks Martijn and Jeremy for all your work on getting this to work.
I have the 1.4.10-SNAPSHOT wicketstuff-core artifacts deploying again
now that they can fetch the snapshots from
https://repository.apache.org/content/repositories/snapshots.
Martijn: your Apache Infrastructure ticket has been updated that the
builds in 1.5.x were failing due to load on the build server. I checked
the log for #111 and the profile is correct but the goal is still
'install' not 'deploy' which is needed to deploy the 1.5-SNAPSHOT artifacts.
A committer can check their ability to deploy by seeing if they can log
into the nexus interface at http://repository.apache.org then check for
the 'Enterprise' left section and the 'Staging' link. There should be
an org.apache.wicket row in the top table and nothing in the bottom
table. The bottom table can be shown by selecting the org.apache.wicket
row in the top table.
You should be able to test the staging release process by downloading a
working copy of trunk, changing the versions to remove the SNAPSHOT (mvn
versions:set -DnewVersions=1.4.11) and then 'mvn -P apache-nexus-deploy
clean deploy'
Once deploy has been run you can reload the bottom table in the web
interface and you should see a unique row for each computer (IP address)
that has run a deploy. At this point you know it works and can just
right click the staging row and click 'drop'.
Thanks again,
Mike
Fixed for 1.4.x, 1.5.x seems to have a hudson error (getting http 500 errors)
Martijn
On Mon, Jun 21, 2010 at 12:13 AM, Michael O'Cleirigh
<michael.ocleir...@rivulet.ca> wrote:
On 20/06/2010 2:12 PM, Jeremy Thomerson wrote:
On Sun, Jun 20, 2010 at 1:01 PM, Martijn Dashorst<
martijn.dasho...@gmail.com> wrote:
I've setup the hudson stuff, but I haven't seen an example build that
deploys snapshots to nexus.
Martijn
I just committed the pom changes from Michael. I think all you'll need to
do in Hudson (for trunk) is change the build profile to use
"apache-nexus-deploy" instead of whatever it's currently using. Then we
can
duplicate for 1.4.x.
You will need to modify the Goals and options text field of the Hudson Job
to something like this:
-Papache-nexus-deploy clean deploy
I looked at build #6 of the 1.4.x branch and the maven command being
executed is:
Executing Maven: -B -f /home/hudson/hudson-slave/workspace/Apache Wicket
1.4.x/wicket-1.4.x/pom.xml
-Dmaven.repo.local=/home/hudson/hudson-slave/workspace/Apache Wicket
1.4.x/.repository clean install
So the key changes will be to active the new profile and to run the deploy
goal instead of install.
When it is working you should see entries like this in the build log:
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from apache.snapshots.https
[INFO] repository metadata for: 'snapshot
org.apache.wicket:wicket-parent:1.5-SNAPSHOT' could not be found on
repository: apache.snapshots.https, so will be created
Uploading:
https://repository.apache.org/content/repositories/snapshots/org/apache/wicket/wicket-parent/1.5-SNAPSHOT/wicket-parent-1.5-20100617.013747-1.pom
26K uploaded
[INFO] -------------
Regards,
Mike
