The disk space on freme-dev is full. This led to strange errors so I deleted 50 GB of old broker builds from Jenkins as first aid. But the problem will come back so we need to
1) We should configure all Jenkins jobs not to keep more then 50 builds. Jenkins used about 90 GB before I deleted the broker builds.
2) For some reason or nexus uses 100 GB of disk space. I guess it keeps a lot of old snapshot artifacts.
3) We have 1000 GB of disk space and I can only explain what happened I checked these and they do not use a lot of disk space:
* MySQL database storage location
* /home directory (including FREME workspace and local maven directory)
* FREME installation
* Webserver directory /var/www
I deleted 700 GB of Jenkins log files. So the problem is solved. It might happen again in a few month but it seems easier to me to delete the logs again then to fix Jenkins log strategy.
The disk space on freme-dev is full. This led to strange errors so I deleted 50 GB of old broker builds from Jenkins as first aid. But the problem will come back so we need to
1) We should configure all Jenkins jobs not to keep more then 50 builds. Jenkins used about 90 GB before I deleted the broker builds. 2) For some reason or nexus uses 100 GB of disk space. I guess it keeps a lot of old snapshot artifacts. 3) We have 1000 GB of disk space and I can only explain what happened I checked these and they do not use a lot of disk space: * MySQL database storage location * /home directory (including FREME workspace and local maven directory) * FREME installation * Webserver directory /var/www