Exclude Service User Commits in Yet Another commit checker

 

We enabled the yet another commit checker recently, what’s happening is maven plug in is trying to update the POM file and yacc is not allowing it because of no JIRA ID so push failed. 

How to Exclude commits from service users with access keys (e.g. CI Server) from commit requirements?

is there any way fix it by adding a 'whitelist' committer (Jenkins service account) in the Yet Another Commit Checker settings. so it allows commits from the service account to be exempt from the JIRA ID validation.?

 

Thanks in advance!!

1 answer

1 accepted

0 votes

Under the "Exclude Commits" option, you will see a checkbox to exclude commits from service users. Once that is checked, users who are using SSH access keys on the project or repository level will be excluded from the checks.

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

676 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot