So, we could drop BUILD_NUMBER, since it's simply causing churn in
target platform definitions and not really providing value here.
Two ways to do this...
A) change this to remove BUILD_NUMBER:
https://github.com/jbosstools/jbosstools-locus/blob/master/pom.xml#L214
B) change jobs to not use the -Phudson profile, which does nothing here
except to add BUILD_NUMBER.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
Thoughts? I'd be for removing the profile AND updating the job. Seems
more complete.
On 05/05/2015 03:27 PM, Mickael Istria wrote:
On 05/05/2015 09:23 PM, Nick Boldt wrote:
> If so, do we need to change the builds so they omit the timestamp and
> build number in their qualifiers, and just use 1.3.0.Final instead of
> 1.3.0.Final-v20150430-1349-B77?
For Locus, timestamp is already a last-modification timestamp. Only the
BUILD_NUMBER is moving between different builds.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com