That's what I thought also, so I tried on my own Jenkins but it didn't work :-(
Maurice
-Message d'origine-
De : Mark Kessler [mailto:kesslerconsult...@gmail.com]
Envoyé : mercredi 11 décembre 2013 10:48
À : Dev@Flex
Objet : Re: [Builds/Jenkins] Help and advise needed
C
gt; Envoyé : mercredi 11 décembre 2013 04:02
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> To avoid the window, run the service under a different user, e.g.
> "System" instead of a specific user or vice versa.
>
> Peter
>
> On
[mailto:p.ginnebe...@gmail.com]
Envoyé : mercredi 11 décembre 2013 04:02
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
To avoid the window, run the service under a different user, e.g.
"System" instead of a specific user or vice versa.
Peter
On 10/12/2013 2
To avoid the window, run the service under a different user, e.g.
"System" instead of a specific user or vice versa.
Peter
On 10/12/2013 22:55, Maurice Amsellem wrote:
According to jenkins gui, there are 4 ways of starting the slave :
- Java web start (JNLP)
- command line from master
- via SS
Thanks for your support and have a good day.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mercredi 11 décembre 2013 00:14
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Om sort of asked already. We'll see how th
o interact with desktop".
>That may solve the problem, but not sure yet...
>
>Can you ask the infra ?
>
>Maurice
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : mardi 10 décembre 2013 23:54
>À : dev@flex.apache.org
>Objet
.amsel...@systar.com]
Envoyé : mardi 10 décembre 2013 23:58
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
One possible fix (I couldn't check it yet ) is to open "Jenkins slave" Windows
service, and check "Allow to interact with desktop".
That ma
> De : Alex Harui [mailto:aha...@adobe.com]
> Envoyé : mardi 10 décembre 2013 23:54
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> Awesome. You are the detective of the day. Thanks for staying with it.
>
> -Alex
>
> On
ilto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 23:54
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Awesome. You are the detective of the day. Thanks for staying with it.
-Alex
On 12/10/13 2:52 PM, "Maurice Amsellem"
wrote:
>Got it! Here is
m [mailto:maurice.amsel...@systar.com]
>Envoyé : mardi 10 décembre 2013 23:41
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Besides, do you know (or can you ask infra) if there are other Apache
>projects that require a window, and what are their ru
di 10 décembre 2013 23:52
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Got it! Here is what happened:
https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service#InstallingJenkinsasaWindowsservice-InstallSlaveasaWindowsservice%28require.NET2.0framework%29
as well, and does not get a window.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 10 décembre 2013 23:41
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Besides, do you know (or can you ask infr
: dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Also, could you ask if jenkins is running on a locked session, or completely
out of session.
The slave window can only work when in session or with session locked, but not
"out of session".
While the other meth
gt;I am trying to do the same now and let you know.
>
>-Message d'origine-----
>De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 10 décembre
>2013 23:22 À : dev@flex.apache.org Objet : Re: [Builds/Jenkins] Help
>and advise needed
>
>Saw it. Have we asked him if the
essage d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : mardi 10 décembre 2013 23:22
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Saw it. Have we asked him if the Flex build is running in a slave and
>t
laves,
so that would explain why it does not get a window.
I am trying to do the same now and let you know.
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 23:22
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
S
,
> >> Om
> >>
> >>
> >>
> >>
> >>>
> >>> On 12/10/13 1:55 PM, "Maurice Amsellem"
> >>> wrote:
> >>>
> >>> >According to jenkins gui, there are 4 ways of starting the slave :
> >>>
wrote:
>>>
>>> >According to jenkins gui, there are 4 ways of starting the slave :
>>> >- Java web start (JNLP)
>>> >- command line from master
>>> >- via SSH on Unix machines
>>> >- as a Windows Service.
>>> >
>>>
- command line from master
>> >- via SSH on Unix machines
>> >- as a Windows Service.
>> >
>> >I am using JNLP, but maybe the other launch methods don't get a window.
>> >I am going to try "as a Windows Service".
>> >
>> >Is
gt; >> [exec]
> >> [exec] OpenGL version as determined by Extensionator...
> >> [exec] OpenGL Version 3.0
> >> [exec] Has NPOT support: TRUE
> >> [exec] Has Framebuffer Obeject Extension support: TRUE
> >> [exec] Completed
he slave is launched on b.a.o?
>
>Maurice
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : mardi 10 décembre 2013 22:46
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>InterestingŠ Is there a way to configu
t;.
Is there a way to know how the slave is launched on b.a.o?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 22:46
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
InterestingŠ Is there a way to con
t; [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>> [exec] ERROR: AIF Internal exception
>> [exec] Result: 1
>>
>>So I am getting the same error.
>>
>>Om says "master" does not get a window, so t
d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 22:40
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Nice. Thanks for sticking with it.
On 12/10/13 1:21 PM, "Maurice Amsellem"
wrote:
>So I just installed
run the job on it.
>
>Maurice
>
>-Message d'origine-
>De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
>Envoyé : mardi 10 décembre 2013 22:07
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>It was from the command
be normal.
I am trying now to create a slave node and run the job on it.
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : mardi 10 décembre 2013 22:07
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
It was f
:49
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Maurice,
When you ran it on your machine, was it on Cygwin or from Jenkins?
I think there is a difference. On Jenkins, the main executor (master) does not
get a window. Only slave executors are configured to get a w
do you want to perform more tests ?
> >
> >Maurice
> >
> >-Message d'origine-
> >De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
> >Envoyé : mardi 10 décembre 2013 20:37
> >À : dev@flex.apache.org
> >Objet : RE: [Builds/Jenkins]
an issue with
>accessing the GPU.
>
>Shall I un-commit the change now, or do you want to perform more tests ?
>
>Maurice
>
>-Message d'origine-
>De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
>Envoyé : mardi 10 décembre 2013 20:37
>À : dev@flex.apache
20:37
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
I don't have a Mac with ApacheFlex SDK for testing.
Can you try on your side, please ?
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mardi 10 décembre 2013 20:34
À : dev@
I don't have a Mac with ApacheFlex SDK for testing.
Can you try on your side, please ?
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 20:34
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Won't
x27;t hurt ;-)
>
>Maurice
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : mardi 10 décembre 2013 20:29
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>I think I'll wait to see how Gavin respond
3 20:29
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
I think I'll wait to see how Gavin responds to Erik's latest request.
BTW, thanks for finding out about the tool.
-Alex
On 12/10/13 11:27 AM, "Maurice Amsellem"
wrote:
>Sure, if you c
lex Harui [mailto:aha...@adobe.com]
>Envoyé : mardi 10 décembre 2013 20:26
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Might be simpler just to ask Gavin to run the tool?
>
>On 12/10/13 11:12 AM, "Maurice Amsellem"
>wrote:
>
>&g
Sure, if you can ask him.
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 20:26
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Might be simpler just to ask Gavin to run the tool?
On 12/10/13 11:
;WDYT ?
>
>Maurice
>
>-Message d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : mardi 10 décembre 2013 18:15
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>I don't think we actually know the cause of the p
r test!
> Return code: 7
>
> Maybe we could temporarily modify the build to run this utility and show
> the output on the b.a.o vm.
>
> WDYT ?
>
> Maurice
>
> -----Message d'origine-
> De : Alex Harui [mailto:aha...@adobe.com]
> Envoyé : mardi 10 décembre 2
aybe we could temporarily modify the build to run this utility and show the
output on the b.a.o vm.
WDYT ?
Maurice
-Message d'origine-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 18:15
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
;> > wrote:
>>>> >
>>>> >>I understand that.
>>>> >>
>>>> >>Actually, my "understanding" on this issue was that pixel bender
>>>> compiler
>>>> >>required some sort of hardware configuration (Op
gt;>required some sort of hardware configuration (OpenGL, etc...) that
>>>were
>>> >>not present on the b.a.o. new Windows Jenkins slave node, so that's
>>>why
>>> >>the build was failing, and the Apache Infra was reluctant to let us
>>&
let us
>> >>modify anything, or even access the VM ourselves.
>> >>So that's why I was proposing a "software only" solution.
>> >>
>> >>Now, it seems from what Om is saying that we can set up and use our own
>> >>Jenkins
>>
> >>Now, it seems from what Om is saying that we can set up and use our own
> >>Jenkins slave node VM.
> >>
> >>That, of course, is much preferable...
> >>
> >>Maurice
> >>
> >>-Message d'origine-
>
referable...
>>
>>Maurice
>>
>>-Message d'origine-
>>De : Erik de Bruin [mailto:e...@ixsoftware.nl]
>>Envoyé : mardi 10 décembre 2013 10:44
>>À : dev@flex.apache.org
>>Objet : Re: [Builds/Jenkins] Help and advise needed
>>
>>
slave node VM.
>
>That, of course, is much preferable...
>
>Maurice
>
>-Message d'origine-
>De : Erik de Bruin [mailto:e...@ixsoftware.nl]
>Envoyé : mardi 10 décembre 2013 10:44
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : mardi 10 décembre 2013 10:44
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Maurice,
Your help is very much appreciated!
I put "legal" in quotes, the issue is not really
;
> ;-)
>
> Regards,
>
> Maurice
>
> -Message d'origine-
> De : Erik de Bruin [mailto:e...@ixsoftware.nl]
> Envoyé : mardi 10 décembre 2013 09:12
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> In addition t
: mardi 10 décembre 2013 09:12
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
In addition to the various "legal" issues with binaries in the repo, we'd be
masking the cause of this failure. In order to prevent further deterioration of
the build process, we need to fi
jet : Re: [Builds/Jenkins] Help and advise needed
On Dec 10, 2013 12:13 AM, "Erik de Bruin" wrote:
>
> In addition to the various "legal" issues with binaries in the repo,
> we'd be masking the cause of this failure. In order to prevent further
> deterioratio
On Dec 10, 2013 12:42 AM, "Erik de Bruin" wrote:
>
> I would suggest that if you have a functioning VM, we use it to run
> the builds that are currently on 'builds@a.o'. That is just too high
> maintenance (I spend about 2 hrs a week on the various issues there).
>
> EdB
Okay, will do.
But still
I would suggest that if you have a functioning VM, we use it to run
the builds that are currently on 'builds@a.o'. That is just too high
maintenance (I spend about 2 hrs a week on the various issues there).
EdB
On Tue, Dec 10, 2013 at 9:36 AM, OmPrakash Muppirala
wrote:
> On Dec 9, 2013 11:31
On Dec 9, 2013 11:31 PM, "Alex Harui" wrote:
>
>
>
> On 12/9/13 11:12 PM, "Erik de Bruin" wrote:
>
> >Remember, Gavin (builds@a.o) claim he changed nothing on the slave
> >that's now failing. I'm sure we didn't change anything on the Jenkins
> >job that is now failing. It isn't something in the S
On Dec 10, 2013 12:13 AM, "Erik de Bruin" wrote:
>
> In addition to the various "legal" issues with binaries in the repo,
> we'd be masking the cause of this failure. In order to prevent further
> deterioration of the build process, we need to figure out what went
> wrong and fix it.
>
> EdB
>
> P
In addition to the various "legal" issues with binaries in the repo,
we'd be masking the cause of this failure. In order to prevent further
deterioration of the build process, we need to figure out what went
wrong and fix it.
EdB
PS. Thanks for leaving the keyboard on the Mustella VM set to FR...
> someone who does use the pbj's will grab the nightly and complain.
I don't understand.
Why would someone complain if the pbj's are in the nightly?
[From the other emai]
>Apache repos aren't supposed to contain compiled code. The pbj files were
>removed during the initial release audit.
>I d
ssage d'origine-
>De : Alex Harui [mailto:aha...@adobe.com]
>Envoyé : mardi 10 décembre 2013 08:33
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>We could take the pixel bender compilation out of the jenkins builds, but
>not our release pa
-
De : Alex Harui [mailto:aha...@adobe.com]
Envoyé : mardi 10 décembre 2013 08:33
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
We could take the pixel bender compilation out of the jenkins builds, but not
our release package. It must contain the source and i
>Envoyé : mardi 10 décembre 2013 08:27
>À : dev@flex.apache.org
>Objet : RE: [Builds/Jenkins] Help and advise needed
>
>Simple yet radical proposition:
>
>The pbk shaders didn't evolve much, and the compiled pbj are already
>committed to the repo (although git history says they
e" from the build ?
If it ever happens to change, we could then recompile the pbj and recommit.
What do you think ?
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl] Envoyé : mardi 10 décembre 2013
08:12 À : dev@flex.apache.org Objet : Re: [Buil
lto:e...@ixsoftware.nl]
>Envoyé : mardi 10 décembre 2013 08:12
>À : dev@flex.apache.org
>Objet : Re: [Builds/Jenkins] Help and advise needed
>
>Remember, Gavin (builds@a.o) claim he changed nothing on the slave that's
>now failing. I'm sure we didn't change anyth
On 12/9/13 11:12 PM, "Erik de Bruin" wrote:
>Remember, Gavin (builds@a.o) claim he changed nothing on the slave
>that's now failing. I'm sure we didn't change anything on the Jenkins
>job that is now failing. It isn't something in the SDK that's causing
>this, lot's of people and the Mustella V
hange, we could then recompile the pbj and recommit.
What do you think ?
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : mardi 10 décembre 2013 08:12
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
Remember, Gavin (bui
Remember, Gavin (builds@a.o) claim he changed nothing on the slave
that's now failing. I'm sure we didn't change anything on the Jenkins
job that is now failing. It isn't something in the SDK that's causing
this, lot's of people and the Mustella VM are building that regularly.
Anyway: I'm not fami
I tried to reproduce the failure on my machine but couldn't. I tried
different path statements, removing the aif_* dlls, and changing execute
rights on those dlls. I did find that the string "Internal Exception" is
in the aif_core.dll.
Not sure what to do next, but now I'm thinking: maybe nobody
On Dec 9, 2013 10:56 AM, "Alex Harui" wrote:
>
> Ah, that thread looked like it was a year old. Did you work around it or
> just stop working on it?
I just stopped working on it because I hit a dead end. I was clueless as
to how to fix it.
>
> Other than checking the path, I don't have any ide
Ah, that thread looked like it was a year old. Did you work around it or
just stop working on it?
Other than checking the path, I don't have any ideas to try at the moment.
On your Azure VM, if you manually launch the compiler from Windows command
prompt you get this error, right?
-Alex
On 12/
On Dec 9, 2013 10:35 AM, "Alex Harui" wrote:
>
> We keep hitting this error, but the mail archives do not document how we
> fix it. This time, we should write down the answer. Om's hit it, Justin
> hit it, I think I had it once. The emails seem to indicate that it ispath
> related, but the buil
We keep hitting this error, but the mail archives do not document how we
fix it. This time, we should write down the answer. Om's hit it, Justin
hit it, I think I had it once. The emails seem to indicate that it ispath
related, but the build.xml does at least check if the pbutil.exe exists
and i
BTW, the test with unchecking "Interact with desktop" didn't give any result
(didn't fail).
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 9 décembre 2013 12:12
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins]
A session log-off was apparently enough.
Ouf !
Maurice
-Message d'origine-
De : Kessler CTR Mark J [mailto:mark.kessler@usmc.mil]
Envoyé : lundi 9 décembre 2013 12:08
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
Sounds like a good idea to re
Sounds like a good idea to restart the instance. Then run his start scripts.
-Mark
-Original Message-
From: Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Sent: Monday, December 09, 2013 5:59 AM
To: dev@flex.apache.org
Subject: RE: [Builds/Jenkins] Help and advise needed
I back
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
The slave agents should load automatically upon restart... If not, there are
shortcuts to start it with all over the place ;-)
EdB
On Mon, Dec 9, 2013 at 11:03 AM, Maurice Amsellem
wrote:
> I have set up the samp
sage d'origine-
> De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
> Envoyé : lundi 9 décembre 2013 10:30
> À : dev@flex.apache.org
> Objet : RE: [Builds/Jenkins] Help and advise needed
>
>>I don't mind experiments on the Mustella VM, but remember we don'
it need to be launched
manually?
Maurice
-Message d'origine-
De : Maurice Amsellem [mailto:maurice.amsel...@systar.com]
Envoyé : lundi 9 décembre 2013 10:30
À : dev@flex.apache.org
Objet : RE: [Builds/Jenkins] Help and advise needed
>I don't mind experiments on the Muste
Exactly.
Usually CI is just for checking. But until the Installer can create a
working FlexJS SDK, the people wanting to play with it, like the nice
folks from FDK, mostly have to rely on the nightly builds. The
certainly can build an SDK themselves, but I don't think they need to
waste their time
nl]
Envoyé : lundi 9 décembre 2013 10:23
À : dev@flex.apache.org
Objet : Re: [Builds/Jenkins] Help and advise needed
I don't mind experiments on the Mustella VM, but remember we don't have a
proper backup in place.
Our nr. 1 priority now, IMHO, must be to have reliable nightly builds in pl
Hi,
> Our nr. 1 priority now, IMHO, must be to have reliable nightly builds
> in place, so any contributors/third parties can get the Flex and
> FlexJS SDKs and have the latest and greatest.
For development and testing purposes only of course :-) If it's not an
officially voted on release then
ice
>
> -Message d'origine-
> De : Erik de Bruin [mailto:e...@ixsoftware.nl]
> Envoyé : lundi 9 décembre 2013 10:01
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> Om told me earlier he had the same error when setting up his local
h
different settings, see if we can reproduce the "AIF error".
Of course, that would temporarily break the mustella tests...
Maurice
-Message d'origine-
De : Erik de Bruin [mailto:e...@ixsoftware.nl]
Envoyé : lundi 9 décembre 2013 10:01
À : dev@flex.apache.org
Objet : R
Bruin [mailto:e...@ixsoftware.nl]
> Envoyé : lundi 9 décembre 2013 09:52
> À : dev@flex.apache.org
> Objet : Re: [Builds/Jenkins] Help and advise needed
>
> Nope, that's not it. When the last work was done on the new machine, the
> builds also stopped working on the ORIGINAL
> -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
o: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
I already did... twice.
EdB
On Mon, Dec 9, 2013 at 9:49 AM, Justin Mclean wrote:
> Hi,
>
> Just checked and here's the config:
> AIR_HOME=${WORKSPACE}/air/AIR Integration Kit
> FLASHPLAYER_DEBUGGER=C\:/Program\ Files\
> (x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
> PLAYERGLOBAL_HOME=${WORKS
--
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 c
Hi,
Just checked and here's the config:
AIR_HOME=${WORKSPACE}/air/AIR Integration Kit
FLASHPLAYER_DEBUGGER=C\:/Program\ Files\
(x86)/Adobe/flashplayer_11_sa_debug_32bit.exe
PLAYERGLOBAL_HOME=${WORKSPACE}/lib/player
PIXELBENDER_HOME=C\:/Program\ Files\ (x86)/Adobe/Adobe Utilities\ -\ CS5/Pixel\
B
Yes, my thoughts exactly. Two things: we cannot change or even check
the settings of the machines themselves, we only have access through
the Jenkins web interface. And the most worrying thing: the builds
also don't work anymore on the original (windows1) machine.
EdB
On Mon, Dec 9, 2013 at 9:4
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 an
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 ben
87 matches
Mail list logo
