<div dir="ltr">I haven’t followed entirely, but back in the day of TorqueBox, we’d use a normal CI build, without modifying the pom.xml or other bits.<div><br></div><div>All we’d do is prior to building the -SNAPSHOT version, we’d</div><div><br></div><div> mvn versions:set -DnewVersion=x.y.z.incremental.$BUILD_NO</div><div><br></div><div>e.g.</div><div><br></div><div><div> mvn versions:set -DnewVersion=11.0.0.incremental.$BUILD_NO</div></div><div><br></div><div>We also actually did that to WildFly proper, since TorqueBox built against WF. This allowed us to build against a non-SNAPSHOT release of WF without having to wait for you guys to produce a release, because -SNAPSHOTs are terrible and WF 8 took quite a while to arrive.</div><div><br></div><div>I called them “incremental” because they happened many times a day, and thus not “nightly” builds in our case. Using the CI-provided builder number ensured they were sequential, and using the base version number helped know what the build roughly was.</div><div><br></div><div>-Bob</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 7, 2017 at 9:27 AM, Tomaž Cerar <span dir="ltr"><<a href="mailto:tomaz.cerar@gmail.com" target="_blank">tomaz.cerar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Yeah we can always bash around it, on our CI or when consuming it,</div><div>but that is not a clean solution in any case.</div><div><br></div><div>Having build updated to easier allow for what we need is a way to go.</div><div><br></div><div>--</div><div>tomaz</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 6, 2017 at 4:09 PM, Josef Cacek <span dir="ltr"><<a href="mailto:jcacek@redhat.com" target="_blank">jcacek@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You can also use a workaround through artifacts.zip. We use something like this in our automation:<br>
<br>
wget --user=guest --password=guest <a href="https://ci.wildfly.org/httpAuth/repository/downloadAll/WF_Nightly/.lastSuccessful/artifacts.zip" rel="noreferrer" target="_blank">https://ci.wildfly.org/httpAut<wbr>h/repository/downloadAll/WF_<wbr>Nightly/.lastSuccessful/<wbr>artifacts.zip</a><br>
unzip -q artifacts.zip<br>
export WILDFLY_DIST_ZIP=$(ls wildfly-*-SNAPSHOT.zip)<br>
unzip -q $WILDFLY_DIST_ZIP<br>
export WILDFLY_HOME=`pwd`/${WILDFLY_D<wbr>IST_ZIP%.zip}<br>
<br>
<br>
Regards,<br>
<br>
-- Josef<br>
<div class="m_-7426163259914258822HOEnZb"><div class="m_-7426163259914258822h5"><br>
----- Original Message -----<br>
> From: "Rostislav Svoboda" <<a href="mailto:rsvoboda@redhat.com" target="_blank">rsvoboda@redhat.com</a>><br>
> To: "WildFly Dev" <<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a>><br>
> Sent: Wednesday, September 6, 2017 2:42:21 PM<br>
> Subject: [wildfly-dev] WildFly nightly builds<br>
><br>
> Hi.<br>
><br>
> <a href="https://developer.jboss.org/thread/224262" rel="noreferrer" target="_blank">https://developer.jboss.org/th<wbr>read/224262</a> announced availability of WildFly<br>
> nightly builds.<br>
><br>
> Current status is that you must know the URL based on current version in<br>
> master<br>
> At this moment it is<br>
> <a href="https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.lastFinished/wildfly-11.0.0.Final-SNAPSHOT.zip" rel="noreferrer" target="_blank">https://ci.wildfly.org/guestAu<wbr>th/repository/download/WF_<wbr>Nightly/latest.lastFinished/<wbr>wildfly-11.0.0.Final-SNAPSHOT.<wbr>zip</a>,<br>
> root dir of the zip is wildfly-11.0.0.Final-SNAPSHOT<br>
><br>
> '11.0.0.Final-SNAPSHOT' is the changing part and when you want to consume<br>
> nightly build in CI (e.g. Travis) you end up doing unnecessary changes to<br>
> .travis.yml (Alpha1-SNAPSHOT ==> Beta1-SNAPSHOT ==> Final-SNAPSHOT) when PRs<br>
> fail because of unavailable nightly bits<br>
><br>
> I would like to make automated consumption of WildFly nightly builds easier<br>
><br>
> Proposal 1 - expose latest bits under the same URL + keep the same root dir<br>
> name<br>
> URL:<br>
> <a href="https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.lastFinished/wildfly-latest-SNAPSHOT.zip" rel="noreferrer" target="_blank">https://ci.wildfly.org/guestA<wbr>uth/repository/download/WF_<wbr>Nightly/latest.lastFinished/<wbr>wildfly-latest-SNAPSHOT.zip</a><br>
> root dir of the zip: wildfly-latest-SNAPSHOT<br>
><br>
> Automation would be prepared just once and "work forever".<br>
><br>
><br>
> Proposal 2 - keep current zip & root dir name + add txt file with version<br>
> information<br>
> introduce<br>
> <a href="https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.lastFinished/version.txt" rel="noreferrer" target="_blank">https://ci.wildfly.org/guestA<wbr>uth/repository/download/WF_<wbr>Nightly/latest.lastFinished/<wbr>version.txt</a><br>
> Currently it would contain '11.0.0.Final-SNAPSHOT'<br>
> Example to get version: mvn help:evaluate -Dexpression=project.version |<br>
> grep -v "^\["<br>
><br>
> Automation could consume content of version.txt and construct the download<br>
> URL + root dir name<br>
> VERSION=`curl<br>
> <a href="https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.lastFinished/version.txt" rel="noreferrer" target="_blank">https://ci.wildfly.org/guestA<wbr>uth/repository/download/WF_<wbr>Nightly/latest.lastFinished/<wbr>version.txt`</a><br>
> <a href="https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.lastFinished/wildfly-$%7BVERSION%7D.zip" rel="noreferrer" target="_blank">https://ci.wildfly.org/guestA<wbr>uth/repository/download/WF_<wbr>Nightly/latest.lastFinished/<wbr>wildfly-${VERSION}.zip</a><br>
> root dir of the zip is wildfly-${VERSION}<br>
><br>
><br>
> WDYT?<br>
><br>
> Regards.<br>
> Rostislav<br>
><br>
> ______________________________<wbr>_________________<br>
> wildfly-dev mailing list<br>
> <a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailma<wbr>n/listinfo/wildfly-dev</a><br>
><br>
______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailma<wbr>n/listinfo/wildfly-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/wildfly-dev</a><br></blockquote></div><br></div>