Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: thinbackup-plugin
-
Labels:
-
Environment:Ubuntu 12.04.4 LTS, Jenkins 1.559, ThinBackup 1.7.4
-
Similar Issues:
Description
Manual backup works fine, Cron driven backups just never happen. Don't see any msgs in the jenkins log.
Attachments
Issue Links
- depends on
-
-
- Resolved
-
Activity
If it is not working directly, try to restart jenkins.
ho Han
added a comment - If it is not working directly, try to restart jenkins. This still happened to me with Jenkins ver. 2.73.3, Windows Server 2012r2.
Created a cron expression: 0 22 * * 1-5
or: H 22 * * 1-5 (as jenkins suggests to use "H"), the scheduled backup never happened. It worked only when triggered manually.
After posting this comment, I updated Jenkins to ver. 2.89.2 (there were some security updates pending, and it was recommended to update Jenkins (LTS) from 2.73.2 to 2.89.2) and now the scheduled backup works according to the cron expression.
Paolo Brocco
added a comment - - edited This still happened to me with Jenkins ver. 2.73.3, Windows Server 2012r2.
Created a cron expression: 0 22 * * 1-5
or: H 22 * * 1-5 (as jenkins suggests to use "H"), the scheduled backup never happened. It worked only when triggered manually.
After posting this comment, I updated Jenkins to ver. 2.89.2 (there were some security updates pending, and it was recommended to update Jenkins (LTS) from 2.73.2 to 2.89.2) and now the scheduled backup works according to the cron expression. Looks related to JENKINS-16714?
Wisen Tanasa
added a comment - Looks related to JENKINS-16714 ? What's the workaround? Many Jenkins instances cannot just be restarted due to many long-running builds.
may be fixed by
JENKINS-28683in in 2.129 or higher when it is available.