But why couldn’t the builds.a.o script just grab artifacts from apacheflexbuilds and deploy them. Does it really need to do its own “get the source and compile”?
On 11/20/14, 5:28 PM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote: >The problem with any other machine than builds.apache.org is that someone >would have to write down his apache credentials in the settings.xml in >order to have anything deployed to maven.apache.org. When building on >builds.apache.org there are default credentials in place, that any build >can use. So I guess for providing daily snapshots, this will be the only >option. > >Other would be to manually deploy snapshots from a developer machine >whenever an update seems to be appropriate. > >Chris > > > >________________________________________ >Von: Frédéric THOMAS <webdoubl...@hotmail.com> >Gesendet: Donnerstag, 20. November 2014 18:58 >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) > >@Alex, >Thanks for remembering me. >> So, IMO, we don’t want to have builds.a.o try to run scripts that do GUI >> tests, but even Squiggly really should have GUI tests some day. Is it >> possible that the “build” that runs on builds.a.o does not compile >>source >> code or runs tests, but instead grabs artifacts from apacheflexbuilds >>and >> packages things? Or I suppose it could grab a known good source package >> from apacheflexbuilds and then run against that and skip tests. >Going that way, I guess we could setup our own private maven repo, deploy >the snapshots on at each build, setup an Ant or Maven build on builds.a.o >which would collect the last snapshots and deploy them on the Maven >Apache Snapshot repo ? Either with Ant using the Deployer principle or >with Maven using aether, @Chris, you've got experiences with, do see a >way in those proposals ? >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 17:36:55 +0000 >> >> >> >> On 11/20/14, 8:30 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: >> > 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 ? >> >> Yes, we tried using the Windows slave on builds.a.o. After spending way >> too much time begging Infra to install and configure custom things we >> needed and then having them choose versions of Jenkins that busted our >> builds, we switched to using my VM at apacheflexbuilds.cloudapp.net and >> have had very few issues since. It does not make sense to me to share a >> Windows build machine with other projects that may have conflicting >>needs >> for versions of dependencies. >> >> And there was no way I could have logged into builds.a.o and debug over >> RDP some problem where a test only failed on the build machine. >> >> So, IMO, we don’t want to have builds.a.o try to run scripts that do GUI >> tests, but even Squiggly really should have GUI tests some day. Is it >> possible that the “build” that runs on builds.a.o does not compile >>source >> code or runs tests, but instead grabs artifacts from apacheflexbuilds >>and >> packages things? Or I suppose it could grab a known good source package >> from apacheflexbuilds and then run against that and skip tests. >> >> Thoughts? >> -Alex >>
