<p dir="ltr">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.</p>
<p dir="ltr">Why inconvenience everyone with false reds and the inability to build locally?</p>
<div class="gmail_quote">On Sep 25, 2015 8:05 AM, "Max Rydahl Andersen" <<a href="mailto:manderse@redhat.com">manderse@redhat.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>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. </div><div><br></div><div>Tricks like moving them over and/or override settings in Jenkins builds should a "last option" tool. <br><br>/max<div><a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a></div><div><br></div></div><div><br>On 24 Sep 2015, at 16:05, Martin Malina <<a href="mailto:mmalina@redhat.com" target="_blank">mmalina@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div>Did you forget about integration tests?<div><a href="http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-tests/master/" target="_blank">http://download.jboss.org/jbosstools/neon/snapshots/updates/integration-tests/master/</a></div><div><br></div><div>-Martin<br>
<br><div><blockquote type="cite"><div>On 24. 9. 2015, at 14:56, Nick Boldt <<a href="mailto:nboldt@redhat.com" target="_blank">nboldt@redhat.com</a>> wrote:</div><br><div>What changed was that I moved all the _master build results folders<br>under /mars/snapshots/ to /neon/snapshots/ so that all the URLs listed<br>in the Alpha1 parent pom could be resolved and therefore all the<br>interproject dependencies could be found.<br><br>This was verified by Fred saying "my job is broken" then I did the<br>move, and he confirmed "build completed ok".<br><br><br><br>On Thu, Sep 24, 2015 at 2:20 AM, Max Rydahl Andersen<br><<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>> wrote:<br><blockquote type="cite">On 24 Sep 2015, at 7:28, Max Rydahl Andersen wrote:<br><br><blockquote type="cite">Looks like this are now fixed since I now see<br><a href="http://download.jboss.org/jbosstools/neon/snapshots/builds/" target="_blank">http://download.jboss.org/jbosstools/neon/snapshots/builds/</a> filled up.<br><br>Nick/Michael - can you give an update on what changed ?<br></blockquote><br>Talked with Michael and seems what changed is just that jbosstools-base<br>were missing<br>version bump. Now that is done it trickles down to all builds as soon<br>as they get their version bumped.<br><br>In past master builds were stopped since jenkins was overloaded, that<br>seem not to be<br>the case anymore so if we just do proper branching with a version bump<br>and stream name change both master and branch can be developed<br>concurrently without any accidental overlaps.<br><br>/max<br><br><blockquote type="cite"><br>Have we restarted the master builds fully now using for now mars based<br>TP, or was it just a single run to make builds<br>work ?<br><br>Thanks,<br>/max<br><br><blockquote type="cite">Hey,<br><br>A few have noticed that when you build on master after updating<br>parent<br>pom you get build failures due to missing neon repos.<br><br>This will unfortunately happen until neon streams start (note, this<br>does<br>not require any Neon TP to be present but jenkinsare busy doing CR1<br>builds so we'll have to wait).<br><br>You can use the CR1 parent pom in the meantime - the minimal change<br>required is just the version bump so your master and branch builds<br>does<br>not collide when building locally.<br><br>sorry for this, but I hope Michael/Nick soon can kick of the master<br>builds so this will not be a problem. (and no,it does not require<br>usage<br>of an actual neon tp - we just need the stream urls built)<br><br>/max<br><a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br>_______________________________________________<br>jbosstools-dev mailing list<br><a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br></blockquote><br><br>/max<br><a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br>_______________________________________________<br>jbosstools-dev mailing list<br><a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br></blockquote><br><br>/max<br><a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br>_______________________________________________<br>jbosstools-dev mailing list<br><a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br></blockquote><br><br><br>-- <br>Nick Boldt :: JBoss by Red Hat<br>Productization Lead :: JBoss Tools & Dev Studio<br><a href="http://nick.divbyzero.com" target="_blank">http://nick.divbyzero.com</a><br>_______________________________________________<br>jbosstools-dev mailing list<br><a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br></div></blockquote></div><br></div></div></blockquote></div></blockquote></div>