www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <pa...@asert.com.au>
Subject Re: [IMPORTANT] - Migration to ci-builds.a.o
Date Wed, 22 Jul 2020 11:48:56 GMT
I just tried the 'git-websites' label for Groovy. Worked without a glitch:
https://ci-builds.apache.org/job/Groovy/job/Groovy%20dev%20website/1/
but about half the speed of before:
https://builds.apache.org/view/E-G/view/Groovy/job/Groovy%20dev%20website/130/

Is that to be expected?

It's not impacting us for this particular build but good to know in terms
of expectations when we convert over some of the other builds.

Cheers, Paul.

On Wed, Jul 22, 2020 at 6:17 AM Roy Lenferink <rlenferink@apache.org> wrote:

> The new build environment uses a so called ‘floating agent’ for deploying
> websites. It is shared over different masters (ci-builds being one of them)
> and will become available when using the ‘git-websites’ label.
>
> I already tested this for Celix and it works.
>
> See for examples:
> - https://ci-builds.apache.org/job/Celix/job/site/job/master/4/console
> - https://github.com/apache/celix-site/blob/master/Jenkinsfile#L22
>
> Op di 21 jul. 2020 om 22:09 schreef Zoran Regvart <zoran@regvart.com>
>
> > On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan <eugen.stan@netdava.com>
> wrote:
> > > I'm pushing to staging.
> > > It should work for live I guess.
> > > Have you tried and failed?
> > >
> > >
> >
> https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/live/3/console
> >
> > I did not, I was wondering if website nodes were missing so I would
> > hold off until those were online. That build ran on ubuntu node, which
> > on builds.a.o did not have the necessary credentials to push to git.
> >
> > zoran
> > --
> > Zoran Regvart
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message