Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,932
Community Members
 
Community Events
176
Community Groups

"Committers to ignore" seems to be failing

Hello, this is the set up i have for my project:

  • A stash repo with the plugin set to build the master branch, ignoring the jenkins user's email
  • A Jenkins job building over the master branch
  • the job:
    • pumps the build version
    • build, test, report, etc
    • commits the changes on the new version to the master branch.

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.

3 answers

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.

(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?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events