Because we have a lot of repos maybe we should have a dedicated CI infra. I know that it's possible to use a dedicated Jenkins controller (and associated agents) to avoid to use the shared resources of all other projects.
On Sat, Feb 6, 2021 at 3:07 PM Arnaud Héritier <aherit...@gmail.com> wrote: > I had a look at it and I am not sure if the comment is recent or not > The job wasn't disabled and the comment not visible without editing the > job because the HTML was invalid > For sure something is not right and it seems that the repo events are > automatically triggering the builds (or add/remove branches) > > The latest commit I see in my emails is: [maven-jxr] 01/01: WIP misc > changes > In the next branch of maven-jxr > > https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=shortlog;h=refs/heads/next > 37min ago > And this branch was effectively not here : > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > The indexation was triggered manually by Sylvester earlier today > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/console > > Started by user Sylwester Lachiewicz > <https://builds.apache.org/user/slachiewicz> > [Sat Feb 06 11:56:54 UTC 2021] Starting branch indexing... > Listing remote references... > Checking branches... > Checking branch master > ‘Jenkinsfile’ found > Met criteria > No changes detected: master (still at > 6df9ba323e04ef7f7612a9ea1c9d64e3f8717cc0) > Checking branch elharo-patch-2 > ‘Jenkinsfile’ found > Met criteria > No changes detected: elharo-patch-2 (still at > 87b2d6681022c5720d57c6803f4f708749cbf146) > Checking branch JXR-154 > ‘Jenkinsfile’ found > Met criteria > No changes detected: JXR-154 (still at > 737fdbed58af9018ce2c096cea5aaf2d60dfe396) > Checking branch JXR-145 > ‘Jenkinsfile’ found > Met criteria > No changes detected: JXR-145 (still at > 13fa0bf46a37e627a64eb1a1e6e9d3bca1f2793b) > Processed 4 branches > [Sat Feb 06 11:56:57 UTC 2021] Finished branch indexing. Indexing took 2.7 sec > Finished: SUCCESS > > > But for now we see no recent event: > https://builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/indexing/events > > I triggered the reindexation > https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jxr/ > 3 new branches added but for each of them we do 16 builds :-/ > > > https://ci-builds.apache.org/blue/organizations/jenkins/Maven%2Fmaven-box%2Fmaven-jxr/detail/unused/1/pipeline > > I understand we want to validate with various versions of maven / OS / > Java but on every branch it looks a lot (too much) > > > On Sat, Feb 6, 2021 at 12:54 PM Robert Scholte <rfscho...@apache.org> > wrote: > >> I see this line in the description: >> <Job disabled, always uses up all available nodes and spawns over 600 >> jobs in the queue, please fix this before re-enabling </p> >> >> On 6-2-2021 12:38:21, Arnaud Héritier <aherit...@gmail.com> wrote: >> I do not have enough privilege to do anything on this instance but the >> scan >> is configured to be done every week even if nothing happens >> Nothing happens means that we got no new event and effectively there is >> nothing on this page after Feb 2nd which is suspicious : >> https://builds.apache.org/job/Maven/job/maven-box/computation/events >> >> On Sat, Feb 6, 2021 at 12:18 PM Robert Scholte wrote: >> >> > Most likely there has been an update at INFRA, which causes that commits >> > aren't picked up automatically. >> > Last scan details[1] >> > [Thu Feb 04 20:27:32 UTC 2021] Finished organization scan. Scan took 1 >> min >> > 31 sec >> > >> > Finished: SUCCESS >> > >> > Would be great if somebody could investigate this. >> > >> > thanks, >> > Robert >> > >> > [1] >> > >> https://builds.apache.org/job/Maven/job/maven-box/computation/consoleFull >> >> >> >> -- >> Arnaud Héritier >> Twitter/Skype : aheritier >> > > > -- > Arnaud Héritier > Twitter/Skype : aheritier > -- Arnaud Héritier Twitter/Skype : aheritier
