Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [emf-dev] Re: Promotion for QTV builds

No, Hudson can't promote bits in the same way that Hudson can't tag&release your bits.

But you can *easily* set up a cron job to do scheduled promotes using the promote.xml script I provide and sample properties files. It's a no-brainer to set up and schedule. And it runs as *you*, rather than some generic/shared/unsafe user.

Example & instructions here:

You can either call the common.releng/promote.xml directly*, or copy it into your .releng project. Or copy the simpler wrapper script that's in the gef.releng project. Options abound.

* If you try this simplest approach, please comment in so I know it actually works. It should, but it's as yet untested.

Anthony Hunter wrote:
Hi Nick, This means that Athena does not have a promote job for Hudson?

Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager: Eclipse Open Source Components
IBM Rational Software: Aurora / GEF / GMF / Modeling Tools
Phone: 613-270-4613

Inactive hide details for Nick Boldt ---2009/08/27 12:48:11 AM---I have disabled (not deleted) the qvt 3-in-1 build and createdNick Boldt ---2009/08/27 12:48:11 AM---I have disabled (not deleted) the qvt 3-in-1 build and created 3 new

Nick Boldt <nickboldt@xxxxxxxxx>

"Kolb, Bernd" <bernd.kolb@xxxxxxx>, Eclipse Modelling Framework <emf-dev@xxxxxxxxxxx>

2009/08/27 12:48 AM

[emf-dev] Re: Promotion for QTV builds


I have disabled (not deleted) the qvt 3-in-1 build and created 3 new
builds for q, v, and t.

You may want to review the permissions and email contacts for each build.

Query is spinning now; when done it should kick validation and
transaction (in parallel); when validation is done, it too should prompt
a transaction build. Thus any upstream changes should cause downstream

In order to do three promotes, you will need three entries in your
crontab. SSH to, and type `crontab -e` to edit your
crontab. Enter items such as this for each build / type you want to
promote on a schedule:

40 15 * * * /opt/public/common/apache-ant-1.7.1/bin/ant -f
 2>/dev/null 1> ~/promo_logs/cbi-ve-1.4-nightly-Ganymede-promo.txt

In addition to nightlies, you can manually kick an I build (by changing
the BUILDTYPE to I), or you can have me create you three more builds (of
default type I) which can run weekly, a little before a scheduled promote:

00 16 * * 2 /opt/public/common/apache-ant-1.7.1/bin/ant -f
 2>/dev/null 1> ~/promo_logs/cbi-ve-1.4-integration-Ganymede-promo.txt

BTW, Transaction had a test failure, perhaps related to the changed path
structure on (single build vs. composite build).


Kolb, Bernd wrote:
 > It might be the best option, yes.
 > Bernd
 > -----Original Message-----
 > From: Nick Boldt [mailto:nickboldt@xxxxxxxxx]
 > Sent: Donnerstag, 20. August 2009 16:31
 > To: Kolb, Bernd
 > Subject: Re: Promotion for QTV builds
 > Should we split you into three builds that run in series instead?
 > N
 > On 8/20/09, Kolb, Bernd <bernd.kolb@xxxxxxx> wrote:
 >> Hi Nick
 >> Boris and myself just tried to get the promotion for the qtv builds
 >> running. However there seems to be a problem as this build actually
 >> builds three projects.
 >> Normally I would expect to
 >> /opt/users/hudsonbuild/.hudson/jobs/cbi-emf-qvt-1.4/lastSuccessful
 >> contain 3 subdirs (one for q one for v and one for t) or at least an
 >> archive folder. This however is not the case. The next problem is that
 >> we need to do three promotions, but I guess this could be fixed in the
 >> promote.xml, right?
 >> Any help is as always appreciated :-)
 >> Cheers,
 >> Bernd

Nick Boldt ::
Release Engineer :: Eclipse Modeling & Dash Athena
emf-dev mailing list


emf-dev mailing list

Nick Boldt ::
Release Engineer :: Eclipse Modeling & Dash Athena

Back to the top