Plugin maintenance: slack-plugin

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

Plugin maintenance: slack-plugin

Gustavo Maia
Hi. I've been talking with Sam Gleske about helping to maintain the slack-plugin and he asked me to go ahead and submit the request here. Here's the main conversation:
https://github.com/jenkinsci/slack-plugin/pull/324
I've @ mentioned Kurt on the PR as well, but haven't got a response yet. Kurt, is it ok if I step up and try to help?

Here's my info:
Github ID: gurumaia
Jenkins infra account: gurumaia

Thanks

--
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/CAC0tQF2ysa%2B0Tx2wWjkhi%2Bf59auWfO_GOHPqKkEycSpwT-UKUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Oleg Nenashev
Commonly we give the maintainer two weeks to respond before transferring the ownership.
Added Kurt to Cc just in case, so let's count from here. OTOH maybe no need to wait since there is +1 from Sam.

Please ping me in this thread on July 27 if there is no response from Kurt.

BR, Oleg

пятница, 7 июля 2017 г., 16:28:04 UTC+2 пользователь Gustavo Maia написал:
Hi. I've been talking with Sam Gleske about helping to maintain the slack-plugin and he asked me to go ahead and submit the request here. Here's the main conversation:
<a href="https://github.com/jenkinsci/slack-plugin/pull/324" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fslack-plugin%2Fpull%2F324\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG2Rsq9VsTLMEQ1pQBWeqtnKDq5cQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fslack-plugin%2Fpull%2F324\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG2Rsq9VsTLMEQ1pQBWeqtnKDq5cQ&#39;;return true;">https://github.com/jenkinsci/slack-plugin/pull/324
I've @ mentioned Kurt on the PR as well, but haven't got a response yet. Kurt, is it ok if I step up and try to help?

Here's my info:
Github ID: gurumaia
Jenkins infra account: gurumaia

Thanks

--
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/d3e0b68d-0cdc-4d8e-9421-ba3f8d1b9c42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Kurt Madel
+1 for me.

-Kurt

On Thu, Jul 13, 2017 at 12:39 PM Oleg Nenashev <[hidden email]> wrote:
Commonly we give the maintainer two weeks to respond before transferring the ownership.
Added Kurt to Cc just in case, so let's count from here. OTOH maybe no need to wait since there is +1 from Sam.

Please ping me in this thread on July 27 if there is no response from Kurt.

BR, Oleg

пятница, 7 июля 2017 г., 16:28:04 UTC+2 пользователь Gustavo Maia написал:
Hi. I've been talking with Sam Gleske about helping to maintain the slack-plugin and he asked me to go ahead and submit the request here. Here's the main conversation:
https://github.com/jenkinsci/slack-plugin/pull/324
I've @ mentioned Kurt on the PR as well, but haven't got a response yet. Kurt, is it ok if I step up and try to help?

Here's my info:
Github ID: gurumaia
Jenkins infra account: gurumaia

Thanks
--
Kurt Madel
Director, Worldwide Solution Architects
804-585-8879

--
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/CAM9PSwr%3DFH7S_VjvRev9PXD8XfDmMojvtEzdCoE0xP4%3DTjzvog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Oleg Nenashev
Thanks Kurt!

Added gurumaia to the committer list.
@Sam, @Gustavo who does want to be the default assignee in JIRA?

BR, Oleg

2017-07-13 18:41 GMT+02:00 Kurt Madel <[hidden email]>:
+1 for me.

-Kurt

On Thu, Jul 13, 2017 at 12:39 PM Oleg Nenashev <[hidden email]> wrote:
Commonly we give the maintainer two weeks to respond before transferring the ownership.
Added Kurt to Cc just in case, so let's count from here. OTOH maybe no need to wait since there is +1 from Sam.

Please ping me in this thread on July 27 if there is no response from Kurt.

BR, Oleg

пятница, 7 июля 2017 г., 16:28:04 UTC+2 пользователь Gustavo Maia написал:
Hi. I've been talking with Sam Gleske about helping to maintain the slack-plugin and he asked me to go ahead and submit the request here. Here's the main conversation:
https://github.com/jenkinsci/slack-plugin/pull/324
I've @ mentioned Kurt on the PR as well, but haven't got a response yet. Kurt, is it ok if I step up and try to help?

Here's my info:
Github ID: gurumaia
Jenkins infra account: gurumaia

Thanks
--
Kurt Madel
Director, Worldwide Solution Architects
<a href="tel:(804)%20585-8879" value="+18045858879" target="_blank">804-585-8879

--
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/CAPfivLDeeVK38_91B9dtFWGKyKeN4y%2BNUUFmxkm%2BH8huv36_7Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Gustavo Maia
I believe leaving one of Kurt or Sam as the default assignee for now is a good bet. This is my first plugin adoption so I might start a little slow.

Shall I add myself as a maintainer on the pom.xml?

Also, should all discussion regarding the plugin happen through here?

Thanks,
Gustavo Maia

On Thu, Jul 13, 2017 at 1:58 PM, Oleg Nenashev <[hidden email]> wrote:
Thanks Kurt!

Added gurumaia to the committer list.
@Sam, @Gustavo who does want to be the default assignee in JIRA?

BR, Oleg

2017-07-13 18:41 GMT+02:00 Kurt Madel <[hidden email]>:
+1 for me.

-Kurt

On Thu, Jul 13, 2017 at 12:39 PM Oleg Nenashev <[hidden email]> wrote:
Commonly we give the maintainer two weeks to respond before transferring the ownership.
Added Kurt to Cc just in case, so let's count from here. OTOH maybe no need to wait since there is +1 from Sam.

Please ping me in this thread on July 27 if there is no response from Kurt.

BR, Oleg

пятница, 7 июля 2017 г., 16:28:04 UTC+2 пользователь Gustavo Maia написал:
Hi. I've been talking with Sam Gleske about helping to maintain the slack-plugin and he asked me to go ahead and submit the request here. Here's the main conversation:
https://github.com/jenkinsci/slack-plugin/pull/324
I've @ mentioned Kurt on the PR as well, but haven't got a response yet. Kurt, is it ok if I step up and try to help?

Here's my info:
Github ID: gurumaia
Jenkins infra account: gurumaia

Thanks
--
Kurt Madel
Director, Worldwide Solution Architects
<a href="tel:(804)%20585-8879" value="+18045858879" target="_blank">804-585-8879

--
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/CAPfivLDeeVK38_91B9dtFWGKyKeN4y%2BNUUFmxkm%2BH8huv36_7Q%40mail.gmail.com.

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

--
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/CAC0tQF0x6p2gd7%3D8S08%2BusO%2BHqkGnPRAbvM1QBtsfajaGH6o2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Sam Gleske
Hey Gustavo,
Yes, please add yourself as a maintainer to pom.xml.  It helps users know they can ping you as well as what timezone you're in.  Feel free to open a separate PR or update your existing open PR.

On Thursday, July 13, 2017 at 10:31:23 AM UTC-7, Gustavo Maia wrote:
I believe leaving one of Kurt or Sam as the default assignee for now is a good bet. This is my first plugin adoption so I might start a little slow.

Shall I add myself as a maintainer on the pom.xml?

Also, should all discussion regarding the plugin happen through here?

Thanks,
Gustavo Maia

On Thu, Jul 13, 2017 at 1:58 PM, Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="-_RQnOhOAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.ne...@...> wrote:
Thanks Kurt!

Added gurumaia to the committer list.
@Sam, @Gustavo who does want to be the default assignee in JIRA?

BR, Oleg

2017-07-13 18:41 GMT+02:00 Kurt Madel <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="-_RQnOhOAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">kma...@...>:
+1 for me.

-Kurt

On Thu, Jul 13, 2017 at 12:39 PM Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="-_RQnOhOAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.ne...@...> wrote:
Commonly we give the maintainer two weeks to respond before transferring the ownership.
Added Kurt to Cc just in case, so let's count from here. OTOH maybe no need to wait since there is +1 from Sam.

Please ping me in this thread on July 27 if there is no response from Kurt.

BR, Oleg

пятница, 7 июля 2017 г., 16:28:04 UTC+2 пользователь Gustavo Maia написал:
Hi. I've been talking with Sam Gleske about helping to maintain the slack-plugin and he asked me to go ahead and submit the request here. Here's the main conversation:
<a href="https://github.com/jenkinsci/slack-plugin/pull/324" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fslack-plugin%2Fpull%2F324\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG2Rsq9VsTLMEQ1pQBWeqtnKDq5cQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fslack-plugin%2Fpull%2F324\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG2Rsq9VsTLMEQ1pQBWeqtnKDq5cQ&#39;;return true;">https://github.com/jenkinsci/slack-plugin/pull/324
I've @ mentioned Kurt on the PR as well, but haven't got a response yet. Kurt, is it ok if I step up and try to help?

Here's my info:
Github ID: gurumaia
Jenkins infra account: gurumaia

Thanks
--
Kurt Madel
Director, Worldwide Solution Architects

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="-_RQnOhOAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDeeVK38_91B9dtFWGKyKeN4y%2BNUUFmxkm%2BH8huv36_7Q%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDeeVK38_91B9dtFWGKyKeN4y%2BNUUFmxkm%2BH8huv36_7Q%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDeeVK38_91B9dtFWGKyKeN4y%2BNUUFmxkm%2BH8huv36_7Q%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDeeVK38_91B9dtFWGKyKeN4y%2BNUUFmxkm%2BH8huv36_7Q%40mail.gmail.com.

For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
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/623532cd-cc9b-4263-b212-93e4d39e5ad6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Sam Gleske
In reply to this post by Gustavo Maia
Gustavo,
When you're ready to attempt your first release, feel free to reach out to me for assistance if you feel you need it.

--
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/d85dd117-709a-45ad-a01f-b385062e42b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Gustavo Maia
Hi Sam, thanks for the help. I've just updated my currently open PR:

I'm still trying to figure out what the merging and release process looks like for Jenkins plugins. Can someone link me some documentation about this or maybe give me an overview level of the steps I'd need to go through?
With that information on hand I think I'd be able to go ahead and perform a first release.

Thanks!

On Thu, Jul 13, 2017 at 11:57 PM, Sam Gleske <[hidden email]> wrote:
Gustavo,
When you're ready to attempt your first release, feel free to reach out to me for assistance if you feel you need it.

--
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/d85dd117-709a-45ad-a01f-b385062e42b2%40googlegroups.com.

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

--
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/CAC0tQF0sDtiaDjvr_LS1i50tX055Mc_RnoRxzVcOf7qu37JoFw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Daniel Beck

> On 18. Jul 2017, at 13:17, Gustavo Maia <[hidden email]> wrote:
>
> I'm still trying to figure out what the merging and release process looks like for Jenkins plugins. Can someone link me some documentation about this or maybe give me an overview level of the steps I'd need to go through?

https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org should have everything you need. Note the message on permissions from the previous section.


--
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/4E7F0F9E-8261-4267-90C3-9185DBE70BFE%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Sam Gleske
I have also documented the release process in https://github.com/jenkinsci/slack-plugin/blob/master/RELEASE.md

The merging process is typically up to the maintainers of each project.  As far as I know, there's no set standard for how changes get included project-wide in Jenkins.  On projects in which I'm active I typically do the following:

- Give roughly a week for anybody to provide feedback.
- During that week I'll review myself; build the PR; test plugin upgrades; ensure that old functionality is not broken; etc
- Then I merge it.
- Then roughly monthly I'll cut a new plugin version release following RELEASE.md (or sooner if I deem that's necessary on a case by case basis)

On Tue, Jul 18, 2017 at 4:41 AM, Daniel Beck <[hidden email]> wrote:

> On 18. Jul 2017, at 13:17, Gustavo Maia <[hidden email]> wrote:
>
> I'm still trying to figure out what the merging and release process looks like for Jenkins plugins. Can someone link me some documentation about this or maybe give me an overview level of the steps I'd need to go through?

https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org should have everything you need. Note the message on permissions from the previous section.


--
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/nc_EZ2kaIgE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4E7F0F9E-8261-4267-90C3-9185DBE70BFE%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



--
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F

https://keybase.io/samrocketman

curl https://keybase.io/samrocketman/key.asc | gpg --import -

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/

--
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/CAKtEXLBNyihwsP60_eDhfXF-bjnWaKuyj%3DUmFW-LP0qr5JOqWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Gustavo Maia
Hey guys, it's been a while but I think now I'll have a bit more time to dedicate to this.

I'm now in the process of merging and releasing my first version. I noticed there is a project setup for this plugin here:
https://jenkins.ci.cloudbees.com/job/plugins/job/slack-plugin/
But it seems to be disabled and I don't seem to have access to that jenkins instance. Can I get access?

I'll move forward with this release because it's being actively requested but for the next ones, I'd like to have a Jenkins job to build it continuously. If this isn't the right jenkins instance to use, is there one I could use?

Thanks!

On Fri, Aug 4, 2017 at 3:17 PM, Sam Gleske <[hidden email]> wrote:
I have also documented the release process in https://github.com/jenkinsci/slack-plugin/blob/master/RELEASE.md

The merging process is typically up to the maintainers of each project.  As far as I know, there's no set standard for how changes get included project-wide in Jenkins.  On projects in which I'm active I typically do the following:

- Give roughly a week for anybody to provide feedback.
- During that week I'll review myself; build the PR; test plugin upgrades; ensure that old functionality is not broken; etc
- Then I merge it.
- Then roughly monthly I'll cut a new plugin version release following RELEASE.md (or sooner if I deem that's necessary on a case by case basis)

On Tue, Jul 18, 2017 at 4:41 AM, Daniel Beck <[hidden email]> wrote:

> On 18. Jul 2017, at 13:17, Gustavo Maia <[hidden email]> wrote:
>
> I'm still trying to figure out what the merging and release process looks like for Jenkins plugins. Can someone link me some documentation about this or maybe give me an overview level of the steps I'd need to go through?

https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org should have everything you need. Note the message on permissions from the previous section.


--
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/nc_EZ2kaIgE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4E7F0F9E-8261-4267-90C3-9185DBE70BFE%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



--
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F

https://keybase.io/samrocketman

curl https://keybase.io/samrocketman/key.asc | gpg --import -

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/

--
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/CAKtEXLBNyihwsP60_eDhfXF-bjnWaKuyj%3DUmFW-LP0qr5JOqWg%40mail.gmail.com.

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

--
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/CAC0tQF2xPq0Yg8Dr%3DeQ_Nj6n_eVr3ATv-__i11E0tYN4V1986A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Oleg Nenashev
Hi Gustavo,

We have moved the plugin CI to Jenkins' own infrastructure.
In order to enable it, you just need to add Jenkinsfile to the repo root.


BR, Oleg

2017-08-14 12:53 GMT+02:00 Gustavo Maia <[hidden email]>:
Hey guys, it's been a while but I think now I'll have a bit more time to dedicate to this.

I'm now in the process of merging and releasing my first version. I noticed there is a project setup for this plugin here:
https://jenkins.ci.cloudbees.com/job/plugins/job/slack-plugin/
But it seems to be disabled and I don't seem to have access to that jenkins instance. Can I get access?

I'll move forward with this release because it's being actively requested but for the next ones, I'd like to have a Jenkins job to build it continuously. If this isn't the right jenkins instance to use, is there one I could use?

Thanks!

On Fri, Aug 4, 2017 at 3:17 PM, Sam Gleske <[hidden email]> wrote:
I have also documented the release process in https://github.com/jenkinsci/slack-plugin/blob/master/RELEASE.md

The merging process is typically up to the maintainers of each project.  As far as I know, there's no set standard for how changes get included project-wide in Jenkins.  On projects in which I'm active I typically do the following:

- Give roughly a week for anybody to provide feedback.
- During that week I'll review myself; build the PR; test plugin upgrades; ensure that old functionality is not broken; etc
- Then I merge it.
- Then roughly monthly I'll cut a new plugin version release following RELEASE.md (or sooner if I deem that's necessary on a case by case basis)

On Tue, Jul 18, 2017 at 4:41 AM, Daniel Beck <[hidden email]> wrote:

> On 18. Jul 2017, at 13:17, Gustavo Maia <[hidden email]> wrote:
>
> I'm still trying to figure out what the merging and release process looks like for Jenkins plugins. Can someone link me some documentation about this or maybe give me an overview level of the steps I'd need to go through?

https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org should have everything you need. Note the message on permissions from the previous section.


--
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/nc_EZ2kaIgE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4E7F0F9E-8261-4267-90C3-9185DBE70BFE%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



--
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F

https://keybase.io/samrocketman

curl https://keybase.io/samrocketman/key.asc | gpg --import -

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/

--
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/CAKtEXLBNyihwsP60_eDhfXF-bjnWaKuyj%3DUmFW-LP0qr5JOqWg%40mail.gmail.com.

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

--
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/nc_EZ2kaIgE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC0tQF2xPq0Yg8Dr%3DeQ_Nj6n_eVr3ATv-__i11E0tYN4V1986A%40mail.gmail.com.

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

--
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/CAPfivLB838D9OXMV0i1aDm0JLmqJSss1DhYsAuf%2BMOoehLSJzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Plugin maintenance: slack-plugin

Gustavo Maia
Alright, awesome. I'll try it out.
Thanks!

On Mon, Aug 14, 2017 at 8:08 AM, Oleg Nenashev <[hidden email]> wrote:
Hi Gustavo,

We have moved the plugin CI to Jenkins' own infrastructure.
In order to enable it, you just need to add Jenkinsfile to the repo root.


BR, Oleg

2017-08-14 12:53 GMT+02:00 Gustavo Maia <[hidden email]>:
Hey guys, it's been a while but I think now I'll have a bit more time to dedicate to this.

I'm now in the process of merging and releasing my first version. I noticed there is a project setup for this plugin here:
https://jenkins.ci.cloudbees.com/job/plugins/job/slack-plugin/
But it seems to be disabled and I don't seem to have access to that jenkins instance. Can I get access?

I'll move forward with this release because it's being actively requested but for the next ones, I'd like to have a Jenkins job to build it continuously. If this isn't the right jenkins instance to use, is there one I could use?

Thanks!

On Fri, Aug 4, 2017 at 3:17 PM, Sam Gleske <[hidden email]> wrote:
I have also documented the release process in https://github.com/jenkinsci/slack-plugin/blob/master/RELEASE.md

The merging process is typically up to the maintainers of each project.  As far as I know, there's no set standard for how changes get included project-wide in Jenkins.  On projects in which I'm active I typically do the following:

- Give roughly a week for anybody to provide feedback.
- During that week I'll review myself; build the PR; test plugin upgrades; ensure that old functionality is not broken; etc
- Then I merge it.
- Then roughly monthly I'll cut a new plugin version release following RELEASE.md (or sooner if I deem that's necessary on a case by case basis)

On Tue, Jul 18, 2017 at 4:41 AM, Daniel Beck <[hidden email]> wrote:

> On 18. Jul 2017, at 13:17, Gustavo Maia <[hidden email]> wrote:
>
> I'm still trying to figure out what the merging and release process looks like for Jenkins plugins. Can someone link me some documentation about this or maybe give me an overview level of the steps I'd need to go through?

https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org should have everything you need. Note the message on permissions from the previous section.


--
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/nc_EZ2kaIgE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4E7F0F9E-8261-4267-90C3-9185DBE70BFE%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.



--
I prefer to encrypt my email

GPG FINGERPRINT 4096 KEY
8D8B F0E2 42D8 A068 572E
BF3C E8F7 3234 7257 E65F

https://keybase.io/samrocketman

curl https://keybase.io/samrocketman/key.asc | gpg --import -

Learn how to encrypt your email with the Email Self Defense guide:
https://emailselfdefense.fsf.org/en/

--
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/CAKtEXLBNyihwsP60_eDhfXF-bjnWaKuyj%3DUmFW-LP0qr5JOqWg%40mail.gmail.com.

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

--
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/nc_EZ2kaIgE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC0tQF2xPq0Yg8Dr%3DeQ_Nj6n_eVr3ATv-__i11E0tYN4V1986A%40mail.gmail.com.

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

--
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/CAPfivLB838D9OXMV0i1aDm0JLmqJSss1DhYsAuf%2BMOoehLSJzw%40mail.gmail.com.

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

--
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/CAC0tQF2%3DMMRuLoU4mGoby%2B%3DUcY8CBd7emBRdqnTuqStaXnBFfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.