Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-23377

cron driven backups never happen

    XMLWordPrintable

Details

    Description

      Manual backup works fine, Cron driven backups just never happen. Don't see any msgs in the jenkins log.

      Attachments

        Issue Links

          Activity

            danielbeck Daniel Beck added a comment -

            What's the workaround? Many Jenkins instances cannot just be restarted due to many long-running builds.

            danielbeck Daniel Beck added a comment - What's the workaround? Many Jenkins instances cannot just be restarted due to many long-running builds.
            ceilfors Wisen Tanasa added a comment -

            Looks related to JENKINS-16714?

            ceilfors Wisen Tanasa added a comment - Looks related to JENKINS-16714 ?
            pbro 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.

            pbro 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.
            hano2 ho Han added a comment -

            If it is not working directly, try to restart jenkins.

            hano2 ho Han added a comment - If it is not working directly, try to restart jenkins.
            teilo James Nord added a comment -

            may be fixed by JENKINS-28683 in in 2.129 or higher when it is available.

            teilo James Nord added a comment - may be fixed by JENKINS-28683 in in 2.129 or higher when it is available.

            People

              tofuatjava Thomas Fürer
              casadelgato John Lussmyer
              Votes:
              5 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated: