Medium Otherwise merges and commits won't work.
[BAM-10945] Author and Committer have to be made configurable (at least for Git)
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1435635 ] | New: JAC Bug Workflow v3 [ 3379559 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 [ 1410452 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1435635 ] |
| Workflow | Original: Bamboo Workflow 2014 v2 [ 610800 ] | New: Bamboo Workflow 2016 v1 [ 1410452 ] |
| Workflow | Original: Bamboo Workflow 2014 [ 593474 ] | New: Bamboo Workflow 2014 v2 [ 610800 ] |
| Workflow | Original: Bamboo Workflow 2010 [ 370068 ] | New: Bamboo Workflow 2014 [ 593474 ] |
Thanks for letting me know Przemek. I didn't know about those ENV variables so I'll try that to see if it fixes my issue for now.
Not sure what has occured because this was all working initially. Not sure if something screwy occured with the latest upgrade or not
Thanks again
Will this bug fix mean I can configure bamboo to use a particular user/email?
The bugfix is limited to merge and commit actions inititiated by Bamboo 4.0 .
I don't see why git tag wouldn't use your user configuration. If you're using remote agents (which I think you aren't) - is the config set on the remote agent too?
If you can't get it to work using config file, try setting a subset of GIT_COMMITTER_NAME / GIT_COMMITTER_EMAIL / GIT_AUTHOR_NAME / GIT_AUTHOR_EMAIL environment variables (just for the build or the whole server/agent).
Just wondering if this bug fixes an issue I ran into after upgrading to 3.4.4
I have a bitbucket git repository and bamboo installed @ Contegix.
Bamboo correctly reports it is running from user j2ee-appfusions-bamboo and cat /home/j2ee-appfusions-bamboo/.gitconfig shows
[user]
email = bamboo@appfusions.com
name = Bamboo Server
However, running a maven release build I get errors tagging (BUT not pushing changes, such as the removal of the SNAPSHOT during the release process)
Checking in modified POMs... 23-Mar-2012 09:16:37 [INFO] Executing: /bin/sh -c cd /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 && git add -- pom.xml 23-Mar-2012 09:16:37 [INFO] Working directory: /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 23-Mar-2012 09:16:37 [INFO] Executing: /bin/sh -c cd /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 && git status 23-Mar-2012 09:16:37 [INFO] Working directory: /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 23-Mar-2012 09:16:37 [INFO] Executing: /bin/sh -c cd /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 && git commit --verbose -F /opt/j2ee/domains/appfusions.com/bamboo/tomcat/temp/GACA-REL-JOB1/maven-scm-1296286834.commit pom.xml 23-Mar-2012 09:16:37 [INFO] Working directory: /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 23-Mar-2012 09:16:37 [INFO] Executing: /bin/sh -c cd /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 && git symbolic-ref HEAD 23-Mar-2012 09:16:37 [INFO] Working directory: /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 23-Mar-2012 09:16:38 [INFO] Executing: /bin/sh -c cd /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 && git push git@bitbucket.org:appfusions/af051-google-apps-auth.git master:master 23-Mar-2012 09:16:38 [INFO] Working directory: /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 23-Mar-2012 09:16:43 [INFO] Tagging release with the label v0.9.4... 23-Mar-2012 09:16:43 [INFO] Executing: /bin/sh -c cd /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 && git tag -F /opt/j2ee/domains/appfusions.com/bamboo/tomcat/temp/GACA-REL-JOB1/maven-scm-1934608505.commit v0.9.4 23-Mar-2012 09:16:43 [INFO] Working directory: /opt/j2ee/domains/appfusions.com/bamboo/webapps/atlassian-bamboo/data/atlassian-bamboo-3.3.3/xml-data/build-dir/GACA-REL-JOB1 23-Mar-2012 09:16:44 [INFO] ------------------------------------------------------------------------ 23-Mar-2012 09:16:44 [ERROR] BUILD FAILURE 23-Mar-2012 09:16:44 [INFO] ------------------------------------------------------------------------ 23-Mar-2012 09:16:44 [INFO] Unable to tag SCM 23-Mar-2012 09:16:44 Provider message: 23-Mar-2012 09:16:44 The git-tag command failed. 23-Mar-2012 09:16:44 Command output: 23-Mar-2012 09:16:44 23-Mar-2012 09:16:44 *** Please tell me who you are. 23-Mar-2012 09:16:44 23-Mar-2012 09:16:44 Run 23-Mar-2012 09:16:44 23-Mar-2012 09:16:44 git config --global user.email "you@example.com" 23-Mar-2012 09:16:44 git config --global user.name "Your Name" 23-Mar-2012 09:16:44 23-Mar-2012 09:16:44 to set your account's default identity. 23-Mar-2012 09:16:44 Omit --global to set the identity only in this repository. 23-Mar-2012 09:16:44 23-Mar-2012 09:16:44 fatal: empty ident <j2ee-appfusions-bamboo@appfusions01.managed.contegix.com> not allowed
So as far as I can tell, the user running bamboo DOES have its config set, but Bamboo isn't using it.
Will this bug fix mean I can configure bamboo to use a particular user/email?
Or do you think an environment issue still somewhere?
It was working in January when we did our last release on this and the only thing that changed was the bamboo upgrade 
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: To be reviewed [ 10026 ] | New: Resolved [ 5 ] |
For those looking where to configure this, the option is located at: Administration => Respository Settings => Automatic Commits.