You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello, this is the set up i have for my project:
When something is committed/merged to the master branch the jenkins jobs starts, so far so good, then when the jenkins job finishes, it triggers itself again and again and again. It seems that whatever is in the "Committers to ignore" field is being ignored.
So, my question is What has to be put in there: email, username, "username <email>"?
Let me know if you need more input about this.
I am caught in the same issue. the "Committers to ignore" field is being ignored. Is there any resolution available now in bitbucket for this?
Yes, the jenkins user it's pushing a commit back with the version file being pumped. When i tested it, i tried a combination of things for the committer to no avail. I implemented a workaround on jenkins level checking for the committer & message of the last commit to skip push part again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
(Plugin developer here) - Sorry for the late response, apparently I wasn't watching the topic when I thought I was. Is your Jenkins instance pushing something (a tag, commit, anything) back to the repository after the build?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.