Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Private Hudson

Hi Ed,

The buckminster section in the job configuration has a combo box to select the level of logging.

If you are happy with a new approach which works for you, feel free to adopt it.

On Mon, Nov 11, 2013 at 8:57 PM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:

Turns out that invoking an extra target from Buckminster is a bad idea. None of the archiving has been done and ... none of the debug is visible, which is hard when the underlying protections are wrong.

Just adding

/opt/public/common/apache-ant-1.8.1/bin/ant -f publishroot/publisher.ant -Dbuild.archives=${WORKSPACE}

to the post script seems to work (at least for QVTd).

Requiring manual addition of the repos seems a desirable protection against test builds and accidents.


On 04/11/2013 18:53, Adolfo Sanchez-Barbudo Herrera wrote:
On 02/11/2013 10:42, Ed Willink wrote:

Adolfo: Is adding the promotion a 'trivial' move so that promoter.ant
gets invoked from buckminster.cspec?

It's not hard invoking ant tasks from buckminster. The point is that, for example, S-builds are not currently and completely promoted in their own so providing that all cases are not automated, and being the S-build the normal case when we want instant promotion, I think that logging to the servers to kick the promotion is not so bad for all cases.

I guess that trying to improve the scripts to do the complete the S-build promotion could see beneficial.

_______________________________________________ mailing list

No virus found in this message.
Checked by AVG -
Version: 2014.0.4158 / Virus Database: 3629/6811 - Release Date: 11/05/13

_______________________________________________ mailing list

Back to the top