[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Trey Duskin commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Thanks. I did some more experimentation and I think my issue is specific to merge commits. My new bug is here: https://issues.jenkins-ci.org/browse/JENKINS-23606 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Trey Duskin could you open a separate bug report for your use case? This bug report is focused on excluded regions and on the implicit requirement that include and exclude regions implicitly require "Force polling using workspace". As far as I can tell, the exclude regions are working as expected (at least as described by this bug report) so long as "Force polling using workspace" is enabled. 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Trey Duskin commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Oh, and to be clear, I am only using Included Paths. I am not specifying any Excluded Paths. 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Trey Duskin commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered My case differs from your example in a few ways. First, my jobs are set up to only check out a specific branch (e.g. '*/dev' instead of 'master'). There could be other commits in the history which are going into other branches, but I don't care about those and I only want to watch for commits in a specific branch which have changes in specific paths. Second, we are using git-flow style development, and so most of the commits are merges of feature branches into the the branch I am watching. If I look at the git polling log on a job which should not have been triggered, I can see it trying to get a history between the last build revision and the commit which triggered the poll (we are using web-hooks from our git provider, Assembla). However, if I repeat the command it uses to get the commit history (e.g. /usr/bin/git log --full-history --no-abbrev --format=raw -M -m --raw ff0ec94a066cee23c13faa16b38b247911cd5ee7..f47993565f701a4f28174c4ea81f35d0e1103590), I see the commits i expect, but weirdly, I also see a commit listed twice - once containing the paths which the commit affected, and another (same hash) which contain paths from some other commit in some other branch! Is this a problem with my git provider? 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Trey Duskin I think you're having some other issue, not what is described in this bug report. When I enable "Force polling from workspace", I see the expected exclusion behavior from the jobs I've created. Here are the steps I took, and the results I observed: Create a git repository with project/common/common-file, project/projectA/A-file, project/projectB/B-file, project/projectC/C-file For testing speed, I added a post-receive "hook" to the repository (see Kohsuke's "polling must die" blog post for the technique) Define a Jenkins job JENKINS-20569-projectA using that repository Add "Force polling using workspace" behavior to that project Add "Polling ignores commits in certain paths" to that project Define the exclusion as project/projectB/.* project/projectC/.* Commit a change to the repository outside the exclusion (like project/common/common-file), confirm projectA builds on next poll Commit a change to the repository inside the exclusions (like project/projectB/B-file), confirm projectA does not build on next poll Copy the JENKINS-20569-projectA job to JENKINS-20569-projectB, define the exclusion as project/projectA/.* project/projectC/.* Commit a change to the repository outside the exclusion (like project/common/common-file), confirm projectA and projectB build on next poll Commit a change to the repository inside the exclusions (like project/projectB/B-file), confirm projectB builds, and projectA does not build on next poll Commit a change to the repository inside the exclusions (like project/projectB/A-file), confirm projectB does not build, and projectA builds on next poll So long as I use "Force polling using workspace", and use a regular _expression_ to match the exclusion, then the exclusion works the way I expect. Can you provide more details on the failure case you found? 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Trey Duskin commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered We are having this issue as well with Included Paths in our Git jobs. We have set up Included Paths for all our jobs, and each job points to a different path in our git repo. When there is a commit which only touches one of these paths, all of our jobs are getting triggered. I have enabled "Force Polling from Workspace" for all of the jobs, but this doesn't seem to help. Any idea when this issue might be addressed? 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Yes, included/excluded regions require "Force polling using workspace". You're welcome to submit a pull request with an improvement to the help, or with forcible enablement of using a workspace for polling. Currently there are pull requests under review and discussion around the issue, including https://github.com/jenkinsci/git-plugin/pull/93 and https://github.com/jenkinsci/git-plugin/pull/89 . Both pull requests may need further work before they can be pulled, and they may be mutually exclusive, but you could consider them . Neither of them do precisely what you've proposed, but they may give you an idea where to investigate in the code. 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Alexander Uvizhev commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered So Included/Excluded Regions doesn't work without "Force polling using workspace", is it? If so, should the first option at least mention it or even forcibly enable the second one? 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] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Liya Katz commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I agree that new features should be be "promoted", but in this case they cause other important features to stop working. You have to mention this limitation when include/exclude regions are chosen. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite updated JENKINS-20569 Polling with excluded regions don't prevent job triggered Change By: Mark Waite (17/Dec/13 4:30 AM) Priority: Blocker Minor 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I disagree that polling using workspace should be the default. Polling using workspace is significantly slower than remote polling. When we have a new feature (like fast remote polling support) that significantly improves performance, it is better to make the faster performance the default so that new users and new jobs have the benefit of the faster performance without any special actions. It is unfortunate that fast remote polling does not work in all cases, but I think it is still better to use that as the default rather than polling using workspace by default, then allowing users the option to execute faster. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Liya Katz commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Polling using workspace should be the default behavior (backward compatibility!) and "remote Polling" should be an option 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Confirmed this works for me. Thanks for the help! 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Select the "Force polling using workspace" option with the "Add" button in the Git plugin section of the job configuration page. That disables 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Ok, I get it. So how do i get the behavior back to not do remote polling and make it work like 1.4.0? 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Nicolas De Loof commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered @Joe change is that remote polling is the default behavior now - this makes polling a lightweight process. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Erik Cokeley edited a comment on JENKINS-20569 Polling with excluded regions don't prevent job triggered I also need the Included Regions. This is failing for me and many builds are being kicked off; I'm not sure if all my builds within the git and branch but at least many. What version has Included Region (or excluded region) working? 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Erik Cokeley commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I also need the Included Regions. This is failing for me. What version has Included Region (or excluded region) working? 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I don't understand that. This feature was working fine in the 1.4.0 git plugin. Something must have been broken. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Nicolas De Loof commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered This happens due to remote polling. This is also the case with 1.x when remote polling is set By nature, remote polling only can compare remote HEAD with last build sha1, not consider commit filters 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich edited a comment on JENKINS-20569 Polling with excluded regions don't prevent job triggered I am having the exact same issue with included regions not being honored. Every job on the branch that git sends gets built regardless of what's in the included regions. Was on 1.4 before this and it was working great. I have to downgrade to 1.4.0 because of this bug. I can't have the entire project building every time one file changes. Please fix this ASAP. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I am having the exact same issue with included regions not being honored. Every job on the branch that git sends gets built regardless of what's in the included regions. Was on 1.4 before this and it was working great. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Liya Katz updated JENKINS-20569 Polling with excluded regions don't prevent job triggered Change By: Liya Katz (19/Nov/13 7:48 AM) Priority: Critical Blocker 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Anthony FLORANT created JENKINS-20569 Polling with excluded regions don't prevent job triggered Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 13/Nov/13 4:42 PM Description: I've three jobs that trigger git with the same repository and branch. In then Excluded Regions I add specific folders for each job. Example: project/common project/projectA project/projectB project/projectC If I made change on projectB folder, all the three job are build. Environment: Git plugin 2.0 Project: Jenkins Priority: Critical Reporter: Anthony FLORANT 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Sonia Shepherd commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered This feature worked at our location in the 1.4 version of the plugin. When I upgraded to the 2.0 version of the plugin, I experienced the issue listed above. The value that was formerly in 'Included Regions' was still present...but, it didn't result in the polling to be specific to the directory. So, I downgraded back to the 1.4 version of the plugin in hopes of getting the functionality back. Unfortunately, when I downgraded, the value present in the 'Included Regions' disappeared. Yikes. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Sonia, the 2.0 release was a major release which included changes to the job definition XML file. Those changes make the new data values unreadable by the old plugin. You will probably need to restore an old copy of the job definition XML file (jobs//config.xml). 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I attempted various combinations of patterns and could not find any pattern which would exclude all the changes in a subdirectory (like project/common). The behavior was the same for the JGit and the command line implementations. I'm reasonably confident this worked in the past, since we used it with older versions 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/groups/opt_out.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Anthony FLORANT commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Yesterday, I downgrade from 2.0 to 1.5. Exculded regions work as expected but included regions as no effect. If I set "projector/.*\.cpp" in the included regions and I changed a .txt in git, a job was triggered... 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/groups/opt_out.
