Lior Tal

Edited August 29, 2018 14:50

I keep seeing this issue over and over again. Attaching logs from the last time it happened for one of our builds (see in logs at around 10:34:16.135 in teamcity-agent.log):https://www.dropbox.com/...

1. Community
2. TeamCity General Topics
3. Why does a full (slow) git checkout is performed

• 0 votes

Created July 20, 2018 20:05

none of these files are related to the trigger rules i had set...

1. Community
2. TeamCity General Topics
3. Build is triggered even without changes matching the trigger rules

• 0 votes

Created July 20, 2018 20:05

This is a screenshot showing that this build was triggered by the schedule trigger (not by me manually):Here is the list of changed files that TeamCity shows:

1. Community
2. TeamCity General Topics
3. Build is triggered even without changes matching the trigger rules

• 0 votes

Created April 12, 2018 12:46

The issue happened again today. here are the logs (from wrapper.log and vcs log files). I changed the repo names BTW. INFO | jvm 1 | 2018/04/12 08:49:06 | [2018-04-12 08:49:06,391] WARN - jetbrains...

1. Community
2. TeamCity General Topics
3. Why does a full (slow) git checkout is performed

• 0 votes

Created April 11, 2018 11:49

In case i run into this again, if i include the full build log, will that help you analyze why it happened?

1. Community
2. TeamCity General Topics
3. Why does a full (slow) git checkout is performed

• 0 votes

Created February 21, 2018 19:35

ok, new theory - i believe the cleanup was not performed since the build agent did not have a git client installed on it. is this possible? cleanup is done by issuing git commands? 

1. Community
2. TeamCity General Topics
3. checkout folder not cleaned before build

• 0 votes

Created February 12, 2018 20:35

i didn't change the default. there wasn't any setting like +:* there. What could've happened (who knows since it was a while ago) was that i've created the VCS root + trigger but only then added mo...

1. Community
2. TeamCity General Topics
3. Schedule trigger is triggered even when there are no changes

• 0 votes

Created February 09, 2018 11:59

No, i just double checked. the VCS trigger will automatically trigger builds on the proper branches, but the schedule trigger will not, hence my question here, since this seemed like counter-intuit...

1. Community
2. TeamCity General Topics
3. Schedule trigger is triggered even when there are no changes

• 0 votes

Created February 08, 2018 18:31

Our VCS root is tracking multiple branches. Other build configurations are using a VCS trigger and they trigger a build on the relevant branch when there are pending changes. I did not specifically...

1. Community
2. TeamCity General Topics
3. Schedule trigger is triggered even when there are no changes

• 0 votes

Created February 07, 2018 11:15

sure, here it is:

1. Community
2. TeamCity General Topics
3. Schedule trigger is triggered even when there are no changes

• 0 votes