[
https://issues.jenkins-ci.org/browse/JENKINS-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161519#comment-161519
]
Rainer Weinhold commented on JENKINS-6846:
------------------------------------------
+1
Same Problem: running nightly UI tests, which take about 3-4 hours to finish. I
want this to run only after an actual change, because running every midnight
will make the test-result-history kind of useless.
Therefore this is definitively a critical bug!
> Poll SCM with post-commit hook or by cron-definition
> ----------------------------------------------------
>
> Key: JENKINS-6846
> URL: https://issues.jenkins-ci.org/browse/JENKINS-6846
> Project: Jenkins
> Issue Type: Improvement
> Components: subversion
> Reporter: manthos
> Priority: Critical
>
> We have splitted some projects from one single job (doing build/test/analyse)
> to two jobs (one only for build and second one for test/analyse). The first
> job polls scm every 10 minutes, the second one polls scm at midnight.
> Now we defined a svn post-commit hook for CI, so we don't have to poll every
> 10 minutes for changes. This is fine for the first job, but the second one
> now starts too (because 'Poll SCM' is checked). For now it is not possible to
> define a job, that polls scm due a cron-definition and another one that is
> triggered by post-commit hook.
> It would be nice to have an additional option like "ignore post-commit hook".
> So 'Poll SCM' could be checked and triggered by cron-definition and not by
> post-commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
