Hmm. Thanks for the update Jesse. My goal was to just keep the plugin at a place were it's still compatible (or relatively so) to make it easier should a new developer want to take it over.
Therefore, it seems that the default behavior is exactly what I wanted ! :-> In a year or so, when I make the next commit, I'll hunt for this message to figure out how the rest of your comments could help next time. For my current intended goal, it looks like I might want to do the same thing next year if I'm still the maintainer. Thanks for the quick response. I'm glad I didn't break anything. Mike On Wednesday, April 17, 2019 at 12:37:21 PM UTC-7, Jesse Glick wrote: > > On Wed, Apr 17, 2019 at 2:33 PM Mike Caspar <mikecan...@gmail.com > <javascript:>> wrote: > > I was concerned to see the CI build server think there are hundreds of > infra changes in my commit > > Well, because there probably were: > > https://github.com/jenkins-infra/pipeline-library/commits > > Since any of these could potentially have affected how the build runs > compared to the previous build, they are listed. Of course we hope > that none of those changes _mattered_ to you and that everything “just > works”. > > My longstanding recommendation was to not expose current `master` of a > library to the `Jenkinsfile`, and instead make it explicitly import a > specific version (which could be managed e.g. via Dependabot), so that > a change to infrastructure would always be tied to a specific commit > in your repository that could be tested in a PR before merging. But > that ship has probably sailed by now! > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f49301ce-1b2a-44b4-8cbe-19c22c93d320%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
