[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Jesse Glick Component/s: workflow-scm-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Jesse Glick resolved as Not A Defect As designed. Polling behavior is done in accordance with the SCMs used in the last successful build. Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Patrick Wolf commented on JENKINS-42749 Re: Polling configuration is not updated until next successful build 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar commented on JENKINS-42749 Re: Polling configuration is not updated until next successful build 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 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Patrick Wolf commented on JENKINS-42749 Re: Polling configuration is not updated until next successful build 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? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Emilio Escobar 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' Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar updated an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Change By: Emilio Escobar 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' Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42749) Polling configuration is not updated until next successful build
Title: Message Title Emilio Escobar created an issue Jenkins / JENKINS-42749 Polling configuration is not updated until next successful build Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2017/Mar/14 10:43 AM Priority: Minor Reporter: Emilio Escobar 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' Add Comment
