[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
pmv commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name @Jean Blanchard - you are correct. 2.3.5 did change behavior and seemed to cover more of our use case than 2.3.4, but yes, it seems your patches are still needed. I've voted for your tickets. Also, for what it's worth, I have been running a SNAPSHOT version with your changes on our Jenkins instance with 1000s of jobs and haven't seen any issues. Thanks for the patches - looking forward to seeing them integrated into future releases. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Jean Blanchard commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name Actually it's not. Created JENKINS-27349 for it to have proper tracking. Also created related issues (that I also fixed in my original PR): JENKINS-27351 and JENKINS-27352. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
pmv commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name FYI for any others searching Jira - in my testing the issue Antoine identifies 3 comments above and Jean created the pull request for is no longer an issue in version 2.3.5 of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Jean Blanchard commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name I created a pull request [1] to address the issue mentioned by Antoine Morisseau (polling should take the default value of a param, not the one from the last build). It also fixes the commit notification for those parametrized jobs. [1] https://github.com/jenkinsci/git-plugin/pull/293 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
SCM/JIRA link daemon commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/75e4e6c2282e069bd26fbce0ead19c1c5b722c04 Log: [FIXED JENKINS-20427] [FIXED JENKINS-14276] expanded vars in branch spec for remote polling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Antoine Morisseau commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name Wonderful ! It's still not working ! Well... it almost work... The parameter variable is resolved. But it doesn't retrieve the proper default value. It retrieve the previous value if it was define by an user. user case : Let's say i have a choice parameter : branche v1 branche v2 master the parameter variable is git_branche_v the default value is ** in the branch specifier is set at */${GIT_BRANCHE_V} If a dev do a git push in branche v1 the scm polling use /*. then if a user manually call the build and select branche v1 the scm polling use */branche v1. And then if a dev do a git push in branche v2 the scm polling use */branche v1. It seems that the variable is not reset properly. or maybe the workspace is not reset. any workaround ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Mark Waite closed JENKINS-14276 as Fixed Git SCM-polling doesn't work when using a parametrized branch-name Fix included in git plugin 2.3.1, released 29 Nov 2014 Change By: Mark Waite (29/Nov/14 1:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Mark Waite commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name The change has been cherry-picked into the branch for the next release of git plugin 2.3 (for example, 2.3.1) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Mark Waite resolved JENKINS-14276 as Fixed Git SCM-polling doesn't work when using a parametrized branch-name Change By: Mark Waite (22/Nov/14 4:00 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Kristofer Lundgren reopened JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name I would really appreciate if you (Mark) applied this patch to git plugin 2.3 as well. Change By: Kristofer Lundgren (21/Nov/14 11:09 AM) Resolution: Fixed Status: Closed Reopened Assignee: Nicolas De Loof Mark Waite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Kristofer Lundgren commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name Bug still exist in git plugin 2.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.