yes but that only real value is the thing we need, then what can we do? On 03/01/2014, Jesse Glick <[email protected]> wrote: > On Fri, Jan 3, 2014 at 4:23 AM, Anatoly Bubenkov <[email protected]> > wrote: >> Im not sure if this can be easily merged into normal mercurial plugin in >> terms of it's design >> our one concentrates on doing commits and merges, pushes > > Seems like a distinct use case. But is this not overkill? You can > already include shell/batch scripts in your job to run hg commands of > your choice, with far more flexibility. The only real value a plugin > could provide here is setting the hg executable path automatically > (which is easily handled by the Tool Environment plugin), and > including masked passwords (handled by Plain Credentials). > > To put it another way, the reason SCM plugins like the Mercurial > plugin exist at all is that they must do some things which cannot be > replicated by regular build steps: creating a changelog, and polling > for remote changes. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/gbl0hgZemKQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. >
-- Anatoly Bubenkov -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
