Re: Google OAuth Plugin does not load scope

2014-09-28 Thread Calvin
Ok sorry, I'm fairly new to using Google's API and Jenkins and I think I 
see where my confusion lies, I was thinking that the Google OAuth Plugin 
automatically provides the scopes, however after relooking 
at https://wiki.jenkins-ci.org/display/JENKINS/Google+OAuth+Plugin, I 
realize that this plugin just provides the Google service account options 
that I can associate to Jenkins and then I would need to probably implement 
another plugin like the GoogleCloudStorage that exposes the scopes needed 
to access the Chrome Web Store APIs.  I want to be able to do something 
like the following within Jenkins as a post process to automatically 
publish/update a Chrome extension we've developed directly to the Chrome 
Store,

 curl \-H Authorization: Bearer $TOKEN  \-H x-goog-api-version: 2 \-X POST 
 \-T $FILE_NAME \-v \
https://www.googleapis.com/upload/chromewebstore/v1.1/items


On Saturday, September 27, 2014 9:58:57 PM UTC-7, Matthew Moore wrote:

 I assume you are building a plugin to access this API, using an OAuth2 
 credential?  Otherwise, I'll probably need some more context on how you 
 plan to wire things up...


 If you are building such a plugin you should look at how the Google Cloud 
 Storage plugin specifies its OAuth2 scope requirement: 
 https://github.com/jenkinsci/google-storage-plugin/blob/master/src/main/java/com/google/jenkins/plugins/storage/GoogleCloudStorageUploader.java#L51

 Putting an appropriately constructed @RequiresDomain on any describable 
 (e.g. Publishers) will make the error you are seeing go away.  As I said 
 (more tersely) before, we scan for these annotations to dynamically 
 populate the pertinent set of scopes for installed plugins.




 Specifically, you are going to want to define:
 public class ChromeWebStoreScopeRequirement extends 
 GoogleOAuth2ScopeRequirement {

 which returns the scope you list, similar to StorageScopeRequirement 
 https://github.com/jenkinsci/google-storage-plugin/blob/master/src/main/java/com/google/jenkins/plugins/storage/StorageScopeRequirement.java,
  
 then annotate something like this:
 @RequiresDomain(value = ChromeWebStoreScopeRequirement.class)
 public class ChromeWebStorePublisher extends Recorder {


 or maybe I am completely misunderstanding your intent...  Hope that helps.
 -M



 On Fri, Sep 26, 2014 at 9:51 AM, Calvin cc...@pingidentity.com 
 javascript: wrote:

 Hi Matt,

 I have both the Google OAuth Plugin as well as the OAuth Credential 
 Plugin installed and enabled.  The scope I'm needing specifically from the 
 Google OAuth Plugin is, scope=
 https://www.googleapis.com/auth/chromewebstore to use this API, 
 https://developer.chrome.com/webstore/using_webstore_api


 https://lh4.googleusercontent.com/-JiykxSQwKIg/VCWZhx-P5UI/AeA/tq0xSrvd-mQ/s1600/Screen%2BShot%2B2014-09-26%2Bat%2B9.48.06%2BAM.png

 On Friday, September 26, 2014 9:35:35 AM UTC-7, Matthew Moore wrote:

 What plugins do you have installed that require OAuth?  This plugin 
 dynamically determines the set of OAuth scopes that might be required by 
 installed plugins, to allow you to pick and choose which should be allowed 
 for a given credential.

 Try installing google-storage-plugin, for example, and the storage scope 
 should show up where you currently have that error message.


 LMK if you are expecting something to show up, which isn't.
 -M

 On Thu, Sep 25, 2014 at 11:04 PM, Calvin cc...@pingidentity.com wrote:

 Just installed the Google OAuth Plugin into Jenkins in addition to 
 having the OAuth Credential Plugin, and upon configuring a new credential 
 domain neither plugins load the Google OAuth scopes.  Anybody experience 
 this before?


 https://lh5.googleusercontent.com/-h5XOtXgqPrM/VCUB1xLwcdI/Adw/VgS-687r3c4/s1600/Screen%2BShot%2B2014-09-25%2Bat%2B5.33.34%2BPM.png

  -- 
 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/d/optout.




 -- 
 Matthew Moore
 DI/Docker (aka Convoy)
 Developer Infrastructure @ Google
  
  -- 
 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 javascript:.
 For more options, visit https://groups.google.com/d/optout.




 -- 
 Matthew Moore
 DI/Docker (aka Convoy)
 Developer Infrastructure @ Google
  

-- 
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Request to publish a Jenkins plug-in

2014-09-28 Thread domi
How is this one different to the existing teamconcert plugin? [1]
It seems very active.
Domi

[1] https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin

 Am 28.09.2014 um 06:09 schrieb Krishna Kishore clkkish...@gmail.com:
 
 Hi Jenkins Dev team,
 
 I am with the Rational Team Concert(RTC) Development team in IBM  
 (www.ibm.com, www.jazz.net). We are developing a plugin which will integrate 
 Jenkins Builds using Git as Source control to RTC Work items and builds. We 
 would like to publish the plugin at jenkins-ci.org. Here are the details 
 related to plugin
 
 Plugin Name: Team Concert Git Plugin
 Github Repository: https://github.com/clkkishore/teamconcert-git-plugin
 Github id: clkkishore
 Plugin Description: Integrates Jenkins with Rational Team Concert for Jenkins 
 Builds which use Git as source control. This plugin will create traceability 
 links from a Jenkins build to RTC work items and build result.
 
 Can someone please clone this to jenkinsci and provide me access for the 
 same. 
 
 Thanks In advance,
 
 Regards,
 Kishore
 
 PS: Currently the project 
 https://github.com/clkkishore/teamconcert-git-plugin contains only a readme 
 file will add the sources once the repository is cloned into jenkinssci space.
 
 -- 
 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-dev+unsubscr...@googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Need help testing JNA upgrade to 4.1.0

2014-09-28 Thread Craig Rodrigues
Hi,

The version of JNA in Jenkins has problems on FreeBSD.
These problems have been fixed in later versions of JNA.

I submitted this PR to upgrade Jenkins to JNA 4.1.0:

https://github.com/jenkinsci/jenkins/pull/1387

I was wondering if I could get some help testing on a few other platforms?
I have successfully tested on Ubuntu, MacOS X, Illumos, FreeBSD and posted
my results here:

https://github.com/jenkinsci/jenkins/pull/1387#issuecomment-57076567

The test I did was:

   - Checkout jenkins from my branch and build it:
  git clone -b JENKINS-24521-2 https://github.com/rodrigc/jenkins

  or download this war file which I built:

   https://people.freebsd.org/~rodrigc/jenkins/JENKINS-24251/

   - Ran:  *java -jar jenkins.war*
   - In Jenkins, *Manage Jenkins - Configure Global Security - Enable
   Security - Unix/user group database*
   - Logged into Jenkins. This uses the libpam4j module which uses JNA.

If people could take that jar file and do some JNA testing and provide
feedback at https://github.com/jenkinsci/jenkins/pull/1387
I would appreciate it.

Specifically, if someone could test on Windows to test JNA, I would
appreciate it.

--
Craig

-- 
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Commit access to xfpanel-plugin

2014-09-28 Thread Tilman Blumenbach
Hello,

I have opened a pull request for the xfpanel-plugin [1], but it does not
appear to get any attention from the maintainer(s) -- just like another
pull request from December 2013 [2].

As per [3], could I please get commit access to that repository so that
I can merge my changes myself (any maybe the other opend pull request as
well)? My GitHub username is Tblue.

Thanks!

Tilman Blumenbach

[1] https://github.com/jenkinsci/xfpanel-plugin/pull/13
[2] https://github.com/jenkinsci/xfpanel-plugin/pull/12
[3] https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories

-- 
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Request to publish a Jenkins plug-in

2014-09-28 Thread Krishna Kishore
Hi,

The existing plugin woks with the RTC Source control, it helps teams which 
use RTC as SCC and Jenkins as CI engine. The new plugin will work with 
projects which use Git as source control and integrate (i.e create 
traceability links) Jenkins builds with RTC Work Items and Builds. This 
plugin is for teams which use Git as Source control and want to use RTC for 
Tracking and Planning.

Thanks,
Kishore

On Sunday, 28 September 2014 12:37:47 UTC+5:30, Dominik Bartholdi wrote:

 How is this one different to the existing teamconcert plugin? [1]
 It seems very active.
 Domi

 [1] https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin

 Am 28.09.2014 um 06:09 schrieb Krishna Kishore clkki...@gmail.com 
 javascript::

 Hi Jenkins Dev team,

 I am with the Rational Team Concert(RTC) Development team in IBM  (
 www.ibm.com, www.jazz.net). We are developing a plugin which will 
 integrate Jenkins Builds using Git as Source control to RTC Work items and 
 builds. We would like to publish the plugin at jenkins-ci.org. Here are 
 the details related to plugin

 Plugin Name: Team Concert Git Plugin
 Github Repository: https://github.com/clkkishore/teamconcert-git-plugin
 Github id: clkkishore
 Plugin Description: Integrates Jenkins with Rational Team Concert for 
 Jenkins Builds which use Git as source control. This plugin will create 
 traceability links from a Jenkins build to RTC work items and build result.

 Can someone please clone this to jenkinsci and provide me access for the 
 same. 

 Thanks In advance,

 Regards,
 Kishore

 PS: Currently the project 
 https://github.com/clkkishore/teamconcert-git-plugin contains only a 
 readme file will add the sources once the repository is cloned into 
 jenkinssci space.

  -- 
 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 javascript:.
 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 jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Google OAuth Plugin does not load scope

2014-09-28 Thread 'Matthew Moore' via Jenkins Developers
Hrm, sadly there doesn't seem to be a nice client library for this API like
there are for a lot of the cloud APIs...



Regardless, the various Credential
http://javadoc.google-oauth-java-client.googlecode.com/hg/1.8.0-beta/com/google/api/client/auth/oauth2/Credential.html?is-external=true
objects implement HttpRequestInitializer
http://javadoc.google-http-java-client.googlecode.com/hg/1.8.3-beta/com/google/api/client/http/HttpRequestInitializer.html?is-external=true.
Translation: they understand how to annotate HttpRequests
http://javadoc.google-http-java-client.googlecode.com/hg/1.8.3-beta/com/google/api/client/http/HttpRequest.html
with:

-H Authorization: Bearer $TOKEN  \

Here is some sample code
https://github.com/jenkinsci/google-oauth-plugin/blob/master/src/main/java/com/google/jenkins/plugins/util/MetadataReader.java
that deals with raw HttpRequests in the oauth2 plugin as a start, although
it doesn't use credentials or POST.




I *think* the code you are going to want in a plugin is going to look
something like (beware, I have not tested this code in any way):
HttpRequestFactory requestFactory =
   new NetHttpTransport().createRequestFactory(*{insert Credential}*);

// Handles loading the file properly with remoting, but proxies thru the
master.
// By comparison, Storage uploads directly from the slave, to decrease load
on
// the master, but the code for that is a bit trickier to get right, and
this is
// a fine starting point.
InputStreamContent content = new InputStreamContent();
content.inputStream = filePath.read();
content.type = *{fill in mime type}*;

HttpRequest request = requestFactory.buildPostRequest(
   new GenericUrl(
https://www.googleapis.com/upload/chromewebstore/v1.1/items;),
   content);

request.getHeaders().set(x-goog-api-version, 2);

// Where the magic happens
request.execute();


There are also pretty good facilities in place for mocking out HttpRequest,
just factor the above code in your plugin such that HttpRequestFactory can
be passed in, and you should be able to write decent tests.  For factoring,
see how the aforementioned sample code
https://github.com/jenkinsci/google-oauth-plugin/blob/master/src/main/java/com/google/jenkins/plugins/util/MetadataReader.java#L77
structures things, and how its tests look
https://github.com/jenkinsci/google-oauth-plugin/blob/master/src/test/java/com/google/jenkins/plugins/util/MetadataReaderTest.java.
Also, there is a fair amount of overlap with the storage plugin, if you
ignore the fact that it has a nice client library.



If you do head down the path of writing the plugin, please let me know and
I'd be happy to give you pointers and help review the code (or loop in a
suitable surrogate).

thanks, and hopefully this is helpful.
-M



On Sat, Sep 27, 2014 at 11:27 PM, Calvin cc...@pingidentity.com wrote:

 Ok sorry, I'm fairly new to using Google's API and Jenkins and I think I
 see where my confusion lies, I was thinking that the Google OAuth Plugin
 automatically provides the scopes, however after relooking at
 https://wiki.jenkins-ci.org/display/JENKINS/Google+OAuth+Plugin, I
 realize that this plugin just provides the Google service account options
 that I can associate to Jenkins and then I would need to probably implement
 another plugin like the GoogleCloudStorage that exposes the scopes needed
 to access the Chrome Web Store APIs.  I want to be able to do something
 like the following within Jenkins as a post process to automatically
 publish/update a Chrome extension we've developed directly to the Chrome
 Store,

  curl \-H Authorization: Bearer $TOKEN  \-H x-goog-api-version: 2 \-X 
  POST \-T $FILE_NAME \-v \
 https://www.googleapis.com/upload/chromewebstore/v1.1/items


 On Saturday, September 27, 2014 9:58:57 PM UTC-7, Matthew Moore wrote:

 I assume you are building a plugin to access this API, using an OAuth2
 credential?  Otherwise, I'll probably need some more context on how you
 plan to wire things up...


 If you are building such a plugin you should look at how the Google Cloud
 Storage plugin specifies its OAuth2 scope requirement: https://github.
 com/jenkinsci/google-storage-plugin/blob/master/src/main/
 java/com/google/jenkins/plugins/storage/GoogleCloudStorageUploader.
 java#L51

 Putting an appropriately constructed @RequiresDomain on any describable
 (e.g. Publishers) will make the error you are seeing go away.  As I said
 (more tersely) before, we scan for these annotations to dynamically
 populate the pertinent set of scopes for installed plugins.




 Specifically, you are going to want to define:
 public class ChromeWebStoreScopeRequirement extends
 GoogleOAuth2ScopeRequirement {

 which returns the scope you list, similar to StorageScopeRequirement
 https://github.com/jenkinsci/google-storage-plugin/blob/master/src/main/java/com/google/jenkins/plugins/storage/StorageScopeRequirement.java,
 then annotate something like this:
 @RequiresDomain(value = ChromeWebStoreScopeRequirement.class)
 public class 

Re: New Jenkins plugin to be hosted; Deployment Dashboard

2014-09-28 Thread Miel Donkers
Hi Ullrich,

As indicated you may give Andreas and Marcel also access, or I'll add them 
to the repository as soon as I can access it.

Thanks in advance,

Miel

On Friday, September 26, 2014 5:48:13 PM UTC+2, Miel Donkers wrote:

 Hi,

 My github account name is mdonkers
 (I've already got access to the appdynamics-plugin repository)

 Thanks!
 /Miel

 On Friday, September 26, 2014 12:45:26 PM UTC+2, Ullrich Hafner wrote:

 Created https://github.com/jenkinsci/deployment-dashboard-plugin
 Currently we are not able to assign group permissions so we need to grant 
 access for individual users only. What is your GitHub user name?

 Welcome aboard! 

 Ulli

 Am 26.09.2014 um 12:09 schrieb Miel Donkers miel.d...@codecentric.nl:

 Dear Jenkins dev team,

 We are developing a new Jenkins plugin (a dashboard for deploying to 
 various environments) that we would like to have hosted on the Jenkins 
 Github.

 Name (also Github repo name): deployment-dashboard-plugin
 Github id: mdonkers
 Github project to be forked: 
 https://github.com/codecentric/jenkins-deployment-dashboard-plugin

 Please let me know if more information is required

 Thanks in advance and best regards,

 Miel

 -- 
 *Miel Donkers | Agile Solution Developer*


 *codecentric Nederland BV | Prinsenkade 7 | 4811VB Breda | 
 Netherlandstel: +31 (0) 85.400.0011 | mobiel: +31 (0) 6.511.977.38 | 
 miel.d...@codecentric.nl*

 *www.codecentric.nl http://www.codecentric.nl/ | blog.codecentric.nl 
 http://blog.codecentric.nl/ | @codecentric_nl 
 http://www.twitter.com/codecentric_nl*


 Volg ons op LinkedIn 
 http://www.linkedin.com/company/codecentric-nederland-bv?trk=company_name
 Tweet met ons op Twitter https://twitter.com/codecentric_nl
 Lees mee op onze blog https://blog.codecentric.de/en/
 Like ons op Facebook https://www.facebook.com/codecentric.nl?fref=ts
 Volg ons op Github https://github.com/organizations/codecentric  

 Meer over ons: codecentric Nederland BV is een Java Software Craftsmen 
 projecten en consultancy organisatie, met focus op Continuous Delivery, 
 Agile development, Agile Testing en Applicatie Performance Management 
 (AppDynamics Pro http://www.appdynamics.com/freetrial/?partnerid=0nxMIw). 
 codecentric is kennis gedreven met ruim 200 medewerkers in Nederland, 
 Duitsland, Bosnië en Herzegovina en Servië.
  
 -- 
 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/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 jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help : Make a new release for dependency-analyzer-plugin

2014-09-28 Thread Etienne Jouvin
I've installed the git application from official web site.
I will try to investigate and read log files.

Recommanding working on Linux can not be a solution for me. I work with my 
company computer... So no way to install Linux on it and for me, this is 
far away from Java philosophy Write once, run everywhere ;)


Le samedi 27 septembre 2014 06:27:06 UTC+2, Ikedam a écrit :

 What git client do you use when you commit and push codes?
 Your problem sounds that git launched from maven doesn't work
 as when you commit codes.

 Anyway, I highly recommend you to work on Linux.
 Most Jenkins developers work on Linux,
 there are often problems only on Windows,
 and few developers can help you.

 Regards,
 ikedam


 On Friday, September 26, 2014 6:01:58 PM UTC+9, Etienne Jouvin wrote:

 This morning, the job on 
 https://jenkins.ci.cloudbees.com/job/plugins/job/dependency-analyzer-plugin/ 
 is OK after commit new pom.

 I really need to study Git, I do not understand anything :(



-- 
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help : Make a new release for dependency-analyzer-plugin

2014-09-28 Thread Ikedam
Oh, wrong git URI.

The one in the pom.xml:
git://github.com/jenkinsci/dependency-analyzer.git

Should be:
git://github.com/jenkinsci/dependency-analyzer-plugin.git

-- 
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


JIRA down again

2014-09-28 Thread Andrew Gray
JIRA has fallen over again sometime in the last 30 odd minutes.

Just letting you know.

Cheers,

Andrew

-- 
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Request to publish a Jenkins plug-in

2014-09-28 Thread domi
How about extending the existing one with your functionality?
From a users point of view this is what I would love to see - as I guess you 
would provite of some of the existing features too
Or maybe extract the parts the two plugins would have in common and create a 
base plugin which can be extended by implementing EPs
Domi

On 28.09.2014, at 16:01, Krishna Kishore clkkish...@gmail.com wrote:

 Hi,
 
 The existing plugin woks with the RTC Source control, it helps teams which 
 use RTC as SCC and Jenkins as CI engine. The new plugin will work with 
 projects which use Git as source control and integrate (i.e create 
 traceability links) Jenkins builds with RTC Work Items and Builds. This 
 plugin is for teams which use Git as Source control and want to use RTC for 
 Tracking and Planning.
 
 Thanks,
 Kishore
 
 On Sunday, 28 September 2014 12:37:47 UTC+5:30, Dominik Bartholdi wrote:
 How is this one different to the existing teamconcert plugin? [1]
 It seems very active.
 Domi
 
 [1] https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin
 
 Am 28.09.2014 um 06:09 schrieb Krishna Kishore clkki...@gmail.com:
 
 Hi Jenkins Dev team,
 
 I am with the Rational Team Concert(RTC) Development team in IBM  
 (www.ibm.com, www.jazz.net). We are developing a plugin which will integrate 
 Jenkins Builds using Git as Source control to RTC Work items and builds. We 
 would like to publish the plugin at jenkins-ci.org. Here are the details 
 related to plugin
 
 Plugin Name: Team Concert Git Plugin
 Github Repository: https://github.com/clkkishore/teamconcert-git-plugin
 Github id: clkkishore
 Plugin Description: Integrates Jenkins with Rational Team Concert for 
 Jenkins Builds which use Git as source control. This plugin will create 
 traceability links from a Jenkins build to RTC work items and build result.
 
 Can someone please clone this to jenkinsci and provide me access for the 
 same. 
 
 Thanks In advance,
 
 Regards,
 Kishore
 
 PS: Currently the project 
 https://github.com/clkkishore/teamconcert-git-plugin contains only a readme 
 file will add the sources once the repository is cloned into jenkinssci 
 space.
 
 
 -- 
 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/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 jenkinsci-dev+unsubscr...@googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.