I'm having exactly the opposite problem - my hudson jobs keep aborting:
[INFO] Resolving target platform for project MavenProject:
org.eclipse.bpmn2.modeler:org.eclipse.bpmn2.modeler.core:0.0.1-SNAPSHOT @
/opt/users/hudsonbuild/workspace/tycho-bpmn2modeler-0.0.1-nightly/org.eclipse.bpmn2.modeler.core/pom.xml
[ERROR] Internal error: java.lang.IllegalArgumentException: Invalid portable
string: p2.osgi.bundle:org.eclipse.update -> [Help 1]
org.apache.maven.InternalErrorException: Internal error:
java.lang.IllegalArgumentException: Invalid portable string:
p2.osgi.bundle:org.eclipse.update
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.IllegalArgumentException: Invalid portable string:
p2.osgi.bundle:org.eclipse.update
at org.eclipse.tycho.p2.repository.GAV.nextColonIndex(GAV.java:103)
at org.eclipse.tycho.p2.repository.GAV.parse(GAV.java:85)
at
org.eclipse.tycho.p2.repository.DefaultTychoRepositoryIndex.read(DefaultTychoRepositoryIndex.java:76)
at
org.eclipse.tycho.p2.repository.FileBasedTychoRepositoryIndex.createRepositoryIndex(FileBasedTychoRepositoryIndex.java:46)
at
org.eclipse.tycho.p2.impl.resolver.ResolutionContextImpl.<init>(ResolutionContextImpl.java:142)
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverFactoryImpl.createResolutionContext(P2ResolverFactoryImpl.java:32)
at
org.eclipse.tycho.p2.impl.resolver.P2ResolverFactoryImpl.createResolutionContext(P2ResolverFactoryImpl.java:1)
at
org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolvePlatform(P2TargetPlatformResolver.java:156)
at
org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:85)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:91)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:273)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
Is this a maven repo problem and, if so, how do I fix it?
Thanks!
Bob
----- Original Message -----
> I'm seeing the same thing. The build page says there were "No
> changes." Checking the polling log, I see:
>
> Started on Feb 26, 2012 3:01:15 AM
> Using strategy: Default
> [poll] Last Build : #255
> [poll] Last Built Revision: Revision
> d39f64adfb1570f6be9f07a636d4d2a1bf781562 (origin/cdt_8_0)
> Last build was not on tied node, forcing rebuild.
> Done. Took 3.1 sec
> Changes found
>
> "forcing rebuild" is probably the key. Is everyone seeing the same?
> What does "not on tied node" mean?
>
> Doug.
>
> On Sun, Feb 26, 2012 at 12:21 PM, David M Williams
> <david_willi...@us.ibm.com> wrote:
> >
> > I know there was a problem where a Gerrit Plugin was triggering
> > jobs
> > (unrelated to Gerrit) but as far as I know, that was
> > disabled/removed from
> > the production Hudson system. (Sorry, don't know bug number).
> > Plus, I had a case where "URL Content Change" trigger stopped
> > working
> > right, and those jobs were building over and over again, even
> > though no
> > content change (bug 363891 [1]).
> >
> > In the past, I've sometimes found it helps "odd Hudson behavior" to
> > "wipe
> > out workspace", essentially resetting what ever is there. To get to
> > that
> > option, click on the job, click on "Workspace" (on left, upper part
> > of
> > page), which displays the workspace, but also reveals a "Wipe out
> > workspace" option. I'm sure it is mostly "superstitious behavior"
> > ... but
> > has seemed to help in some cases.
> >
> > In any case, I'd encourage you see if any existing bugs are related
> > to your
> > observations [2] and if not, to open one [3] being sure to make
> > note "it is
> > on Eclipse Infrastructure".
> >
> > Good luck,
> >
> > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=363891
> >
> > [2]
> > https://bugs.eclipse.org/bugs/query.cgi?classification=Technology&product=Hudson&query_format=advanced
> >
> > [3] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Hudson
> >
> >
> >
> >
> >
> >
> >
> > From: Eike Stepper <step...@esc-net.de>
> > To: cross-project-issues-dev@eclipse.org,
> > Date: 02/25/2012 10:58 PM
> > Subject: [cross-project-issues-dev] Hudson job keeps
> > rebuilding
> > Sent by: cross-project-issues-dev-boun...@eclipse.org
> >
> >
> >
> > Hi,
> >
> > One of my Hudson jobs,
> > https://hudson.eclipse.org/hudson/job/emf-cdo-maintenance ,
> > repeatedly sees
> > Git changes (SCM
> > trigger) that do not exist. It always reports (a) Started by SCM
> > change and
> > (b) No changes. But then it triggers a build
> > rather than just exit. I'm polling for SCM changes every 2 hours.
> > That
> > results in 12 unnecessary builds per day ;-(
> >
> > This strange behaviour started yesterday. Does anybody see the same
> > behaviour?
> >
> > Cheers
> > /Eike
> >
> > ----
> > http://www.esc-net.de
> > http://thegordian.blogspot.com
> > http://twitter.com/eikestepper
> >
> >
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> >
> >
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@eclipse.org
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
