Re: Git Source Code Management Oddity
On Thursday, May 19, 2022 at 8:42:29 AM UTC-6 Eric Fetzer wrote: > OK, I've been having some major issues with Git source code management in > Jenkins. So I have several repositories I pull from to do builds. I use > my same credentials to pull from each. If the pull succeeds, I push a tag > at it. I was noticing certain tags were failing saying it already existed > even though it didn't exist. Well, it didn't exist in THAT repository. > But it did exist in one of the other repositories. I tested by creating > these tags in git command line and pushing them and it worked fine. Anyone > have a clue what could be happening here? The jenkins task goes to my > repository's url with my credentials selecting from the branch I tell it. > It's set to clean before check out. It does all of this fine. It has a > Git Publisher post build step to push my tag only if the checkout succeeds > with the box checked to create new tag. This works UNLESS that same tags > exists in any of the projects I run this checkout task against. Can anyone > think of a reason for this odd behavior? Thanks!!! I don't know if the git publisher in the git plugin is able to handle checkout from multiple repositories. It may not be that sophisticated. You may need to switch to use the "with credentials" feature that was added in Google Summer of Code 2021 to allow you to perform the push of the tag yourself rather than using the git publisher. Docs on the "with credentials" feature are available at https://plugins.jenkins.io/git/#plugin-content-credential-binding (Pipeline) and https://plugins.jenkins.io/git/#plugin-content-git-bindings (freestyle) Mark Waite -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ef07f787-0884-49a9-9ea3-960b6eeb021fn%40googlegroups.com.
Git Source Code Management Oddity
OK, I've been having some major issues with Git source code management in Jenkins. So I have several repositories I pull from to do builds. I use my same credentials to pull from each. If the pull succeeds, I push a tag at it. I was noticing certain tags were failing saying it already existed even though it didn't exist. Well, it didn't exist in THAT repository. But it did exist in one of the other repositories. I tested by creating these tags in git command line and pushing them and it worked fine. Anyone have a clue what could be happening here? The jenkins task goes to my repository's url with my credentials selecting from the branch I tell it. It's set to clean before check out. It does all of this fine. It has a Git Publisher post build step to push my tag only if the checkout succeeds with the box checked to create new tag. This works UNLESS that same tags exists in any of the projects I run this checkout task against. Can anyone think of a reason for this odd behavior? Thanks!!! -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f0fcd019-bb4a-4126-96a1-8f912c6e7adan%40googlegroups.com.
Re: Scriptler using GET in Jenkins2
On Wed, May 18, 2022 at 10:02 PM adam.l...@gmail.com < adam.l.lev...@gmail.com> wrote: > But the way I read that is as a warning: subject to CSRF problems, be > warned. I don't see any indication that GET has been disabled. > > What am I not seeing? > With publication of the advisory, we suspended distribution of the plugin for a while until the issues were fixed in release 3.0. The fix for this was to require POST, which Jenkins applies CSRF protection to. Advisories are not updated when previously unresolved issues are fixed, so it still says that as of publication, there is no fix. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAMo7Pt%2BRzvyUo6r4H9GHqREyY3ePiAiBdw0bPHh6nUnvZVqiqA%40mail.gmail.com.
