Hi,
I changed the jenkins job to only run on windows boxes (of which there are 4)
and it is working so that gets rid of those minor issues.
Note that you need to specify the windows version of ant and java in the job to
get it working.
It’s currently not running the checkin tests but that shou
There is also the option to sign up for Microsoft credits via the program they
already have set up for Apache projects?
Is this what was meant by option 1?
On 31 December 2017 09:07:30 GMT+00:00, Piotr Zarzycki
wrote:
>Hi,
>
>Infra does have windows machines. Builds of Maven Royale are runnin
Hi,
Infra does have windows machines. Builds of Maven Royale are running on
Windows as I think.
Piotr
On Sun, Dec 31, 2017, 02:15 Justin Mclean wrote:
> Hi,
>
> One other minor thing is that it’s not running rat but that should be easy
> to fix.
>
> Thanks,
> Justin
Hi,
One other minor thing is that it’s not running rat but that should be easy to
fix.
Thanks,
Justin
Hi,
> As a temporary measure it should be easy enough to set up a build on
> builds.apache.org that makes the release package but doesn’t run the checkin
> tests.
After a few minor changes to the build scripts to get the release to compile on
Linux I have it set up and running here. [1] This p
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
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
Hi,
Flex nightly Ant builds have been available on an Azure VM
(apacheflexbuild.cloudapp.net) I've been paying for over the past few
years. Microsoft has generously made some Azure credits available but it
requires a separate account and Azure VM. I've set up a new VM for Royale
builds and would
13 matches
Mail list logo
