cleanup policy and vcs history

Hello,

We were trying to establish a cleanup policy that deletes artifacts but nothing else.
Thus we checked the 'Remove artifacts, but keep history and statistical data' option.

With this policy in place we noticed that also the vcs history gets cleaned up.

Is there any way to prevent this vcs history to get removed ?

thanks,

Koen

9 comments

Do you have a default cleanup rule too? I suppose builds were cleaned up because of this rule.

--
Pavel Sher

0

The rule was configured to 'All Configurations'.
Does this cause the loss of vcs history ?
Should I use 'per build configuration' rules to solve this problem?

Koen

0

There are different cleanup levels:
- clean artifacts
- clean history
- clean everything

Default rule specified for a cleanup level is applied to a build configuration if in this build configuration there is no rule for the same level. This might not be obvious from the UI in 3.1 version. However in the Calcutta (4.0) we redesigned cleanup policy configuration page and such behavior should now be more evident.

--
Pavel Sher

0

We have only one rule (the default rule).
And that is configured to
- All Configurations
- Remove artifacts, but keep history and statistical data
- Older than the 20th successful build

There aren't any other (more specific rules).

An excerpt from the logs that hinted me to thinking the loss of vcs data is related to the cleanup policy:
INFO - jetbrains.buildServer.SERVER - Performing VCS cleanup...
INFO - jetbrains.buildServer.SERVER - Removing 53 modifications

(logfile for that day is attached)



Attachment(s):
excerpt.log
0

What version of TeamCity do you use? Could you please submit a screenshot of cleanup rules configured in your system?

--
Pavel Sher

0

We use TeamCity Professional Version 3.1.1 (build 6828)

well, we have currently disabled the auto-clean feature.
I re-enabled it just for taking the attached screenshot.



Attachment(s):
cleanup.jpg
0

Oh, I am sorry, I probably confused you with my questions because I have not seen that you mean VCS history (not BUILDS history). As for VCS history it won't be cleaned in the upcoming Calcutta 4.0 EAP. To be more precise we will clean changes only if they are not visible in the UI, for example, if they belong to removed build configuration. In other cases we'll try to preserve changes history.

--
Pavel Sher

0

Pavel,

This is not what I'm seeing.
I can still see the builds in the UI, but not their vcs changes.

Is there anything that I can do with the current release version?
If not, what is the anticipated release date for 4.0 ?

thx

Koen

0

Unfortunately in 3.1 there is no way to prevent VCS modifications cleaning. We are going to release next Calcutta 4.0 EAP build soon (most likely on the next week). This EAP build will have fix for this problem.

Oficial TeamCity 4.0 release is planned in November.

--
Pavel Sher

0

Please sign in to leave a comment.