Remote Parameterized Trigger Plugin

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Remote Parameterized Trigger Plugin

Kevin Phillips
I'd like to offer my assistance with the Remote Parameterized Trigger plugin project. There are a handful of issues and merge requests reported against the project, with minimal activity in recent months, and I think I could help move some of these forward. 

I have extensive experience with the Jenkins REST API which I think would overlap nicely with this particular plugin.

If I could be granted commit access to this repo that would be great. I'm not sure if there is an official maintainer for the plugin, but if not I wouldn't mind adopting that responsibility as well.

My GitHub ID is TheFriendlyCoder, and my Jenkins account ID is leedega.

Kevin

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANNNLMB4kc_6ve826S3B-%3DsyLOkW5C75WT4JA55x_wUVpSe3hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Remote Parameterized Trigger Plugin

Alexander Link
Hello,

we also recognized this project seems to be not maintained anymore (last change in August 2015, 19 unprocessed Pull Requests).
In the meantime we forked this GitHub repo, fixed some bugs, enabled it for usage in Pipelines, improved the Authentication, and released internal versions for use at SAP internally.
We tried to contribute some changes back, but no reaction on the PR.

What is your recommendation how to continue? One option for us would be to continue the internal fork, but that's not the preferred way.
The diff is quite big already btw. Creating single Pull Requests would be extremely cumbersome.

Thanks and kind regards,
Alex

Alexander Link
Development Expert, PI SAP HCP Engineering Services Production
SAP SE
Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
E [hidden email]  



On Tuesday, May 16, 2017 at 8:20:11 PM UTC+2, Kevin Phillips wrote:
I'd like to offer my assistance with the Remote Parameterized Trigger plugin project. There are a handful of issues and merge requests reported against the project, with minimal activity in recent months, and I think I could help move some of these forward. 

I have extensive experience with the Jenkins REST API which I think would overlap nicely with this particular plugin.

If I could be granted commit access to this repo that would be great. I'm not sure if there is an official maintainer for the plugin, but if not I wouldn't mind adopting that responsibility as well.

My GitHub ID is TheFriendlyCoder, and my Jenkins account ID is leedega.

Kevin

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d8b80419-6a60-484e-881e-dd0a26ad7b9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Remote Parameterized Trigger Plugin

Daniel Beck

> On 18. May 2017, at 16:28, Alexander Link <[hidden email]> wrote:
>
> What is your recommendation how to continue? One option for us would be to continue the internal fork, but that's not the preferred way.

Abandoned plugins can be taken over by new maintainers:

https://jenkins.io/project/governance/#helping-and-taking-over-dormant-plugins

Of course, just dropping a giant patch with dozens of changes on users is probably not a good idea, so if this is the way you'd like to proceed, consider whether you can land your changes incrementally.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/31D086FC-AD00-4484-9CB1-DAEFDBC390CF%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Remote Parameterized Trigger Plugin

Alexander Link
Hello Daniel,

thanks for the information. We will discuss this and come back to you.

> Of course, just dropping a giant patch with dozens of changes on users is probably not a good idea, so if this is the way you'd like to proceed, consider whether you can land your changes incrementally. 
Yes, you're right. We need to check how easy to consume PRs could be portioned.

best regards, Alex

On Thursday, May 18, 2017 at 8:10:02 PM UTC+2, Daniel Beck wrote:

> On 18. May 2017, at 16:28, Alexander Link <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="2Q8wf8_sAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">alexand...@...> wrote:
>
> What is your recommendation how to continue? One option for us would be to continue the internal fork, but that's not the preferred way.

Abandoned plugins can be taken over by new maintainers:

<a href="https://jenkins.io/project/governance/#helping-and-taking-over-dormant-plugins" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fproject%2Fgovernance%2F%23helping-and-taking-over-dormant-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGtPn2YqCob8hikkue1E_Hu_sjMeA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fproject%2Fgovernance%2F%23helping-and-taking-over-dormant-plugins\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGtPn2YqCob8hikkue1E_Hu_sjMeA&#39;;return true;">https://jenkins.io/project/governance/#helping-and-taking-over-dormant-plugins

Of course, just dropping a giant patch with dozens of changes on users is probably not a good idea, so if this is the way you'd like to proceed, consider whether you can land your changes incrementally.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4acd4dbb-48dd-4f42-b4c2-86a590c0ab64%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Remote Parameterized Trigger Plugin

Raphael Pionke-2
In reply to this post by Kevin Phillips
Hello,

is there any new activity with this plugin / repository?

Regards,
Raphael

Am Dienstag, 16. Mai 2017 20:20:11 UTC+2 schrieb Kevin Phillips:
I'd like to offer my assistance with the Remote Parameterized Trigger plugin project. There are a handful of issues and merge requests reported against the project, with minimal activity in recent months, and I think I could help move some of these forward. 

I have extensive experience with the Jenkins REST API which I think would overlap nicely with this particular plugin.

If I could be granted commit access to this repo that would be great. I'm not sure if there is an official maintainer for the plugin, but if not I wouldn't mind adopting that responsibility as well.

My GitHub ID is TheFriendlyCoder, and my Jenkins account ID is leedega.

Kevin

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46d68e98-45e4-4b7e-aaf1-c3a654a57dab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Remote Parameterized Trigger Plugin

Alejandra Ferreiro Vidal
In reply to this post by Kevin Phillips
Hi,

I did prepare the following PR that enables the plugin for Jenkins 2.x Pipelines.


I would like to apologize because there is one big commit, but it is too much effort to split it.

This code is the work of many colleagues, especially I would like to thank the contribution to Alexander Link who was the main contributor.

Thanks in advance and best regards,
Alejandra

El martes, 16 de mayo de 2017, 20:20:11 (UTC+2), Kevin Phillips escribió:
I'd like to offer my assistance with the Remote Parameterized Trigger plugin project. There are a handful of issues and merge requests reported against the project, with minimal activity in recent months, and I think I could help move some of these forward. 

I have extensive experience with the Jenkins REST API which I think would overlap nicely with this particular plugin.

If I could be granted commit access to this repo that would be great. I'm not sure if there is an official maintainer for the plugin, but if not I wouldn't mind adopting that responsibility as well.

My GitHub ID is TheFriendlyCoder, and my Jenkins account ID is leedega.

Kevin

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/22d460e7-e6f8-4d7e-8289-fad9d11c9304%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.