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

Implement option in GUI to disable checkpointing feature

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When running two or more unrelated concurrent builds of the same project in Jenkins, some of the builds do not complete until the first build has completed. This is caused by the publish-over-cifs plugin and we see the following message in the console logs of the slaves that are affected: Send build artifacts to a windows share is waiting for a checkpoint on CAD Conversions #1040 . It would be great if this checkpoint feature could be turned off on a per-project basis with an option like "Don't wait for other concurrent builds to complete"

        Attachments

          Activity

          Show
          whitlabell Gary Bell added a comment - see also: https://issues.jenkins-ci.org/browse/JENKINS-9913
          Hide
          slide_o_mix Alex Earl added a comment -

          Is this still an issue?

          Show
          slide_o_mix Alex Earl added a comment - Is this still an issue?
          Hide
          whitlabell Gary Bell added a comment -

          Hi Alex. The job that exhibited the underlying issue isn't really used much so we don't see concurrent builds any more. I'll try and reproduce it and report back. But in any case this ticket was an improvement suggestion, so I think that it would still be useful to have this feature as I believe the underlying problem is caused by individual plugins not using the correct process for checkpointing. Giving the User control over this at a project level is the best way to avoid hung executors until all plugins are updated.

          Show
          whitlabell Gary Bell added a comment - Hi Alex. The job that exhibited the underlying issue isn't really used much so we don't see concurrent builds any more. I'll try and reproduce it and report back. But in any case this ticket was an improvement suggestion, so I think that it would still be useful to have this feature as I believe the underlying problem is caused by individual plugins not using the correct process for checkpointing. Giving the User control over this at a project level is the best way to avoid hung executors until all plugins are updated.
          Hide
          whitlabell Gary Bell added a comment -

          I constructed an artificial test case to check this and I can no longer reproduce the problem using our current Jenkins v1.651.1 and Publish over cifs v0.3 plugin. This means that we no longer need the enhancement requested in this ticket. The enhancement may be generally useful however in the case where other plugins are misbehaving in a similar manner.

          Show
          whitlabell Gary Bell added a comment - I constructed an artificial test case to check this and I can no longer reproduce the problem using our current Jenkins v1.651.1 and Publish over cifs v0.3 plugin. This means that we no longer need the enhancement requested in this ticket. The enhancement may be generally useful however in the case where other plugins are misbehaving in a similar manner.

            People

            Assignee:
            slide_o_mix Alex Earl
            Reporter:
            whitlabell Gary Bell
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: