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!!
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 ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot