{"action":"closed","issue":{"url":"https://api.github.com/repos/jenkinsci/docker-plugin/issues/111","labels_url":"https://api.github.com/repos/jenkinsci/docker-plugin/issues/111/labels{/name}","comments_url":"https://api.github.com/repos/jenkinsci/docker-plugin/issues/111/comments","events_url":"https://api.github.com/repos/jenkinsci/docker-plugin/issues/111/events","html_url":"https://github.com/jenkinsci/docker-plugin/issues/111","id":47303325,"number":111,"title":"Git SCM \"Included Regions\" broken with docker-plugin 0.7","user":{"login":"tehranian","id":297015,"avatar_url":"https://avatars.githubusercontent.com/u/297015?v=3","gravatar_id":"","url":"https://api.github.com/users/tehranian","html_url":"https://github.com/tehranian","followers_url":"https://api.github.com/users/tehranian/followers","following_url":"https://api.github.com/users/tehranian/following{/other_user}","gists_url":"https://api.github.com/users/tehranian/gists{/gist_id}","starred_url":"https://api.github.com/users/tehranian/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tehranian/subscriptions","organizations_url":"https://api.github.com/users/tehranian/orgs","repos_url":"https://api.github.com/users/tehranian/repos","events_url":"https://api.github.com/users/tehranian/events{/privacy}","received_events_url":"https://api.github.com/users/tehranian/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2014-10-30T17:42:11Z","updated_at":"2015-04-23T22:41:59Z","closed_at":"2015-04-23T22:41:59Z","body":"Hi there,\r\n\r\nWe hit an issue while transitioning our build jobs over from static slave VMs to dynamically provisioned Docker containers... Using Docker containers seems to break the functionality of restricting SCM-triggered builds to a certain path in the repo.\r\n\r\nEx:\r\n* We have a Git repo with many subdirectories\r\n* There are several Jenkins jobs defined, each job building a separate module from that repo. The modules themselves live in isolated subdirectories in that repo.\r\n* Since it's wasteful to rebuild \"module A\" every time **anything** in the repo is changed, we only want \"module A\" to be rebuilt when files under the \"moduleA\" subdirectory are changed. Like while for \"module B\".\r\n* To that end, we use the \"Included Regions\" functionality of the Git SCM plugin and define a file path (via regex) for each job such that each job only gets triggered when files under the respective directory of that module are changed.\r\n\r\nThis worked well with static slaves. For some reason, this seems to be broken when using dynamically provisioned Docker containers. :(\r\n\r\nFWIW - We've currently on the following:\r\n* Jenkins 565.2\r\n* Docker plugin 0.7\r\n* Docker 1.1.2\r\n"}}