[JIRA] [git-plugin] (JENKINS-31828) Specifiying multiple refspecs in git-plugin will make polling for changes make fail always
Title: Message Title
Sven S. updated an issue
Jenkins / JENKINS-31828
Specifiying multiple refspecs in git-plugin will make polling for changes make fail always
Change By:
Sven S.
We use the git notes functionality to add notes during build and for many other things. We have to fetch them from the repository next to the code related things, so we specified this refspec: {noformat}+refs/heads/*:refs/remotes/origin/* +refs/notes/*:refs/notes/*{noformat}Checkout, and fetch works as before, but as soon as we want to use the scm-polling feature, no changes will be detected. Viewing the SCM poll protocol will give:{noformat}Started on Dec 1, 2015 3:02:00 PMUsing strategy: Default[poll] Last Built Revision: Revision cefd54a11d3b85981409065ebb073a5e5715b36c (refs/remotes/origin/master)using GIT_SSH to set credentials Jenkins CI System Login for GIT registered at Administrator root account on gitlab > git --version # timeout=10 > git -c core.askpass=true ls-remote -h ssh://git@/jenkins-test.git # timeout=10Found 2 remote heads on ssh://git@/jenkins-test.gitIgnoring refs/heads/testBranch as it doesn't match configured refspecsIgnoring refs/heads/master as it doesn't match configured refspecsDone. Took 0.63 secNo changes{noformat}In the case we remove the additional refspec (using only {noformat}+refs/heads/*:refs/remotes/origin/*{noformat}) and use only one, everything works as expected:{noformat}Started on Dec 1, 2015 2:51:00 PMUsing strategy: Default[poll] Last Built Revision: Revision cefd54a11d3b85981409065ebb073a5e5715b36c (refs/remotes/origin/master)using GIT_SSH to set credentials Jenkins CI System Login for GIT registered at Administrator root account on gitlab > git --version # timeout=10 > git -c core.askpass=true ls-remote -h ssh://git@***/jenkins-test.git # timeout=10Found 2 remote heads on ssh://git@/jenkins-test.git[poll] Latest remote head revision on refs/heads/master is: cefd54a11d3b85981409065ebb073a5e5715b36c - already built by 51Done. Took 0.56 secNo changes{noformat}There seems to be a problem with refspec parsing / matching if there are multiple. We are using Jenkins v. 1.638 and git-plugin 2.4.0
Add Comment
[JIRA] [git-plugin] (JENKINS-31828) Specifiying multiple refspecs in git-plugin will make polling for changes make fail always
Title: Message Title
Sven S. updated an issue
Jenkins / JENKINS-31828
Specifiying multiple refspecs in git-plugin will make polling for changes make fail always
Change By:
Sven S.
We use the git notes functionality to add notes during build and for many other things. We have to fetch them from the repository next to the code related things, so we specified this refspec: {noformat} +refs/heads/*:refs/remotes/origin/* +refs/notes/*:refs/notes/* {noformat} Checkout, and fetch works as before, but as soon as we want to use the scm-polling feature, no changes will be detected. Viewing the SCM poll protocol will give:{noformat}Started on Dec 1, 2015 3:02:00 PMUsing strategy: Default[poll] Last Built Revision: Revision cefd54a11d3b85981409065ebb073a5e5715b36c (refs/remotes/origin/master)using GIT_SSH to set credentials Jenkins CI System Login for GIT registered at Administrator root account on gitlab > git --version # timeout=10 > git -c core.askpass=true ls-remote -h ssh://git@/jenkins-test.git # timeout=10Found 2 remote heads on ssh://git@/jenkins-test.gitIgnoring refs/heads/testBranch as it doesn't match configured refspecsIgnoring refs/heads/master as it doesn't match configured refspecsDone. Took 0.63 secNo changes{noformat}In the case we remove the additional refspec (using only {noformat} +refs/heads/*:refs/remotes/origin/* {noformat} ) and use only one, everything works as expected:{noformat}Started on Dec 1, 2015 2:51:00 PMUsing strategy: Default[poll] Last Built Revision: Revision cefd54a11d3b85981409065ebb073a5e5715b36c (refs/remotes/origin/master)using GIT_SSH to set credentials Jenkins CI System Login for GIT registered at Administrator root account on gitlab > git --version # timeout=10 > git -c core.askpass=true ls-remote -h ssh://git@***/jenkins-test.git # timeout=10Found 2 remote heads on ssh://git@/jenkins-test.git[poll] Latest remote head revision on refs/heads/master is: cefd54a11d3b85981409065ebb073a5e5715b36c - already built by 51Done. Took 0.56 secNo changes{noformat}There seems to be a problem with refspec parsing / matching if there are multiple.
Add Comment
[JIRA] [git-plugin] (JENKINS-31828) Specifiying multiple refspecs in git-plugin will make polling for changes make fail always
Title: Message Title Sven S. created an issue Jenkins / JENKINS-31828 Specifiying multiple refspecs in git-plugin will make polling for changes make fail always Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 01/Dec/15 2:03 PM Labels: plugin Priority: Major Reporter: Sven S. We use the git notes functionality to add notes during build and for many other things. We have to fetch them from the repository next to the code related things, so we specified this refspec: +refs/heads/:refs/remotes/origin/ +refs/notes/:refs/notes/ Checkout, and fetch works as before, but as soon as we want to use the scm-polling feature, no changes will be detected. Viewing the SCM poll protocol will give: Started on Dec 1, 2015 3:02:00 PM Using strategy: Default [poll] Last Built Revision: Revision cefd54a11d3b85981409065ebb073a5e5715b36c (refs/remotes/origin/master) using GIT_SSH to set credentials Jenkins CI System Login for GIT registered at Administrator root account on gitlab > git --version # timeout=10 > git -c core.askpass=true ls-remote -h ssh://git@/jenkins-test.git # timeout=10 Found 2 remote heads on ssh://git@/jenkins-test.git
[JIRA] [blamesubversion-plugin] (JENKINS-21154) Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized-trigger-plugin will lead to a non working pipeline
Title: Message Title Sven S. updated an issue Jenkins / JENKINS-21154 Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized-trigger-plugin will lead to a non working pipeline Change By: Sven S. Summary: Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build -trigger-plugin will lead to a non working pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blamesubversion-plugin] (JENKINS-21154) Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build will lead to a non working pipeline
Title: Message Title Sven S. updated an issue Jenkins / JENKINS-21154 Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build will lead to a non working pipeline Change By: Sven S. Summary: Usage of UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 conjunction with parameterized build will lead to a non working pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. edited a comment on JENKINS-21154 Re: UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 The problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken. After further investigations, I found out, this problem can be temporary fixed by removing the UpDownStreamNumberSychronizedNotify and then restarting the jenkins itself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. edited a comment on JENKINS-21154 Re: UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 Teh The problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. updated an issue Jenkins / JENKINS-21154 UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 Change By: Sven S. Component/s: parameterized-trigger-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. commented on JENKINS-21154 Re: UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 Teh problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [multiple-scms-plugin] (JENKINS-26734) Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Title: Message Title Sven S. commented on JENKINS-26734 Re: Subversion Plugin 2.5 is incompatible with Multiple SCM plugin Same problem here with 1.638 reverted to 2.4.5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
