We began to notice that the plug-in creates records of changes for no apparent reason for Job Configuration History Plugin 2.24 on Jenkins ver. 2.176.3, which ultimately led to exhaustion inode on the disk array.
I think it is necessary to modify the plugin, for the absence of empty saves.
We began to notice that the plug-in creates records of changes for no apparent reason for Job Configuration History Plugin 2.24 on [Jenkins ver. 2.176.3|https://jenkins.io/], which ultimately led to exhaustion inode on the disk array.
I think it is necessary to modify the plugin, for the absence of empty saves.