|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-11102) Give the possibility ... [email protected] (JIRA)
- [JIRA] (JENKINS-11102) Give the possibi... [email protected] (JIRA)
- [JIRA] (JENKINS-11102) Give the possibi... [email protected] (JIRA)

@Jesse Nice post on stack. You hit the nail on the head there per build history mirroring the VCS tree. An API like you describe would be ideal. Hopefully it's an item we can bring to the attention of Kohsuke and the community. That being said, I don't think feature clash should prevent the Mercurial plugin from moving forward in the meantime. E.g. It's fairly intuitive to avoid use of 'discard all but latest stable' if you're building from multiple branches. In a similar vein I need to avoid certain features or other plugins when using the Maven Release Plugin-Plugin.