jetbrains / teamcity-caches-cleanup-plugin Goto Github PK

Reason: TC blocks access to Build Agent files, except temp and work directories.
Since system.agent.persistent.cache resides in agent system directory, it's blacklisted.
Builds would fail with messages like:

Failed to resolve artifact dependency <Project / Configuration, build #42 [id 42]>: downloading files to C:\BuildAgent\ is prohibited (jetbrains.buildServer.artifacts.impl.SourcePathAwareResolvingFailedException)

For details see https://youtrack.jetbrains.com/issue/TW-60343

Plugin should not report each log file separately

Hi,

I had some issues on the dependencies when building the project. Maven could not resolve them. And they were still on TC9 libs. Not the TC10 libs. I've modified the pom and now it "mvn package" is working.

Here is my modified pom. I couldn't make a branch or pull request, because I'm wasnt allowed to.

Greetings from Switzerland

caches-cleanup-plugin.pom

    <executions>
      <execution>
        <id>compile</id>
        <phase>process-sources</phase>
        <goals> <goal>compile</goal> </goals>
      </execution>

      <execution>
        <id>test-compile</id>
        <phase>process-test-sources</phase>
        <goals> <goal>test-compile</goal> </goals>
      </execution>
    </executions>
  </plugin>
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <version>3.1</version>
    <configuration>
      <source>1.6</source>
      <target>1.6</target>
    </configuration>
  </plugin>
  <plugin>
    <groupId>org.jetbrains.teamcity</groupId>
    <artifactId>teamcity-sdk-maven-plugin</artifactId>
    <version>0.1</version>
    <configuration>
      <!-- <teamcityDir>/path/to/tc/distro</teamcityDir> -->
    </configuration>
  </plugin>
</plugins>

It is not clear to me how this plugin works/integrates into the builds/infrastructure, as there are no screenshots for how this plugin would be configured.
What we would like is something that performs a periodic cleanup, where the periodicity can be set by us for various agents individually. What we would not like is something that is executed as part of a pre/post step for each build. That would slow down all builds significantly. An added bonus would be if from the local maven repository one could delete only a configurable set of groupIds (e.g. artifacts related to our project..), instead of the entire maven repository.

Any information on the topics above is more than welcomed :)

Thx a lot!

Hi and thank you for your plugin!
I was wondering if you have any plans on adding support for Docker clean up, or maybe I have overseen the existing functionality?

I think Docker, unlike Maven or npm, requires a bit more graceful cleanup (e.g. with docker system prune ), and not just removal of some directories.

It would be a great feature to support Docker as well since now we have to do this manually and free up tens of gigabytes each time.

Is it possible to use this plugin to clean up multiple drives on Windows agents?
Our use case is that we have an "OS" drive and an "Agent" drive C: and D: respectively.
It appears that the plugin is only triggered when the D: drive needs free space cleared but not for C:.
We have caches from NuGet, Conda, npm, etc. filling up on the C: drive but the agent is unaware of this since it is located on the D: drive.
Is this something that would need to fundamentally change in the agent code or can it be added in this plugin?

Hi Team,

Please share if we have official procedure to setting up this plugin.

I have requirement for clearing .m2/repository and few in teamcity agent system with some time limits