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

Cron based jobs are no longer triggered

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Cannot Reproduce
    • Labels:
      None
    • Environment:
      Centos 6.6
      Jenkins 1.621

      See attachment system_info.txt for full dump.
    • Similar Issues:

      Description

      This issue was originally opened off the stash-build-plugin but after further investigation we found that the cron system of core jenkins stop working as expected.

      Approximately weekly as of now with the introduction of more cron based plugins like stash-pullrequest-builder; the cron system stops working. With jenkins_debug_10072015.tar attachment; the system indicated for most jobs a last time polling of around 9:05-9:10am. All polling cron type jobs no longer responded.

      Very close to JENKINS-25704; almost a duplicate.

        Attachments

        1. debug_sockets.txt
          14 kB
        2. jenkins_cron_problem-10-7-2015.zip
          3.18 MB
        3. jenkins_logs.txt
          75 kB
        4. jenkins_threaddump_1.txt
          66 kB
        5. jenkins_threaddump_2.txt
          67 kB
        6. screenshot-1.png
          screenshot-1.png
          3 kB
        7. screenshot-2.png
          screenshot-2.png
          16 kB
        8. support_2015-09-20_20.18.47.zip
          2.00 MB
        9. system_info.txt
          10 kB
        10. triggers_fine_log_10_8_2015.txt
          47 kB

          Issue Links

            Activity

            Hide
            jwstric2 Jonathan Strickland added a comment -

            kang hao

            Kang,

            I would recommend opening up a new issue with your problem. If the upgrade of the Stash Trigger Plugin is causing issues, please note this in the new issue (to and from version)

            Regards,
            Jonathan

            Show
            jwstric2 Jonathan Strickland added a comment - kang hao Kang, I would recommend opening up a new issue with your problem. If the upgrade of the Stash Trigger Plugin is causing issues, please note this in the new issue (to and from version) Regards, Jonathan
            Hide
            vzhang Vivian Zhang added a comment -

            kang hao I have the exact issue as you do, that is the stash pull request plugin causes the cron based jobs to be triggered randomly. In addition, these jobs also get triggered when Stash becomes unavailable, such as during backup. Hence these jobs are being triggered every day at the beginning of the Stash backup, and all of them failed of course. This must have caused by the fix in the new release. They should be refixed to not introduce new bug. Hence it's better to continue use this same issue id to complete the resolution. Did you open a new issue for it? Can I have the new issue id?

            Show
            vzhang Vivian Zhang added a comment - kang hao I have the exact issue as you do, that is the stash pull request plugin causes the cron based jobs to be triggered randomly. In addition, these jobs also get triggered when Stash becomes unavailable, such as during backup. Hence these jobs are being triggered every day at the beginning of the Stash backup, and all of them failed of course. This must have caused by the fix in the new release. They should be refixed to not introduce new bug. Hence it's better to continue use this same issue id to complete the resolution. Did you open a new issue for it? Can I have the new issue id?
            Hide
            jags Jagadish added a comment -

            Issue is still persisting.Entire Jenkins core trigger system has been affected due to stash pull request builder plugin :|

            Show
            jags Jagadish added a comment - Issue is still persisting.Entire Jenkins core trigger system has been affected due to stash pull request builder plugin :|
            Hide
            jbochenski Jakub Bochenski added a comment -

            This issue has been automatically closed because of inactivity. Please reopen it if you think it's still valid

            Show
            jbochenski Jakub Bochenski added a comment - This issue has been automatically closed because of inactivity. Please reopen it if you think it's still valid
            Hide
            proski Pavel Roskin added a comment -

            I see that the socket timeout and the request timeout were introduced in the same PR. Does anybody know a reason why request timeouts are needed in presence of socket timeouts? Running HTTP requests in separate threads adds a lot of complexity. Other plugins doesn't do it. I assume every request should use a limited number of packets sent over the socket, so the socket timeout should put a limit on the request duration.

            I'm going to move requests back to the main thread unless I hear any objections.

            Show
            proski Pavel Roskin added a comment - I see that the socket timeout and the request timeout were introduced in the same PR. Does anybody know a reason why request timeouts are needed in presence of socket timeouts? Running HTTP requests in separate threads adds a lot of complexity. Other plugins doesn't do it. I assume every request should use a limited number of packets sent over the socket, so the socket timeout should put a limit on the request duration. I'm going to move requests back to the main thread unless I hear any objections.

              People

              Assignee:
              jwstric2 Jonathan Strickland
              Reporter:
              jwstric2 Jonathan Strickland
              Votes:
              3 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: