Git plugin 5.0 require Jenkins 2.190.3

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Git plugin 5.0 require Jenkins 2.190.3

Mark Waite-2
The git plugin and git client plugin currently require Jenkins 2.138.4.  I chose that Jenkins version almost 18 months ago while working on the transition from JGit 4 to JGIt 5.

I think it is time to switch the minimum Jenkins version for the git plugin and the git client plugin.  I propose that the minimum Jenkins version for git plugin 5.0 and git client plugin 5.0 will be Jenkins 2.190.3.

We can still release versions of the git plugin and git client plugin for Jenkins releases older than 2.190.3 by basing those releases on earlier branches.

I frequently test the git plugin and git client plugin with the current Jenkins LTS line.  I sometimes test with the prior Jenkins LTS line.  Choosing 2.190.3 seems conservative enough to me and is much closer to what I'm actually testing than Jenkins 2.138.4.

Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

Fran and Bobby, what do you think of the idea?

Thanks,
Mark Waite

--
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/35aace60-ecbc-4251-a539-bb3c7cb5ec9e%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Git plugin 5.0 require Jenkins 2.190.3

James Nord-2
> Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

did you think of potential security issues and the need to to backport to the 4.x line so that older (commercially supported) LTS lines can upgrade?

--
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/e3a200be-8901-4071-8398-fb6baea987e4%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Daniel Beck
In reply to this post by Mark Waite-2


> On 26. Mar 2020, at 14:43, Mark Waite <[hidden email]> wrote:
>
> Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

2.190.x requires the BOM (-Duse-jenkins-bom) otherwise it won't compile out of the box. At least that's how I solved it for matrix-auth.

2.190.x seems like a solid choice at the moment, and also won't have implied dependencies as of today. But if the beta cycle is as long as it was for the previous major line, I'd recommend going with a more recent baseline; 2.138.x was a bad choice by the time Git Plugin 4.0.0 was finally released: obsolete for almost a year, two implied dependencies on newest releases, and its update center was retired just a month later.

--
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/3282626D-CB14-4C9E-BBAC-1C3F3E440A20%40beckweb.net.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Robert Sandell-2
In reply to this post by Mark Waite-2
I think 2.204.x is the current favorite, but I don't think there is anything against 2.190 more than age.

/B

On Thursday, March 26, 2020 at 2:43:45 PM UTC+1, Mark Waite wrote:
The git plugin and git client plugin currently require Jenkins 2.138.4.  I chose that Jenkins version almost 18 months ago while working on the transition from JGit 4 to JGIt 5.

I think it is time to switch the minimum Jenkins version for the git plugin and the git client plugin.  I propose that the minimum Jenkins version for git plugin 5.0 and git client plugin 5.0 will be Jenkins 2.190.3.

We can still release versions of the git plugin and git client plugin for Jenkins releases older than 2.190.3 by basing those releases on earlier branches.

I frequently test the git plugin and git client plugin with the current Jenkins LTS line.  I sometimes test with the prior Jenkins LTS line.  Choosing 2.190.3 seems conservative enough to me and is much closer to what I'm actually testing than Jenkins 2.138.4.

Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

Fran and Bobby, what do you think of the idea?

Thanks,
Mark Waite

--
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/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Mark Waite-2
In reply to this post by James Nord-2


On Thu, Mar 26, 2020 at 8:18 AM James Nord <[hidden email]> wrote:
> Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

did you think of potential security issues and the need to to backport to the 4.x line so that older (commercially supported) LTS lines can upgrade?


I think we've resolved that for older LTS lines by releasing security fixes simultaneously on multiple branches.  For example, SECURITY-1723 was released simultaneously in git plugin 4.2.1, git plugin 4.0.1, git plugin 3.12.2, and git plugin 3.10.0.1.  That was a lot of work, but it assured users of those specific plugin versions that they could increment from their current version to current version plus security fix.

That pattern can continue as needed.
 
--
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/e3a200be-8901-4071-8398-fb6baea987e4%40googlegroups.com.

--
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/CAO49JtGGwzKXsfxst1WzQwjtonPtYHJMqQu76BAxC%2BT9AGs%2BSA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Mark Waite-2
In reply to this post by Daniel Beck


On Thu, Mar 26, 2020 at 8:30 AM Daniel Beck wrote:


> On 26. Mar 2020, at 14:43, Mark Waite wrote:
>
> Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

2.190.x requires the BOM (-Duse-jenkins-bom) otherwise it won't compile out of the box. At least that's how I solved it for matrix-auth.


If that is needed, I think that would be reasonable.  The git plugin and git client plugin are using the plugin bom to simplify their management of dependencies (for workflow tests among others).
 
2.190.x seems like a solid choice at the moment, and also won't have implied dependencies as of today. But if the beta cycle is as long as it was for the previous major line, I'd recommend going with a more recent baseline; 2.138.x was a bad choice by the time Git Plugin 4.0.0 was finally released: obsolete for almost a year, two implied dependencies on newest releases, and its update center was retired just a month later.


I don't intend to have an 18 month beta cycle ever again.  That was a bad experience for everyone.  

This beta cycle should be no more than 1-2 months because it does not require changes from other plugins like the git client plugin 3.x change required.  No breaking changes in API's in the transition from current git client plugin to git client plugin 5.0.  No breaking changes in API's in the transition from current git plugin to git plugin 5.0.
 
--
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/3282626D-CB14-4C9E-BBAC-1C3F3E440A20%40beckweb.net.

--
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/CAO49JtE6ZD0TOucWpHZC8_pYzVcKYLD7Y6uw1Vv95zU2G_qn4Q%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Mark Waite-2
In reply to this post by Robert Sandell-2


On Thu, Mar 26, 2020 at 8:37 AM Robert Sandell <[hidden email]> wrote:
I think 2.204.x is the current favorite, but I don't think there is anything against 2.190 more than age.


Thanks for that insight.  I hadn't reviewed the deployment statistics when I sent my proposal for 2.190.x.

Based on deployment statistics, it seems like 2.204 or 2.204.1 are a better choice than 2.190.3.  Stats show:
  • Almost 10x more installations of git client plugin on Jenkins 2.204.2 than any other single release (over 40 000 installations)
  • 53% of git client plugin installations are running 3.0.0 or newer
  • Almost 10x more installations of git plugin on Jenkins 2.204.2 than any other single release (over 40 000 installations)
  • 48% of git plugin installations are running 4.0.0 or newer
I interpret that to mean that half the users are "staying current" with at least Jenkins 2.204.  That half of users are also the most likely to update to git plugin 5.0 and git client plugin 5.0.

I think the proposal should be revised to base on Jenkins 2.204.1 with a 1-2 month beta period (instead of 18 months).

Are there significant negatives to choosing 2.204.1 instead of 2.190.3?

Mark Waite
 
/B

On Thursday, March 26, 2020 at 2:43:45 PM UTC+1, Mark Waite wrote:
The git plugin and git client plugin currently require Jenkins 2.138.4.  I chose that Jenkins version almost 18 months ago while working on the transition from JGit 4 to JGIt 5.

I think it is time to switch the minimum Jenkins version for the git plugin and the git client plugin.  I propose that the minimum Jenkins version for git plugin 5.0 and git client plugin 5.0 will be Jenkins 2.190.3.

We can still release versions of the git plugin and git client plugin for Jenkins releases older than 2.190.3 by basing those releases on earlier branches.

I frequently test the git plugin and git client plugin with the current Jenkins LTS line.  I sometimes test with the prior Jenkins LTS line.  Choosing 2.190.3 seems conservative enough to me and is much closer to what I'm actually testing than Jenkins 2.138.4.

Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

Fran and Bobby, what do you think of the idea?

Thanks,
Mark Waite

--
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/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com.

--
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/CAO49JtGWk7-fjL16fDkTBGjCXhQgD79uB_Qft1oggAC6TMm4_w%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Francisco Javier Fernandez
After seeing the stats, I'd go for the 2.204

El jueves, 26 de marzo de 2020, 15:57:31 (UTC+1), Mark Waite escribió:


On Thu, Mar 26, 2020 at 8:37 AM Robert Sandell <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="wOjNjMrDBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">rsan...@...> wrote:
I think 2.204.x is the current favorite, but I don't think there is anything against 2.190 more than age.


Thanks for that insight.  I hadn't reviewed the deployment statistics when I sent my proposal for 2.190.x.

Based on deployment statistics, it seems like 2.204 or 2.204.1 are a better choice than 2.190.3.  Stats show:
  • Almost 10x more installations of git client plugin on Jenkins 2.204.2 than any other single release (over 40 000 installations)
  • 53% of git client plugin installations are running 3.0.0 or newer
  • Almost 10x more installations of git plugin on Jenkins 2.204.2 than any other single release (over 40 000 installations)
  • 48% of git plugin installations are running 4.0.0 or newer
I interpret that to mean that half the users are "staying current" with at least Jenkins 2.204.  That half of users are also the most likely to update to git plugin 5.0 and git client plugin 5.0.

I think the proposal should be revised to base on Jenkins 2.204.1 with a 1-2 month beta period (instead of 18 months).

Are there significant negatives to choosing 2.204.1 instead of 2.190.3?

Mark Waite
 
/B

On Thursday, March 26, 2020 at 2:43:45 PM UTC+1, Mark Waite wrote:
The git plugin and git client plugin currently require Jenkins 2.138.4.  I chose that Jenkins version almost 18 months ago while working on the transition from JGit 4 to JGIt 5.

I think it is time to switch the minimum Jenkins version for the git plugin and the git client plugin.  I propose that the minimum Jenkins version for git plugin 5.0 and git client plugin 5.0 will be Jenkins 2.190.3.

We can still release versions of the git plugin and git client plugin for Jenkins releases older than 2.190.3 by basing those releases on earlier branches.

I frequently test the git plugin and git client plugin with the current Jenkins LTS line.  I sometimes test with the prior Jenkins LTS line.  Choosing 2.190.3 seems conservative enough to me and is much closer to what I'm actually testing than Jenkins 2.138.4.

Are there pitfalls or problems that I have not considered in making the Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?

Fran and Bobby, what do you think of the idea?

Thanks,
Mark Waite

--
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="wOjNjMrDBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com.

--
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/216b5d83-1e1a-481a-b367-7aae17ffffb2%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Jesse Glick-4
In reply to this post by Mark Waite-2
On Thu, Mar 26, 2020 at 10:47 AM Mark Waite <[hidden email]> wrote:
> No breaking changes in API's in the transition from current git client plugin to git client plugin 5.0.  No breaking changes in API's in the transition from current git plugin to git plugin 5.0.

So why bother bumping the major version to begin with?

--
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/CANfRfr035Sn9SKtVj9OE0JYvSYOx1oQE%3D9bg%3D6RxJYjem6N2wg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Mark Waite-2

On Thu, Mar 26, 2020 at 3:17 PM Jesse Glick <[hidden email]> wrote:
On Thu, Mar 26, 2020 at 10:47 AM Mark Waite <[hidden email]> wrote:
> No breaking changes in API's in the transition from current git client plugin to git client plugin 5.0.  No breaking changes in API's in the transition from current git plugin to git plugin 5.0.

So why bother bumping the major version to begin with?


Good question.  I assumed (possibly incorrectly) that a change of required Jenkins version would best be handled by increasing the major number.  

Increasing the major number is also a chance to reduce the confusion caused when users mistakenly decide to use git plugin 3.x with git client plugin 3.x.

Is it a general practice that we can change the minimum Jenkins version without updating the major number?
 
--
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/CANfRfr035Sn9SKtVj9OE0JYvSYOx1oQE%3D9bg%3D6RxJYjem6N2wg%40mail.gmail.com.

--
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/CAO49JtFjJ_HSWJxkvYJZ0Li8wWHUseFDczpBDd43wovjbQZ25w%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Tim Jacomb
You aren’t breaking anything so I don’t know why you would need to break it.

On Thu, 26 Mar 2020 at 21:29, Mark Waite <[hidden email]> wrote:

On Thu, Mar 26, 2020 at 3:17 PM Jesse Glick <[hidden email]> wrote:
On Thu, Mar 26, 2020 at 10:47 AM Mark Waite <[hidden email]> wrote:
> No breaking changes in API's in the transition from current git client plugin to git client plugin 5.0.  No breaking changes in API's in the transition from current git plugin to git plugin 5.0.

So why bother bumping the major version to begin with?


Good question.  I assumed (possibly incorrectly) that a change of required Jenkins version would best be handled by increasing the major number.  

Increasing the major number is also a chance to reduce the confusion caused when users mistakenly decide to use git plugin 3.x with git client plugin 3.x.

Is it a general practice that we can change the minimum Jenkins version without updating the major number?
 
--
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/CANfRfr035Sn9SKtVj9OE0JYvSYOx1oQE%3D9bg%3D6RxJYjem6N2wg%40mail.gmail.com.

--
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/CAO49JtFjJ_HSWJxkvYJZ0Li8wWHUseFDczpBDd43wovjbQZ25w%40mail.gmail.com.

--
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/CAH-3Biez6Z%2BREJWMgd%3Dd%3DV0UqkJkyU1eQmQbKTgE4%2B-_Y%2BpDrA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Jesse Glick-4
In reply to this post by Mark Waite-2
On Thu, Mar 26, 2020 at 5:29 PM Mark Waite <[hidden email]> wrote:
> confusion caused when users mistakenly decide to use git plugin 3.x with git client plugin 3.x.

Are there incompatible changes in `git-client` that would mean you
cannot use an older `git`?

> Is it a general practice that we can change the minimum Jenkins version without updating the major number?

No.

--
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/CANfRfr3jGyBTMYj%2BXaQ8TuPkJvOE7zku%3D%3Df8u%2BV0%3DwzJWKdUdw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Jesse Glick-4
On Fri, Mar 27, 2020 at 4:18 PM Jesse Glick <[hidden email]> wrote:
>> Is it a general practice that we can change the minimum Jenkins version without updating the major number?
>
> No.

I mean, yes, you can. (“No” we do not generally update the major
version component of plugins just because `jenkins.version` has been
updated.)

--
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/CANfRfr1yuPo6Ha3ZewLkkcY7zoHcrVLNXfJXEr8XnQqPeDu6RA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Git plugin 5.0 require Jenkins 2.190.3

Mark Waite-2
In reply to this post by Jesse Glick-4


On Fri, Mar 27, 2020 at 2:19 PM Jesse Glick <[hidden email]> wrote:
On Thu, Mar 26, 2020 at 5:29 PM Mark Waite <[hidden email]> wrote:
> confusion caused when users mistakenly decide to use git plugin 3.x with git client plugin 3.x.

Are there incompatible changes in `git-client` that would mean you
cannot use an older `git`?


The transition from git client plugin 2.x to git client plugin 3.x included a breaking API change.  The breaking API change was due to the transition from JGit 4.x to JGit 5.x.   No incompatible changes have been made since git client plugin 3.0.0.

Git plugin 3.x depends on git client plugin 2.x and JGit 4.x.

Git plugin 4.x depends on git client plugin 3.x and JGit 5.x.

Other than the JGit API change, there were no other breaking changes in the transition from git client plugin 2.x to 3.x. 

There is at least one case where a user chose to upgrade the git client plugin to 3.x without upgrading the git plugin to 4.x.  I never tested git plugin 3.x with git client plugin 3.x and never intended that someone would choose that combination.  The combination appears to work, but it is not a combination I ever tested.

One excuse to change major number was to possibly reduce user confusion from version numbers.  However, I don't think that is enough justification, since typical sets of plugins have many different version numbers and users do not expect any correlation between one plugin version number and another.  The git plugin and git client plugin may be coupled in my mind but they are not necessarily coupled in the thinking of Jenkins administrators.

 
> Is it a general practice that we can change the minimum Jenkins version without updating the major number?

No.


That's good.  That means I can increment the minor version number instead, since the change of required Jenkins version is not justification to increment the major number.

I'll increment the minor number for the next release in any case, since there will be new functionality in the release.  It seems like that is enough in this case.  Changing the required Jenkins version is a much less significant change than I thought.

Thanks for the clarification!
 
--
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/CANfRfr3jGyBTMYj%2BXaQ8TuPkJvOE7zku%3D%3Df8u%2BV0%3DwzJWKdUdw%40mail.gmail.com.

--
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/CAO49JtHgrL33aao31X3wELe2JPWGUiwQPrExzAu8MB3ciN2SMg%40mail.gmail.com.