For some weird reason, after a couple of successful deployments, bamboo starts crashing, with the error "bash.exe warning could not find tmp please create". I don't know what it's trying to do, but if we restart the WHOLE server, it works again, browsing online it pointed me to the TEMP folder and how to configure it, but that works for a couple of times after reboot, then nothing. Is there something I can do to get GIT to stop breaking?
Thanks.
We're also experiencing this issues. Were you able to find a solution?
On our build system, Msysgit and Bamboo seem to be confused by the environment variables moving around because of Remote Desktop. Even after disabling some RDP features (based on http://technet.microsoft.com/en-us/library/cc755098.aspx), we still get errors until we restart Bamboo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@przemek,
The plan crashes and just keeps getting thrown into a look of failure/retries.
The only way to stop it from happening is to uncheck the submodule option on the repository, but we need it enabled for this particular plan.
After the error happens, the plan gets into this corrupted state and only recovers when the server is restarted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does it work if you execute these commands from the command line?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The commands to fetch init checkout and submodule update all work from the command line in this state.
I am not getting this exception - /libexec/git-core/git-sh-setup
: line 270:
cd
: .git:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you mean by "starts crashing"? Do you mean the agent or the server? When does it crash?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The build starts crashing for no reason. The issue is that the git repository doesn't get checked out. Here are the logs.
28-Aug-2012 02:26:24 Fetching branch 'refs/heads/DEV' from 'git@bitbucket.org:repo/repo.git'. 28-Aug-2012 02:26:24 C:\Program Files (x86)\Git\bin\Git.exe fetch ssh://77b015b8-861c-481b-a874-5da574f772d9@127.0.0.1:55827/repo/repo.git +refs/heads/DEV:refs/heads/DEV --update-head-ok --progress --verbose 28-Aug-2012 02:26:24 Warning: Permanently added '[127.0.0.1]:55827' (RSA) to the list of known hosts. 28-Aug-2012 02:26:25 From ssh://127.0.0.1:55827/repo/repo 28-Aug-2012 02:26:25 = [up to date] DEV -> DEV 28-Aug-2012 02:26:25 C:\Program Files (x86)\Git\bin\Git.exe log -1 --format=%H ab885f539d97fd10fc0d4b87715cba19307be99c 28-Aug-2012 02:26:26 Checking out revision ab885f539d97fd10fc0d4b87715cba19307be99c. 28-Aug-2012 02:26:26 C:\Program Files (x86)\Git\bin\Git.exe log -1 --format=%d --decorate=full ab885f539d97fd10fc0d4b87715cba19307be99c 28-Aug-2012 02:26:26 C:\Program Files (x86)\Git\bin\Git.exe checkout -f DEV 28-Aug-2012 02:26:26 Switched to branch 'DEV' 28-Aug-2012 02:26:26 C:\Program Files (x86)\Git\bin\Git.exe submodule update --init --recursive 28-Aug-2012 02:26:27 TROUBLESHOOT 28-Aug-2012 02:26:27 ls: .: No such file or directory 28-Aug-2012 02:26:27 f/BambooData/xml-data/build-dir/PE-PEGITTEST-PULLANDBUILDINDPROJECTS/Main 28-Aug-2012 02:26:27 .git 28-Aug-2012 02:26:27 /libexec/git-core/git-sh-setup: line 270: cd: .git: No such file or directory 28-Aug-2012 02:26:27 Unable to determine absolute path of git directory 28-Aug-2012 02:26:27 Checkout to revision ab885f539d97fd10fc0d4b87715cba19307be99c has failed. 28-Aug-2012 02:26:27 Warning: failed to checkout source code to directory 'F:\BambooData\xml-data\build-dir\PE-PEGITTEST-PULLANDBUILDINDPROJECTS\Main', trying to recover...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.