plugins request hosting

[Anatoly Bubenkov]

Hi there,


We've created a several plugins:

https://github.com/paylogic/jenkins-fogbugz-plugin

A Jenkins plugin to link Jenkins builds and jobs to Fogbugz cases

https://github.com/paylogic/jenkins-gatekeeper-plugin

A Jenkins plugin that performs Gatekeepering by merging 'feature' branches with 'release' branches.

https://github.com/paylogic/jenkins-upmerge-plugin

A Jenkins plugin that performs Upmerging of 'release' branches.

We would like to host the plugin on https://github.com/jenkinsci. You can clone the sources from corresponding github repos, my GitHub ID is bubenkoff.

Thanks,
Anatoly

[Slide]

Can we use just fogbugz-plugin and gatekeeper-plugin, etc as the names?

--
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 jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Website: http://earl-of-code.com

[Slide]

Also, how does your fogbugz plugin differ from this one? https://wiki.jenkins-ci.org/display/JENKINS/Fogbugz+Plugin would it be possible to merge the plugins together and just contribute to one?

On Thu, Jan 2, 2014 at 8:30 AM, Anatoly Bubenkov <bube...@gmail.com> wrote:

--

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 jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Website: http://earl-of-code.com

[Anatoly Bubenkov]

that's fixed now

--
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 jenkinsci-de...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

Anatoly Bubenkov

[Anatoly Bubenkov]

great point

so will do pull a request then

thanks

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 jenkinsci-de...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

--

Anatoly Bubenkov

[Slide]

I forked the other two into jenkinsci and added you as a committer. Please also sign up for an account on the issue tracker (issues.jenkins-ci.org) so that I can create components for your new plugins and make you the owner.

[Anatoly Bubenkov]

thanks!

my username there is bubenkoff

[Slide]

Done

[Anatoly Bubenkov]

thanks

sorry forgot to mention

https://github.com/paylogic/advancedmercurial-plugin

this also should be published

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

[Jesse Glick]

On Fri, Jan 3, 2014 at 4:23 AM, Anatoly Bubenkov <bube...@gmail.com> 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.

[Anatoly Bubenkov]

yes but that only real value is the thing we need, then what can we do?

[Jesse Glick]

Just pointing out that you can get a similar effect without a custom
plugin, just possibly with a less pretty configuration UI.

[Anatoly Bubenkov]

but how could we authenticate hg for example?

without credentials thingy from jenkins

having an access by ssh key from every slave is not a good option i think...

On 3 January 2014 16:42, Jesse Glick <jgl...@cloudbees.com> wrote:

Just pointing out that you can get a similar effect without a custom
plugin, just possibly with a less pretty configuration UI.

--
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 jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Anatoly Bubenkov

[Jesse Glick]

On Fri, Jan 3, 2014 at 10:52 AM, Anatoly Bubenkov <bube...@gmail.com> wrote:
> but how could we authenticate hg for example?
> without credentials thingy from jenkins

https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Binding+Plugin

[Anatoly Bubenkov]

valid point...

thanks for your thoughts

still think that it's better to abstract from direct running of hg commands in build steps

--
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 jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Anatoly Bubenkov

[Anatoly Bubenkov]

please add maikelwever username as collaborator both for upmerge and gatekeeper plugins

--

Anatoly Bubenkov

[Ulli Hafner]

Done.

Welcome aboard!

Ulli

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 jenkinsci-de...@googlegroups.com.

[Anatoly Bubenkov]

thanks a lot!

--
Anatoly Bubenkov

[Anatoly Bubenkov]

Hi

we decided to merge Plugins:

Upmerge was merged into Gatekeepers

it will make potential auditory wider and will remove the confusion

so i've removed Upmerge plugin repo and corresponding wiki page

--

Anatoly Bubenkov

[Anatoly Bubenkov]

btw neither me or maikel are not able to trigger the jenkins test job on https://jenkins.ci.cloudbees.com/

how can we get access there via github?

--

Anatoly Bubenkov

[Jesse Glick]

On Fri, Jan 10, 2014 at 8:49 AM, Anatoly Bubenkov <bube...@gmail.com> wrote:
> neither me or maikel are not able to trigger the jenkins test job on
> https://jenkins.ci.cloudbees.com/

Sorry, can you be more specific about what you need to do? Which test
job, and why would you need to trigger it manually (these all have GH
push triggers configured)?

[Anatoly Bubenkov]

ah, then no worries, sorry

--
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 jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Anatoly Bubenkov

[Anatoly Bubenkov]

can you please add larsderidder as a maintainer of 

fogbugz-plugin

gatekeeper-plugin

his github account is todayispotato