I like Proposal #1.  

On Sep 6, 2017, at 7:42 AM, Rostislav Svoboda <rsvoboda@redhat.com> wrote:


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`
 root dir of the zip is wildfly-${VERSION}



wildfly-dev mailing list

Jason T. Greene
Chief Architect, JBoss EAP
Red Hat