Hi Justin, Yep we have FlexJS and Royale [1], but this is Maven build and we need to have also ANT. All PMCs have access to the build server (always was like that). Since Alex won't be paying at all for the new Azure - I personally don't see any issue with current setup at all. We have more options for modification of that server than in case of builds.a.o.
Hi Alex, It is really not good if we won't move that jobs to the new Azure, cause we loose Nightly builds of Apache Flex. :( I don't have cycles in the next weeks to take a look either. [1] https://builds.apache.org/job/Royale%20Pipeline/ Thanks, Piotr 2017-12-29 5:58 GMT+01:00 Justin Mclean <jus...@classsoftware.com>: > Hi, > > > There are some choices: > > 1) Some other PMC member get an Azure VM and move the jobs there > > 2) Run Flex jobs on the new Royale VM. > > There is a 3rd option and that is to run it on builds.apache.org. We did > have this working at one point and I can’t see why it wouldn’t be possible > to do so again. > > The FlexJS builds were running on builds.apache.org [1] so I don’t see > why the Royale builds couldn’t be there as well. What’s the requirement to > run them on a seperate VM? (But that is up to the Royale PMC to decide.) > > > For #2, we would need a volunteer or two to move the jobs. > > Moving the Flex nightly builds to a machine where not all of the Flex PMC > has access is probably not the best option IMO. > > Thanks, > Justin > > 1.https://builds.apache.org/job/FlexJS%20Pipeline/ > > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
