You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2016/04/08 16:32:20 UTC

Broken Build Notices

Hi,

Infra has informed us that archives.a.o is down for maintenance for
possible the entire weekend.  This will break most or all of our builds.
I'd rather not spend time finding workarounds.  Volunteers are welcome if
interested, but otherwise, I would say we just ignore the pile of broken
build emails.  Or if it really annoys folks, we could just shut off our CI
server for a couple of days.

-Alex


AW: Broken Build Notices

Posted by Christofer Dutz <ch...@c-ware.de>.
I can't remember a millisecond in which Maven central has been down for the last 10 years. But google is mirroring Maven central so this would just be a base url that has to be changed for all artifacts.

I always feel bad when I hear something about hacking and patching :-(

Chris

Von meinem Samsung Galaxy Smartphone gesendet.


-------- Ursprüngliche Nachricht --------
Von: Alex Harui <ah...@adobe.com>
Datum: 09.04.16 07:03 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: Broken Build Notices

Bummer.  The server and path for commons is not in an Ant variable so I
can't redirect it.  I guess I never thought archive.a.o would go away for
that long.

I suppose I could hack a binary package with altered ant scripts, post it
somewhere and redirect to it from the installer.  Do folks think that is
worth it?

And for the future, I would imagine we'll end up pulling these things from
Maven Central, but we could also bundle these things so we don't have to
worry about Maven Central going down.

Thoughts?
-Alex

On 4/8/16, 9:50 PM, "Alex Harui" <ah...@adobe.com> wrote:

>Yes, Om already warned the list that it would affect the installer.
>
>I'm not going to try to fix older SDK builds unless we get a complaint.
>But I will try to fix FlexJS 0.6.0.
>
>-Alex
>
>On 4/8/16, 9:36 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
>>Hi,
>>
>>JFYI - this breaks installing both Flex JS 0.5 and Flex JS 0.6.
>>Installing the latest Flex 4.15 still works, older versions of the Flex
>>SDK will also be broken.
>>
>>Flex JS 0.6 is failing on:
>>Downloading dist/commons/cli/binaries/commons-cli-1.2-bin.tar.gz from:
>>http://archive.apache.org
>>
>>There are other places a later version of this could be downloaded from
>>(see https://commons.apache.org/proper/commons-cli/download_cli.cgi
>><https://commons.apache.org/proper/commons-cli/download_cli.cgi>) are
>>later versions compatible?
>>
>>Thanks,
>>Justin
>


Re: Broken Build Notices

Posted by Alex Harui <ah...@adobe.com>.
Bummer.  The server and path for commons is not in an Ant variable so I
can't redirect it.  I guess I never thought archive.a.o would go away for
that long.

I suppose I could hack a binary package with altered ant scripts, post it
somewhere and redirect to it from the installer.  Do folks think that is
worth it?

And for the future, I would imagine we'll end up pulling these things from
Maven Central, but we could also bundle these things so we don't have to
worry about Maven Central going down.

Thoughts?
-Alex

On 4/8/16, 9:50 PM, "Alex Harui" <ah...@adobe.com> wrote:

>Yes, Om already warned the list that it would affect the installer.
>
>I'm not going to try to fix older SDK builds unless we get a complaint.
>But I will try to fix FlexJS 0.6.0.
>
>-Alex
>
>On 4/8/16, 9:36 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
>>Hi,
>>
>>JFYI - this breaks installing both Flex JS 0.5 and Flex JS 0.6.
>>Installing the latest Flex 4.15 still works, older versions of the Flex
>>SDK will also be broken.
>>
>>Flex JS 0.6 is failing on:
>>Downloading dist/commons/cli/binaries/commons-cli-1.2-bin.tar.gz from:
>>http://archive.apache.org
>>
>>There are other places a later version of this could be downloaded from
>>(see https://commons.apache.org/proper/commons-cli/download_cli.cgi
>><https://commons.apache.org/proper/commons-cli/download_cli.cgi>) are
>>later versions compatible?
>>
>>Thanks,
>>Justin
>


Re: Broken Build Notices

Posted by Alex Harui <ah...@adobe.com>.
Yes, Om already warned the list that it would affect the installer.

I'm not going to try to fix older SDK builds unless we get a complaint.
But I will try to fix FlexJS 0.6.0.

-Alex

On 4/8/16, 9:36 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>Hi,
>
>JFYI - this breaks installing both Flex JS 0.5 and Flex JS 0.6.
>Installing the latest Flex 4.15 still works, older versions of the Flex
>SDK will also be broken.
>
>Flex JS 0.6 is failing on:
>Downloading dist/commons/cli/binaries/commons-cli-1.2-bin.tar.gz from:
>http://archive.apache.org
>
>There are other places a later version of this could be downloaded from
>(see https://commons.apache.org/proper/commons-cli/download_cli.cgi
><https://commons.apache.org/proper/commons-cli/download_cli.cgi>) are
>later versions compatible?
>
>Thanks,
>Justin


Re: Broken Build Notices

Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,

JFYI - this breaks installing both Flex JS 0.5 and Flex JS 0.6. Installing the latest Flex 4.15 still works, older versions of the Flex SDK will also be broken.

Flex JS 0.6 is failing on:
Downloading dist/commons/cli/binaries/commons-cli-1.2-bin.tar.gz from: http://archive.apache.org

There are other places a later version of this could be downloaded from (see https://commons.apache.org/proper/commons-cli/download_cli.cgi <https://commons.apache.org/proper/commons-cli/download_cli.cgi>) are later versions compatible?

Thanks,
Justin

Re: Broken Build Notices

Posted by Alex Harui <ah...@adobe.com>.
We can redirect the installer. I won't be able to do it until this evening.  It involves changing the properties files on the flex website.


Sent from my LG G3, an AT&T 4G LTE smartphone


------ Original message------

From: OmPrakash Muppirala

Date: Fri, Apr 8, 2016 10:12 AM

To: dev@flex.apache.org;

Subject:Re: Broken Build Notices


This is going to break our Installer and the npm installs as well.  We are
downloading some stuff from archive.apache.org.

Thanks,
Om
On Apr 8, 2016 7:40 AM, "Alex Harui" <ah...@adobe.com> wrote:

> I changed my mind.  I hit a button in Jenkins to try to prevent further
> builds.
>
> -Alex
>
> On 4/8/16, 7:32 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >Hi,
> >
> >Infra has informed us that archives.a.o is down for maintenance for
> >possible the entire weekend.  This will break most or all of our builds.
> >I'd rather not spend time finding workarounds.  Volunteers are welcome if
> >interested, but otherwise, I would say we just ignore the pile of broken
> >build emails.  Or if it really annoys folks, we could just shut off our CI
> >server for a couple of days.
> >
> >-Alex
> >
>
>

Re: Broken Build Notices

Posted by OmPrakash Muppirala <bi...@gmail.com>.
This is going to break our Installer and the npm installs as well.  We are
downloading some stuff from archive.apache.org.

Thanks,
Om
On Apr 8, 2016 7:40 AM, "Alex Harui" <ah...@adobe.com> wrote:

> I changed my mind.  I hit a button in Jenkins to try to prevent further
> builds.
>
> -Alex
>
> On 4/8/16, 7:32 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >Hi,
> >
> >Infra has informed us that archives.a.o is down for maintenance for
> >possible the entire weekend.  This will break most or all of our builds.
> >I'd rather not spend time finding workarounds.  Volunteers are welcome if
> >interested, but otherwise, I would say we just ignore the pile of broken
> >build emails.  Or if it really annoys folks, we could just shut off our CI
> >server for a couple of days.
> >
> >-Alex
> >
>
>

Re: Broken Build Notices

Posted by Alex Harui <ah...@adobe.com>.
I changed my mind.  I hit a button in Jenkins to try to prevent further
builds.

-Alex

On 4/8/16, 7:32 AM, "Alex Harui" <ah...@adobe.com> wrote:

>Hi,
>
>Infra has informed us that archives.a.o is down for maintenance for
>possible the entire weekend.  This will break most or all of our builds.
>I'd rather not spend time finding workarounds.  Volunteers are welcome if
>interested, but otherwise, I would say we just ignore the pile of broken
>build emails.  Or if it really annoys folks, we could just shut off our CI
>server for a couple of days.
>
>-Alex
>