Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dash-dev] Lastsuccessful Artifacts not being saved
Nick Boldt and I both recommend this way going forward. It is safer especially since in the not to distant future we'll have the capability to build on not just one machine. By using the URL the Master server keeps track of where the file is actually stored (which may or may not be on the Master server itself). 

Dave

Nicolas Bros wrote:
Since the last Hudson update, symlinks have stopped working again (bug 292629 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=292629>). David Carver suggested here on Dash-Dev to use the Hudson REST API to access the lastSuccessfulBuild. 
What I've done for the MoDisco build is change the promote bash script:

echo "$DATE: getting last successful build" >> $logFile
mkdir -p $BUILD_LOC
rm -f $BUILD_LOC/build.zip
rm -rf $BUILD_LOC/build
cd $BUILD_LOC
wget --no-check-certificate "https://build.eclipse.org/hudson/job/cbi-modisco-nightly/lastSuccessfulBuild/artifact/build/*zip*/build.zip"; if [ ! -f build.zip ]; then echo "ERROR:build.zip (from Hudson) not found" >> $logFile; exit -2; fi 
unzip build.zip
echo "$DATE: publishing nightly build ..." >> $logFile
mkdir -p $PROMO_LOGS_DIR
$ANT -f $RELENG_DIR/promote.xml -Dpromote.properties=$RELENG_DIR/promote-N.properties 2>/dev/null 1> $PROMO_LOGS_DIR/cbi-modisco-nightly-promo-${DATE}.txt
And change the promote-N.properties so that it looks for the lastSuccessfulBuild in the "$BUILD_LOC/build" directory instead of in "/opt/users/hudsonbuild/hudson/jobs/...".
On Wed, Dec 16, 2009 at 9:56 AM, Miles Parker <milesparker@xxxxxxxxx <mailto:milesparker@xxxxxxxxx>> wrote: 


    Hi all,

    After Dave and I spent some time trying to get findbugs working
    with cb-amp-nightly and discovering the svn bug prevventing that,
    I've been struggling to get back to my last good build
    configuration. I'm pretty sure that I've got the build.properties
    and build.xml back to the right place and everything is building
    correctly into the N2009... dirs, but I'm not getting the files to
    where they need to be to be promoted.

    ls /opt/users/hudsonbuild/.hudson/jobs/cbi-amp-nightly/

    Doesn't have a lastSuccessful dir as specified in my boiler-plate
    promote-N.properties.

    The only thing I can't rollback is the config so I've tried to
    reconstruct that but perhaps there is something messed up there.
    Is there an example configuration out there that we can look at?
    I'm wondering if the issue might be here:

    _Archive the artifacts_

    I have:

    build/?20*/**


    Other settings..


    Params has EXTRA_FLAGS -forceContextQualifier -fetchTag HEAD

    Execute Shell:
    # configuration export PROJRELENGROOT='-projRelengRoot
    :pserver:anonymous@xxxxxxxxxxxxxxx:/cvsroot/modeling' export
    PROJRELENGPATH='-projRelengPath
    org.eclipse.amp/releng/org.eclipse.amp.releng' # parameters
    #export SNAPSHOT="true" # run the build .
    /opt/public/cbi/build/org.eclipse.dash.common.releng/hudson/run.sh


    Any ideas?

    thanks,

    Miles


    _______________________________________________
    dash-dev mailing list
    dash-dev@xxxxxxxxxxx <mailto:dash-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/mailman/listinfo/dash-dev




--
Nicolas Bros
R&D
tel: 06 75 09 19 88
nbros@xxxxxxxxxxxxxxxx <mailto:nbros@xxxxxxxxxxxxxxxx>
nbros.mia@xxxxxxxxx <mailto:nbros.mia@xxxxxxxxx>
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
http://www.mia-software.com
.: model driven agility :.
------------------------------------------------------------------------

_______________________________________________
dash-dev mailing list
dash-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dash-dev

Back to the top