search

eclipse / amalgam

Eclipse Public License 1.0
1 stars 4 forks source link

Since the migration to Jenkins, the build timestamp is replaced by the build number #131

Open eclipse-amalgam-bot opened 3 years ago

eclipse-amalgam-bot commented 3 years ago

To set the build timestamp of published version, the publish-nightly.sh script uses BUILD_ID variable, but in Jenkins this variable returns the number, not the build timestamp (see https://issues.jenkins-ci.org/browse/JENKINS-26520).

So now new published version have name like 1.9.0-N11 instead of 1.9.0-N20171004-042126 (see http://download.eclipse.org/modeling/amalgam/updates/nightly/?d).

🆔 ECLIPSE-525992 👷 jeremy.aubry 📅 2017-10-13

eclipse-amalgam-bot commented 3 years ago

frederic.gurr commented on 2017-10-13

Thanks for the heads-up. As mentioned in the comments on the linked bug, there are several workarounds available, like using a Groovy script or the ZenTimestamp plugin (https://wiki.jenkins.io/display/JENKINS/ZenTimestamp+Plugin).

Let us know, if you want us to install an additional plugin on your JIPP.

nick.boldt commented on 2018-02-02

An easier workaround is to do this:

BUILDTIMESTAMP=`date -u +%Y-%m-%d%H-%M-%S`

then use that value in scripts.

For example, you could run a bash script to echo that into a properties file, then load the properties file for all your downstream operations.

But if you only need the variable in publish-nightly.sh, just define it there and you're done. :)

(This is what we had to do a year or two ago when updating Jenkins versions for JBoss Tools builds.)

mikaël.barbero commented on 2018-03-07

Closing as NOT_ECLIPSE as this is a Jenkins specific behavior and workarounds exist. Feel free to open a new bug to request installation of ZnTimestamp if you ever want it.

pierre-charles.david commented on 2018-03-08

FWIW, we've installed ZenTimestamp on the Sirius JIPP, and it works fine.

cedric.brun commented on 2018-03-12

Well, I'd like to keep this open as long as it's not fixed in Amalgam's releng.

mikaël.barbero commented on 2018-03-12

My bad. I overlooked the component to which this bug is assigned to (I though it was a CI-Jenkins one).

pierre-charles.david commented on 2018-03-12

I submitted [ECLIPSE-532310 to obtain the administration rights on the Amalgam JIPP, so that I can apply the same fix as the one we did on the Sirius side.](https://github.com/search?q=ECLIPSE-532310 to obtain the administration rights on the Amalgam JIPP, so that I can apply the same fix as the one we did on the Sirius side.&type=Issues)