I finally found a way to fix that, but I did not understand really
why it fixes anything...
1. removed "-P build-server" from command-line (disable signing and
publishing)
2. start a build -> download went well, build started
3. abort build
4. re-add "-P build-server" to command line and run
5. build goes well...
On 19/12/2011 18:29, Mickael Istria wrote:
Hi all,
This is just a note to inform you that current Nebula builds
always freeze on hudson.eclipse.org for several days. They freeze
on a "Scanning for projects" step.
See https://hudson.eclipse.org/hudson/job/nebula.nebula/266/console
I'm clueless. Can you please all spend the couple of minutes
necessary to do the following test and report what you get:
1. Get a clone of the Nebula repo
2. go to the root of the repo
3. "mvn -f releng/org.eclipse.nebula.nebula-release/pom.xml
-Declipse.p2.mirrors=false
-Dmaven.repo.local=/opt/users/hudsonbuild/.hudson/jobs/nebula.nebula/workspace/.repository
clean install javadoc:aggregate -Pbuild-server"
This command line should finish by a failed build because of
signer plugin error, but what I'd like to know is whether it goes
further that it goes on hudson.eclipse.org.
Thanks in advance.
_______________________________________________
nebula-dev mailing list
nebula-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/nebula-dev
|
