|RFC: more source control capabilities for Buckminster [message #546987]
||Wed, 14 July 2010 16:44
| Johannes Tysiak
Registered: April 2010
I would like to request your comments on an issue which I have been thinking about lately:
I very much like Buckminster's capability to materialize build artifacts. Because of this, I use (headless) Buckminster to checkout sources from <insert-your-favorite-SCM>. However, after the build has finished, I would like to be able to tag the sources I have just build in the SCM. Currently this does not seem to be possible using Buckminster. However, it is a requirement for quite a lot of build environments.
What do you do to circumvent this issue? I know I could checkout my sources outside of Buckminster. However, this would mean I would have to duplicate the information about what I want to build, so both Buckminster and the framework on the outside (e.g. Ant) would both have to know about this (this does not only include the SCM URL, but also which branch to check out, which version, etc.). Because of this I would rather not do it.
Do you think it would be feasible for Buckminster to support a subset of (generic) SCM commands, which would work on any of the supported SCM systems (CVS, SVN, Git, ...), which could triggered from headless Bucky commands? These should at least support the capability to tag and branch.
Maybe I oversaw another possible approach. I would be happy to hear your thoughts on this issue.
[Updated on: Wed, 14 July 2010 16:44]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.14517 seconds