Nope, that's not it. When the last work was done on the new machine, the builds also stopped working on the ORIGINAL, supposedly untouched, machine.
EdB On Mon, Dec 9, 2013 at 9:49 AM, Maurice Amsellem <maurice.amsel...@systar.com> wrote: > Hi, > > I have checked the jenskins workspace, there is no env.properties in the root > folder, which means all the env variables are set through system properties. > So there is a possibility that they were not set the same in the new machine. > > Makes sense ? > > Maurice > > -----Message d'origine----- > De : Justin Mclean [mailto:jus...@classsoftware.com] > Envoyé : lundi 9 décembre 2013 09:43 > À : dev@flex.apache.org > Objet : Re: [Builds/Jenkins] Help and advise needed > > Hi, > > I'd think it would be unlikely that the Pixel Bender path would of changed as > I would assume the Jenkins job was just copied over from the original windows > machine. A good first set would be to check the setup on both (if we can) and > set that the environment variable are the same on both and then ask if pixel > bender has been installed on the second machine in the same location. > > Thanks, > Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
