I have a github based multibranch project that uses pipeline libraries. Triggering the scan of a repository (either manually or through a schedule) rebuilds all open branches and pull requests if there has been a change made to the pipeline code even if no change has happened on the main repository that the project. This behaviour causes problems as a change made to the pipeline library can now cause a rebuild of all branches and pull requests in hundreds of projects. Is there a way by which we can configure a multibranch project in such a way that changes made to pipeline libraries do not cause a rebuild when a scan is triggered?
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bc182cff-df6c-40ca-aa32-4cc5b005a861%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
