Re: plugin data migration - potential incompatibility

[Robert St. John]

I think you might tell me this is dirty and knock it off, but suppose I did 
something like the following in my SimpleBuildStep.

@Override
public boolean prebuild(Build build, BuildListener listener) {
if (this.entries == null) {
return true;
}
if (build == null) {
return true;
}
Job job = build.getParent();
if (!(job instanceof Project)) {
return true;
}
Project project = (Project) job;
DescribableList builders = 
project.getBuildersList();
List upgraded = new ArrayList<>(builders.size() + 
getEntries().size() - 1);
for (Builder builder : builders) {
if (builder == this) {
for (Apk apk : getEntries()) {
SignApksBuilder b = new SignApksBuilder(null);
b.setKeyStore(apk.getKeyStore());
b.setKeyAlias(apk.getAlias());
b.setApksToSign(apk.getApksToSign());
b.setArchiveSignedApks(apk.getArchiveSignedApks());
b.setArchiveUnsignedApks(apk.getArchiveUnsignedApks());
upgraded.add(b);
}
}
else {
upgraded.add(builder);
}
}
try {
builders.replaceBy(upgraded);
}
catch (IOException e) {
listener.getLogger().println("[SignApksBuilder] error migrating 
job data");
e.printStackTrace(listener.getLogger());
}
return true;
}


On Thursday, February 16, 2017 at 10:20:09 AM UTC-7, Jesse Glick wrote:
>
> On Thu, Feb 16, 2017 at 1:47 AM, Robert St. John  > wrote: 
> > instead of a job with one 
> > SignApksBuilder with multiple Apk objects, one would need to add 
> multiple 
> > SignApksBuilder steps to a job to achieve the same result.  Does Jenkins 
> > offer a mechanism to support a data migration like this? 
>
> Not easily. And if it is a `SimpleBuildStep` actually used from 
> Pipeline, not at all, since you cannot migrate scripts, only 
> `config.xml` for freestyle projects. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/36659b89-a948-42a9-9a94-c1517eeb87c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Update Center not updating?

[Daniel Beck]

> On 16.02.2017, at 23:29, Shawn MacArthur  wrote:
> 
> I've updated a plugin here
> 
> https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/nouvola-divecloud/
> 
> but the latest version doesn't appear in 
> 
> https://updates.jenkins-ci.org/update-center.json
> 
> It's been about 14 hours since my first update. Any ideas? Thanks!

We've had problems with the mirrors today, so wouldn't be surprised if that's a 
bit delayed. FWIW I can see it there, version 1.03.

The other one is probably a bit too recent, it may take an few hours to show up.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/020FEC80-E964-4431-96B6-25DBAC787E14%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Update Center not updating?

[Shawn MacArthur]

I've updated a plugin here

https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/nouvola-divecloud/

but the latest version doesn't appear in 

https://updates.jenkins-ci.org/update-center.json

It's been about 14 hours since my first update. Any ideas? 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d50399b0-10a7-4ffc-8e98-3ce6bbbe8b3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: EnvironmentContributingAction.buildEnvVars doesn't work

[Jesse Glick]

On Thu, Feb 16, 2017 at 2:53 PM, sohl  wrote:
> The plugin uses a standard method to set the variable by implementing
> "EnvironmentContributingAction.buildEnvVars"

This interface is not currently compatible with Pipeline I am afraid.

Anyway where steps should provide information to other steps in the
build, it is better to implement `Step` directly (rather than
`SimpleBuildStep`), and have a non-void return value.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0vHN12%3DQW-WfiqPS7OTgsX0nZCB41Qa3awBb0jWLyNUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put NUnit Plug-in up for adoption

[Slide]

Since you are the current maintainer, I'll take that as a blessing to do it
:-)

Thanks!

On Thu, Feb 16, 2017 at 2:21 PM 'Bruno P. Kinoshita' via Jenkins Developers
 wrote:

> +1
>
> Bruno
>
>
>
>
> 
> From: slide 
> To: Jenkins Developers 
> Cc: brunodepau...@yahoo.com.br
> Sent: Friday, 17 February 2017 10:17 AM
> Subject: Re: Put NUnit Plug-in up for adoption
>
>
>
> I would like to take up ownership of this plugin, if no one objects I can
> change the default assignee and submit the PR for the repo permissions.
>
> Thanks,
>
> Alex
>
> On Wednesday, January 18, 2017 at 12:25:47 PM UTC-7, kinow wrote:
> Hi,
> >
> >
> >There was a few requests lately for me to fix an issue in order to
> provide nunit3 compatibility with the plug-in.
> >
> >
> >Unfortunately I'm on a 45 days vacation, and won't work on much Open
> Source until March.
> >
> >
> >So I'd like to put the nunit plugin up for adoption. This way someone
> else can help the users and prepare a new release.
> >
> >
> >Could someone refresh my memory on the process for that? Do I need to
> update a git repo or wiki page?
> >
> >
> >Cheers
> >Bruno
> >
> >
> >Sent from Yahoo Mail on Android
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3c41ac81-d4f5-4b46-878b-153adaa56eed%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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/1816982514.1162990.1487279926440%40mail.yahoo.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVe607UYHYY2spMBRwAvnN9yEEka3z4ej%2B-BCFr5UBJabg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put NUnit Plug-in up for adoption

['Bruno P. Kinoshita' via Jenkins Developers]

+1

Bruno





From: slide 
To: Jenkins Developers  
Cc: brunodepau...@yahoo.com.br
Sent: Friday, 17 February 2017 10:17 AM
Subject: Re: Put NUnit Plug-in up for adoption



I would like to take up ownership of this plugin, if no one objects I can 
change the default assignee and submit the PR for the repo permissions.

Thanks,

Alex

On Wednesday, January 18, 2017 at 12:25:47 PM UTC-7, kinow wrote:
Hi,
>
>
>There was a few requests lately for me to fix an issue in order to provide 
>nunit3 compatibility with the plug-in.
>
>
>Unfortunately I'm on a 45 days vacation, and won't work on much Open Source 
>until March.
>
>
>So I'd like to put the nunit plugin up for adoption. This way someone else can 
>help the users and prepare a new release.
>
>
>Could someone refresh my memory on the process for that? Do I need to update a 
>git repo or wiki page?
>
>
>Cheers
>Bruno
>
>
>Sent from Yahoo Mail on Android
-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3c41ac81-d4f5-4b46-878b-153adaa56eed%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1816982514.1162990.1487279926440%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put NUnit Plug-in up for adoption

[slide]

I would like to take up ownership of this plugin, if no one objects I can 
change the default assignee and submit the PR for the repo permissions.

Thanks,

Alex

On Wednesday, January 18, 2017 at 12:25:47 PM UTC-7, kinow wrote:
>
> Hi,
>
> There was a few requests lately for me to fix an issue in order to provide 
> nunit3 compatibility with the plug-in.
>
> Unfortunately I'm on a 45 days vacation, and won't work on much Open 
> Source until March.
>
> So I'd like to put the nunit plugin up for adoption. This way someone else 
> can help the users and prepare a new release.
>
> Could someone refresh my memory on the process for that? Do I need to 
> update a git repo or wiki page?
>
> Cheers
> Bruno
>
> Sent from Yahoo Mail on Android 
> 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3c41ac81-d4f5-4b46-878b-153adaa56eed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Email-ext plugin conflicting with token-macro plugin

[Daniel Beck]

> On 16.02.2017, at 20:56, Pino Alu  wrote:
> 
> Using Jenkins core v 1.625.3

Jenkins 2.16 and up tell you when your plugin configuration is invalid and 
refuse to load plugins with unsatisfied dependencies. I recommend you upgrade 
to a recent release.

Also, please ask further questions on the jenkinsci-users mailing list. This is 
a user question.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2569D8F9-FB81-4790-9336-8550CA7DB7B7%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Email-ext plugin conflicting with token-macro plugin

[Pino Alu]

Any idea on how to resolve this error when email is triggered?

ERROR: Step ‘Editable Email Notification’ aborted due to exception: 

*19:00:14* *java.lang.NoSuchMethodError* 
: 
org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/Run;Lhudson/FilePath;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String;



On Thursday, February 16, 2017 at 9:44:08 AM UTC-6, Pino Alu wrote:

I am trying to locate which version of Email-ext goes with token-macro 
> plugin?  Currently we have *Email-Ext v2.55* installed and *token-macro 
> v1.12.1* installed and Email-ext is not sending email but the Jenkins 
> mail plugin is configured and works.  We receive this error and I feel it 
> is an issue with token-macro version not playing nice with Email-ext.  Any 
> help would be great.
>
>  
>
> Error:
>
>  
>
> *19:00:14* Sending email for trigger: Success
>
> *19:00:14* ERROR: Step ‘Editable Email Notification’ aborted due to 
> exception: 
>
> *19:00:14* *java.lang.NoSuchMethodError* 
> : 
> org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/Run;Lhudson/FilePath;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String;
>
> *19:00:14*   at 
> *hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:80)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:706)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:595)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:355)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:345)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:253)*
>  
> 
>
> *19:00:14*   at 
> *hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)* 
> 
>
> *19:00:14*   at 
> *hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)*
>  
> 
>
> *19:00:14*   at 
> *hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)*
>  
> 
>
> *19:00:14*   at 
> *hudson.model.Build$BuildExecution.cleanUp(Build.java:195)* 
> 
>
> *19:00:14*   at *hudson.model.Run.execute(Run.java:1788)* 
> 
>
> *19:00:14*   at *hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)* 
> 
>
> *19:00:14*   at 
> *hudson.model.ResourceController.execute(ResourceController.java:98)* 
> 
>
> *19:00:14*   at *hudson.model.Executor.run(Executor.java:408)* 
> 
>
>  
>
> Here is our config for email-ext.
>
> 
> 
> $DEFAULT_RECIPIENTS
> 
> 
> 
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> 
> 
> 
> false
> false
> $PROJECT_DEFAULT_REPLYTO
> project
> 
> 
> 
> 
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> 
> 
> 
> 
> 
> false
> false
> $PROJECT_DEFAULT_REPLYTO
> project
> 
> 
> 
> text/plain
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> $DEFAULT_PRESEND_SCRIPT
> 
> false
> false
> $DEFAULT_REPLYTO
> false
> false
> 
> 
>
>  
>
> Thanks,
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop 

Re: Email-ext plugin conflicting with token-macro plugin

[Pino Alu]

Yes, I installed from plugin manager.  Where is the email-ext pom.xml 
located as I would need another team member to locate it and send to me?

On Thursday, February 16, 2017 at 10:23:03 AM UTC-6, slide wrote:
>
> Did you install via the plugin manager? If so, then the correct version of 
> token macro should have been installed. If not, then you need to check the 
> pom file for email-ext and determine from there what version is needed for 
> each dependency.
>
> On Thu, Feb 16, 2017, 09:01 Pino Alu  
> wrote:
>
>> Using Jenkins core v 1.625.3
>>
>>
>> On Thursday, February 16, 2017 at 9:44:08 AM UTC-6, Pino Alu wrote:
>>>
>>> I am trying to locate which version of Email-ext goes with token-macro 
>>> plugin?  Currently we have *Email-Ext v2.55* installed and *token-macro 
>>> v1.12.1* installed and Email-ext is not sending email but the Jenkins 
>>> mail plugin is configured and works.  We receive this error and I feel it 
>>> is an issue with token-macro version not playing nice with Email-ext.  Any 
>>> help would be great.
>>>
>>>  
>>>
>>> Error:
>>>
>>>  
>>>
>>> *19:00:14* Sending email for trigger: Success
>>>
>>> *19:00:14* ERROR: Step ‘Editable Email Notification’ aborted due to 
>>> exception: 
>>>
>>> *19:00:14* *java.lang.NoSuchMethodError* 
>>> :
>>>  
>>> org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/Run;Lhudson/FilePath;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String;
>>>
>>> *19:00:14*   at 
>>> *hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:80)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:706)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:595)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:355)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:345)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:253)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)* 
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)*
>>>  
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.model.Build$BuildExecution.cleanUp(Build.java:195)* 
>>> 
>>>
>>> *19:00:14*   at *hudson.model.Run.execute(Run.java:1788)* 
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)* 
>>> 
>>>
>>> *19:00:14*   at 
>>> *hudson.model.ResourceController.execute(ResourceController.java:98)* 
>>> 
>>>
>>> *19:00:14*   at *hudson.model.Executor.run(Executor.java:408)* 
>>> 
>>>
>>>  
>>>
>>> Here is our config for email-ext.
>>>
>>> 
>>> 
>>> $DEFAULT_RECIPIENTS
>>> 
>>> 
>>> 
>>> $PROJECT_DEFAULT_SUBJECT
>>> $PROJECT_DEFAULT_CONTENT
>>> 
>>> 
>>> 
>>> 
>>> false
>>> false
>>> $PROJECT_DEFAULT_REPLYTO
>>> project
>>> 
>>> 
>>> 
>>> 
>>> $PROJECT_DEFAULT_SUBJECT
>>> $PROJECT_DEFAULT_CONTENT
>>> 
>>> 
>>> 
>>> 

EnvironmentContributingAction.buildEnvVars doesn't work

[sohl]

I'm using Saltstack plugin (https://github.com/jenkinsci/saltstack-plugin) 
in the pipeline. The plugin has an option to return output 
into SALTBUILDOUTPUT variable.

Although the plugin is not listed as pipeline compatible, it nevertheless 
works i.e. I'm able to run it using pipeline:
-
node {
  salt authtype: 'pam', clientInterface: local(arguments: 'xxx', 
blockbuild: true, function: 'grains.get', target: 'atarget', targetType: 
'glob'), credentialsId: '497b...', saveEnvVar: true, servername: 
'http://172'

println("SALTBUILDOUTPUT 1 = ${env.SALTBUILDOUTPUT}")
printf("SALTBUILDOUTPUT 3 = %s\n", env)
}
-

The output:
-
Running jid: 20170215152138504719

SALTBUILDOUTPUT 1 = null
SALTBUILDOUTPUT 3 = 
org.jenkinsci.plugins.workflow.cps.EnvActionImpl@1765f04e
...
-

The plugin uses a standard method to set the variable by implementing 
"EnvironmentContributingAction.buildEnvVars" in "class PublishEnvVarAction 
extends InvisibleAction implements EnvironmentContributingAction".

Here is a snippet where it is called:
-
public boolean perform(Run build,...) {
...
if (saveEnvVar) {
build.addAction(new PublishEnvVarAction("SALTBUILDOUTPUT", 
returnArray.toString()));
build.getEnvironment(listener);
}
...
}
--
I ran the plugin in the debugger and attest the snippet above was called as 
expected. 
On the other hand 'buildEnvVars' has never been called i.e. the breakpoint 
was never hit. Consequently the SALTBUILDOUTPUT remained NULL.
-

I used a few versions of Jenkins while debugging including one built from 
Git (2.47-SNAPSHOT)

I also built the Saltstack plugin from sources with parent 
"org.jenkins-ci.plugins/plugin/2.20". Note that plugin has an obvious bug. 
It tries to readdress returnArray parameter within the scope of the called 
method, so that after the call returns all the information in returnArray 
is lost. I fixed the bug and the job returns output OK i.e. 
"returnArray.toString()" above returns information that can be seen in the 
debugger and is also printed by Jenkins into the log.

I suspect that some changes in Jenkins API rendered 
"EnvironmentContributingAction.buildEnvVars" useless. This is NOT a 
Saltstack plugin problem.

Please, help with resolving this.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/560d8a8c-ce4a-4fee-9351-fbbc9aba6e3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: plugin data migration - potential incompatibility

[Jesse Glick]

On Thu, Feb 16, 2017 at 1:47 AM, Robert St. John  wrote:
> instead of a job with one
> SignApksBuilder with multiple Apk objects, one would need to add multiple
> SignApksBuilder steps to a job to achieve the same result.  Does Jenkins
> offer a mechanism to support a data migration like this?

Not easily. And if it is a `SimpleBuildStep` actually used from
Pipeline, not at all, since you cannot migrate scripts, only
`config.xml` for freestyle projects.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1v7N-WCgqmMwQ%3D5ayzZzJdu5A3TGQk1nt6%2BYtF8S0qhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly/Plugin pipeline script support for optionalBlock

[Jesse Glick]

On Thu, Feb 16, 2017 at 4:30 AM,  wrote:
>The only example I can find this the ui-samples-plugin which has an overly 
>complicated example that I cannot follow.

That is the cleanest example I know of. You can use GitHub search to
look for others but I cannot say whether they will be good examples or
bad examples, unless I wrote them myself.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2%2BQ2nfLDXGXcGrA3fkmp%2B-ZKjt1%3DutNkcSQ5_td%3DH7OQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Email-ext plugin conflicting with token-macro plugin

[Slide]

Did you install via the plugin manager? If so, then the correct version of
token macro should have been installed. If not, then you need to check the
pom file for email-ext and determine from there what version is needed for
each dependency.

On Thu, Feb 16, 2017, 09:01 Pino Alu  wrote:

> Using Jenkins core v 1.625.3
>
>
> On Thursday, February 16, 2017 at 9:44:08 AM UTC-6, Pino Alu wrote:
>
> I am trying to locate which version of Email-ext goes with token-macro
> plugin?  Currently we have *Email-Ext v2.55* installed and *token-macro
> v1.12.1* installed and Email-ext is not sending email but the Jenkins
> mail plugin is configured and works.  We receive this error and I feel it
> is an issue with token-macro version not playing nice with Email-ext.  Any
> help would be great.
>
>
>
> Error:
>
>
>
> *19:00:14* Sending email for trigger: Success
>
> *19:00:14* ERROR: Step ‘Editable Email Notification’ aborted due to exception:
>
> *19:00:14* *java.lang.NoSuchMethodError* 
> : 
> org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/Run;Lhudson/FilePath;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String;
>
> *19:00:14*   at 
> *hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:80)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:706)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:595)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:355)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:345)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:253)*
>  
> 
>
> *19:00:14*   at 
> *hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)* 
> 
>
> *19:00:14*   at 
> *hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)*
>  
> 
>
> *19:00:14*   at 
> *hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)*
>  
> 
>
> *19:00:14*   at 
> *hudson.model.Build$BuildExecution.cleanUp(Build.java:195)* 
> 
>
> *19:00:14*   at *hudson.model.Run.execute(Run.java:1788)* 
> 
>
> *19:00:14*   at *hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)* 
> 
>
> *19:00:14*   at 
> *hudson.model.ResourceController.execute(ResourceController.java:98)* 
> 
>
> *19:00:14*   at *hudson.model.Executor.run(Executor.java:408)* 
> 
>
>
>
> Here is our config for email-ext.
>
> 
> 
> $DEFAULT_RECIPIENTS
> 
> 
> 
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> 
> 
> 
> false
> false
> $PROJECT_DEFAULT_REPLYTO
> project
> 
> 
> 
> 
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> 
> 
> 
> 
> 
> false
> false
> $PROJECT_DEFAULT_REPLYTO
> project
> 
> 
> 
> text/plain
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> $DEFAULT_PRESEND_SCRIPT
> 
> false
> false
> $DEFAULT_REPLYTO
> false
> false
> 
> 
>
>
>
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To 

Re: Email-ext plugin conflicting with token-macro plugin

[Pino Alu]

Using Jenkins core v 1.625.3

On Thursday, February 16, 2017 at 9:44:08 AM UTC-6, Pino Alu wrote:
>
> I am trying to locate which version of Email-ext goes with token-macro 
> plugin?  Currently we have *Email-Ext v2.55* installed and *token-macro 
> v1.12.1* installed and Email-ext is not sending email but the Jenkins 
> mail plugin is configured and works.  We receive this error and I feel it 
> is an issue with token-macro version not playing nice with Email-ext.  Any 
> help would be great.
>
>  
>
> Error:
>
>  
>
> *19:00:14* Sending email for trigger: Success
>
> *19:00:14* ERROR: Step ‘Editable Email Notification’ aborted due to 
> exception: 
>
> *19:00:14* *java.lang.NoSuchMethodError* 
> : 
> org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/Run;Lhudson/FilePath;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String;
>
> *19:00:14*   at 
> *hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:80)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:706)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:595)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:355)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:345)*
>  
> 
>
> *19:00:14*   at 
> *hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:253)*
>  
> 
>
> *19:00:14*   at 
> *hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)* 
> 
>
> *19:00:14*   at 
> *hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)*
>  
> 
>
> *19:00:14*   at 
> *hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)*
>  
> 
>
> *19:00:14*   at 
> *hudson.model.Build$BuildExecution.cleanUp(Build.java:195)* 
> 
>
> *19:00:14*   at *hudson.model.Run.execute(Run.java:1788)* 
> 
>
> *19:00:14*   at *hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)* 
> 
>
> *19:00:14*   at 
> *hudson.model.ResourceController.execute(ResourceController.java:98)* 
> 
>
> *19:00:14*   at *hudson.model.Executor.run(Executor.java:408)* 
> 
>
>  
>
> Here is our config for email-ext.
>
> 
> 
> $DEFAULT_RECIPIENTS
> 
> 
> 
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> 
> 
> 
> false
> false
> $PROJECT_DEFAULT_REPLYTO
> project
> 
> 
> 
> 
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> 
> 
> 
> 
> 
> false
> false
> $PROJECT_DEFAULT_REPLYTO
> project
> 
> 
> 
> text/plain
> $PROJECT_DEFAULT_SUBJECT
> $PROJECT_DEFAULT_CONTENT
> 
> $DEFAULT_PRESEND_SCRIPT
> 
> false
> false
> $DEFAULT_REPLYTO
> false
> false
> 
> 
>
>  
>
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e483b174-f35a-472d-ba54-15cde5632963%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Email-ext plugin conflicting with token-macro plugin

[Pino Alu]

 

I am trying to locate which version of Email-ext goes with token-macro 
plugin?  Currently we have *Email-Ext v2.55* installed and *token-macro 
v1.12.1* installed and Email-ext is not sending email but the Jenkins mail 
plugin is configured and works.  We receive this error and I feel it is an 
issue with token-macro version not playing nice with Email-ext.  Any help 
would be great.

 

Error:

 

*19:00:14* Sending email for trigger: Success

*19:00:14* ERROR: Step ‘Editable Email Notification’ aborted due to exception: 

*19:00:14* *java.lang.NoSuchMethodError* 
: 
org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/Run;Lhudson/FilePath;Lhudson/model/TaskListener;Ljava/lang/String;ZLjava/util/List;)Ljava/lang/String;

*19:00:14*   at 
*hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:80)*
 


*19:00:14*   at 
*hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:706)*
 


*19:00:14*   at 
*hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:595)*
 


*19:00:14*   at 
*hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:355)*
 


*19:00:14*   at 
*hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:345)*
 


*19:00:14*   at 
*hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:253)*
 


*19:00:14*   at 
*hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)* 


*19:00:14*   at 
*hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)*
 


*19:00:14*   at 
*hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)*
 


*19:00:14*   at *hudson.model.Build$BuildExecution.cleanUp(Build.java:195)* 


*19:00:14*   at *hudson.model.Run.execute(Run.java:1788)* 


*19:00:14*   at *hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)* 


*19:00:14*   at 
*hudson.model.ResourceController.execute(ResourceController.java:98)* 


*19:00:14*   at *hudson.model.Executor.run(Executor.java:408)* 


 

Here is our config for email-ext.



$DEFAULT_RECIPIENTS



$PROJECT_DEFAULT_SUBJECT
$PROJECT_DEFAULT_CONTENT




false
false
$PROJECT_DEFAULT_REPLYTO
project




$PROJECT_DEFAULT_SUBJECT
$PROJECT_DEFAULT_CONTENT






false
false
$PROJECT_DEFAULT_REPLYTO
project



text/plain
$PROJECT_DEFAULT_SUBJECT
$PROJECT_DEFAULT_CONTENT

$DEFAULT_PRESEND_SCRIPT

false
false
$DEFAULT_REPLYTO
false
false



 

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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5f6b1ee0-739f-49a7-8fe3-67a1d13b447c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.32.3 LTS RC testing started

[Oliver Gondža]

Hello everyone,

Latest LTS RC was made public and it is ready to be tested. Release is
scheduled for 2017-03-01.

Report your findings in this thread or on the test plan wiki page.

Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.32.3/jenkins.war
Check community maintained LTS test plan 
https://wiki.jenkins-ci.org/display/JENKINS/LTS+2.32.x+RC+Testing


Thanks
--
oliver

--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/91d9b4f6-3e3e-c26e-f04e-14b74016f7da%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: plugin data migration - potential incompatibility

[Daniel Beck]

> On 16.02.2017, at 07:47, Robert St. John  wrote:
> 
> Does Jenkins offer a mechanism to support a data migration like this?

These are the resources we currently have for format changes:

- http://javadoc.jenkins-ci.org/index.html?hudson/XmlFile.html
- 
https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility
- https://wiki.jenkins-ci.org/display/JENKINS/XStream+Tips


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1A7B796C-917A-46FE-B148-6930BC4DD771%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Project ideas for student projects in the area of testing

[Oleg Nenashev]

Hi Ulli,

Do you consider aligning these activities with Google Summer of Code? 
Currently we are looking for project ideas, and actually test framework 
improvements + test improvements could be a good project. 

I understand that GSoC implies a significant time dedication by students, 
which likely goes far beyond a single course, but it may it can be an 
option if the students are interested.

Thanks in advance,
Oleg

понедельник, 13 февраля 2017 г., 22:40:00 UTC+3 пользователь Mark Waite 
написал:
>
> I'd love to have students help create Jenkins jobs which illustrate 
> specific bugs in the git plugin, for example.  Sample jobs which illustrate 
> different bugs as Jenkins jobs are available from the lts-with-plugins 
> branch of my docker repository.  I've found it very powerful to have a 
> Jenkins job per bug report, either as a pipeline job (branch in a git 
> repository like my jenkins-bugs repository) or as a freestyle job which 
> shows the bug and marks itself unstable when the bug is detected.
>
> I hope to propose a blog posting describing the technique of using one or 
> more Jenkins job definitions for each bug.  I've found it very helpful to 
> verify bugs remain fixed while detecting problems on multiple platforms.
>
> Mark Waite
>
> On Mon, Feb 13, 2017 at 11:44 AM Victor Martinez  > wrote:
>
>> Maybe it is a bit out of the scope and I don't know whether there is 
>> already a ongoing testing framework for the pipeline. But, is it something 
>> feasible? It might be a really good contribution to the community
>> Cheers
>>
>> --
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/bf2dbfa0-c524-4673-bfb5-6e55c05de2d2%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/75a29c62-c428-4ffe-8b59-a74053281829%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSOC 2017 - Regarding getting started with project "Support core plugin improvements"

[Oleg Nenashev]

Hi Rushal,

Yes, some ramp-up will be really useful. I have CCed Adrien and Steven. 
They would be the best contacts during the initial study if you consider 
working on the Support Core plugin.

Currently we are working on preparing this and other project ideas. If 
Jenkins project gets accepted to GSoC2017, we will schedule public office 
hours with potential students and mentors.

Best regards,
Oleg Nenashev

понедельник, 13 февраля 2017 г., 21:42:58 UTC+3 пользователь Rushal Verma 
написал:
>
> Hello everyone,
> I am Rushal Verma from India. I am currently a third-year undergraduate 
> student and wanted to participate in GSOC 17. This is my first-time 
> participation in the GSOC. I am interested in Jenkins project "Support core 
> plugin improvements". It needs java basic and I worked with java 
> technologies before as well and interested in expanding my knowledge of it. 
> I worked with java awt image, swing and sql libraries in my college project(
> https://github.com/rusrushal13/Genetic_Algorithm). I also get selected in 
> Season of KDE 16(https://season.kde.org/?q=view_projects=41=786). 
> I haven't used Jenkins before so I wanted to get started with it and get 
> used to it before GSOC 17 to showcase myself and one more thing what I 
> wanted is to someone mentor me for my proposal as this is my first time 
> participation in GSOC so if someone just gets me reviewed, it will assure 
> me that I am going good in my preparation for GSOC 17.
>
> Contact Information :
> Github : https://github.com/rusrushal13
> Twitter : https://twitter.com/rusrushal13
> Linkedin: https://linkedin.com/in/rushalverma
> Email : rusru...@gmail.com 
> Blog: rushalvera.wordpress.com
> Mobile No : +91-8004938694
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/03074ec6-6a2d-420b-a8e1-6bef285ceee8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly/Plugin pipeline script support for optionalBlock

[andrew . sumner]

 

Maybe I'm not looking in the right places or I just don't understand the 
code but I cannot see how to get an optionalProperty to work.  The only 
example I can find this the ui-samples-plugin which has an overly 
complicated example that I cannot follow.

 
1. Do you have any advice on how to search existing plugin code for 
optionalProperty usage?  Google isn't that helpful...

2. Can you either:

   - point me at a plugin that has a simple implementation that I could use 
   to adapt the following code 

or


   - suggest what changes I need to make to convert the following 
   optionalBlock to an optionalProperty? 

  



 

*Jelly
 
Snippet*






 
  


 

*Class Snippet*

@DataBoundSetter 
public final void setSetBuildVariables(SetBuildVariables setBuildVariables) 
{
if (setBuildVariables != null) {
this.setBuildVariables = true;
this.preserveVariables = setBuildVariables.preserveVariables;
this.variables = setBuildVariables.variables;
} else {
this.setBuildVariables = false;
this.preserveVariables = false;
this.variables = null;
}
}
 
public static final class SetBuildVariables {
private final boolean preserveVariables;
private final String variables;

@DataBoundConstructor 
public SetBuildVariables(boolean preserveVariables, String variables) {
this.preserveVariables = preserveVariables;
this.variables = variables;
}
}

 

Thanks in advance

  Andrew


On Thursday, January 19, 2017 at 5:13:37 AM UTC+13, Jesse Glick wrote:
>
> On Tue, Jan 17, 2017 at 7:55 PM,   
> wrote: 
> > When updating a plugin to support pipeline script, how do I handle an 
> > optionalBlock section? 
>
> Do not use `f:optionalBlock`. This is a low-level control. Do not 
> refer to `JSONObject` either. All this is old-style deprecated form 
> binding. 
>
> Use a high-level control like `f:optionalProperty` for nullable 
> structs (`ui-samples-plugin` has an example), or simple independent 
> `f:checkbox`es for `boolean` properties (`doCheck*` form validation 
> can reject invalid combinations). 
>
> Also use `@DataBoundSetter` for any property with a plausible default. 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e7fe9147-aeab-4b9e-9e34-1b63b1f87d2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Discontinuing Office Hours

[Oleg Nenashev]

+1

четверг, 16 февраля 2017 г., 1:19:52 UTC+3 пользователь Baptiste Mathus 
написал:
>
> +1
>
> 2017-02-15 20:27 GMT+01:00 Mark Waite 
> :
>
>> +1
>>
>> On Wed, Feb 15, 2017, 11:42 AM Jesse Glick > > wrote:
>>
>>> On Wed, Feb 15, 2017 at 12:21 PM, Daniel Beck >> > wrote:
>>> > I propose we remove office hours from our calendar, update wiki pages 
>>> to state it's discontinued, etc.
>>>
>>> +1
>>>
>>> --
>>> 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 .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k%3D9uGU%3D%2BkXWWWCu6jSQYRrevoLY5_JJwdVxqPDUCSWQ%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 jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEjXovio5dRZLNSW5m1YAOo_ytnA93AQnmh%3DNC%3DvnYimQ%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/06bf09c7-f6b8-4feb-839b-d232807ac0bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.