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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f0fcd019-bb4a-4126-96a1-8f912c6e7adan%40googlegroups.com.
