I applied the same restrictions now to the other JR2 jobs. Konrad > On 16. Sep 2022, at 10:09, Konrad Windszus <[email protected]> wrote: > > I now reconfigured the Jenkins job at > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.16/configure > <https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.16/configure> > To only run on “ubuntu” labelled nodes > (https://cwiki.apache.org/confluence/display/INFRA/ci-builds.apache.org > <https://cwiki.apache.org/confluence/display/INFRA/ci-builds.apache.org>) and > to abort builds (in “Build Environment” -> About the build if it is stuck”) > after 120 minutes. > > If that works fine, we should also apply this setting to both > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/ > <https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.20/> and > https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/ > <https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-trunk/>. > > Konrad > > >> On 16. Sep 2022, at 10:02, Konrad Windszus <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi, >> We probably need to tweak the Jenkins configuration for JR2. >> The job at >> https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.16/jdk=jdk_11_latest,profile=integrationTesting/791/ >> >> <https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit-2.16/jdk=jdk_11_latest,profile=integrationTesting/791/> >> is running for more than 12 hours now. >> Also it is running on a new shared node >> https://ci-builds.apache.org/computer/jenkins-shared-arm6 >> <https://ci-builds.apache.org/computer/jenkins-shared-arm6> which doesn’t >> seem useful. >> >> So we should IMHO: >> - cancel jobs running for more than 1(?) hour >> - only execute Jobs on ubuntu nodes >> >> WDYT? >> Konrad >
- https://ci-builds.apache.org/job/Jackrabbit/job/jackrabbit... Konrad Windszus
- Re: https://ci-builds.apache.org/job/Jackrabbit/job/j... Konrad Windszus
- Re: https://ci-builds.apache.org/job/Jackrabbit/j... Konrad Windszus
