[JIRA] (JENKINS-46476) Environment and Options blocks do not take effect from within groovy shared variable
Title: Message Title Brandon Parker commented on JENKINS-46476 Re: Environment and Options blocks do not take effect from within groovy shared variable Since this is actually supported in Jenkins, this is a serious issue that should be addressed. https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines So I'd really like to see some movement on getting this solved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42067) Any commit to common library SCM repository triggers all pipeline build plans
Title: Message Title Brandon Parker commented on JENKINS-42067 Re: Any commit to common library SCM repository triggers all pipeline build plans This is a major issue as there is no reason for this to be the default behavior. It is certainly not something that I would have expected. This also happens when using a repo as the source of a Jenkinsfile, all jobs using that repo get built. In our workflow that causes the builds to fail because there are no changes to build. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
