[wildfly-dev] WildFly nightly builds

[Rostislav Svoboda]

Hi.

I prepared https://github.com/rsvoboda/wildfly/commit/7c48c50f8b054c4f7e06a78de6bea7f5292171eb to fix dist module so it can leverage already existing 'jboss.as.release.version' property.

mvn clean install -DskipTests -Denforcer.skip=true -Dcheckstyle.skip=true -Djboss.as.release.version=latest -Prelease 
...
ls dist/target | grep wildfly
  wildfly-latest
  wildfly-latest.jar
  wildfly-latest-src.tar.gz
  wildfly-latest-src.zip
  wildfly-latest.tar.gz
  wildfly-latest.zip

So WF_Nightly job would just use '-Djboss.as.release.version=latest' and we would have Option #1 solved.


Can I proceed with PR? Is it something I should propose also for product branch ?


Rostislav

----- Original Message -----
> 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 at 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/wildfly-nightly-201709070001.zip
> 
> Maybe we could also put a "symlink" to it when upload is finished like
> https://ci.wildfly.org/guestAuth/repository/download/WF_Nightly/latest/wildfly-nightly-latest.zip
> 
> Emmanuel
> 
> 
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> 
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev