Hi,
what exactly is the current Problem? As far as I understood, the stability of
the build-server seems to be a Problem.
I had similar Problems when Setting up the Flexmojos CI Server. After doing all
sorts of Amazon EC2, MS Azure VM stuff, I did a fallback to a central CI Server
and multiple Agents installed on normal Desktop PCs. So eventually this could
be an Option for us. Setting up Jenkins Agents on our own machines, but having
the central CI Server, so a build is done as soon as any Agent is available.
This way we don't have to rely on the Apache Windows Agent being available.
As far as I know another incubating Project (NPanday - .Net Maven Plugin) has
to rely on this machine too and they are having Major Problems with it.
Mabe private Agents could be a solution. For Flexmojos it certainly helped.
Chris
________________________________________
Von: Maurice Amsellem <maurice.amsel...@systar.com>
Gesendet: Montag, 9. Dezember 2013 09:16
An: dev@flex.apache.org
Betreff: RE: [Builds/Jenkins] Help and advise needed
Thanks Erik for the clarification.
I confirm to you, I had to send the updated swc manually for testing because
the nightly build was down.
Sorry, I didn't follow the thread from the beginning, so I checked the
archives, maybe have missed something.
I can see from the build logs that pixel bender build failed and it seems to be
a path issue.
If that's correct, this is the path I am using on my local build in my
env.properties:
env.PIXELBENDER_HOME=C:\\Program Files (x86)\\Adobe\\Adobe Utilities -
CS5\\Pixel Bender Toolkit 2
I can see that in the build log, the path is:
check-pixelbender-home:
[echo] PIXELBENDER_HOME is C:/Program Files (x86)/Adobe/Adobe Utilities -
CS5/Pixel Bender Toolkit 2
When I run it on my local env, it gives the following:
[echo]
PIXELBENDER_HOME is C:\Program Files (x86)\Adobe\Adobe Utilities - CS5\Pixel
Bender Toolkit 2
So maybe using "\" instead of "/" could fix the issue ?
WDYT?
Maurice
-----Message d'origine-----
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 08:53
À : dev@flex.apache.org
Objet : [Builds/Jenkins] Help and advise needed
Hi,
I'm having some difficulty getting the 'regular' builds on 'build@a.o'
working. For those not subscribed to the builds list, the situation is as
follows:
- there are supposedly 9 admins for the windows1 slave, but only one is
sporadically active. I've requested access to the machine, but got the answer:
"nine is enough." A suggestions there was actually only one, with 8 ghosts fell
on deaf ears. Apparently, it makes no sense to remove old, inactive admins and
add new, active ones
- since the windows1 slave is old, full and overworked, it regularly went down
for days on end. We are one of the few projects that uses the windows slaves,
so I ended up being the guy who always complains the slave is down...
- the one active admin is now working on a second slave (windows2). In itself,
that is a very good thing. However, in his own words, "he feels entitled to use
our builds to experiment." I feel that is wrong, but I know better than to
further aggravate my relation with him by objecting too strongly.
The point of this elaborate introduction is this: somewhere in his experiments
he broke the Windows slaves for our builds. We have not had a successful build
in a week. Normally, not that big a deal, but with the third party IDE people
working on FlexJS and the very active mobile development both relying on
nightly builds, I feel this is not a time to NOT have clean, daily builds of
all our projects...
Anything 'negative' I say on the builds list will certainly make things worse -
my NL temperament and lack of finesse often does not sit well with US
recipients ;-) - so I would ask you to please chime in on the builds list and
that we together get our builds back to functioning.
Thanks!
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
