[releng] I/N-builds are not being promoted

[eclipse-ocl-bot]

| --- | --- | | Bugzilla Link | 388626 | | Status | CLOSED FIXED | | Importance | P3 normal | | Reported | Sep 02, 2012 11:46 EDT | | Modified | May 27, 2014 09:52 EDT | | Reporter | Ed Willink |

Description

Adolfo: I suspect your promotion script has not been updated for the changed Hudson job names.

[eclipse-ocl-bot]

By Ed Willink on Sep 04, 2012 13:10

Please fix this. I can't do QVTd builds without it.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Sep 04, 2012 13:59

I think I've fixed that. I'll verify it tomorrow looking at the logs which are written in the home directory.

Concerning the last Kepler builds, I've also manually promoted them (This step should also be done by you).

Finally, I've pushed a minor fix to master and maintenance/R4_0 branches concerning the releng/org.eclipse.ocl.releng.buckminster/cron/crontab.txt file

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Ed Willink on Sep 05, 2012 00:57

The N-builds have now promoted thanks, but not I-builds; e.g.

https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-tools-kepler-master/311/artifact/MDT-OCL.downloads/

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Sep 05, 2012 05:23

Ok... The crontab entries only promote the last successful builds. However, we may manually and easily promote an specific build changing the parameter.

In this case, replace

ant -f /shared/jobs/buckminster-mdt-ocl-tools-kepler-master/lastSuccessful/archive/publishroot/publisher.ant -Dbuild.archives=/shared/jobs/buckminster-mdt-ocl-tools-kepler-master/lastSuccessful/archive

by:

ant -f /shared/jobs/buckminster-mdt-ocl-tools-kepler-master/builds/311/archive/publishroot/publisher.ant -Dbuild.archives=/shared/jobs/buckminster-mdt-ocl-tools-kepler-master/builds/311/archive

I've already done that for you and verified that the logs created by the crontab are correct.

Resolving as fixed.

[eclipse-ocl-bot]

By Ed Willink on Sep 05, 2012 06:55

Thanks. Hopefully we won't have a backlog so that promotions get lost again.

[eclipse-ocl-bot]

By Ed Willink on Feb 02, 2013 03:04

I did a Core I-build, and a Tools I and N-build before 19:00 GMT last night.

At 08:00 GMT none of them has appeared on the downloads page.

[eclipse-ocl-bot]

By Ed Willink on Feb 02, 2013 04:46

(In reply to comment #6)

At 08:00 GMT none of them has appeared on the downloads page.

09:44 and they're there. Maybe the polling time should be reduced to 6 hours.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Feb 04, 2013 05:00

... my crontab entries have been changed to make the builds be published earlier.

Resolving as fixed.

[eclipse-ocl-bot]

By Ed Willink on Feb 15, 2013 07:31

It's 12:30 GMT and yesterday's successful tools N-build #373 at 9:40 Eclipse time has not been promoted.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Feb 15, 2013 09:23

Yes. Looking at the log produced:

BUILD FAILED\ /shared/jobs/buckminster-mdt-ocl-core-kepler-master/lastSuccessful/archive/publishroot/publisher.ant:95: The following error occurred while executing this line:\ /shared/jobs/buckminster-mdt-ocl-core-kepler-master/lastSuccessful/archive/publishroot/publisher.ant:119: java.io.IOException: Cannot run program "/usr/local/jre1.6.0_20/bin/java" (in directory "/shared/jobs/buckminste\ r-mdt-ocl-core-kepler-master/lastSuccessful/archive/publishroot"): java.io.IOException: error=2, No such file or directory

I'm going out for some lunch. I'll investigate later.

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Feb 15, 2013 11:57

Well the point is that the build tells in a properties file that the java home is:

/usr/local/jre1.6.0_20

but when ls-ing at build.eclipse.org such a java directory doesn't exist.

This property is not manually set, it's supposed to use the java home which is used during the build. The only explanation I have for this is that the job build is physically executed in a machine different to build.eclipse.org. The job was configured to run in slave-4. I've just run a new build in fastlane/master config to see what is the result of such a property.

Giving that the promotion is done always in build.eclipse.org and the build execution could be done at any different internal server, I guess that the path to the java.home should be set in a different manner.

One solution could be hard-coding the path of the java home of the build.eclipse.org server. I don't like that this one.

I've also noticed the following piece of code in the promoter.ant file:

    <condition property="java.executable" value="${saved.java.home}/bin/java" else="java">\
        <isset property="saved.java.home" />\
    </condition>\
    \

Perhaps no setting the java.home, should simply the use of "java" command, which should make all work again using the default java (whichever it's the default version). I'll try that.

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Ed Willink on Feb 15, 2013 12:06

Certainly needs to be slave independent.

I changed the build from "build2" to "slave4" to overcome a problem that the transformation for documentation generation was failing with a bad file name (on "slave2").

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Feb 15, 2013 12:17

With fastlane now:

java.home=/opt/public/common/sun-jdk1.6.0_21_x64/jre

Promotion worked like a charm.

I've just kicked a build with the aforementioned solution.

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Feb 18, 2013 05:46

In spite of removing the java.home property creation done by the promoter.ant file, the property is still there... I thought I had also wiped out the workspace, but the same unexpected result is obtained [1].

I've wiped again the build workspace and kicked out a new build on slave-4. Let's see what happens now.

P.S: Have I ever said that releng is hateful ? :P

[1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-tools-kepler-master/382/artifact/promote.properties/*view*/

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Feb 18, 2013 06:43

Well, it looks like all was fine now...

The promotion worked with a build done at slave-4.

Resolving as fixed.

[eclipse-ocl-bot]

By Ed Willink on May 27, 2014 09:44

CLOSED after more than a year in RESOLVED state.

[eclipse-ocl-bot]

By Ed Willink on May 27, 2014 09:52

and CLOSE