Community
Participate
Working Groups
See https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/303/ (marked as keep forever pending investigation of this bug) In build 302 Hudson was malfunctioning and threw an exception while copying artefacts to the repositories, probably leaving the repositories in an anomalous state. In build 303 everything is fine except that [ant] WARN: Unable to qualify version [ant] org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/lastSuccessfulBuild/artifact/MDT-OCL.p2.repository/. [ant] at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:391) [ant] at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:635) occurs for each artefact and so the update site has plugins named ...qualifier rather then the numeric version. In build 304 everything is fine. It seems that ant has unjustified expectations on repository content.
This is now a solid fault. Both builds 331 and 332 failed because INFO: [start org.eclipse.ocl:osgi.bundle$3.1.0.qualifier#manifest] [ant] WARN: Unable to qualify version [ant] org.eclipse.core.runtime.CoreException: java.net.URISyntaxException: Illegal character in path at index 126: https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/lastSuccessfulBuild/artifact/MDT-OCL.p2.repository/" [ant] at org.eclipse.buckminster.runtime.BuckminsterException.fromMessage(BuckminsterException.java:57) [ant] at org.eclipse.buckminster.runtime.BuckminsterException.wrap(BuckminsterException.java:123) [ant] at org.eclipse.buckminster.runtime.URLUtils.normalizeToURI(URLUtils.java:218)
> [ant] org.eclipse.core.runtime.CoreException: java.net.URISyntaxException: > Illegal character in path at index 126: > https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/lastSuccessfulBuild/artifact/MDT-OCL.p2.repository/" Char 126, is the last slash. Perhaps, by removing it, buckminster won't complain about it... I guess that that the new version of buckminster used by hudson doesn't like the URI we have been using since time ago... Our job has been configured to use the same URI without the last slash, as soon as the curren job finishes, I'll relaunch again...
Oops The offending character is not the slash, but the double quote... It looks like buckminster is receiving an extra "... Looking into this...
Well, weird things usually come from either things really hard to discover/know or by stupidities... The latter in this case... When setting reference.repository property via buckminster command arguments, an extra doble quote was provided... Our last successful P2 repository is correctly generated: https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/lastSuccessfulBuild/artifact/MDT-OCL.p2.repository/plugins/ Resolving as fixed.
mmm.... sorry, I've only fixed the problem in comment1 The original problem needs investigation. I guess that it could be good that if the repository is not correct, the build must fail in somehow... I'll look into, as soon as possible (I get some time at work :)). Cheers, Adolfo.
Given how dificult the quotes and $WORKSPACE etc are, it's probably worth commenting the invocation lines into each of the scripts, enabling the Hudson Job page to be reconstructed by cut and pastes.
Ping. Has this gone away now?
I think this has gone away Possibly the HIPP makes things more reliable Possible Buckminster or something else got better Anyway WORKSFORME now.
CLOSED after more than a year in the RESOLVED state.
