Want includedRegions feature analogous to excludedRegions feature

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      It often happens (at least for me!) that in order to do a build I must check out an svn tree, say,

      /trunk/myapp

      but I don't want to actually trigger the build unless certain subsets of that tree have changed, e.g.

      /trunk/myapp/dir1
      /trunk/myapp/library/dira
      /trunk/myapp/library/dirb

      I would like to have a feature analogous to excludedRegions where I could specify these paths as includedRegions and the build would only be triggered if a checkin occurred that modified something in the includedRegions.

      If both excludedRegions and includedRegions were specified, it would work in the obvious way, i.e. a change would have to have at least one path that was in includedRegions, but not in excludedRegions.

            Assignee:
            pgweiss
            Reporter:
            pgweiss
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: