Re: Alternative OS builds failing on Camel repo fork

[Zoran Regvart <zo...@regvart.com>]

Hi Steve,
Same suggestions apply when building using GitHub Actions, you'll need
to avoid contacting ASF Maven repository. Alternatively you can try
contacting INFRA (via ASF Slack[1] or JIRA[2]), to look into
unblocking GitHub[3] egress IPs. I would not expect INFRA to change
their policy though.

zoran

[1] https://infra.apache.org/slack.html
[2] https://issues.apache.org/jira/projects/INFRA/
[3] https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses

On Fri, Sep 30, 2022 at 9:36 PM Steve973 <st...@gmail.com> wrote:
>
> Hello, Zoran.  I am talking about my fork on Github that builds
> automatically.  I am not talking about performing this build locally.
>
> On Fri, Sep 30, 2022 at 4:26 AM Zoran Regvart <zo...@regvart.com> wrote:
>
> > Hi Steve,
> > you could have been put on a ban-list by the INFRA, see[1]. Best
> > approach would be to configure Maven not to contact the ASF Maven
> > repository at all by removing references to it, or to have a local
> > repository manager in its place[2].
> >
> > zoran
> >
> > [1] https://infra.apache.org/infra-ban.html
> > [2]
> > https://maven.apache.org/guides/mini/guide-mirror-settings.html#Using_A_Single_Repository
> >
> > On Thu, Sep 29, 2022 at 9:32 PM Steve973 <st...@gmail.com> wrote:
> > >
> > > Hello.  I see that the alternative os build for my Camel fork
> > > always exceeds 360 minutes.  It regularly passes on the official Apache
> > > repo, so is there something that I can do that will fix this problem?
> > >
> > > Thanks,
> > > Steve
> >
> >
> >
> > --
> > Zoran Regvart
> >



-- 
Zoran Regvart