Discard old builds not working

[Arpit Gupta]

Hi

I am running version 1.595 and running into issues where old builds are not being discarded. I had previously set both Days to keep builds and max number of builds to keep. What i noticed is that days to keep old builds was not being respected.

Thinking there might be an issue when providing both i emptied out max number of builds to keep and only set days to keep builds to 2. However when i see all the builds available i am seeing a builds that are more than 2 days old.

I checked jenkins service logs and i cant find anything interesting in it. Wanted to check here before i logged a bug in case there is something i am missing.

CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You.

[Daniel Beck]

Old builds get discarded after a new build finishes. It's not immediate.

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ee63f599-68f8-417f-bb2d-855853457442%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Arpit Gupta]

I have builds that have finished today(this morning) and as far out as 5 days.

I had made the configuration change yesterday.
--
Arpit

> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/33cjrcyLb-w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4C949A1D-FE66-4347-9BCD-DFA4C606504B%40beckweb.net.

> For more options, visit https://groups.google.com/d/optout.
>

> --

[Daniel Beck]

Maybe some of the builds have a log badge, indicating they're kept for a reason?

To find out why log rotation doesn't delete some builds, go to /log URL and create a log recorder for the logger hudson.tasks.LogRotator at level FINER. Run a build for the affected jog. Check the log recorder you created for diagnostic information.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/BFBC34DF-A78C-4CF5-93A4-BE6CF644B215%40hortonworks.com.

[Arpit Gupta]

You are right it looks like there are 242 builds marked to keeping. I will clean that up and see if that resolves the issue.

--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/F628C244-E3B1-4605-8357-DD6F3C1163A6%40beckweb.net.

[Arpit Gupta]

Looks like there is still a problem

I see the following in the logs

Running the log rotation for hudson.model.FreeStyleProject@c59337d[JOB_NAME] with numToKeep=-1 daysToKeep=1 artifactNumToKeep=-1 artifactDaysToKeep=-1

When i go to the job/JOB_NAME/rssAll

i see builds that are more than 1 day old.

For example

JOB_NAME #51544 (stable)

January 14, 2015 at 6:07 AM

And when i click that job it does not have keep this build for ever set.

Also i do not see any messages in the log that say the following:

JOB_NAME #BUILD_NUMBER is not to be removed or purged of artifacts because it’s marked as a keeper

in the log after it says running log rotation. I waited about 10 mins since that log that it was doing log rotation was printed and it still had not cleared up.

--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/C704BA33-E3E9-4C42-9288-990F88BD7092%40hortonworks.com.

For more options, visit https://groups.google.com/d/optout.

[Arpit Gupta]

Any thoughts? Or any other logs i can check that will provide me more info.

Thanks

--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7687C264-D421-459D-8821-7A7A5E2B196F%40hortonworks.com.

[Arpit Gupta]

More weirdness.

I installed the discard old builds plugin and when i run that it will clean up builds that are older than 1 day. But when using the default options it leaves them.

I had run it yesterday morning and had to run it again today to clean up artifacts again. Also this seems to be happening only of one job. There are other jobs that are getting cleaned up using the inbuilt feature.

Post build action of discard old build plugin does not work very well when there are concurrent builds running. It seems to spend a lot of time check pointing other builds. If any one knows a way one can get that post build action to run faster when there are concurrent builds i can just use that.

Thanks
--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/

[Arpit Gupta]

Ended up logging https://issues.jenkins-ci.org/browse/JENKINS-26576 as it seems like a bug to me.

--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/F8CC1961-79AB-4F89-8795-32566113ABCD%40hortonworks.com.