Hi,
> We could copy the last good build somewhere. Unless changes are actually
> committed to the Flex repos, there isn't going to be any difference
> between one nightly build and another.
As a temporary measure it should be easy enough to set up a build on
builds.apache.org that makes the rel
Hi,
> If someone wants to move the jobs to builds.a.o and deal with working with
> Infra or joining
> Infra and maintaining the builds as Infra requires updating versions of
> things, that is a third option.
I would be willing to do that.
> But if that volunteer disappears, then Flex is back t
On 12/29/17, 2:43 AM, "Piotr Zarzycki" wrote:
>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.
We could copy the last good build somewhere. Unless ch
On 12/29/17, 2:50 AM, "Justin Mclean" wrote:
>Hi,
>
>> Yep we have FlexJS and Royale [1], but this is Maven build and we need
>>to
>> have also ANT.
>
>Jenkins can run ant builds as well.
We've used apacheflexbuilds and Erik's CI server for mustella because that
way we have control over the ma
Hi,
> Yep we have FlexJS and Royale [1], but this is Maven build and we need to
> have also ANT.
Jenkins can run ant builds as well.
> All PMCs have access to the build server
Currently the Flex PMC doesn’t have access to the server AFAIK. Please email
the login details to the Flex private lis
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 option
