Sorry, my fault. I should have read the stack trace more carefully.

Can you please set

sourceEncoding: 'YOUR-SOURCE-FILES-ENCODING‘

as well? The error is thrown during the fingerprinting. Here a different 
encoding is used.

Which encoding is used for your source code?

I created an issue:
https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=421&view=planning&selectedIssue=JENKINS-54398
 
<https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=421&view=planning&selectedIssue=JENKINS-54398>
The plugin should rather report a helpful text...

> Am 01.11.2018 um 12:22 schrieb dean warren <[email protected]>:
> 
> Ok so changed the scanForIssues line using the encoding as suggested. Even 
> when using the latest checkstyle (8.14) I get the same error
> e.g.
> java.nio.charset.MalformedInputException: Input length = 1
> 
> Below is my current script (note we are using java 1.7 on the target, so have 
> to explicity utilise 1.8 for latest checkstyle).
> 
> sh '/home/user/jdk1.8.0_144/bin/java -jar 
> /home/user/checkstyle/checkstyle-8.14-all.jar -c 
> /home/user/Metrics_Checkstyle.xml -f xml -o target/checkstyle-results.xml 
> mof-api/src'
> 
> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
> '**/target/checkstyle-results.xml', reportEncoding: 'UTF-8'
> publishIssues issues:[checkstyle]
> 
> What next?
> 
> On Thu, Nov 1, 2018 at 11:02 AM Ullrich Hafner <[email protected] 
> <mailto:[email protected]>> wrote:
> Colon not Equals:
> 
> reportEncoding: 'UTF-8'
> 
> You are using an ancient checkstyle version, maybe this is the problem? 
> Current version is 8.12.
> 
>> Am 01.11.2018 um 10:55 schrieb dean warren <[email protected] 
>> <mailto:[email protected]>>:
>> 
>> What is the format for the scanForIssues line including the 'reportEncoding'.
>> I've done this e.g.
>> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], 
>> reportEncoding='UTF-8', pattern: '**/mof-api/target/checkstyle-results.xml'
>> but it throws an error e.g.
>> java.lang.IllegalArgumentException: Expected named arguments but got 
>> [{tool={$class=CheckStyle}, 
>> pattern=**/mof-api/target/checkstyle-results.xml}, null]
>> 
>> And as requested the check-style file is generated from this command e.g.
>> sh 'java -jar /home/user/checkstyle/checkstyle-6.5-all.jar -c 
>> /home/user/Metrics_Checkstyle.xml -f xml -o target/checkstyle-results.xml 
>> src'
>> 
>> On Tue, Oct 30, 2018 at 2:32 PM Ullrich Hafner <[email protected] 
>> <mailto:[email protected]>> wrote:
>> and one additional question: how is the checkstyle file created?
>> 
>>> Am 30.10.2018 um 15:30 schrieb Ullrich Hafner <[email protected] 
>>> <mailto:[email protected]>>:
>>> 
>>> Can you add the encoding property:
>>> 
>>> checkstyle = scanForIssues reportEncoding='YOUR-ENCODING‘, ...
>>> 
>>> and replace YOUR-ENCODING with the encoding that is defined in the xml line 
>>> of your checkstyle results.xml file?
>>> 
>>> If this does not work, please create an issue in our issue tracker and 
>>> attach the XML file. (Or if it is confidential you may also send it via 
>>> email).
>>> 
>>> 
>>>> Am 30.10.2018 um 13:47 schrieb deanwarrenuk <[email protected] 
>>>> <mailto:[email protected]>>:
>>>> 
>>>> Have reduced the check-style from 200+ issues to just two. Works fine now.
>>>> 
>>>> So something incompatible with checkstyle-resutls.xml generated and the 
>>>> scanForIssues.
>>>> @Ullrich, can I send you the checkstyle-resutls.xml to debug (email? would 
>>>> prefer not to post file directly here)?
>>>> 
>>>> Or perhpas advise on how I can progress?
>>>> 
>>>> 
>>>> On Tuesday, 30 October 2018 12:16:41 UTC, deanwarrenuk wrote:
>>>> Looks like this is def an issue with the line
>>>> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
>>>> '**/mof-api/target/checkstyle-results.xml'
>>>> 
>>>> As removed all steps except that above and issue still occurs.
>>>> 
>>>> 
>>>> Do you have a known working checkstyle-results.xml file, just in case 
>>>> somethink funny with mine?
>>>> 
>>>> 
>>>> On Tuesday, 30 October 2018 11:46:24 UTC, deanwarrenuk wrote:
>>>> StackTrace:
>>>> 
>>>> java.nio.charset.MalformedInputException: Input length = 1
>>>>    at java.nio.charset.CoderResult.throwException(CoderResult.java:281)
>>>>    at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:339)
>>>>    at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
>>>>    at java.io.InputStreamReader.read(InputStreamReader.java:184)
>>>>    at java.io.BufferedReader.fill(BufferedReader.java:161)
>>>>    at java.io.BufferedReader.readLine(BufferedReader.java:324)
>>>>    at java.io.BufferedReader.readLine(BufferedReader.java:389)
>>>>    at java.io.BufferedReader$1.hasNext(BufferedReader.java:571)
>>>> Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to moftpa
>>>>            at 
>>>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
>>>>            at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
>>>>            at hudson.remoting.Channel.call(Channel.java:908)
>>>>            at hudson.FilePath.act(FilePath.java:986)
>>>>            at hudson.FilePath.act(FilePath.java:975)
>>>>            at 
>>>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.postProcess(IssuesScanner.java:148)
>>>>            at 
>>>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scanInWorkspace(IssuesScanner.java:92)
>>>>            at 
>>>> io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:71)
>>>>            at 
>>>> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:173)
>>>>            at 
>>>> io.jenkins.plugins.analysis.core.steps.ScanForIssuesStep$Execution.run(ScanForIssuesStep.java:138)
>>>>            at 
>>>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
>>>>            at hudson.security.ACL.impersonate(ACL.java:260)
>>>>            at 
>>>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
>>>>            at 
>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>>>>            at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>>            at 
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>>            at 
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>>            at java.lang.Thread.run(Thread.java:745)
>>>> Caused: java.io.UncheckedIOException
>>>>    at java.io.BufferedReader$1.hasNext(BufferedReader.java:574)
>>>>    at 
>>>> java.util.Spliterators$IteratorSpliterator.tryAdvance(Spliterators.java:1811)
>>>>    at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
>>>>    at 
>>>> edu.hm.hafner.analysis.FullTextFingerprint.extractContext(FullTextFingerprint.java:111)
>>>>    at 
>>>> edu.hm.hafner.analysis.FullTextFingerprint.createFingerprint(FullTextFingerprint.java:84)
>>>>    at 
>>>> edu.hm.hafner.analysis.FullTextFingerprint.compute(FullTextFingerprint.java:73)
>>>>    at 
>>>> edu.hm.hafner.analysis.FingerprintGenerator.run(FingerprintGenerator.java:35)
>>>>    at 
>>>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.createFingerprints(IssuesScanner.java:237)
>>>>    at 
>>>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:195)
>>>>    at 
>>>> io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor.invoke(IssuesScanner.java:170)
>>>>    at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2760)
>>>>    at hudson.remoting.UserRequest.perform(UserRequest.java:207)
>>>>    at hudson.remoting.UserRequest.perform(UserRequest.java:53)
>>>>    at hudson.remoting.Request$2.run(Request.java:358)
>>>>    at 
>>>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>>>>    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>>    at 
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>>>    at 
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>>>    at java.lang.Thread.run(Thread.java:748)
>>>> Finished: FAILURE
>>>> 
>>>> 
>>>> On Tue, Oct 30, 2018 at 11:41 AM Ullrich Hafner <[email protected] 
>>>> <mailto:[email protected]>> wrote:
>>>> This looks like an exception from one of the steps. Is there a stacktrace? 
>>>> If there is no result visible then this is due to an exception.
>>>> 
>>>>> Am 30.10.2018 um 12:16 schrieb dean warren <[email protected] 
>>>>> <mailto:[email protected]>>:
>>>>> 
>>>>> And also noted this for the same some, following emailing results
>>>>> 
>>>>> 10:58:11 Sending e-mails to: ....
>>>>> [Pipeline] }
>>>>> [Pipeline] // node
>>>>> [Pipeline] }
>>>>> [Pipeline] // timestamps
>>>>> [Pipeline] End of Pipeline
>>>>> java.nio.charset.MalformedInputException: Input length = 1
>>>>> 
>>>>> 
>>>>> On Tue, Oct 30, 2018 at 11:15 AM dean warren <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> 
>>>>> Ahh... I am clearly a doofus 's' !
>>>>> Sorry, you know what its like, doing one thing with left hand, something 
>>>>> else with other... and miss things.
>>>>> 
>>>>> So now I see the following
>>>>> 10:58:10 [CheckStyle] Searching for all files in 
>>>>> '/home/user/workspace/TG.integrate_jenkins_ci-TKKXRODLMWWUDKMVKENHFQYQ7E2ZP5QAC72HYNHV6PXXEX75DW2Q'
>>>>>  that match the pattern '**/target/checkstyle-results.xml'
>>>>> 10:58:10 [CheckStyle] -> found 1 file
>>>>> 10:58:10 [CheckStyle] Successfully parsed file 
>>>>> /home/user/workspace/TG.integrate_jenkins_ci-TKKXRODLMWWUDKMVKENHFQYQ7E2ZP5QAC72HYNHV6PXXEX75DW2Q/target/checkstyle-results.xml
>>>>> 10:58:10 [CheckStyle] -> found 2983 issues (skipped 0 duplicates)
>>>>> 
>>>>> However the build now fails,I assume because of all of the checkstyle 
>>>>> issues (all 2983 of them!) - this is fine.
>>>>> 
>>>>> But the checkstyle icon has dissapeared for this build.
>>>>> e.g. a good build, but not finding the checkstyle file, so no build 
>>>>> failure and the checkstyle icons appear but with no warnings/errors.
>>>>> <image.png>
>>>>> But on the failed build the icons have dissappeared.
>>>>> <image.png>
>>>>> How do I view the checkstyle warnings/errors in Jenksin?
>>>>> 
>>>>> On Tue, Oct 30, 2018 at 10:57 AM Ullrich Hafner <[email protected] 
>>>>> <mailto:[email protected]>> wrote:
>>>>> You should see an info message in the snippet generator. The default (if 
>>>>> left empty) is '**/checkstyle-result.xml‘. Or you can view the JavaDoc 
>>>>> documentation (or documentation in 
>>>>> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md
>>>>>  
>>>>> <https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md>).
>>>>> 
>>>>> Is your file called checkstyle-result.xml or checkstyle-result*s*.xml?
>>>>> 
>>>>>> Am 30.10.2018 um 11:48 schrieb dean warren <[email protected] 
>>>>>> <mailto:[email protected]>>:
>>>>>> 
>>>>>> Awesome, that works! Thanks guys.
>>>>>> 
>>>>>> One last question... :) Where can I find info for the 'pattern' part of 
>>>>>> the line
>>>>>> e.g.
>>>>>> def checkstyle = scanForIssues tool: [$class: 'CheckStyle'], pattern: 
>>>>>> '**/target/checkstyle-result.xml' 
>>>>>> <https://wiki.jenkins.io/display/JENKINS/checkstyle-result.xml'>
>>>>>> 
>>>>>> As my resutls are created in the dersired place (I can see them), but 
>>>>>> scanForIssues isn't finding the checkstyle-results.xml (I think)
>>>>>> i.e.
>>>>>> [CheckStyle] [ERROR] No files found for pattern 
>>>>>> '**/target/checkstyle-result.xml'. Configuration error?
>>>>>> 
>>>>>> 
>>>>>> On Tue, Oct 30, 2018 at 9:48 AM deanwarrenuk <[email protected] 
>>>>>> <mailto:[email protected]>> wrote:
>>>>>> Ok found it here
>>>>>> https://updates.jenkins.io/experimental/latest/ 
>>>>>> <https://updates.jenkins.io/experimental/latest/>
>>>>>> 
>>>>>> On Monday, 29 October 2018 16:28:31 UTC, Ullrich Hafner wrote:
>>>>>> You need to point your update center to the experimental update center 
>>>>>> url, see 
>>>>>> https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
>>>>>>  
>>>>>> <https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/>
>>>>>> 
>>>>>> Von meinem iPad gesendet
>>>>>> 
>>>>>> Am 29.10.2018 um 15:43 schrieb dean warren <[email protected] <>>:
>>>>>> 
>>>>>>> Thanks @sagar for your reply.
>>>>>>> 
>>>>>>> But the link https://updates.jenkins.io/download/plugins/warnings/ 
>>>>>>> <https://updates.jenkins.io/download/plugins/warnings/> does not 
>>>>>>> contain version 5.0. Perhaps because this is a beta?
>>>>>>> 
>>>>>>> So do I have to build / repackage it, of is there another link that 
>>>>>>> will give me the .hpi file?
>>>>>>> 
>>>>>>> On Mon, Oct 29, 2018 at 2:22 PM sagar utekar <[email protected] <>> 
>>>>>>> wrote:
>>>>>>> from here you can download hpi file for warnings plugin
>>>>>>> https://updates.jenkins.io/download/plugins/warnings/ 
>>>>>>> <https://updates.jenkins.io/download/plugins/warnings/>
>>>>>>> 
>>>>>>> and add it using upload section of manage plugin -> advanced section
>>>>>>> 
>>>>>>> On Mon, Oct 29, 2018 at 7:39 PM def <[email protected] <>> wrote:
>>>>>>> OK, from here:
>>>>>>> https://github.com/jenkinsci/warnings-plugin/tree/5.0 
>>>>>>> <https://github.com/jenkinsci/warnings-plugin/tree/5.0>
>>>>>>> 
>>>>>>> But Jnekins requires a .hpi file.
>>>>>>> Do I have to build this, or package it somehow?
>>>>>>> 
>>>>>>> On Monday, 29 October 2018 14:02:45 UTC, def wrote:
>>>>>>> Thanks @ulli for your reply.
>>>>>>> 
>>>>>>> 'Did you install the 5.0 beta version of the plugin? This step is not 
>>>>>>> available in the 4.x version.'
>>>>>>> Ahh... :) No. Where do I get that from and how to install in Jenkins?
>>>>>>> 
>>>>>>> On Sat, Oct 27, 2018 at 6:07 PM Ulli Hafner <[email protected] <>> 
>>>>>>> wrote:
>>>>>>> 
>>>>>>> 
>>>>>>> Von meinem iPad gesendet
>>>>>>> 
>>>>>>> Am 26.10.2018 um 09:50 schrieb dean warren <[email protected] <>>:
>>>>>>> 
>>>>>>>> I am trying to get the Warnings plugin collecting CheckStyle results 
>>>>>>>> within a pipeline.
>>>>>>>> I believe I am using all the latest versions of pipeline related 
>>>>>>>> modules, and the warnings modules.
>>>>>>>> 
>>>>>>>> A simplified version of my Jenkinsfile is something like:
>>>>>>>> 
>>>>>>>> timestamps {
>>>>>>>>     node ('name') {
>>>>>>>>             try
>>>>>>>>             {
>>>>>>>>                 stage ('Checkout') {
>>>>>>>>                     checkout scm
>>>>>>>>                 }
>>>>>>>>                 stage ('Build & Test') {
>>>>>>>>                     sh 'bash -x test.sh'
>>>>>>>>                 }
>>>>>>>>                 stage ('CheckStyle') {
>>>>>>>>                     sh 'java -jar 
>>>>>>>> /home/user/checkstyle/checkstyle-6.5-all.jar -c 
>>>>>>>> /home/user/checkstyle.xml -f xml -c target/checkstyle-results.xml src'
>>>>>>>> // Doesn't work
>>>>>>>> //                    step([$class: 'CheckStylePublisher',
>>>>>>>> //                        canRunOnFailed: true,
>>>>>>>> //                        defaultEncoding: '',
>>>>>>>> //                        healthy: '100',
>>>>>>>> //                        pattern: '**/target/checkstyle-result.xml',
>>>>>>>> //                        unHealthy: '90',
>>>>>>>> //                        useStableBuildAsReference: true
>>>>>>>> //                        ])
>>>>>>> 
>>>>>>> This publisher requires the CheckStyle plugin.
>>>>>>> 
>>>>>>>> // Doesn't work
>>>>>>>> //                    step([$class: 'WarningsPublisher', 
>>>>>>>> consoleParsers: [[parserName: 'CheckStyle']]])
>>>>>>>> 
>>>>>>> 
>>>>>>> The warnings publisher from the 4.x version does not support CheckStyle 
>>>>>>> yet.
>>>>>>> 
>>>>>>>> // Doesn't work
>>>>>>>>                     def checkstyle = scanForIssues tool: [$class: 
>>>>>>>> 'CheckStyle'], pattern: '**/target/checkstyle-result.xml'
>>>>>>>>                     publishIssues issues:[checkstyle]
>>>>>>>>                 }
>>>>>>>>             }
>>>>>>>>             catch (caughtErr)
>>>>>>>>             {
>>>>>>>>             }
>>>>>>>>             finally
>>>>>>>>             {
>>>>>>>>             }
>>>>>>>>     }
>>>>>>>> }
>>>>>>>> 
>>>>>>> 
>>>>>>> Did you install the 5.0 beta version of the plugin? This step is not 
>>>>>>> available in the 4.x version.
>>>>>>> 
>>>>>>>> Where I have tried three different methods to collect the checkstype 
>>>>>>>> results, none of which work (I have left two of them commented out for 
>>>>>>>> reference - but beleive these are methods for the legacy checkstyle 
>>>>>>>> plugin, not the newly integrated warnigns plugin?).
>>>>>>>> 
>>>>>>>> I believe the last method using scanForIssues is the correct method as 
>>>>>>>> per here:
>>>>>>>> https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local
>>>>>>>>  
>>>>>>>> <https://github.com/jenkinsci/warnings-plugin/blob/master/Jenkinsfile.local>
>>>>>>>> 
>>>>>>>> However on build, I see the checkstyle results being generated, but 
>>>>>>>> get the following error message
>>>>>>>> java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found 
>>>>>>>> among steps
>>>>>>>> 
>>>>>>>> Any ideas?
>>>>>>>> Thanks in advance!
>>>>>>>> 
>>>>>>>> 
>>>>>>>> --
>>>>>>>> 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 [email protected] <>.
>>>>>>>> To view this discussion on the web visit 
>>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.com
>>>>>>>>  
>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/00750112-2e37-4213-91b3-01c87686433c%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>>>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>>>>> <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 [email protected] <>.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/71651BEB-5A46-4E4C-B8E5-C8C688B3D162%40gmail.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/71651BEB-5A46-4E4C-B8E5-C8C688B3D162%40gmail.com?utm_medium=email&utm_source=footer>.
>>>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>>>> <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 [email protected] <>.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/1d291cec-9b90-44bb-9a82-cd47b0db906b%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/1d291cec-9b90-44bb-9a82-cd47b0db906b%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>>>> <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 [email protected] <>.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAH_GKWuSX%2BiQjqPwwb0jM8nc6oLnCW37HaWM1RffCA_bcNsumQ%40mail.gmail.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAH_GKWuSX%2BiQjqPwwb0jM8nc6oLnCW37HaWM1RffCA_bcNsumQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>>>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>>>> <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 [email protected] <>.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYzcArn7JE6mCTVO0-SKXWrbUKtY82pxkXa7PGJ%2BFp1K0Q%40mail.gmail.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYzcArn7JE6mCTVO0-SKXWrbUKtY82pxkXa7PGJ%2BFp1K0Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>>>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>>>> <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 [email protected] 
>>>>>> <mailto:[email protected]>.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/546f6fb6-2578-4e03-92a2-c2db865415ab%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/546f6fb6-2578-4e03-92a2-c2db865415ab%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>>> <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 [email protected] 
>>>>>> <mailto:[email protected]>.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYy8XzcznAug_SbJCFCctPkM1XhO-MuYww9%3D90cLUeDO-w%40mail.gmail.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYy8XzcznAug_SbJCFCctPkM1XhO-MuYww9%3D90cLUeDO-w%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>>> <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 [email protected] 
>>>>> <mailto:[email protected]>.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/3FB143F1-C598-4C62-A175-A8D54D836024%40gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/3FB143F1-C598-4C62-A175-A8D54D836024%40gmail.com?utm_medium=email&utm_source=footer>.
>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>> <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 [email protected] 
>>>>> <mailto:[email protected]>.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYxk3Ca2ZqgxaUk1_oXAzkutsemvrPo2%2B2PgrQ_ocB6Log%40mail.gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYxk3Ca2ZqgxaUk1_oXAzkutsemvrPo2%2B2PgrQ_ocB6Log%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>>>>> For more options, visit https://groups.google.com/d/optout 
>>>>> <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 [email protected] 
>>>> <mailto:[email protected]>.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-users/6CF96490-9536-4F70-B078-B61AEFD07592%40gmail.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/6CF96490-9536-4F70-B078-B61AEFD07592%40gmail.com?utm_medium=email&utm_source=footer>.
>>>> For more options, visit https://groups.google.com/d/optout 
>>>> <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 [email protected] 
>>>> <mailto:[email protected]>.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-users/d3876eab-a906-47ca-a585-9840821a3e4f%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/d3876eab-a906-47ca-a585-9840821a3e4f%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>>> For more options, visit https://groups.google.com/d/optout 
>>>> <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 [email protected] 
>> <mailto:[email protected]>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/A70AF29D-CC37-43F7-B291-8E6C54DA49DD%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/A70AF29D-CC37-43F7-B291-8E6C54DA49DD%40gmail.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 [email protected] 
>> <mailto:[email protected]>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYw7JSdDKL4X7DMTj55dotjF3FROhM-_-KUJ5BO2UCf%2B5g%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYw7JSdDKL4X7DMTj55dotjF3FROhM-_-KUJ5BO2UCf%2B5g%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/9BB4E4D0-BD40-4D61-969E-149240806592%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/9BB4E4D0-BD40-4D61-969E-149240806592%40gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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 [email protected] 
> <mailto:[email protected]>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYwmzTN1Sd6YsOqHKN6ZAvnZQ2jEfkLajKQeLneExq0seQ%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/CAKYjVYwmzTN1Sd6YsOqHKN6ZAvnZQ2jEfkLajKQeLneExq0seQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/468B4CE5-36E7-4F8A-ABE7-D9F5E3368A94%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to