Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Slide 
They are defined by creating a properties file with the messages. See
https://github.com/jenkinsci/warnings-plugin/blob/c5db29ed729c201e37e553521f4daf099ff36a52/src/main/resources/hudson/plugins/warnings/parser/Messages.properties#L87
for
examples.

On Wed, Jun 7, 2017 at 5:22 PM Simon M  wrote:

> Anyone?
>
> As far as I can see the method
> Messages._Warnings_runbluepearl_ParserName() isn't defined, but looking at
> other extensions, (for example GccParser), this and similar methods don't
> appear to be explicitly defined. So, how to define them implicitly?
>
> Simon
>
>
>
> On Wednesday, June 7, 2017 at 12:03:37 PM UTC-7, Simon M wrote:
>
>> I really appreciate the help you have given me.
>>
>> However, my plugin extension is still not working.
>>
>> I updated my git repository:
>> https://github.com/SimonMatthews-BP/BPWarnings
>>
>> The Jenkins log shows the following error:
>>
>>
>> Jun 07, 2017 6:54:02 PM
>> hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
>> WARNING: Failed to instantiate
>> Key[type=hudson.plugins.bluepearl.RunBluePearlParser,
>> annotation=[none]]; skipping this component
>> com.google.inject.ProvisionException: Unable to provision, see the
>> following errors:
>>
>> 1) Error injecting constructor, java.lang.NoSuchMethodError:
>> hudson.plugins.warnings.parser.Messages._Warnings_runbluepearl_ParserName()Lorg/jvnet/localizer/Localizable;
>>
>>   at
>> hudson.plugins.bluepearl.RunBluePearlParser.(RunBluePearlParser.java:44)
>>
>>
>> 1 error
>> at
>> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
>>
>> at
>> com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)
>> at
>> hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424)
>>
>> at
>> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
>>
>> at
>> com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
>> at
>> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
>>
>> at
>> com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
>> at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386)
>> at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377)
>> at
>> hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:477)
>> at hudson.ExtensionList.load(ExtensionList.java:365)
>> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:303)
>> at hudson.ExtensionList.iterator(ExtensionList.java:157)
>> at
>> hudson.plugins.warnings.parser.ParserRegistry.addParsersWithDeprecatedApi(ParserRegistry.java:69)
>>
>> at
>> hudson.plugins.warnings.parser.ParserRegistry.all(ParserRegistry.java:62)
>> at
>> hudson.plugins.warnings.parser.ParserRegistry.getAllParsers(ParserRegistry.java:209)
>>
>> at
>> hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:169)
>>
>> at
>> hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:139)
>>
>> at
>> hudson.plugins.warnings.parser.ParserRegistry.exists(ParserRegistry.java:186)
>>
>> at
>> hudson.plugins.warnings.WarningsPublisher.replaceConsoleParsersWithChangedName(WarningsPublisher.java:214)
>>
>> at
>> hudson.plugins.warnings.WarningsPublisher.readResolve(WarningsPublisher.java:204)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>> com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66)
>>
>> at
>> hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:271)
>>
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
>>
>> at
>> com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
>>
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
>>
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
>>
>> at
>> com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)
>>
>> at
>> hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197)
>>
>> at
>> hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:273)
>>
>> at
>> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
>>
>> at
>>

Re: Does Jenkis need the workspace in order to compare previous commits for Git repository

2017-06-07 Thread Mark Waite 
On Wed, Jun 7, 2017 at 5:46 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> On Wed 7 Jun 2017 at 22:48, Łukasz Zachulski  wrote:
>
>> I've found Jenkins article Triggering a build using hooks in Bitbucket
>> server
>> 
>> and it states that
>>
>> You need to ensure that your workspace is not deleted after every build.
>>> The Git plugin needs the workspace in order to compare previous commits to
>>> check if there were changes in the repository or not.
>>
>>
>>
As far as I understand it, that statement is incorrect.  The git plugin
does not need the workspace to check if there were changes in the
repository or not.  The plugin remembers the SHA1 associated with a build.
If a SHA1 is detected which has not been previously built, then it is
assumed a new build is needed.

Remote polling (the default) does not require a workspace, unless you're
using certain special cases, like ignoring commits based on the commit
author or commit message.

Mark Waite


> What will happen if the workspace will be deleted or when build will be
>> simply executed on different node? Will Jenkins not be able to correctly
>> depict changes between previous and current builds?
>>
>>
Changes from build to build are calculated using the git repository that
was used for the build.  That repository is assumed to have enough history
in it to compute the differences between the build and its predecessor.

Yes, it is possible to violate that assumption using a shallow clone value
that is less than the number of intervening commits between the build and
its predecessor.

No, I haven't tested the behavior when that assumption is violated.

Mark Waite


> How does this rule apply to *Pipeline*, especially *Multibranch* and 
> *Bitbucket
>> Team* jobs and the fact that mult-ibranch jobs do it own branch
>> indexing?
>>
>
> Multibranch keeps its own track. You can ignore that rule for multibranch
>
>>
>>
>> With Regards,
>> Lukasz.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/2060c2f6-78a9-4421-a15d-aabafb3877d8%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Sent from my phone
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwj%3DwH1-ue599HspTL8vkDzTYCfjJjM%3DBWbZF6CrK0t0A%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtESjZSr4rgh08pE_rgrAvoqjLT4nJCy1L%3DE2dMZquAXVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Simon M 
Anyone? 

As far as I can see the method Messages._Warnings_runbluepearl_ParserName() 
isn't defined, but looking at other extensions, (for example GccParser), 
this and similar methods don't appear to be explicitly defined. So, how to 
define them implicitly? 

Simon


On Wednesday, June 7, 2017 at 12:03:37 PM UTC-7, Simon M wrote:
>
> I really appreciate the help you have given me. 
>
> However, my plugin extension is still not working. 
>
> I updated my git repository: 
> https://github.com/SimonMatthews-BP/BPWarnings 
>
> The Jenkins log shows the following error: 
>
>
> Jun 07, 2017 6:54:02 PM 
> hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error 
> WARNING: Failed to instantiate 
> Key[type=hudson.plugins.bluepearl.RunBluePearlParser, 
> annotation=[none]]; skipping this component 
> com.google.inject.ProvisionException: Unable to provision, see the 
> following errors: 
>
> 1) Error injecting constructor, java.lang.NoSuchMethodError: 
> hudson.plugins.warnings.parser.Messages._Warnings_runbluepearl_ParserName()Lorg/jvnet/localizer/Localizable;
>  
>
>   at 
> hudson.plugins.bluepearl.RunBluePearlParser.(RunBluePearlParser.java:44)
>  
>
>
> 1 error 
> at 
> com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
>  
>
> at 
> com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) 
> at 
> hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424)
>  
>
> at 
> com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
>  
>
> at 
> com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) 
> at 
> com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) 
>
> at 
> com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) 
> at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) 
> at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) 
> at 
> hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:477) 
> at hudson.ExtensionList.load(ExtensionList.java:365) 
> at hudson.ExtensionList.ensureLoaded(ExtensionList.java:303) 
> at hudson.ExtensionList.iterator(ExtensionList.java:157) 
> at 
> hudson.plugins.warnings.parser.ParserRegistry.addParsersWithDeprecatedApi(ParserRegistry.java:69)
>  
>
> at 
> hudson.plugins.warnings.parser.ParserRegistry.all(ParserRegistry.java:62) 
> at 
> hudson.plugins.warnings.parser.ParserRegistry.getAllParsers(ParserRegistry.java:209)
>  
>
> at 
> hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:169)
>  
>
> at 
> hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:139)
>  
>
> at 
> hudson.plugins.warnings.parser.ParserRegistry.exists(ParserRegistry.java:186) 
>
> at 
> hudson.plugins.warnings.WarningsPublisher.replaceConsoleParsersWithChangedName(WarningsPublisher.java:214)
>  
>
> at 
> hudson.plugins.warnings.WarningsPublisher.readResolve(WarningsPublisher.java:204)
>  
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
>
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  
>
> at java.lang.reflect.Method.invoke(Method.java:498) 
> at 
> com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66)
>  
>
> at 
> hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:271)
>  
>
> at 
> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
>  
>
> at 
> com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
>  
>
> at 
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
>  
>
> at 
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
>  
>
> at 
> com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)
>  
>
> at 
> hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197) 
>
> at 
> hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:273) 
>
> at 
> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
>  
>
> at 
> com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
>  
>
> at 
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
>  
>
> at 
> hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:393)
>  
>
> at 
>

Re: Does Jenkis need the workspace in order to compare previous commits for Git repository

2017-06-07 Thread Stephen Connolly 
On Wed 7 Jun 2017 at 22:48, Łukasz Zachulski  wrote:

> I've found Jenkins article Triggering a build using hooks in Bitbucket
> server
> 
> and it states that
>
> You need to ensure that your workspace is not deleted after every build.
>> The Git plugin needs the workspace in order to compare previous commits to
>> check if there were changes in the repository or not.
>
>
> What will happen if the workspace will be deleted or when build will be
> simply executed on different node? Will Jenkins not be able to correctly
> depict changes between previous and current builds?
>
> How does this rule apply to *Pipeline*, especially *Multibranch* and 
> *Bitbucket
> Team* jobs and the fact that mult-ibranch jobs do it own branch indexing?
>

Multibranch keeps its own track. You can ignore that rule for multibranch

>
>
> With Regards,
> Lukasz.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/2060c2f6-78a9-4421-a15d-aabafb3877d8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwj%3DwH1-ue599HspTL8vkDzTYCfjJjM%3DBWbZF6CrK0t0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to reset build number

2017-06-07 Thread Daniel Becroft 
Would the Next Build Number plugin provide any benefit?

https://wiki.jenkins-ci.org/display/JENKINS/Next+Build+Number+Plugin

It looks like it allows you to control the build number, but it might need
two builds to take effect.

On Thu, Jun 8, 2017 at 7:58 AM Derrik Ammons  wrote:

> pchitale, did you get an answer?  I am wondering the same thing.  I need to
> reset the build number back to 1 if the release version has been
> incremented.  I have a multibranch pipeline jenkinsfile that kicks off a
> build upon commits.  When product marketing wants to publish a new release,
> the merged code would have gradle file updated for android, and plist files
> for iOS with a new version.  I read these files after checking out the
> source code to see if the build number needs to be reset back to 1.  I
> can't
> figure out how to actually set the build number back to 1 from the Mac OS X
> agent node building our iOS app.
>
>
>
> --
> View this message in context:
> http://jenkins-ci.361315.n4.nabble.com/how-to-reset-build-number-tp1289785p4898876.html
> Sent from the Jenkins users mailing list archive at Nabble.com.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1496868418893-4898876.post%40n4.nabble.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAJM0iSTeApLLDUW44JtnToFLzXb8E7_xc1Un23WXGPsOt3XxdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Passing extensible choice parameter from Controller to Downstream job (groovy system script) fails

2017-06-07 Thread Victoria Kozel 
Hello,

I've written a System Groovy script that generates a dropdown list based on 
the current user's role. Everything works fine except when I am trying to 
call a downstream job from a Controller job, I get  

ERROR: Build step failed with exception
java.lang.IllegalArgumentException: Illegal choice 'PARAMETER_VALUE' in 
parameter 'PARAMETER_NAME&
at 
jp.ikedam.jenkins.plugins.extensible_choice_parameter.ExtensibleChoiceParameterDefinition.createValueCommon(ExtensibleChoiceParameterDefinition.java:397)


The parameter I am trying to pass as a "current build parameter" from a 
Controller to the downstream job is defined in identical ways in both jobs 
(extensible choice system groovy.) Any clues/ideas are greatly appreciated!


Thank you!!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7125f911-3a95-4dab-a0dc-4168b5898742%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Job Scheduling per 10 secs

2017-06-07 Thread Ramanathan Muthaiah 
Hi ,

Freestyle or pipeline job configuration has few items that should satisfy 
what you're looking for.

1) Build Periodically

2) Do not allow concurrent builds.

Have you looked at them and tried to customize for your wants?

/Ram

On Wednesday, June 7, 2017 at 9:37:35 PM UTC+5:30, Ashish Kaushik wrote:
>
> Hi, 
> I am looking for a solution which allow me schedule a job which can run 
> every 10 secs and also the job should not run if the previous instance has 
> not yet finished. 
>
> I have checked the plugin store but can't find anything that supports this 
> requirements. Any pointers would be greatly appreciated. 
>
> Thanks
>
> --
> * Ashish *Kaushik
>  SourceFuse Technologies
>
> --
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e996d324-e550-416b-8741-f93f13e4aaf0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to reset build number

2017-06-07 Thread Derrik Ammons 
pchitale, did you get an answer?  I am wondering the same thing.  I need to
reset the build number back to 1 if the release version has been
incremented.  I have a multibranch pipeline jenkinsfile that kicks off a
build upon commits.  When product marketing wants to publish a new release,
the merged code would have gradle file updated for android, and plist files
for iOS with a new version.  I read these files after checking out the
source code to see if the build number needs to be reset back to 1.  I can't
figure out how to actually set the build number back to 1 from the Mac OS X
agent node building our iOS app.



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/how-to-reset-build-number-tp1289785p4898876.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1496868418893-4898876.post%40n4.nabble.com.
For more options, visit https://groups.google.com/d/optout.

Does Jenkis need the workspace in order to compare previous commits for Git repository

2017-06-07 Thread Łukasz Zachulski 
I've found Jenkins article Triggering a build using hooks in Bitbucket 
server 

 
and it states that

You need to ensure that your workspace is not deleted after every build. 
> The Git plugin needs the workspace in order to compare previous commits to 
> check if there were changes in the repository or not.


What will happen if the workspace will be deleted or when build will be 
simply executed on different node? Will Jenkins not be able to correctly 
depict changes between previous and current builds?

How does this rule apply to *Pipeline*, especially *Multibranch* and *Bitbucket 
Team* jobs and the fact that mult-ibranch jobs do it own branch indexing? 


With Regards,
Lukasz.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2060c2f6-78a9-4421-a15d-aabafb3877d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Simon Matthews 
I really appreciate the help you have given me.

However, my plugin extension is still not working.

I updated my git repository: https://github.com/SimonMatthews-BP/BPWarnings

The Jenkins log shows the following error:


Jun 07, 2017 6:54:02 PM
hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
WARNING: Failed to instantiate
Key[type=hudson.plugins.bluepearl.RunBluePearlParser,
annotation=[none]]; skipping this component
com.google.inject.ProvisionException: Unable to provision, see the
following errors:

1) Error injecting constructor, java.lang.NoSuchMethodError:
hudson.plugins.warnings.parser.Messages._Warnings_runbluepearl_ParserName()Lorg/jvnet/localizer/Localizable;
  at 
hudson.plugins.bluepearl.RunBluePearlParser.(RunBluePearlParser.java:44)

1 error
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)
at 
hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016)
at 
com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092)
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386)
at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377)
at 
hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:477)
at hudson.ExtensionList.load(ExtensionList.java:365)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:303)
at hudson.ExtensionList.iterator(ExtensionList.java:157)
at 
hudson.plugins.warnings.parser.ParserRegistry.addParsersWithDeprecatedApi(ParserRegistry.java:69)
at hudson.plugins.warnings.parser.ParserRegistry.all(ParserRegistry.java:62)
at 
hudson.plugins.warnings.parser.ParserRegistry.getAllParsers(ParserRegistry.java:209)
at 
hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:169)
at 
hudson.plugins.warnings.parser.ParserRegistry.getParsers(ParserRegistry.java:139)
at 
hudson.plugins.warnings.parser.ParserRegistry.exists(ParserRegistry.java:186)
at 
hudson.plugins.warnings.WarningsPublisher.replaceConsoleParsersWithChangedName(WarningsPublisher.java:214)
at 
hudson.plugins.warnings.WarningsPublisher.readResolve(WarningsPublisher.java:204)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66)
at 
hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:271)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at 
com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71)
at 
hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:197)
at 
hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:273)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:393)
at 
hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:331)
at 
hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:270)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)
at 
com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50)
at 
com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134)
at

Re: [Jenkins-infra] Confluence maintenance window tomorrow (2017-06-07) from 15:30 - 17:30 UTC

2017-06-07 Thread R. Tyler Croy 

The wiki is back online, but some users may have difficulty logging in with
fresh sessions. Confluence is still syncing user data from LDAP and is likely
going to be doing so for the next couple hours.



- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20170607183211.6ijht2y3kfij5hnz%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: Confluence maintenance window tomorrow (2017-06-07) from 15:30 - 17:30 UTC

2017-06-07 Thread R. Tyler Croy 
(replies inline)

On Tue, 06 Jun 2017, R. Tyler Croy wrote:

> 
> We're planning to perform a Confluence upgrade tomorrow in a maintenance 
> window
> between 15:30 and 17:30 UTC (8:30 - 10:30 PDT).
> 
> The ticket tracking this work is:
> https://issues.jenkins-ci.org/browse/INFRA-1201


Just a heads up, this window is taking longer than we had hoped as some
migrations timed out when running.


I'm optimistic that we'll be wrapping this up in the next 30-45 minutes


- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20170607173253.dn4kjfukaeelbpqs%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: sh returnStdout:true leaking deleted file handles

2017-06-07 Thread 'Kieran Shaw' via Jenkins Users 
Hi Michael,

Thanks for your reply. I can reliably run that simple little pipeline that 
uses returnStdout and get a leak. I'm using the latest versions of 
everything. I find it hard to believe it is a bug in the 'sh' command as it 
is going to be so widely used, it can't just have been me that comes across 
it. So I wonder if it is a combination of plugins I've got going on. 

It would be good to hear from more people if they have had any similar 
problems.

On Wednesday, 7 June 2017 14:18:59 UTC+1, Michael Kobit wrote:
>
> We see massive file handle leaks on a different Jenkins we have that does 
> not use Pipeline. The leaks were on the build logs. We haven't figured out 
> if it is a plugin or something in Jenkins core and we just dealt with it by 
> restarting Jenkins nighty.
>
> On another instance we use pipelines extensively (and the returnStdout) 
> but haven't ran into file handle leaks hitting the limit. I'll have to 
> check today to see if we are just getting lucky.
>
> On Wed, Jun 7, 2017, 04:39 'Kieran Shaw' via Jenkins Users <
> jenkins...@googlegroups.com > wrote:
>
>> Anyone got any thoughts or experience with this: 
>> https://issues.jenkins-ci.org/browse/JENKINS-43639?focusedCommentId=302114=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302114
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/2fd3edc0-79d3-4e4c-9f79-611a929b25ba%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/256719dc-2d1d-4a55-ac28-d20b6ab88228%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Job Scheduling per 10 secs

2017-06-07 Thread Ashish Kaushik 
Hi,
I am looking for a solution which allow me schedule a job which can run
every 10 secs and also the job should not run if the previous instance has
not yet finished.

I have checked the plugin store but can't find anything that supports this
requirements. Any pointers would be greatly appreciated.

Thanks
--
* Ashish *Kaushik
 SourceFuse Technologies
--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAG4zR1HU72CaFdiZWB8%2Bo-dBeEgxrZUZbrhfwA2%2B-RkifhLk4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Same git repo with multiple jenkins job creating build problems

2017-06-07 Thread Gopi Polisetti 
Hi,

Am using Git repository,  Git Repository A it has multiple solutions b, c , 
d , e ... , 
Each solution has one jenkins job,
Jenkin Job B 
Jenkin Job C
Jenkin Job D
--

If I change any code (B,C,D) under Repository A -  All jenkin - B,C,D job 
triggers build.

If I change any code related to B then Jenkins B only has to trigger 
If I Change any code related to C then Jenkins C only has to trigger not 
all jobs

Any solution for this

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ed78c51d-3d83-4822-974d-37358ee59deb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multibranch pipeline job doesn't fully support Subversion?

2017-06-07 Thread David Aldrich 
Hi

There is a known issue with the Subversion plugin that 'Additional Credentials' 
must be specified if Externals are used.

Most job types allow the user to specify the 'Additional Credentials' in the 
GUI, but the Multibranch pipeline job does not.  To me, this is a show-stopper 
for using that job type - my job is regularly failing because of svn error: 
'E200015: ISVNAuthentication provider did not provide credentials'.

This issue is raised as JENKINS-35227 but that was created in May 2016 and is 
unassigned.

Seems a shame that the Multibranch pipeline job doesn't fully support 
Subversion.  Can we raise the profile of this problem?

Best regards

David


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ee8de0c7f8e34484af029a790e52b374%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

Checkout from multiple SCMs/repos in declarative pipeline?

2017-06-07 Thread Kirill Peskov 
Hi All,

Due to some project restrictions I have to combine sources from 3
repositories (1 Subversion and 2 Git repos), is there an easy way to
achieve that in a declarative pipeline? Neither project subdirs nor
files in the root of each repo are not overlapping with each other, so
merging them in one workspace is actually safe.

Something like that:

pipeline {
agent {
dockerfile { dir 'ubuntu-xenial-mysql' }
   
}
stages {
stage('Sources & Additional Tools Checkout'){
steps {
svn url:'url-to-installer-sources'
git url:'url-to-test-tools'
git url:'url-to-packager-sources'
}
}
stage('Test suite') {
steps {
// Do some tests ...
}
stage('Build the package') {
steps {
// Invoke deb-package builder ...
}
   
}

I've tested the simplified version of it trying to combine 2 GIT repos,
it didn't work, second 'git' step wipes everything out of workspace...


Cheers,

Kirill

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/9e0bab78-e1eb-7f46-ed5d-2d212aeb59ad%40paranoid.email.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Simon M 


On Wednesday, June 7, 2017 at 6:13:15 AM UTC-7, slide wrote:
>
> It should show up after installing your plugin and restarting Jenkins. I 
> checked the source and it looked like you added the @Extension to your 
> parser, so it should get pulled in once the plugin is installed. What do 
> you mean by #2? Are you asking how to use the warnings plugin in general?
>
>
I realized my misunderstanding which resulted in question #2. 

Simon 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cea40891-f930-4a71-bbf4-da72d852e638%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Slide 
By the way, you shouldn't need this at all

https://github.com/SimonMatthews-BP/BPWarnings/blob/master/src/main/java/hudson/plugins/bluepearl/RunBluePearlParser.java#L41

The ID is one of the parameters you are passing to super in your
constructor.

On Wed, Jun 7, 2017 at 6:12 AM Slide  wrote:

> It should show up after installing your plugin and restarting Jenkins. I
> checked the source and it looked like you added the @Extension to your
> parser, so it should get pulled in once the plugin is installed. What do
> you mean by #2? Are you asking how to use the warnings plugin in general?
>
> On Tue, Jun 6, 2017 at 5:16 PM Simon M  wrote:
>
>> So, after getting my own log parser written and built, my next questions
>> are:
>>
>> 1. How to get it to show up when adding a new parser? What needs to be
>> defined for this?
>> 2. How the input file to the parser is defined.
>>
>> I would very much appreciate any advice on these topics. My present
>> current version (which doesn't show up in the list of Parsers is in:
>> https://github.com/SimonMatthews-BP/BPWarnings.git
>>
>> Simon
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/28f0e216-7dca-472f-af11-9766bd1a653e%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVdbtzNwVVVmCwac6GjZThrx4bXupEduwsfEboRZR23_qw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: sh returnStdout:true leaking deleted file handles

2017-06-07 Thread Michael Kobit 
We see massive file handle leaks on a different Jenkins we have that does
not use Pipeline. The leaks were on the build logs. We haven't figured out
if it is a plugin or something in Jenkins core and we just dealt with it by
restarting Jenkins nighty.

On another instance we use pipelines extensively (and the returnStdout) but
haven't ran into file handle leaks hitting the limit. I'll have to check
today to see if we are just getting lucky.

On Wed, Jun 7, 2017, 04:39 'Kieran Shaw' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Anyone got any thoughts or experience with this:
> https://issues.jenkins-ci.org/browse/JENKINS-43639?focusedCommentId=302114=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302114
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/2fd3edc0-79d3-4e4c-9f79-611a929b25ba%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CALELY9HqdwF9AxJWBUFqbAt41JWGXXC-3h84v8BmRGfDwDcYrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings plugin extension: how to make it show up and to define input log file

2017-06-07 Thread Slide 
It should show up after installing your plugin and restarting Jenkins. I
checked the source and it looked like you added the @Extension to your
parser, so it should get pulled in once the plugin is installed. What do
you mean by #2? Are you asking how to use the warnings plugin in general?

On Tue, Jun 6, 2017 at 5:16 PM Simon M  wrote:

> So, after getting my own log parser written and built, my next questions
> are:
>
> 1. How to get it to show up when adding a new parser? What needs to be
> defined for this?
> 2. How the input file to the parser is defined.
>
> I would very much appreciate any advice on these topics. My present
> current version (which doesn't show up in the list of Parsers is in:
> https://github.com/SimonMatthews-BP/BPWarnings.git
>
> Simon
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/28f0e216-7dca-472f-af11-9766bd1a653e%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeiwMRs1Kp6qnLkx%3D-R6y9CXx4ytq0Z1%2BJVkLQfAXutzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Blu Ocean Pipeline PNG

2017-06-07 Thread Joaquin Henriquez 
Hi

Is there a possibility go the the visual pipeline png somehow? I want to send 
it via email or via #slack when finished
[cid:image001.jpg@01D2DF98.10673CF0]

https://i.stack.imgur.com/pZ4r4.png

BR

Jo

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/bf193cb403044e84ab784ddd54c7d1da%40BSKEXCH2013HYPV.mwrinfosecurity.com.
For more options, visit https://groups.google.com/d/optout.

[pipeline] approve input statement from another job with pipeline code

2017-06-07 Thread Bill Dennis 
(re-posting with corrections)

Has anyone managed to write pipeline code (or even their own plugin) to 
approve an input using pipeline code from another job (shared library 
NonCPS method or whatever)?

I have this scenario -

JobA

input id: 'JOBA_CALLBACK', message: 'Waiting for JobB', parameters: [string(
defaultValue: '', description: 'ID of the callback', name: 'CALLBACK_ID')]


JobB

I want to write this with this hypothetical pipeline DSL which doesn't 
exist:

approveInput jobName:'JobA', buildNumber: 1234, , inputId: 'JOBA_CALLBACK', 
parameters: [CALLBACK_ID: '5678']

Job B in my scenario is actually called by an external system and can route 
to a couple of other jobs based on job parameters (so I cannot simply put 
Job B code into A).

CloudBees support recommended that I use a REST call-back onto Jenkins to 
do this (REST call onto Jenkins from JobB), 

I do have this and it works, the code looks like this using the HTTP 
Request plugin:

def REQUEST_URL = 
"${env.JENKINS_URL}/job/JobA/1234/wfapi/inputSubmit?inputId=JOBA_CALLBACK".
toString()


def formJsonParamUrlEncoded = java.net.URLEncoder.encode(
"{\"parameter\":[{\"name\":\"CALLBACK_ID\",\"value\":5678]}").toString()


request = httpRequest authentication: 'LOCAL_JENKINS',
 consoleLogResponseBody: true,
 customHeaders: [[name: 'content-type', value: 
'application/x-www-form-urlencoded']],
 httpMode: 'POST',
 requestBody: "json=${formJsonParamUrlEncoded}",
 url: REQUEST_URL,
 validResponseCodes: '200'


echo "Request returned: ${request.toString()}"

However this does introduce some failures into our system when our IT folks 
have outages that affect our authentication and such like (the REST call to 
Jenkins has authentication).

I would like to remove this possibility of failure hence looking at code to 
do it.

I feel that there ought to be a way to call Jenkins internals to do this, 
but probably it would be best to write a plugin that implements the 
hypothetical DSL I have.

If I did write a plugin, would others find this useful?

--Bill

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1a2f3183-1243-4f71-aeec-a499c6e5bf77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[pipeline] approve input from another job using pipeline code

2017-06-07 Thread Bill Dennis 
Has anyone managed to write pipeline code (or even their own plugin) to 
approve an input using pipeline code from another job (shared library 
NonCPS method or whatever)?

I have this scenario -

*JobA*

input id: 'JOBA_CALLBACK', message: 'Waiting for JobB', parameters: [string(
defaultValue: '', description: 'ID of the callback', name: 'CALLBACK_ID')]

*JobB*

I want to write this with this hypothetical pipeline DSL which doesn't 
exist:

approveInput jobName:'JobA', buildNumber: 1234, , inputId: 'JOBA_CALLBACK', 
parameters: [CALLBACK_ID: '5678']

Job B in my scenario is actually called by an external system and can route 
to a couple of other jobs based on job parameters (so I cannot simply put 
Job B code into A).

CloudBees support recommended that I use a REST call-back onto Jenkins to 
do this (REST call onto Jenkins from JobB), 

I do have this and it works, the code looks like this using the HTTP 
Request plugin:

def REQUEST_URL = 
"${env.JENKINS_URL}/job/JobA/1234/wfapi/inputSubmit?inputId=V6_CALLBACK".
toString()

def formJsonParamUrlEncoded = java.net.URLEncoder.encode(
"{\"parameter\":[{\"name\":\"CALLBACK_ID\",\"value\":5678]}").toString()

request = httpRequest authentication: 'LOCAL_JENKINS',
 consoleLogResponseBody: true,
 customHeaders: [[name: 'content-type', value: 
'application/x-www-form-urlencoded']],
 httpMode: 'POST',
 requestBody: "json=${formJsonParamUrlEncoded}",
 url: REQUEST_URL,
 validResponseCodes: '200'

echo "Request returned: ${request.toString()}"


However this does introduce some failures into our system when our IT folks 
have outages that affect our authentication and such like (the REST call to 
Jenkins has authentication).

I would like to remove this possibility of failure hence looking at code to 
do it.

I feel that there ought to be a way to call Jenkins internals to do this, 
but probably it would be best to write a plugin that implements the 
hypothetical DSL I have.

If I did write a plugin, would others find this useful?

--Bill

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/63a511e7-c6f7-408e-a05d-699c4b6d850b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

sh returnStdout:true leaking deleted file handles

2017-06-07 Thread 'Kieran Shaw' via Jenkins Users 
Anyone got any thoughts or experience with 
this: 
https://issues.jenkins-ci.org/browse/JENKINS-43639?focusedCommentId=302114=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-302114

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/2fd3edc0-79d3-4e4c-9f79-611a929b25ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugins metadata failing signature check?

2017-06-07 Thread David Aldrich 
After checking for updated plugins this morning I see:

"None of the tool installer metadata passed the signature check"

Best regards

David

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a44c1703fd854ab886c6cfd93073cab1%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

Re:

2017-06-07 Thread James Nord 
So I guess you have been using https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Remote+Trigger+Plugin, other than that I do not know of an oss pluggin. There is a proprietary comercial feature that does sound Ds like it does exactly what you want in CloudBees Jenkins Enterprise (https://support.cloudbees.com/hc/en-us/articles/226408088-Trigger-jobs-across-masters)  On 5 Jun 2017 22:01, John Mellor  wrote:

I’m about ready to throw in the towel regarding remote job triggers.  It is definitely a *LOT* too hard.
 
I’m trying to start an Ansible construction job on a Jenkins-2 cluster from a Jenkins-1 cluster, as a workaround for a massive number of items not working in
 Jenkins-1.
 
My prototyping appears to show that
1.  
I need to know the login credentials and Jenkins user key for the person who pushed the button.  These do not appear to be exposed as variables to the
 job on Jenkins-1.  For my prototyping, I’m just hardcoding my own credentials, but moving forward I will need some way of obtaining these in a shell script for production use.
2.  
The obvious API way of doing this job start refuses to work, I believe ever since the XSRF additions were added.
3.  
You need an XSRF cookie to do this remote job start, for unclear reasons.  Both of my Jenkins sites are exposed through an nginx redirect from port
 80, which may have something to do with this.  Is this an unresolved bug?
4.  
The XSRF cookie is not accepted, for unclear reasons.  The log is totally useless to figure out why.
 
There must be an undocumented trick, so what is it?  Has anyone got remote job initiation actually working?
 
 
CRUMB=$(curl -s http://$OWNER:$OWNERKEY@$JENKINS2/crumbIssuer/api/xml?$JENKINS2/crumbRequestField,":",//crumb)
 
curl -o $RUNLOG \
  -X POST \
  -H "Jenkins-Crumb: $CRUMB" \
  $JENKINS2/job/$FOLDER/$JOB/buildWithParameters?token=$JOBTOKEN \
  --user $OWNER:$OWNERKEY \
  --data-urlencode json='{"parameter": [{"name":"OS_TEMPLATE", "value":"{OS_TEMPLATE}"},
    {"name":"VM_HOST", "value":"{VM_HOST}"    },
    {"name":"VM_MEMORY",   "value":"{VM_MEMORY}"  },
    {"name":"VM_CPU",  "value":"{VM_CPU}" },
    {"name":"VM_DISK", "value":"{VM_DISK}"    },
    {"name":"STATIC_IP",   "value":"{STATIC_IP}"  }]}'
cat $RUNLOG    # (obfuscation added as xxx):
 
 
  % Total    % Received % Xferd  Average Speed   Time    Time Time  Current
     Dload  Upload   Total   Spent    Left  Speed
 
  0 0    0 0    0 0  0  0 --:--:-- --:--:-- --:--:-- 0
100  1564  100   354  100  1210  50348   168k --:--:-- --:--:-- --:--:--  196k
+ cat /tmp/run.log



Error 404 Not Found

HTTP ERROR 404
Problem accessing /job/xxx/xxx/buildWithParameters. Reason:
    Not Foundhttp://eclipse.org/jetty">Powered by Jetty:// 9.4.z-SNAPSHOT
 


+ grep -q 'HTTP ERROR 403' /tmp/run.log
Build step 'Execute shell' marked build as failure
Finished: FAILURE
 





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b57477b973114bb7947a873cafa910ec%40mbx02cmb01p.esentire.local.
For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c025c0ae-3cb6-4ced-b12c-feeead17e7b6%40email.android.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remove / disable the Replay capability for Jenkins Pipeline consumers

2017-06-07 Thread Jim Coll 
Worked it out - the Run/Reply permission was getting greyed out when the 
Job/Configure permission is selected which implies that it's automatically 
granted with the latter permission.

On Tuesday, June 6, 2017 at 6:45:54 PM UTC+1, Jim Coll wrote:
>
> I want to remove the ability for users of Jenkins Pipeline to be able to 
> modify the Jenkinsfile or other loaded pipeline scripts using the Replay 
> option. 
> I have tried removing the permission from the roles that I've assigned to 
> a user group but for some reason they still have the access to the Replay 
> option on the Console Output screen. I have also created a new role without 
> the permission but the option still shows up for the user.
>
> I also noticed that the Run/Replay permissions in the Manage Roles Matrix 
> is greyed out for some of the older Jenkins roles. 
>
> Has anyone else experienced this or similar issues? Any assistance would 
> be greatly appreciated!
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5e188814-2932-4663-9ebc-26804fc688a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AWS Simple AD Issue

2017-06-07 Thread Brian Mills 
I've been using Active Directory plugin for years in an AWS environment, 
using AWS Simple AD as a back end. 

Today for no apparent reason the AD auth plugin stopped being able to 
communicate to Simple AD. Some updates were done yesterday to Jenkins 
plugins, but I don't believe AD was one of them, I also have tried rolling 
back the plugin to 2 previous versions with no success in resolving the 
issue. 

I haven't found any similar issues in the jenkins-ci.org tracker, one 
report https://issues.jenkins-ci.org/browse/JENKINS-43967 suggests 
inconsistent behaviour, in my case it doesn't work at all. 

It fails every time with a java exception Any Domain Controller is 
reachable java.net.SocketException: Socket closed at

I haven't really managed to work out a way to debug it other than the fact 
I have have other applications that are communicating with Simple AD fine 
(you can log out of those applications, and back in again with no problem). 

Any help would be appreciated. 

Cheers,
Brian


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1c6e423d-ddcb-40c8-a227-cdfadce97144%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.