I have a similar issue – Jenkins logs state, that the strategy "cancels"
the build due to the entirety of changed files falling under the excluded
regions, but the build proceeds anyway.
It appears the plugin is completely broken.
On Wednesday, March 10, 2021 at 7:32:50 PM UTC+1 Ven H wrote:
>
Hi!
Recently while reading an error raised when incorrectly specifying an
option in the options section of the declarative pipeline, I noticed
several options which supposedly are accepted, though not documented in the
snippet generator nor in the online documentation. One of these options is
Hi Dominik,
High load on the master might be caused by incorrectly implemented
Jenkinsfiles which contain complex logic, thus inducing load on the master
instead of the nodes. Furthermore, this load will not be visible in the
node overview. I think this is the best point to start investigating
