On Wed, Nov 24, 2021 at 2:36 PM Damien Duportal
wrote:
> the setting "Ignore rebuilding merge branches when only the target branch
> changed" had been applied…
>
That probably suffices as a workaround (I have not tried this plugin
If this is a problem of regular Multibranch scanning, we can avoid it via
https://www.jvt.me/posts/2020/02/23/jenkins-multibranch-skip-branch-index/:
```
// execute this before anything else, including requesting any time on an agent
if
Thanks a lot Jesse for the explanation. I wasn't enough specific on the
"why does the builds were started almost everyday", your explanation is
what we understood, but using the crystal clear words :heart:
By the way, the setting "Ignore rebuilding merge branches when only the
target branch
On Tue, Nov 23, 2021 at 2:32 PM Damien Duportal
wrote:
> As part of reducing the infrastructure costs, we would like to stop
> triggering builds of the pull requests on the BOM project when the target
> branch is updated (as suggested in
> https://issues.jenkins.io/browse/INFRA-1633 if I'm
No objection from me to the proposed technique to reduce bom builds.
On Tuesday, November 23, 2021 at 12:31:55 PM UTC-7 damien@gmail.com
wrote:
> Hello dear maintainers,
>
> As part of reducing the infrastructure costs, we would like to stop
> triggering builds of the pull requests on the
Hello dear maintainers,
As part of reducing the infrastructure costs, we would like to stop
triggering builds of the pull requests on the BOM project when the target
branch is updated (as suggested in
https://issues.jenkins.io/browse/INFRA-1633 if I'm correct).
The rationale is that each
