Had I not moved them you'd be getting red balls for all the projects with long dep chains simply because a project like Server had not migrated to Alpha1 parent and kicked a new build.
Why inconvenience everyone with false reds and the inability to build locally?
These really should not be moved - it's up to components itself to use the right parent Pom which will make it publish to the right place.Tricks like moving them over and/or override settings in Jenkins builds should a "last option" tool.
/maxDid you forget about integration tests?-Martin
On 24. 9. 2015, at 14:56, Nick Boldt <nboldt@redhat.com> wrote:What changed was that I moved all the _master build results folders
under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed
in the Alpha1 parent pom could be resolved and therefore all the
interproject dependencies could be found.
This was verified by Fred saying "my job is broken" then I did the
move, and he confirmed "build completed ok".
On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen
<manderse@redhat.com> wrote:On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:Looks like this are now fixed since I now see
http://download.jboss.org/jbosstools/neon/snapshots/builds/ filled up.
Nick/Michael - can you give an update on what changed ?
Talked with Michael and seems what changed is just that jbosstools-base
were missing
version bump. Now that is done it trickles down to all builds as soon
as they get their version bumped.
In past master builds were stopped since jenkins was overloaded, that
seem not to be
the case anymore so if we just do proper branching with a version bump
and stream name change both master and branch can be developed
concurrently without any accidental overlaps.
/max
Have we restarted the master builds fully now using for now mars based
TP, or was it just a single run to make builds
work ?
Thanks,
/maxHey,
A few have noticed that when you build on master after updating
parent
pom you get build failures due to missing neon repos.
This will unfortunately happen until neon streams start (note, this
does
not require any Neon TP to be present but jenkinsare busy doing CR1
builds so we'll have to wait).
You can use the CR1 parent pom in the meantime - the minimal change
required is just the version bump so your master and branch builds
does
not collide when building locally.
sorry for this, but I hope Michael/Nick soon can kick of the master
builds so this will not be a problem. (and no,it does not require
usage
of an actual neon tp - we just need the stream urls built)
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
/max
http://about.me/maxandersen
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev