flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maurice Amsellem <maurice.amsel...@systar.com>
Subject RE: PixelBender and Builds.a.o
Date Wed, 11 Dec 2013 19:27:27 GMT
I am almost sure that he actually clicked on the "Install as service" menu in the Jenkins
slave (startup command line of Jenkins slave match the "service" pattern, not the JNLP pattern).
That would make sense for them, because they certainly prefer that the Jenkins process could
be run out of session, which is not the case with JNLP (the window is closed when you close
the session).


-----Message d'origine-----
De : Erik de Bruin [mailto:erik@ixsoftware.nl] 
Envoyé : mercredi 11 décembre 2013 20:21
À : dev@flex.apache.org
Objet : Re: PixelBender and Builds.a.o

Your solution sounds good, and I like the "bring Linux up to par" part.

What I still can't figure out is why the builds stopped working suddenly a week ago, with
Gavin maintaining he never changed a thing.
Well, I guess it doesn't really matter. I hope Om gets his VM online soon, so we can leave
build@a.o behind us and maintain all aspects of our CI ourselves.


On Wed, Dec 11, 2013 at 8:09 PM, Alex Harui <aharui@adobe.com> wrote:
> Thanks to Maurice, we have a pretty good idea of why Jenkins on 
> builds.a.o is not able to build the Flex SDK.  Unfortunately, it isn't 
> clear that infra knows how to fix it or can fix it given how they want 
> to run that server.
> Meanwhile, I'm still trying to get access to the PB compiler source, 
> but one person I talked to said that Alchemy-based shaders will 
> outperform PB shaders.  So, one potential way to solve this problem is 
> to replace our shaders with Alchemy shaders.  I have no idea how hard that would be.
> Anybody think they can do it quickly?
> Another option, which is a variant of what Maurice was proposing 
> yesterday is that we quickly create an official release package that 
> contains just the PBK files.  Then the corresponding convenience 
> binary package would have the PBJ files.  We call this an upstream 
> package that only is supported on Mac and Win.  We would not use CI for this release.
> Then we adjust the SDK build to use this upstream package.  This is 
> make more official the workaround we are using for Linux and bring 
> Linux up to par with Mac and Win.  Yes, the installer has to change as 
> well, but hopefully I'll have new installer capability ready shortly 
> anyway that should make it easier for us to make these changes.
> Thoughts?
> -Alex

Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

View raw message