Ok ... sorry for the spelling ... was trying to follow the discussion using my phone ... not ideal :-)
I wanted to say that I only created/updated/maintained the builds.apache.org jobs for parts I was working on so I didn't create jobs for everything or re-activate the existing jobs if I wasn't doing something on that part of flex. If you would like me to setup a build for anything, I'd gladly do that. Even better if it produces Maven artifacts. I know that in general it is sub-optimal that we currently can't really execute Flash or Air tests, but I was more thinking of using builds.apache.org for automatically creating the SNAPSHOT versions so people interested in the project don't have to do much to test the latest builds. However I did notice that Infra is very interested in giving us the resources we need to run the tests on their hardware. Also I have the impression that we have some dedicated build slaves assigned to our projects. (While the build queue is 30 entries long, whenever I click on a "start build" that happens automatically and I think I remember to have seen that our build agent is flagged "flex") That being said ... for which part should I setup a job? Chris ________________________________________ Von: Frédéric THOMAS <webdoubl...@hotmail.com> Gesendet: Donnerstag, 20. November 2014 17:30 An: dev@flex.apache.org Betreff: RE: AW: [Maven - Squiggly] release (was: RE: [jira] [Created] (FLEX-34640) Squiggly: Generate / Package RSLs and deploy with Maven) @Chris > I only stop the jobs for parts I was actually working on Didn't get what you meant, sorry for my English. > Could setup that build, if you want Same here, does it mean you are proposing yourself to create a build at builds.apache.org ? If there's a way I can help, tell me. > I think a release should be deployed manually. Sure, me too, was thinking about automatize the SNAPSHOT deployment only and find a way to enhance the release process to include the Maven releases deployment as conveniently as possible, even though it would be ok for Squiggly, as Alex said, for some of our builds which require tests, we need a Windows machine, I can't remember for sure but I think we used one from builds.apache.org, can't remember what was the problem with, can someone refresh my memory ? Thanks,Frédéric THOMAS > From: aha...@adobe.com > To: dev@flex.apache.org > Subject: Re: AW: [Maven - Squiggly] release (was: RE: [jira] [Created] > (FLEX-34640) Squiggly: Generate / Package RSLs and deploy with Maven) > Date: Thu, 20 Nov 2014 15:58:52 +0000 > > We probably should have a Jenkins build for Squiggly running on > apacheflexbuilds. > > We’ve had so many problems with builds.a.o that I wouldn’t want to rely on > it for nightly builds, but I guess Chris is saying we pretty much have to > for building release candidates that deploy to Maven? Once we get into > maven deployment for releases whose build script involves GUI tests we are > probably going to have problems with builds.a.o again. > > -Alex > > On 11/20/14, 7:42 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: > > >In order to release I usually added install and deploy targets. All the > >builds with a maven.xml file deploy to the staging repo if the release > >variable is set to true. > > > >I think a release should be deployed manually. > > > >Chris > > > >Gesendet mit meinem HTC > > > >----- Reply message ----- > >Von: "Frédéric THOMAS" <webdoubl...@hotmail.com> > >An: "dev@flex.apache.org" <dev@flex.apache.org> > >Betreff: [Maven - Squiggly] release (was: RE: [jira] [Created] > >(FLEX-34640) Squiggly: Generate / Package RSLs and deploy with Maven) > >Datum: Do., Nov. 20, 2014 16:28 > > > >Hi Chris, > >> I think I finished the maven stuff shortly after the release > >Not sure what you mean, what did you finished exactly ? > > > >I've seen it was an Ant build to generate and deploy the maven > >corresponding artifacts, I even modified them to include RSLs but haven't > >seen any Jenkins job to run the build and deploy it automatically and > >therefore, I don't know how the 1.0-SNAPSHOT has been deploy to Apache > >Maven (probably you ran it manually because you have some credentials ?), > >for the releases, I can't see anything, why as 1.0 and 1.1 have been > >released ? can you enlighten me please ? > >What is the process to release the next one, except a standard vote on > >RCs , what about the Maven bits ? > >Should we create a Jenkins job to automatically deploy the current > >snapshots (currently 1.2-SNAPSHOT) ? > > > >Thanks, > >Frédéric THOMAS > > > >> From: christofer.d...@c-ware.de > >> To: dev@flex.apache.org > >> Subject: AW: [Maven - Squiggly] release (was: RE: [jira] [Created] > >>(FLEX-34640) Squiggly: Generate / Package RSLs and deploy with Maven) > >> Date: Thu, 20 Nov 2014 14:42:27 +0000 > >> > >> I think I finished the maven stuff shortly after the release, if I'm > >>not remembering it wrong. > >> > >> Chris > >> > >> Gesendet mit meinem HTC > >> > >> ----- Reply message ----- > >> Von: "Frédéric THOMAS" <webdoubl...@hotmail.com> > >> An: "dev@flex.apache.org" <dev@flex.apache.org> > >> Betreff: [Maven - Squiggly] release (was: RE: [jira] [Created] > >>(FLEX-34640) Squiggly: Generate / Package RSLs and deploy with Maven) > >> Datum: Do., Nov. 20, 2014 14:08 > >> > >> I reverted the version as what it was before (1.1), I haven't seen we > >>released it in a standard way with this version, now I wonder: > >> A- Have we got the Jenkins build for Squiggly ?B- Why a maven released > >>versions (1.0 and 1.1) hasn't been publish yet ? > >> > >> Thanks, > >> Frédéric THOMAS > >> > From: webdoubl...@hotmail.com > >> > To: dev@flex.apache.org > >> > Subject: RE: [jira] [Created] (FLEX-34640) Squiggly: Generate / > >>Package RSLs and deploy with Maven > >> > Date: Thu, 20 Nov 2014 10:11:06 +0000 > >> > > >> > Ok, just pushed it. > >> > > >> > Frédéric THOMAS > >> > > >> > > From: webdoubl...@hotmail.com > >> > > To: dev@flex.apache.org > >> > > Subject: RE: [jira] [Created] (FLEX-34640) Squiggly: Generate / > >>Package RSLs and deploy with Maven > >> > > Date: Tue, 18 Nov 2014 11:39:15 +0000 > >> > > > >> > > @Alex, Thanks > >> > > @Chris, any thoughts on that: > >> > > In maven.xml, the next version is 1.1 (<property name="version" > >>value="1.1"/>), is it wise given 1.0-snapshot hasn't been released yet ? > >> > > > >> > > Frédéric THOMAS > >> > > > >> > > > From: aha...@adobe.com > >> > > > To: dev@flex.apache.org > >> > > > Subject: Re: [jira] [Created] (FLEX-34640) Squiggly: Generate / > >>Package RSLs and deploy with Maven > >> > > > Date: Mon, 17 Nov 2014 18:23:50 +0000 > >> > > > > >> > > > OK, added. > >> > > > > >> > > > On 11/17/14, 4:01 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> > >>wrote: > >> > > > > >> > > > >Squiggly as Components is not set yet, I selected "Runtime Shared > >> > > > >Libraries".If someone as the Karma and the time to set > >>"Squiggly" as > >> > > > >Components, I'll change it. > >> > > > > > >> > > > >Frédéric THOMAS > >> > > > > > >> > > > >> Date: Mon, 17 Nov 2014 11:59:33 +0000 > >> > > > >> From: j...@apache.org > >> > > > >> To: iss...@flex.apache.org > >> > > > >> Subject: [jira] [Created] (FLEX-34640) Squiggly: Generate / > >>Package > >> > > > >>RSLs and deploy with Maven > >> > > > >> > >> > > > >> Frédéric THOMAS created FLEX-34640: > >> > > > >> -------------------------------------- > >> > > > >> > >> > > > >> Summary: Squiggly: Generate / Package RSLs and > >>deploy with > >> > > > >>Maven > >> > > > >> Key: FLEX-34640 > >> > > > >> URL: > >>https://issues.apache.org/jira/browse/FLEX-34640 > >> > > > >> Project: Apache Flex > >> > > > >> Issue Type: Improvement > >> > > > >> Components: Runtime Shared Libraries > >> > > > >> Reporter: Frédéric THOMAS > >> > > > >> Assignee: Frédéric THOMAS > >> > > > >> Priority: Minor > >> > > > >> > >> > > > >> > >> > > > >> Squiggly should come with RSLs > >> > > > >> > >> > > > >> > >> > > > >> > >> > > > >> -- > >> > > > >> This message was sent by Atlassian JIRA > >> > > > >> (v6.3.4#6332) > >> > > > > > >> > > > > >> > > > >> > > >> > > >
