 |
History
| Log In
|
|
|
|
Hi Steve,
I mean that despite the fact we do not change repository settings, and git-scm.xml stays the same, QuickBuild detects some change (we get "Repository setting changed, removing working directory", or something like that in logs), which results in entire working directory being deleted, even though it is not necessary (as the settings do not change). It is very troublesome for us as we have huge Git repository, and checking it out again takes up to 30 minutes, casuing build to last over 30% longer. We want repository to not be deleted when it is not necessary, and we don't know why it is being deleted in first place, since we don't change its settings. I can't reproduce this issue and I have added some logs to see what setting is changed, please replace your old plugin with the below one:
https://www.dropbox.com/s/cm4skncenpjl6qu/com.pmease.quickbuild.plugin.scm.helper_7.0.56.jar?dl=0 to replace the old plugin: 1. shutdown the server 2. copy the plugin to ${quickbuild-home}/plugins 3. delete the old plugin 4. start the server again We don't want to shutdown our server since it's a production environment, and is critical for our operations. Will do it though, if we have no other choice.
Can you tell me instead, whether running any git commands in build steps, like git remote add, or any other, can affect properties in .qbcache directory? Also, maybe I'm wrong, not sure now to be honest, I have probably seen two kinds of files: .qbcache/git-scm.xml, and .qbcache/qb-scm.xml (doesn't exist simultaneously). Is it a thing? If it is, why the files have different names, while they have the exact same content? Hi Sebastian,
I notice that one of our own configuration also cleaned up the directory. But finally I found that it was because we clean up the workspace in master step. So please verify whether you have also cleaned up the workspace before check out step. I have also searched our code base and don't see any text "git-scm", so I don't know why you see this file. Hi,
Thanks for the response. We don't clean up workspace, that's the point. It is being cleaned whenever it detects a change in the mentioned qb-scm.xml file (even though it doesn't change), and indicates it with log: INFO - Repository setting changed, deleting working directory As for git-scm.xml, you are right, I got it wrong. It's qb-scm.xml only. Sorry for confusion. What about the other thing I asked about: does executing a command / script running git commands on checked out repository might have impact on the qb-sc.xml files?
Ping. Can you answer the question above?
Hi Sebastian,
A possible reason I think may be that you have checked in qb-scm.xml to git, which is different from the actual properties. So you may check if this is the case. If so, please add .qbcache/** to your .gitignore file. We have also published a new patch release 7.0.30 which added some logs so we can know what kind of settings have been changed and whether the file itself is there or not. So please upgrade to that version and then you can look through the build log. The changes including below words: Repository setting changed: xxxxxx, deleting working directory xxxxxx if you see this, you can know which settings have been changed. or Repository RC file xxxx doesn't exist! This means that your workspace has been deleted for some reasons. Hi Steve,
Thanks for a quick answer. As for .qbcache directory, we already have it in .gitignore, so that's not the case. We will probably upgrade to 7.0.30. Are there any breaking changes since 7.0.28? (I think not, but we have to be sure) | |||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Major
Git repository settings change detected improperly causing working directory to be deleted and recreated
Thank you very much for the detailed information. But sorry I still don't get your point.
As you already know, we compare previous git settings (load from git-scm.xml) with current settings (read from git definition) one entry by one entry. Do you mean here can cause the error? Or do you mean anything else?