You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Gregor Zurowski <gr...@list.zurowski.org> on 2022/03/28 08:26:48 UTC

Website build stuck

Hi Everyone,

I pushed some changes for the 3.16.0 release to the camel-website
repository, but it seems that the build is stuck on "Waiting for next
available executor":
https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/800/console

Anything I can do there?

Thanks in advance,
Gregor

Re: Website build stuck

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Thanks Zoran

I stopped and delete these PR jobs - its a waste of time when people
work on a draft PR.

The website is just updated with the 3.16 release blurb.

On Mon, Mar 28, 2022 at 11:30 AM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> This reminds me of the "Are we the baddies" sketch/meme[1].
>
> The reason why PR#800 is not built is because PR#809[2] is taking up
> all the CI resources. I do wish that branches are not pushed to
> camel-website git repository directly but built from forks using
> GitHub Actions. For branches in the camel-website repository both
> GitHub Actions and ASF Jenkins are triggered and the ASF Jenkins bit
> isn't the one pushing to Netlify for a preview, so not much benefit in
> doing that at all - the build and checks are equal on both.
>
> zoran
>
> [1] https://knowyourmeme.com/memes/are-we-the-baddies
> [2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/PR-809/
>
> --
> Zoran Regvart



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Website build stuck

Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
This reminds me of the "Are we the baddies" sketch/meme[1].

The reason why PR#800 is not built is because PR#809[2] is taking up
all the CI resources. I do wish that branches are not pushed to
camel-website git repository directly but built from forks using
GitHub Actions. For branches in the camel-website repository both
GitHub Actions and ASF Jenkins are triggered and the ASF Jenkins bit
isn't the one pushing to Netlify for a preview, so not much benefit in
doing that at all - the build and checks are equal on both.

zoran

[1] https://knowyourmeme.com/memes/are-we-the-baddies
[2] https://ci-builds.apache.org/job/Camel/job/Camel.website/job/PR-809/

--
Zoran Regvart

Re: Website build stuck

Posted by Andrea Cosentino <an...@gmail.com>.
It's related to the other jobs. I don't think there is so much we could do.
Don't know of there is an ongoing issue on Jenkins, but i don't think so

Il lun 28 mar 2022, 10:27 Gregor Zurowski <gr...@list.zurowski.org> ha
scritto:

> Hi Everyone,
>
> I pushed some changes for the 3.16.0 release to the camel-website
> repository, but it seems that the build is stuck on "Waiting for next
> available executor":
>
> https://ci-builds.apache.org/job/Camel/job/Camel.website/job/main/800/console
>
> Anything I can do there?
>
> Thanks in advance,
> Gregor
>