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

Polling configuration is not updated until next successful build

    Details

    • Similar Issues:

      Description

      Polling configuration is not updated until next successful build. Thus if a polling is failing because is trying to reuse a workspace for polling (in an ephemeral node), any configuration change won't be effective until successful manual trigger.

      A pipeline will try to reuse the workspace if has configured the branch like * /releases/ *, or is using an extension like 'AuthorInChangelog'

       

        Attachments

          Activity

          Hide
          hrmpw Patrick Wolf added a comment -

          I don't understand this description, Emilio Escobar .  Is this for a multibranch pipeline or a standalone pipeline? Is this git, svn, github, bitbucket?  What are the replication steps?

          Show
          hrmpw Patrick Wolf added a comment - I don't understand this description, Emilio Escobar .  Is this for a multibranch pipeline or a standalone pipeline? Is this git, svn, github, bitbucket?  What are the replication steps?
          Hide
          escoem Emilio Escobar added a comment -

          Patrick Wolf git related (git, github and bitbucket)

          Configure an SCM with the extension AuthorInChangelog and use an ephemeral node (docker?). The polling will be performed reusing the workspace. As the node has been removed, the polling will fail.

          Then, try to remove the AuthorInChangelog from the SCM but the polling will still fail because will try to reuse the workspace.

          It will happen until you rebuild the job successfully

          Show
          escoem Emilio Escobar added a comment - Patrick Wolf git related (git, github and bitbucket) Configure an SCM with the extension AuthorInChangelog and use an ephemeral node (docker?). The polling will be performed reusing the workspace. As the node has been removed, the polling will fail. Then, try to remove the AuthorInChangelog from the SCM but the polling will still fail because will try to reuse the workspace. It will happen until you rebuild the job successfully
          Hide
          hrmpw Patrick Wolf added a comment -

          Emilio Escobar this isn't related to Pipeline is it? This should be true for any polling on an ephemeral node.

          In Pipeline you could check the author directly in the Pipeline and skip sections or the entire Pipeline based on the author rather than relying on workspace polling.

          Show
          hrmpw Patrick Wolf added a comment - Emilio Escobar this isn't related to Pipeline is it? This should be true for any polling on an ephemeral node. In Pipeline you could check the author directly in the Pipeline and skip sections or the entire Pipeline based on the author rather than relying on workspace polling.
          Hide
          jglick Jesse Glick added a comment -

          As designed. Polling behavior is done in accordance with the SCMs used in the last successful build.

          Show
          jglick Jesse Glick added a comment - As designed. Polling behavior is done in accordance with the SCMs used in the last successful build.

            People

            • Assignee:
              Unassigned
              Reporter:
              escoem Emilio Escobar
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: