Camels builds are definitely an issue and are consuming the 'websites' label seemingly constantly from many PRs, minor changes are triggering a new complete build each time. Builds are taking a minimum of 20 minutes each time.
This needs to be looked into and see if there can be a better workflow. Gav... On Thu, Mar 26, 2020 at 4:40 PM Robert Munteanu <romb...@apache.org> wrote: > Hello Zoran, > > On Thu, 2020-03-26 at 16:06 +0100, Zoran Regvart wrote: > > Hi builders, > > Apache Camel is participating in the Outreachy program[1], and we > > have > > a lot of pull requests[2] for which we run builds. > > That's cool and a nice problem to have :-) > > > > > I think the other projects are having issues because of this. Not > > sure > > what can be done about this, we have no other way to check and > > preview > > the change if we don't run the build. > > I looked at the preview step of one of your builds and it seems that > it's not actually publishing the changes anywhere, but instead > archiving them in Jenkins > > [2020-03-26T13:19:05.101Z] [htmlpublisher] Archiving HTML reports... > [2020-03-26T13:19:05.103Z] [htmlpublisher] Archiving at PROJECT level > /home/jenkins/jenkins-slave/workspace/Camel.website_PR-273/camel- > website/public to /x1/jenkins/jenkins- > home/jobs/Camel.website/branches/PR-273/htmlreports/Preview > > I think that means you can run the PR check on any executor, e.g. > 'ubuntu', just that the regular build needs to build on 'websites'. > > Note that this is independent of Vladimir's email discussing whether > PRs should be built on ASF resources or not, just a comment on how to > optimise executor usage. > > Thanks, > Robert > > -- Gav...
