I'm having an issue with git. Not sure exactly what the problem is but Go is not automatically picking up changes to the repositories. I can manually run the build after the server has been rebooted but after the server has been running a couple of days and I try to manually run a build, the button disables and nothing happens. I wanted to post this before I dug into it in case you might know what the issue is. Also I have 7 pipelines associated with git repos, not sure if that could be part of it.
Here are my details:
| Go Server Version: | 2.2.0(13083-b0ad4e4db6ef) |
| JVM version: | 14.3-b01 |
| OS Information: | Windows Server 2008 R2 6.1 |
| Usable space in artifacts repository: | 3811 Mb |
| Database schema version: | 90 |
| License expiry date: | 2109-06-27 |
| Number of remote agents Go is licensed for: | 0 |
| Number of users Go is licensed for: | 99999 |
| Go edition: | Community |
Comments
2 comments
Hi Mike,
Does a restart of the Go server enable the trigger buttons that were earlier disabled?
If it does not, then this a known bug with 2.2.0. We have since made a patch release (2.2.1) and the installers are available on the site to download.
Can you upgrade and verify that the problem is fixed?
- Rajesh
I'm not sure, I can give it a shot and see. Actually the button issue is not as much of a concern. The issue where the builds arent not being automatically triggered is the biggie.
Another thing I've noticed is the time it takes for the actual build to start (Sometimes minutes). So the build is triggered at 12:00 and the build starts at 12:03 for example. So something is happening in there that I've not seen with SVN. It seems like each time it does a build its re-cloning the repository or something. It's hard to tell whats going on becuase we run go under a service account. What is Go doing when it checks the repo and right before the build?
What would be really helpful is a log of the console output (With timestamps). I think it would help troubleshoot the above situation as well as other situations where git is prompting and getting stuck (Like I'm dealing with now on another project).
Please sign in to leave a comment.