From: "Rostislav Svoboda" <rsvoboda(a)redhat.com&gt; To: "WildFly Dev" <wildfly-dev(a)lists.jboss.org&gt; Sent: Wednesday, September 6, 2017 2:42:21 PM Subject: [wildfly-dev] WildFly nightly builds Hi. https://developer.jboss.org/thread/224262 announced availability of WildFly nightly builds. Current status is that you must know the URL based on current version in master At this moment it is https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la..., root dir of the zip is wildfly-11.0.0.Final-SNAPSHOT '11.0.0.Final-SNAPSHOT' is the changing part and when you want to consume nightly build in CI (e.g. Travis) you end up doing unnecessary changes to .travis.yml (Alpha1-SNAPSHOT ==> Beta1-SNAPSHOT ==> Final-SNAPSHOT) when PRs fail because of unavailable nightly bits I would like to make automated consumption of WildFly nightly builds easier Proposal 1 - expose latest bits under the same URL + keep the same root dir name URL: https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la... root dir of the zip: wildfly-latest-SNAPSHOT Automation would be prepared just once and "work forever". Proposal 2 - keep current zip & root dir name + add txt file with version information introduce https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la... Currently it would contain '11.0.0.Final-SNAPSHOT' Example to get version: mvn help:evaluate -Dexpression=project.version | grep -v "^\[" Automation could consume content of version.txt and construct the download URL + root dir name VERSION=`curl https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la... https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la... root dir of the zip is wildfly-${VERSION} WDYT? Regards. Rostislav _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Yeah we can always bash around it, on our CI or when consuming it, but that is not a clean solution in any case. Having build updated to easier allow for what we need is a way to go. -- tomaz On Wed, Sep 6, 2017 at 4:09 PM, Josef Cacek <jcacek(a)redhat.com&gt; wrote: > You can also use a workaround through artifacts.zip. We use something > like this in our automation: > > wget --user=guest --password=guest https://ci.wildfly.org/httpAut > h/repository/downloadAll/WF_Nightly/.lastSuccessful/artifacts.zip > unzip -q artifacts.zip > export WILDFLY_DIST_ZIP=$(ls wildfly-*-SNAPSHOT.zip) > unzip -q $WILDFLY_DIST_ZIP > export WILDFLY_HOME=`pwd`/${WILDFLY_DIST_ZIP%.zip} > > > Regards, > > -- Josef > > ----- Original Message ----- > > From: "Rostislav Svoboda" <rsvoboda(a)redhat.com&gt; > > To: "WildFly Dev" <wildfly-dev(a)lists.jboss.org&gt; > > Sent: Wednesday, September 6, 2017 2:42:21 PM > > Subject: [wildfly-dev] WildFly nightly builds > > > > Hi. > > > > https://developer.jboss.org/thread/224262 announced availability of > WildFly > > nightly builds. > > > > Current status is that you must know the URL based on current version in > > master > > At this moment it is > > https://ci.wildfly.org/guestAuth/repository/download/WF_ > Nightly/latest.lastFinished/wildfly-11.0.0.Final-SNAPSHOT.zip, > > root dir of the zip is wildfly-11.0.0.Final-SNAPSHOT > > > > '11.0.0.Final-SNAPSHOT' is the changing part and when you want to > consume > > nightly build in CI (e.g. Travis) you end up doing unnecessary changes > to > > .travis.yml (Alpha1-SNAPSHOT ==> Beta1-SNAPSHOT ==> Final-SNAPSHOT) > when PRs > > fail because of unavailable nightly bits > > > > I would like to make automated consumption of WildFly nightly builds > easier > > > > Proposal 1 - expose latest bits under the same URL + keep the same root > dir > > name > > URL: > > https://ci.wildfly.org/guestAuth/repository/download/WF_ > Nightly/latest.lastFinished/wildfly-latest-SNAPSHOT.zip > > root dir of the zip: wildfly-latest-SNAPSHOT > > > > Automation would be prepared just once and "work forever". > > > > > > Proposal 2 - keep current zip & root dir name + add txt file with > version > > information > > introduce > > https://ci.wildfly.org/guestAuth/repository/download/WF_ > Nightly/latest.lastFinished/version.txt > > Currently it would contain '11.0.0.Final-SNAPSHOT' > > Example to get version: mvn help:evaluate > -Dexpression=project.version | > > grep -v "^\[" > > > > Automation could consume content of version.txt and construct the > download > > URL + root dir name > > VERSION=`curl > > https://ci.wildfly.org/guestAuth/repository/download/WF_ > Nightly/latest.lastFinished/version.txt` > <https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest.la... > > https://ci.wildfly.org/guestAuth/repository/download/WF_ > Nightly/latest.lastFinished/wildfly-${VERSION}.zip > > root dir of the zip is wildfly-${VERSION} > > > > > > WDYT? > > > > Regards. > > Rostislav > > > > _______________________________________________ > > wildfly-dev mailing list > > wildfly-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

Whatever we decide to do, we need to update WildFly build to do so, not just CI job. probably best thing to add some new profile to dist module that would provide what we need. On Thu, Sep 7, 2017 at 9:57 AM, Emmanuel Hugonnet < ehugonne(a)redhat.com > wrote: Hi, Why not jut have a root dir named latest and put the date (aka resolve the snapshot) in the zip name as I think the date of production is an important information for a nightly build thus it should be part of the artifact name: https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest/wi... Maybe we could also put a "symlink" to it when upload is finished like https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest/wi... Emmanuel _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev