AW: Excessive use on the "git-websites" runners?
Hi all, Guess our release is out and the website was updated before that … so guess I’m fine. And if you say that this is an unusual case, I also see no problems. From my perspective it just looked as if every PR was blocking a runner and that would have been a problem, of course. If that’s not the case, I guess there’s no big problem. But limiting the parallel usage of these runners is of course a good idea anyway. Chris Von: Claus Ibsen Datum: Montag, 19. Februar 2024 um 13:43 An: dev@camel.apache.org Betreff: Re: Excessive use on the "git-websites" runners? Hi Yeah ideally those CVEs should be in 1 merge to main - so they were released together. And frankly the website is rebuild from scratch each time, instead of being able to update only parts of it. The CVEs only affect the security page + a new page per CVE. I stopped one of the builds, as there is a 2nd build in the queue to publish the last CVE. That should put your job ahead of ours. On Mon, Feb 19, 2024 at 1:37 PM Andrea Cosentino wrote: > I don't think it would work on our website, but Zoran could have more > information about this. > > What we could do, it's maybe limit the number of builds on git-websites > nodes concurrently. > > Il giorno lun 19 feb 2024 alle ore 13:30 Christofer Dutz < > christofer.d...@c-ware.de> ha scritto: > > > Hi, > > > > as the PLC4X build also uses that, perhas what we did would be also an > > option for you? > > We build the website on our own VM, but stash the built website … then on > > the git-websites agent, we simply unstash what was built on our VM and > > deploy that … this reduces the lock we have on shared infra to the > minimum > > … We’re also doing the same with deploying snapshots: We build on our VM > > and use one of the ubuntu agents to deploy. > > > > Cause running a build on a PR, should probably not require staging of > > website changes … as soon as the PR is merged, then of course. > > > > Chris > > > > > > Von: Andrea Cosentino > > Datum: Montag, 19. Februar 2024 um 13:20 > > An: dev > > Betreff: Re: Excessive use on the "git-websites" runners? > > Usually there is not that much activities. There were 3 PRs related to > cves > > and some related to the last release done during the weekend. So this > > should be just a temporary saturation. We don't have other way of > > publishing the website except using that mechanism. > > > > Il lun 19 feb 2024, 13:13 Christofer Dutz ha > > scritto: > > > > > Hi all, > > > > > > I’m currently trying to finish up some stuff for the upcoming PLC4X > > > release. However am having problems because every time I want to update > > our > > > website, I have to wait a long, long time, because all 3 runners in the > > > “git-websites” class (websites1, websites2 and websites3) are blocked > > with > > > really long running builds of Apache Camel. > > > > > > Most all have the tags associated with PRs … so I am asking myself: Do > > > these builds have to be on git-websites? If not … it would be > appreciated > > > if you wouldn’t keep on blocking all runners. Of is currently something > > out > > > of the ordinary going on? > > > > > > Chris > > > > > > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Community Over Code Asia 2024 Travel Assistance Applications now open!
Hello to all users, contributors and Committers! The Travel Assistance Committee (TAC) are pleased to announce that travel assistance applications for Community over Code Asia 2024 are now open! We will be supporting Community over Code Asia, Hangzhou, China July 26th - 28th, 2024. TAC exists to help those that would like to attend Community over Code events, but are unable to do so for financial reasons. For more info on this year's applications and qualifying criteria, please visit the TAC website at < https://tac.apache.org/ >. Applications are already open on https://tac-apply.apache.org/, so don't delay! The Apache Travel Assistance Committee will only be accepting applications from those people that are able to attend the full event. Important: Applications close on Friday, May 10th, 2024. Applicants have until the the closing date above to submit their applications (which should contain as much supporting material as required to efficiently and accurately process their request), this will enable TAC to announce successful applications shortly afterwards. As usual, TAC expects to deal with a range of applications from a diverse range of backgrounds; therefore, we encourage (as always) anyone thinking about sending in an application to do so ASAP. For those that will need a Visa to enter the Country - we advise you to apply now so that you have enough time in case of interview delays. So do not wait until you know if you have been accepted or not. We look forward to greeting many of you in Hangzhou, China in July, 2024! Kind Regards, Gavin (On behalf of the Travel Assistance Committee)
Re: Remove old EOL releases from website docs
Yes, 2.1 is no longer supported. Thanks. Pasquale. On Tue, Feb 20, 2024 at 9:23 AM Claus Ibsen wrote: > Hi > > Okay the old Camel K 1.12.x release is EOL and can be removed. > This will allow the removal of EOL of Camel Quarkus and Kamelets and > whatnot. > > > On Mon, Feb 19, 2024 at 7:39 AM Claus Ibsen wrote: > > > CKC 4.0.x docs is now published, and removed the old 3.x docs. > > > > > > On Sun, Feb 18, 2024 at 1:53 PM Claus Ibsen > wrote: > > > >> Hi > >> > >> Okay we have 4.4 docs published. > >> > >> I am going to try to remove 3.14.x docs now. > >> > >> > >> > >> > >> > >> On Sun, Feb 18, 2024 at 11:11 AM Claus Ibsen > >> wrote: > >> > >>> Hi > >>> > >>> We have some old releases like 3.14, and old Camel Q and K releases as > >>> well. > >>> After we have 4.4 LTS docs published. Then we can take a look at > >>> removing old stuff. > >>> > >>> > >>> > >>> -- > >>> Claus Ibsen > >>> - > >>> @davsclaus > >>> Camel in Action 2: https://www.manning.com/ibsen2 > >>> > >> > >> > >> -- > >> Claus Ibsen > >> - > >> @davsclaus > >> Camel in Action 2: https://www.manning.com/ibsen2 > >> > > > > > > -- > > Claus Ibsen > > - > > @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 >
Re: Remove old EOL releases from website docs
Hi Okay the old Camel K 1.12.x release is EOL and can be removed. This will allow the removal of EOL of Camel Quarkus and Kamelets and whatnot. On Mon, Feb 19, 2024 at 7:39 AM Claus Ibsen wrote: > CKC 4.0.x docs is now published, and removed the old 3.x docs. > > > On Sun, Feb 18, 2024 at 1:53 PM Claus Ibsen wrote: > >> Hi >> >> Okay we have 4.4 docs published. >> >> I am going to try to remove 3.14.x docs now. >> >> >> >> >> >> On Sun, Feb 18, 2024 at 11:11 AM Claus Ibsen >> wrote: >> >>> Hi >>> >>> We have some old releases like 3.14, and old Camel Q and K releases as >>> well. >>> After we have 4.4 LTS docs published. Then we can take a look at >>> removing old stuff. >>> >>> >>> >>> -- >>> Claus Ibsen >>> - >>> @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 >>> >> >> >> -- >> Claus Ibsen >> - >> @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> > > > -- > Claus Ibsen > - > @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen - @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
