]> git-server-git.apps.pok.os.sepia.ceph.com Git - ceph-build.git/commit
pull requests: rm "cron" settings 89/head
authorKen Dreyer <kdreyer@redhat.com>
Thu, 25 Jun 2015 14:40:30 +0000 (08:40 -0600)
committerKen Dreyer <kdreyer@redhat.com>
Thu, 25 Jun 2015 14:43:41 +0000 (08:43 -0600)
commit33bf14ecb187ba7af98414e4084864c52e495df7
tree594ea215eaeff1c569652fb5660fe2e4e8344208
parentbbaf5383b90e4e54371b02f8a232564832772569
pull requests: rm "cron" settings

From the Jenkins GitHub Pull Requests plugin docs on "useGitHubHooks":

  Checking this option will disable regular polling (cron) for changes
  in GitHub and will try to create a GitHub hook. Creating a GitHub hook
  requires that the user which is specified in the GitHub Pull Request
  Builder configuration has admin rights to the specified repository.

Based on the documentation above, since our PR jobs have "github-hooks:
true", the "cron" values have no effect and can be removed.
ceph-build-pull-requests/config/definitions/ceph-build-pull-requests.yml
ceph-deploy-pull-requests/config/definitions/ceph-deploy-pull-requests.yml
ceph-qa-suite-pull-requests/config/definitions/ceph-qa-suite-pull-requests.yml
jenkins-slave-chef-pull-requests/config/definitions/jenkins-slave-chef-pull-requests.yml
radosgw-agent-pull-requests/config/definitions/radosgw-agent-pull-requests.yml
teuthology-pull-requests/config/definitions/teuthology-pull-requests.yml