Hi Maven folks,
Over 800 builds in the Jenkins queue right now, most of them Maven - and
its been above 500 , mostly Maven for over 12 hours now - Please take a
look and see what is going on ASAP, or I might have to cancel all Maven
jobs to allow other projects to proceed
--
*Gavin McDonald*
Sy
Looking at it.
It seems like most are waiting for a Windows executor, but these are all taken
too.
Need to investigate a bit more, but it looks like all branches are triggered
for some reason.
That's weird, because we didn't touch are shared Jenkins scripts
Robert
On 21-7-2020 18:22:12, Gavin Mc
2020-07-09_20-33-20
2020-07-21_11-38-13
This caused new configuration for *all* our branches and triggered new builds.
The Ubuntu builds were often ready, but a lot were still waiting for Windows
Executors.
Most of these builds are quite short so under normal circumstances there
shouldn't
Hi Gavin,
can websites with the current ability to push to asf-site branch be
built on the new infrastructure?
zoran
On Thu, Jul 16, 2020 at 6:33 PM Gavin McDonald wrote:
>
> Hi All,
>
> This NOTICE is for everyone on builds.apache.org. We are migrating to a new
> Cloudbees based Client Master c
La 21.07.2020 22:31, Zoran Regvart a scris:
Hi Gavin,
can websites with the current ability to push to asf-site branch be
built on the new infrastructure?
zoran
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/Apac
On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan 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
hol
La 21.07.2020 23:08, Zoran Regvart a scris:
On Tue, Jul 21, 2020 at 9:40 PM Eugen Stan 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 we
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.
For Sling we need
- sling-github-token
- sonarcloud-token-rombert
Can we have those restored on ci-builds?
On 2020/07/19 10:59:01 Gavin McDonald wrote:
> Hi All,
>
> There are a lot of credentials stored on builds.a.o - likely the majority
> are now
> not in use.
>
> For those that need migrati
