Dear developers, The main "Saros" job on Jenkins has been unstable for 4 builds. I understand that this is (at least partially) due to a change to the build scripts.
This is to make things clear to everyone who is not familiar with our setup (and some of its history) -- in case you are not interested, just jump to the last paragraph: * Most of our Jenkins jobs rely on external scripts, which are not stored in the job's configuration, but in separate files. * These script files are stored under "/var/lib/jenkins/scripts". * This includes an Ant file "build.xml". Besides others, this file is used by the job "Saros-Gerrit" which uses it to *overwrite* the project-internal build.xml files of "de.fu_berlin.inf.nebula", "de.fu_berlin.inf.dpp", and "de.fu_berlin.inf.dpp.whiteboard". * The job "Saros", however, does *not* use the Jenkins version of the build file, but the original one which resides under "de.fu_berlin.inf.dpp/" and can be seen in everybody's Eclipse project. * Until some months ago, these files (under /var/lib/jenkins/scripts) weren't under version control: You modified one of the scripts, and the deed was done. No one knew "who/what/when/why". I don't know how this weird setup evolved, but that's how things were some months ago. To better the situation I put the Jenkins scripts under version control; the rest of the setup remained the same. To alter the used build scripts, you need to clone the respective Git repository [1]. The procedure for submitting patches is the same as for the "normal" Saros source code repository. As soon as a patch is merged, a special Jenkins job takes care of deploying the new scripts [2]. Please note that this is still no perfect setup! It just resolved the issue of unnoticed changes to Jenkins's build scripts. A cleaner solution would use the project-internal build.xml consequently. So every project that needs a build.xml should provide one. The goal is to remove the build.xml files (yes, there is more than one) from the saros-ci-scripts repository. This brings me back to the original topic of this mail: The unstable Saros builds. @Stefan: I did not take a deeper look at the failures. I assume you know what happened here. So, could you enlighten us and say what needs to be done in order to resolve this? Best Regards, Franz [1] git clone http://saros-build.imp.fu-berlin.de/gerrit/saros-ci-scripts (there is no access via web browser) [2] http://saros-build.imp.fu-berlin.de/jenkins/job/CI-Scripts-Deploy/ ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
