[
https://issues.jenkins-ci.org/browse/JENKINS-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=155875#comment-155875
]
Lars Kruse edited comment on JENKINS-1682 at 2/24/12 10:40 AM:
---------------------------------------------------------------
We have implemented this feature in the ClearCase UCM plugin:
https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+UCM+Plugin
We have used a little different approach than Koshuke has laid out in:
https://wiki.jenkins-ci.org/display/JENKINS/Designing+pre-tested+commit
We do use a "branchy solution" but we do not take any decision on what kind of
test should approve or reject the build. We simply let the Jenkins build's
build step decide. And in stead we just use the post build step to decide
whether to do a commit or a revert. That is - our approach uses an extensions
point in the post build step.
Our plugin use built-in relations between streams in ClearCase UCM - but these
relations don't exist in SCM like git, Hg and SVN but they could easily be
implemented in the plugins by listing branches or regular expressions to match
- such as Kohsuke suggests too.
We advocate for manual rebases/updates of the developers branches.
Have a look at our paper on the subject too:
http://www.praqma.net/papers
Lars Kruse
was (Author: lars_kruse):
We have implemented this feature in the ClearCase UCM plugin:
https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+UCM+Plugin
We have used a little different approach than Koshuke has laid out in:
https://wiki.jenkins-ci.org/display/JENKINS/Designing+pre-tested+commit
We do use a "branchy solution" but we do not take any decision on what kind of
test should approve or reject the build. We simply let the Jenkins build's
build step decide. And in stead we just use the post build step to decide
whether to do a commit or a revert. That is - our approach uses an extensions
point in the post build step.
Our plugin use built-in relations between streams in ClearCase UCM - but these
relations don't exist in SCM like git, Hg and SVN but they could easily be
implemented in the plugins by listing branches or regular expressions to match
- such as Kohsuke suggests too.
We advocate for manual rebases/updates of the developers branches.
Have a look at our paper on the subject too:
http://www.praqma.net/papers/pretestedint
Lars Kruse
> Pre-tested commit feature
> -------------------------
>
> Key: JENKINS-1682
> URL: https://issues.jenkins-ci.org/browse/JENKINS-1682
> Project: Jenkins
> Issue Type: New Feature
> Components: other
> Affects Versions: current
> Environment: Platform: All, OS: All
> Reporter: felipeal
>
> Hi Koshuke,
> As we talked at JavaOne, it would be nice if Hudson provided a pre-tested
> commit
> feature, similar to TeamCity's:
> http://www.jetbrains.com/teamcity/delayed_commit.html
> -- Felipe
--
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
