Open nickcodefresh opened 7 years ago
I have a Jenkins job that's committing code to my master branch and then pushing to origin using the user "flexteam". In BitBucket I have added that user to "Committers to Ignore" but Jenkins still kicks off a Jenkins build.
Here's a snipped of the Jenkins build job.
+ git config --global user.email flexteam@abc.com + git config --global user.name flexteam + git config --global push.default simple + git config --list user.email=flexteam@abc.com user.name=flexteam push.default=simple core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.origin.url=XXXXXXXXXXXXXXXXXXXXXXXXXX remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* + find . -name pom.xml + xargs git add + git commit -m Updated POM version to 1.0.58 [detached HEAD f8fed8f] Updated POM version to 1.0.58 5 files changed, 5 insertions(+), 5 deletions(-) + git push origin HEAD:master To XXXXXXXXXXXXXXXXXXXXXXXXXX ebfd76a..f8fed8f HEAD -> master
Any ideas why this is happening?
It works for me. Are you sure that the user has the name flexteam in your bitbucket?
flexteam
Can you print the results of git log that has the commit performed by this user?
I have a Jenkins job that's committing code to my master branch and then pushing to origin using the user "flexteam". In BitBucket I have added that user to "Committers to Ignore" but Jenkins still kicks off a Jenkins build.
Here's a snipped of the Jenkins build job.
Any ideas why this is happening?