Mark Waite commented on Bug JENKINS-20569

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:

  1. Create a git repository with project/common/common-file, project/projectA/A-file, project/projectB/B-file, project/projectC/C-file
  2. For testing speed, I added a post-receive "hook" to the repository (see Kohsuke's "polling must die" blog post for the technique)
  3. Define a Jenkins job JENKINS-20569-projectA using that repository
  4. Add "Force polling using workspace" behavior to that project
  5. Add "Polling ignores commits in certain paths" to that project
  6. Define the exclusion as
    project/projectB/.*
    project/projectC/.*
    
  7. Commit a change to the repository outside the exclusion (like project/common/common-file), confirm projectA builds on next poll
  8. Commit a change to the repository inside the exclusions (like project/projectB/B-file), confirm projectA does not build on next poll
  9. Copy the JENKINS-20569-projectA job to JENKINS-20569-projectB, define the exclusion as
    project/projectA/.*
    project/projectC/.*
    
  10. Commit a change to the repository outside the exclusion (like project/common/common-file), confirm projectA and projectB build on next poll
  11. 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
  12. 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.

Reply via email to