Re: jQuery 1.12.4 plugin

[Ullrich Hafner]

You can have a look here to see which plugins depend on jQuery 1:
https://plugins.jenkins.io/jquery/dependencies/

If you do not need one of those then it should be safe to remove  jQuery 1 as 
well...

> Am 02.05.2024 um 23:39 schrieb s.p...@gmail.com :
> 
> Our scan reports are showing an out-of-date version of jQuery. Upon some 
> investigation, I figured out there are two jQuery plugins installed. 1) 
> jQuery 1.12.4-1   2) jQuery 3.7.1-2 . I'm not able to delete the older jQuery 
> plugin either from the UI or from the server. How do I remove the older 
> plugin ? Does it break any other plugins? Please advise.
> 
> -- 
> 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/2ab6f4d6-5f0e-4d02-9ff6-51e159b5c7fdn%40googlegroups.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/8F4A0D6A-A40B-4678-B0A3-845A08633B41%40gmail.com.

Re: Regarding unable to view the jobs in jenkins

[Ullrich Hafner]

> 
> Is it okay to use 2.176.1 version?
> 

No, use 2.387.1

https://www.jenkins.io/changelog-stable/
LTS Changelog
jenkins.io


> I am trying to install the 2.176.1 version . But I have been facing issues as 
> class not found exception matrix authorization strategy plugin .
> 
> Can you please help out?
> 
> Thanks in advance for your help.
> 
> On Fri, 24 Mar 2023 at 5:34 AM, Ullrich Hafner  <mailto:ullrich.haf...@gmail.com>> wrote:
>> This version is not supported. Please use a more recent Jenkins LTS release.
>> 
>> 
>>> Am 23.03.2023 um 12:33 schrieb Ashok Reddy >> <mailto:ashokrd...@gmail.com>>:
>>> 
>> 
>> 
>>> I am using jenkins2.138.1 verstion we used to see a jobs under view but now 
>>> we are unable to see the jobs under views.
>>> 
>>> On Thu, 23 Mar 2023 at 7:27 PM, gaurav thosani >> <mailto:gthosa...@gmail.com>> wrote:
>>>> Could you share some more details about the issue at hand with following 
>>>> questions answered 
>>>> 
>>>> 1 - the job is not visible when you visit your Jenkins url only ?  Yes
>>>> 2 - the job is not visible in specific view on your Jenkins ? 
>>>> 3 - is RBAC turned on your Jenkins using 
>>>> https://plugins.jenkins.io/role-strategy/ ?  Yes
>>>> 4 - is anyone else facing same issue on your Jenkins ? Yes no one can’t 
>>>> see the jobs under view
>>>> 
>>>> With RBAC enabled, you have to review job name/ pattern mapping to your 
>>>> configured access role by going to Jenkins manage settings and clicking 
>>>> Manage roles and access ( may not be quoting exact words ) 
>>>> 
>>>> Thank you
>>>> Gaurav Thosani
>>>> 
>>>>> On Mar 23, 2023, at 1:24 AM, Ashok Reddy >>>> <mailto:ashokrd...@gmail.com>> wrote:
>>>>> 
>>>>> Hi Team, 
>>>> 
>>>>> 
>>>>> I have the jobs in jenkins server and couldn’t be able to view the jobs 
>>>>> in jenkins dashboard.
>>>>> 
>>>>> Can some one help me?
>>>>> 
>>>>> -- 
>>>>> 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 
>>>>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-users/CAKRLcHhWiY8y2gP87Ys9qN12LFQiEHCuB61fp7ZShjeMBwnG6A%40mail.gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKRLcHhWiY8y2gP87Ys9qN12LFQiEHCuB61fp7ZShjeMBwnG6A%40mail.gmail.com?utm_medium=email_source=footer>.
>>>> 
>>>> 
>>>> -- 
>>>> 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 
>>>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-users/CADC4002-725B-4643-A7EA-C9D9E087A011%40gmail.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CADC4002-725B-4643-A7EA-C9D9E087A011%40gmail.com?utm_medium=email_source=footer>.
>>> 
>>> 
>>> -- 
>>> 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 
>>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>> 
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAKRLcHiHs0fdw5e1JgqKCHxkrH-Svjc8n0R7%3Dk2-_NwEmTp_jw%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKRLcHiHs0fdw5e1JgqKCHxkrH-Svjc8n0R7%3Dk2-_NwEmTp_jw%40mail.gmail.com?utm_medium=email_source=footer>.
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscrib

Re: Regarding unable to view the jobs in jenkins

[Ullrich Hafner]

This version is not supported. Please use a more recent Jenkins LTS release.

> Am 23.03.2023 um 12:33 schrieb Ashok Reddy :
> 
> I am using jenkins2.138.1 verstion we used to see a jobs under view but now 
> we are unable to see the jobs under views.
> 
> On Thu, 23 Mar 2023 at 7:27 PM, gaurav thosani  > wrote:
>> Could you share some more details about the issue at hand with following 
>> questions answered 
>> 
>> 1 - the job is not visible when you visit your Jenkins url only ?  Yes
>> 2 - the job is not visible in specific view on your Jenkins ? 
>> 3 - is RBAC turned on your Jenkins using 
>> https://plugins.jenkins.io/role-strategy/ ?  Yes
>> 4 - is anyone else facing same issue on your Jenkins ? Yes no one can’t see 
>> the jobs under view
>> 
>> With RBAC enabled, you have to review job name/ pattern mapping to your 
>> configured access role by going to Jenkins manage settings and clicking 
>> Manage roles and access ( may not be quoting exact words ) 
>> 
>> Thank you
>> Gaurav Thosani
>> 
>>> On Mar 23, 2023, at 1:24 AM, Ashok Reddy >> > wrote:
>>> 
>>> Hi Team, 
>> 
>>> 
>>> I have the jobs in jenkins server and couldn’t be able to view the jobs in 
>>> jenkins dashboard.
>>> 
>>> Can some one help me?
>>> 
>>> -- 
>>> 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/CAKRLcHhWiY8y2gP87Ys9qN12LFQiEHCuB61fp7ZShjeMBwnG6A%40mail.gmail.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/CADC4002-725B-4643-A7EA-C9D9E087A011%40gmail.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/CAKRLcHiHs0fdw5e1JgqKCHxkrH-Svjc8n0R7%3Dk2-_NwEmTp_jw%40mail.gmail.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/75C33341-8069-499A-AA96-39A39A430FB3%40gmail.com.

Re: Building Jenkins-plugins failed in maven enforcer plugins

[Ullrich Hafner]

Which maven version are you using? The error message says that you need to use 
at least Maven 3.8.1.

> Am 30.01.2023 um 07:37 schrieb Ahmed Rafiq :
> 
> Hello,
> trying to update our inhouse Jenkins plugins. But it gets failed from 
> maven-enforcer-plugin at
> 
> [ERROR] Rule 1: org.apache.maven.plugins.enforcer.RequireMavenVersion failed 
> with message:
> 3.8.1 required to no longer download dependencies via HTTP (use HTTPS 
> instead).
> 
> In our settings.xml and POM.xml there's no dependencies with HTTP url, 
> therefore quite confused where to solve / debug for this error.
> 
> Can anyone give me some ideas?
> 
> 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/CAOxCx6%3DPjBJaREhmwdW5NVGKW%2BahvxApkCw1c6AovyH0pSdTUw%40mail.gmail.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/FD82F910-F032-4BA5-BABF-6F2033DAE061%40gmail.com.

Re: Unittest xml file not valid

[Ullrich Hafner]

Ok, good to see. Then you might not need the xunit plugin at all, since the 
JUnit plugin supports this XML format out-of-the-box.


> Am 07.12.2022 um 16:13 schrieb Fabian Cenedese :
> 
> At 13:16 07.12.2022, Ullrich Hafner wrote:
> 
>> The best way would be to clone the xunit plugin and feed your file as a new 
>> test case. Then you can directly see what is broken.
> 
> I found that pytest generates a JUnit format file. With JUnit as parser
> insteap of CppUnit it works. So it was a user error, sorry for that.
> 
> Thanks for helping.
> 
> bye  Fabi
> 
> -- 
> 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/5a7afe81055c313ce9cf7aeb457128cb%40indel.ch.

-- 
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/24D78DE3-A8C2-4057-A49A-DBA64FA5D259%40gmail.com.

Re: Unittest xml file not valid

[Ullrich Hafner]

The best way would be to clone the xunit plugin and feed your file as a new 
test case. Then you can directly see what is broken.

> Am 07.12.2022 um 06:50 schrieb Fabian Cenedese :
> 
> Hello
> 
> I'm using pytest for testing and have it generate a unittest
> xml file that can be read by Jenkins. This has worked fine
> for other jobs but now I have a new job where Jenkins doesn't
> like the file:
> 
> 01:12:52  org.jenkinsci.plugins.xunit.service.TransformerException: The 
> result file 
> 'C:\Jenkins\workspace\applicationtest\applicationtest\unittest.xml' for the 
> metric 'CppUnit' is not valid. The result file has been skipped.
> 
> However the file exists and XmlLint doesn't see a problem with it.
> No un-escaped special chars or < > etc. There's a 
> tag and it just looks like other files from other jobs that work.
> 
>  errors="0" failures="31" skipped="0" tests="37" time="342.813" 
> timestamp="2022-12-07T01:07:09.246626" hostname="TestHost7"> classname="tests.test_explorer.TestClass" name="test_Exp_Invisible" 
> time="85.074"> />
> 
> Is there a way to see what exactly it is that Jenkins doesn't like
> about this file?
> 
> Thanks
> 
> bye  Fabi
> 
> -- 
> 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/770c9b9f82cede0ddb2e83a818ba0f09%40indel.ch.

-- 
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/925EE961-3E29-43FA-85EF-F15E7B013D74%40gmail.com.

Re: git metrics for pipeline jobs

[Ullrich Hafner]

I don’t think that this is possible in the moment. 

> Am 29.08.2022 um 11:16 schrieb tiz...@gmail.com :
> 
> Hi,
> I want to be able to see the trend of the duration for each git step in my 
> pipeline jobs.
> what I refer to is the different steps (rev-parse, checkout, rev-list) of 
> checking out the repository with the Jenkinsfile and more important the 
> repository of shared libraries. 
> 
> is there a way to do it currently or it requires changes to the git plugin?
> 
> Thanks,
> Tidhar
> 
> -- 
> 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/efc0a217-f22d-4c04-8a1b-e32b06ae72bbn%40googlegroups.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/32D3FEDC-8E78-46AF-838F-A519FA215FF2%40gmail.com.

Re: Display of job results

[Ullrich Hafner]

> Am 01.02.2022 um 22:27 schrieb 'christop...@googlemail.com' via Jenkins Users 
> :
> 
> [...]
> 
> Any recommendations how I can improve that situation? Is there a way to 
> realize some of these ideas:
> - customize position of a plugin output in the job view

This is one of the major drawbacks of Jenkins UI in the moment and there is no 
workaround available yet. We started a new plugin that tries to solve this 
problem with https://muuri.dev  on a new page but this 
promising approach still needs to be implemented for the old views.
 
>  - split display of xunit test results per tool?

This is also not possible right now. I am using this approach in the warnings 
plugin and plan to make this concept available for coverage data as well. But 
for unit tests this is not planned yet. I’m also not sure if that information 
actually is so helpful: if a test fails then I am not really not that 
interested in which suite it failed.  

>  
> What about the ranorex plugin itself? I do have a number of ranorex test 
> executables and these are called by a script from the build system. I do not 
> want to replicate a list in jenkins scripts. That's why I don't like to use 
> the ranorex plugin here.
> 
> Thanks for reading up to here and many thanks in advance for any advice!
> Regards,
> Christoph
> 
> -- 
> 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/5c0dc622-e9c0-498b-9d8d-8bac93caace6n%40googlegroups.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/08878689-D443-4AEA-8B28-C2F6EF4DA303%40gmail.com.

Re: Blue Ocean Status Update

[Ullrich Hafner]

> Am 18.10.2021 um 10:43 schrieb Oleg Nenashev :
> 
> Hi all,
> 
> To whomever sees this thread, please see Bringing Blue Ocean into the future 
> of Jenkins 
> 
>  by Tim Jacomb. Taking the state of BlueOcean that has not changed much over 
> the past two years, I suggest making the Pipeline Graph View Plugin an 
> official path for Jenkins.
> 
> Under that, I mean:
> Add "Pipeline Graph View Plugin" to the Jenkins Roadmap, in the preview or 
> released status
> Add "Pipeline Graph View Plugin" to the list of the recommended Jenkins 
> plugins in the plugin installation manager
+1
> Remove Blue Ocean from the list of recommended plugins in Jenkins
> TBD: Announce the future plan to double down on consolidating Blue Ocean 
> features in Jenkins and then deprecating Blue Ocean
Since we have nobody working on UI improvements anymore it does not make sense 
for me to announce a future plan. We already have a plan on our web page (which 
is as obsolete as the Blue Ocean plan). In my opinion Jenkins UI Development is 
at a dead end in the moment (Except Cliffs’ and Tims' tremendous work in 
getting the pipeline view ported back to classic Jenkins UI).
> TBD: Create tasks for replacing Jenkins newcomer user documentation that 
> related on Blue Ocean
> Note that there are still gaps in Jenkins features, e.g. Visual Declarative 
> Pipeline Editor is available only in Blue Ocean. Probably it is too early to 
> announce deprecation of Blue Ocean, but we need to make a decision at some 
> point.

Hmm, for me Blue Ocean is deprecated since 2 years. I wonder why we still use 
it as the default view in ci.jenkins.io  even though we 
know that it is dead since two years now. 

> 
> Opinions?
> 
> Best regards,
> Oleg
> 
> On Thursday, November 28, 2019 at 8:21:34 AM UTC+1 Jeremy Hartley wrote:
> Thank you Peter for your feedback. I don't expect subversion support to be 
> added to Blue Ocean, but once you switch to Git it will hopefully be a useful 
> addition to you
> 
> 
> On Thursday, November 28, 2019 at 3:54:44 AM UTC+1, Peter wrote:
> Followed the blue ocean attempt for some time, but missing support for 
> subversion makes it impossible to integrate in our environment (until we'll 
> switch to git). Cool stuff, anyways.
> 
> 
> -- 
> 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/cabb4d45-be58-468a-9291-8d3bdf4bfcdbn%40googlegroups.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/63E0557A-D6CC-4557-94D7-54B8BFCA70F1%40gmail.com.

Re: "Changes" reference build/commit

[Ullrich Hafner]

> Am 12.10.2021 um 22:40 schrieb Cristian Morales Vega 
> :
> 
> In a multibranch pipeline I noticed that the first job in a branch
> always has an empty list of "changes" (i.e.
> https:///job//1/changes).
> https://plugins.jenkins.io/git/#changelog-extensions mentions a
> "Calculate changelog against a specific branch" option, but I can't
> find it anywhere. Where is it?

This option is available in the Git plugin configuration of a pipeline or 
freestyle job. I think it is (not yet?) available in a GitHub branch source, I 
don’t know why it is missing there. Maybe it would be helpful to create a 
feature request?

> But actually I'm not even sure that's
> what I want, shouldn't the "Changes" use the "Reference build" from
> the Forensics API (https://plugins.jenkins.io/git-forensics/)?
> 

The forensics plugin actually knows those changes but does not render them in 
the UI. (The Git plugin actually records the ChangeLog and renders them. But 
the Git plugin does not know the concept of a reference build so far. I’m not 
sure if there is an API so that I can show those changes in my forensics plugin 
by using the UI of the Git plugin) 

> What's the best I can currently achieve with Jenkins regarding the
> "Changes" generation?
> 
> -- 
> 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/CAOWQn3QOB1u-ouFv4EWqJ1Qpdd%2BqksQmPkNncA%2BM0z8o_5kb3Q%40mail.gmail.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/8A726494-8D76-484E-9CAB-D45646747FFB%40gmail.com.

Re: bootstrap 4 plugin deprecated - how to address?

[Ullrich Hafner]

> Am 11.10.2021 um 17:28 schrieb Alan Sparks :
> 
> This morning my Jenkins instances showed an alert the the “bootstrap 4 API” 
> plugin was now deprecated.  I also have the bootstrap 5 plugin.  I went 
> looking for either an uninstall to test or a way to confirm the message, but 
> found neither.  The “uninstall” button is greyed out for the plugin (shows as 
> a dependency of JUnit), and I don’t see a way to confirm/hide the 
> notification.  Am I missing something?

I removed the deprecated label again. The plugin is deprecated but the PR for 
the JUnit plugin is still not merged.

>  
> All else is up to date, running Jenkins 2.202.2

This is a very very old Jenkins instance, you should consider upgrading.

> and all plugins showing up to date.
> Thanks for any advice.
> -Alan
> 
> -- 
> 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/DM6PR18MB3306FDD72AAE10519C7125B3C5B59%40DM6PR18MB3306.namprd18.prod.outlook.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/6D175F09-65A3-4FB6-9912-5E4A0E554891%40gmail.com.

Re: replace text with user defined text

[Ullrich Hafner]

I don’t think that this is possible with a plugin right now. These texts are 
localized messages. Maybe you can create a new localization file that 
overwrites the existing files. You can have a look at the plugin that does this 
for the first item and try to achieve the same for the rest.


> Am 23.09.2021 um 09:48 schrieb sambonta :
> 
> Anyone got any idea on this ? 
> On Saturday, September 18, 2021 at 10:23:34 PM UTC+5:30 sambonta wrote:
> Hi, 
> 
> can someone please help me to find a plugin or assist to write a plugin to 
> replace the phrases containing "build" with other things
> 
> Build Now => Run Job Now (there is a plugin to replace this)
> Build History => Job Run History
> Build Queue => Job Queue
> Build Executor Status => Job Executor Status
> Last Build => Last Run
> Last Stable Build => Last Stable Run
> 
> 
> -- 
> 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/fa91c451-1ab7-4f7c-9503-eb1b1caec52cn%40googlegroups.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/19B33F36-7038-483C-8006-EAD66F479124%40gmail.com.

Re: Restricting Cobertura trend graph to main branch?

[Ullrich Hafner]

Do you build different branches in the same job?

> Am 02.08.2021 um 03:49 schrieb 'Dan Kegel' via Jenkins Users 
> :
> 
> Hi!  I am using this line in my Jenkinsfile:
> 
>  cobertura autoUpdateHealth: true, autoUpdateStability: true, failNoReports: 
> false, coberturaReportFile: '**/coverage-**.xml', failUnhealthy: true, 
> failUnstable: false, maxNumberOfBuilds: 0, onlyStable: false, sourceEncoding: 
> 'ASCII', zoomCoverageChart: true, enableNewApi: true, lineCoverageTargets: 
> "80, 0, 10"
> 
> and I get a lovely coverage trend graph.  However, try builds (builds for 
> merge requests) show up in the trendline, so it looks like coverage is 
> bouncing all over the place.
> 
> I'm trying setting autoUpdateFoo to false when not on main branch, but I'm 
> not sure it's doing what I expect.  Anyone have suggestions?
> 
> Thanks,
> 
> Dan
> 
> 
> 
> 
> -- 
> 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/328fc0ea-d032-43dc-9b42-9524160010f2n%40googlegroups.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/94F4BBDC-EC35-4C17-BF07-709382D1CA61%40gmail.com.

Re: jenkins status page checkmark instrad of green balls

[Ullrich Hafner]

> Am 17.06.2021 um 15:13 schrieb Fabian Cenedese :
> 
> At 14:41 17.06.2021, you wrote:
>> a) Downgrade your Jenkins version (not recommended). 
>> b) Write a Jenkins theme that uses the old and ugly ball images 
>> 
>>> Am 15.06.2021 um 08:36 schrieb sabsac123 
>>> <sab...@gmail.com>:
>>> 
>>> My jenkins project status page is showing a green checkmark for successful 
>>> buld instead of green balls. how to bring back the balls icon to the staus 
>>> page? 
> 
> Just to add to the original poster's comment. We too were surprised to
> see the new icons. The problem is not whether the new or the old ones
> were ugly or not. It's a simple case of clarity. The old icons (ugly or not)
> were a lot clearer to grasp.

You are talking about the weather icons? This is a different point, please add 
your comments in https://issues.jenkins.io/browse/JENKINS-65124 


> The new weather icons are all the same color.
> It's harder to see at one glance what the state of the dozens of jobs is.
> Obviously we eventually will get used to the new theme. But I still don't
> understand why all people think that flat and abstract is more modern.
> Modern is not necessarily also practical.
> Just my 1 cent.
> 
> bye  Fabi
> 
> -- 
> 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/20210617131335.AB085467EA38%40macserver.private.

-- 
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/1BC191A9-75A4-4599-AC1D-8F8A16D2F947%40gmail.com.

Re: jenkins status page checkmark instrad of green balls

[Ullrich Hafner]

a) Downgrade your Jenkins version (not recommended). 
b) Write a Jenkins theme that uses the old and ugly ball images 

> Am 15.06.2021 um 08:36 schrieb sabsac123 :
> 
> My jenkins project status page is showing a green checkmark for successful 
> buld instead of green balls. how to bring back the balls icon to the staus 
> page?
> 
> -- 
> 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/2b4c4cb4-e459-4a8e-8b86-670620e69295n%40googlegroups.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/D6035D8B-5ED6-452D-9695-E61C95EEF843%40gmail.com.

Re: Upgraded Plugins: Jenkins fails to start

[Ullrich Hafner]

Is there a reason that you are still using the old and unmaintained JaCoCo 
plugin and not the code-coverage-api plugin? The functionality should be the 
same.

> 
> On Tuesday, June 1, 2021 at 2:30:34 AM UTC+1 raould...@gmail.com 
>  wrote:
> We stumbled on the same error after upgrading plugins on Jenkins last week.
> Search in your Jenkins plugin directory for the jar file starting with the 
> name: guice.
> The results should only list one version of the guice jar.
> 
> In our case it turned out that the Jacoco plugin came with a newer version of 
> guice than the other plugins did, That caused this problem. We downgraded the 
> Jacoco plugin and it worked again (from jacoco 3.2.0 back to 3.1.1 )
> 
> Op zondag 23 mei 2021 om 19:55:03 UTC+2 schreef sverr...@gmail.com 
> :
> I have upgraded all the plugins, then restarted Jenkins.
> It fails to start properly.
> Any idea what the problem here is about?
> 
> The website is loading, but shows the following Stacktrace
> java.lang.IllegalArgumentException: Unable to inject class 
> hudson.model.UserIdMapper   at 
> hudson.init.TaskMethodFinder.lookUp(TaskMethodFinder.java:125)
>  at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) 
>  at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) 
>  at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) 
>  at jenkins.model.Jenkins$5.runTask(Jenkins.java:1131) 
>  at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) 
>  at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
>  at 
> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
>  
>  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) 
> Caused: org.jvnet.hudson.reactor.ReactorException 
>  at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) 
>  at jenkins.InitReactorRunner.run(InitReactorRunner.java:49) 
>  at jenkins.model.Jenkins.executeReactor(Jenkins.java:1164)
>  at jenkins.model.Jenkins.(Jenkins.java:962) 
>  at hudson.model.Hudson.(Hudson.java:85) 
>  at hudson.model.Hudson.(Hudson.java:81) 
>  at hudson.WebAppMain$3.run(WebAppMain.java:295) 
> Caused: hudson.util.HudsonFailedToLoad at 
> hudson.WebAppMain$3.run(WebAppMain.java:312)
> 
> The jenkins log output shows rthe following Exceptions:
> 2021-05-23 16:50:01.547+ [id=37]INFO
> jenkins.InitReactorRunner$1#onAttained: Listed all plugins
> 2021-05-23 16:50:09.041+ [id=36]SEVERE  
> h.ExtensionFinder$GuiceFinder#: Failed to create Guice container from 
> all the plugins
> java.lang.LinkageError: loader constraint violation: loader (instance of 
> hudson/PluginFirstClassLoader) previously initiated loading for a different 
> type with name "com/google/inject/Binder"
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at 
> jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1155)
> at 
> jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1326)
> at 
> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1377)
> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342)
> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1095)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 
> com.google.inject.multibindings.Multibinder.newSetBinder(Multibinder.java:136)
> at 
> com.google.inject.multibindings.Multibinder.newSetBinder(Multibinder.java:99)
> at 
> hudson.plugins.depgraph_view.model.graph.DependencyGraphModule.configure(DependencyGraphModule.java:49)
> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
> at 
> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
> at com.google.inject.spi.Elements.getElements(Elements.java:110)
> at 
> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
> at 
> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
> at com.google.inject.Guice.createInjector(Guice.java:96)
> at com.google.inject.Guice.createInjector(Guice.java:73)
> at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:285)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native 
> Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at 

Re: Still stuck on older Jenkins because of table-to-div -- what to do?

[Ullrich Hafner]

> Am 04.06.2021 um 12:51 schrieb Roland Asmann :
> 
> 
> Hi all,
> 
> Because of the table-to-div changes in 2.277.1 not working in several 
> plugins, I am still running 2.263.4.  Every time I check the list of known 
> plugins that aren't working since this update, the list seems to grow...
> A different change in Jenkins a couple of years back made us setup a second 
> Jenkins instance, because of projects that weren't able run on the new 
> version. I am still migrating some of those projects and I really don't want 
> to setup a 3rd instance and maintain all 3.
> 
> So, how do I proceed? Can someone 'force' the plugin developers to update 
> their plugins?

No. If a plugin does not yet support 2.277.1 then the plugin is probably not 
maintained at all anymore. Then it would help if someone who still uses the 
plugin would volunteer to take over the ownership. This is how our open source 
model in Jenkins works. 

> Or maybe someone can look some of the plugins over and get them running again?
> 

See above. We do not have a support policy for plugins, so if something does 
not work and the maintainer has no spare time to fix then it is up to the 
community to help here.

> And maybe it would be good if someone could check over all open issues in 
> this list 
> (https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=20741) and see 
> if they are actually still existing/are referencing the correct plugin -- 
> some issues were created saying it was an issue in the core, but the comments 
> later state it was actually a plugin. I really need to know if there are 
> still issues in the core or if it's only in some plugins, so I can decide on 
> how to move on...
> 
> Thanks.
> 
> Roland
> 
> -- 
> 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/ff4acd22-e8c5-4dc7-8284-645c5c1375d6n%40googlegroups.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/C6997362-A032-4300-B131-9E70A953CDE5%40gmail.com.

Re: How to distinct errors and failures in tests

[Ullrich Hafner]

Typically you do not set the status of a build by setting the return code. Your 
build should never alter the return code just because the tests are failing. So 
I would suggest that your build always returns 0 if the build is successful 
(ignoring the test results). The JUnit plugin will do the build status handling 
for you: if there are test failures, then the JUnit plugin will set the build 
status to unstable. If not, the status remains successful. You can then 
navigate with lastSuccessful or lastStable to the last build without 
testfailures.

BTW: I don’t think that there is a way to differentiate between test errors and 
failures in Jenkins yet.

> Am 21.04.2021 um 11:26 schrieb Nick N :
> 
> Hey, guys!
> 
> I have a freestyle project. It builds an app and run tests (python, 
> unittest). It is quite straightforward if return codes are 0 then build is 
> successful, otherwise it is failed. Earlier I returned amount of errors and 
> failures as a returncode to see tests results on the dashboard (passed or 
> failed). But test results may contain failures and errors, and I want to know 
> if there were errors on tests or they all finished, but found some bugs. 
> Actually I need to get last build (via jenkins api) without errors, no matter 
> if there were failures.
> 
> I've tried to look at "lastStableBuild", but it seems it sticks to 
> "lastSuccessfulBuild". I've tried to find information about build statuses 
> but had no success. Particularly what are criteria of each of them? Maybe it 
> is completely wrong approach and there's a better way?
> 
> 
> -- 
> 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/CACA70iDR0X9RTWv2051vTuO3pC5odS10kssRYLQe6%2B1A2DjGDg%40mail.gmail.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/61D82A4F-D2EF-4D49-909C-D0D55BC4A556%40gmail.com.

Re: how to access all classes and methods of a plugin in jenkins pipeline?

[Ullrich Hafner]

Can you please file a bug report for the warnings plugin, it seems something 
broken in my build...

> Am 14.04.2021 um 18:55 schrieb jesus fernandez :
> 
> yes all the other plugins I have checked so far have a woeking javadoc
> 
> El mié., 14 abr. 2021 18:20, Ullrich Hafner  <mailto:ullrich.haf...@gmail.com>> escribió:
> I publish one, but never looked at the results. Does that work for other 
> plugins?
> 
>> Am 13.04.2021 um 13:32 schrieb jesus fernandez > <mailto:jesusfernandez0...@gmail.com>>:
>> 
>> is there a javadoc for warnings-ng plugin? or just the github? I get a 404 
>> when accesing the warnings-ng javadoc
>> 
>> El lunes, 12 de abril de 2021 a las 14:28:33 UTC+2, ullrich...@gmail.com 
>> <http://gmail.com/> escribió:
>> In the source code in GitHub?
>> 
>> You can also look for methods annotated with ExportedBean.
>> 
>> 
>>> Am 12.04.2021 um 10:16 schrieb jesus fernandez >:
>>> 
>> 
>>> 
>>> where can I see that? in the javadoc I do not see any method with that 
>>> annotation, thoug I could use the getResults() with no problems
>>> El domingo, 11 de abril de 2021 a las 21:43:06 UTC+2, ullrich...@gmail.com 
>>> <http://gmail.com/> escribió:
>>> Due to security considerations only methods marked with @Whitelisted are 
>>> accessible in Groovy scripts. Does your getter have such an annotation?
>>> 
>>> 
>>>> Am 11.04.2021 um 19:02 schrieb jesus fernandez >:
>>>> 
>>> 
>>>> I am a junior dev trying to lear about Jenkins, I have been learning on my 
>>>> own for a couple of months. Currently I have a pipeline (just for learning 
>>>> purposes) which runs static analysis on a folder, and then publish it, I 
>>>> have been able to send a report through email using jelly templates, from 
>>>> there I realized it is posbile to instantiate the classes of a plugin to 
>>>> use its methods so I went to the cppcheck javadoc here 
>>>> https://javadoc.jenkins.io/plugin/cppcheck/ 
>>>> <https://javadoc.jenkins.io/plugin/cppcheck/> and did some trial and error 
>>>> so I can get some values of my report and then do something else with them 
>>>> something, so I had something like this in my pipeline:
>>>> ```
>>>> pipeline {
>>>> agent any
>>>> 
>>>> stages {
>>>>   stage('analysis') {
>>>> steps {
>>>>   script{
>>>> bat'cppcheck "E:/My_project/Source/" --xml --xml-version=2 . 2> 
>>>> cppcheck.xml'
>>>>   }
>>>>}
>>>> }
>>>> stage('Test'){
>>>>   steps {
>>>> script {
>>>>   publishCppcheck pattern:'cppcheck.xml'
>>>>   for (action in currentBuild.rawBuild.getActions()) {
>>>> def name = action.getClass().getName()
>>>> if (name == 'org.jenkinsci.plugins.cppcheck.CppcheckBuildAction') {
>>>>def cppcheckaction = action
>>>>def totalErrors = cppcheckaction.getResult().report.getNumberTotal()
>>>>println totalErrors
>>>>def warnings = 
>>>> cppcheckaction.getResult().statistics.getNumberWarningSeverity()
>>>>println warnings
>>>>   }
>>>> }
>>>>   }
>>>> }
>>>> }
>>>> }
>>>> 
>>>> }
>>>> ```
>>>> which output is:
>>>> ```
>>>> [Pipeline] echo
>>>> 102
>>>> [Pipeline] echo
>>>> 4
>>>> ```
>>>> 
>>>> My logic (wrongly) tells me that if I can access to the report and 
>>>> statistics classes like that and uses their methods getNumberTotal() and 
>>>> getNumberWarningSeverity() respectively, therefore I should be able to 
>>>> also access the ```DiffState``` class in the same way and use the 
>>>> ```valueOf()``` method to get an enum of the new errors. But adding this 
>>>> to my pipeline:
>>>> ```
>>>> def nueva = cppcheckaction.getResult().diffState.valueOf(NEW)
>>>> println nueva
>>>> ```
>>>> Gives me an error:
>>>> ```
>>>> org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: No 
>>>> such field found: field org.jenkinsci.plugins.cppcheck.CppcheckBuildAction 
>>>> diffState
>>>> at 

Re: Can I send cppcheck results through slack in a jenkins pipeline?

[Ullrich Hafner]

You must wrap it into tm: see 
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/ui-tests/src/test/java/io/jenkins/plugins/analysis/warnings/SmokeTests.java#L99


> Am 13.04.2021 um 16:17 schrieb jesus fernandez :
> 
> How can I access those token macros? (sorry if this is a silly question) I 
> have never used them before, I tried to print the value with ```println 
> ${ANALYSIS_ISSUES_COUNT, tool="cppcheck", type="NEW"}``` but I get an 
> unexpected token error
> 
> El viernes, 9 de abril de 2021 a las 14:03:39 UTC+2, ullrich...@gmail.com 
> escribió:
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#token-macro-support
>  
> 
> 
> 
>> Am 09.04.2021 um 13:59 schrieb jesus fernandez > >:
>> 
> 
>> Thanks for replying, any documentation or link to guide me in the right 
>> direction on how to do it? I am quite Junior and have been learning Jenkins 
>> on my own
>> 
>> El viernes, 9 de abril de 2021 a las 13:46:48 UTC+2, ullrich...@gmail.com 
>>  escribió:
>> Exporting results from one plugin into another plugin is definitely 
>> possible. You typically have two steps:
>> 1) Export the data from a producer plugin
>> a) using Tokens
>> b) using API methods of the plugin
>> 2) Import the data (or reformat and aggregate it) into a consumer plugin
>> 
>> For step 1 I can say this works for the warnings plugin, it can export the 
>> results of CppCheck either into tokens or into objects (that you can process 
>> using your pipeline). 
>> 
>> I have no idea if the slack plugin is capable of doing step 2 though, but I 
>> would assume that it works in that way...
>> 
>> 
>>> Am 09.04.2021 um 08:39 schrieb jesus fernandez >:
>>> 
>> 
>>> I just started using cppcheck, and I was wondering if there is any way to 
>>> access to the report values (for instance number of total errors) and send 
>>> it to slack. I have been searching in the documentation and here in SO but 
>>> I have found nothing, as I just have been using Jenkins for a couple of 
>>> months ( I am a junior dev) I was wondering if somebody know if this is 
>>> possible and could drive me in the right direction.
>>> 
>> 
>>> -- 
>>> 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/d3aee90e-5331-480f-84d7-4df7c3ebcf6fn%40googlegroups.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-use...@googlegroups.com 
>> .
> 
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/abdfdbec-e2cf-4f69-a089-1cb93dcef30en%40googlegroups.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/c5ba204c-fa9f-4f6c-800f-69dba9680f87n%40googlegroups.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/27FB6AD8-66DF-4BC2-A076-8CD00535F39A%40gmail.com.

Re: how to access all classes and methods of a plugin in jenkins pipeline?

[Ullrich Hafner]

I publish one, but never looked at the results. Does that work for other 
plugins?

> Am 13.04.2021 um 13:32 schrieb jesus fernandez :
> 
> is there a javadoc for warnings-ng plugin? or just the github? I get a 404 
> when accesing the warnings-ng javadoc
> 
> El lunes, 12 de abril de 2021 a las 14:28:33 UTC+2, ullrich...@gmail.com 
> escribió:
> In the source code in GitHub?
> 
> You can also look for methods annotated with ExportedBean.
> 
> 
>> Am 12.04.2021 um 10:16 schrieb jesus fernandez > >:
>> 
> 
>> 
>> where can I see that? in the javadoc I do not see any method with that 
>> annotation, thoug I could use the getResults() with no problems
>> El domingo, 11 de abril de 2021 a las 21:43:06 UTC+2, ullrich...@gmail.com 
>>  escribió:
>> Due to security considerations only methods marked with @Whitelisted are 
>> accessible in Groovy scripts. Does your getter have such an annotation?
>> 
>> 
>>> Am 11.04.2021 um 19:02 schrieb jesus fernandez >:
>>> 
>> 
>>> I am a junior dev trying to lear about Jenkins, I have been learning on my 
>>> own for a couple of months. Currently I have a pipeline (just for learning 
>>> purposes) which runs static analysis on a folder, and then publish it, I 
>>> have been able to send a report through email using jelly templates, from 
>>> there I realized it is posbile to instantiate the classes of a plugin to 
>>> use its methods so I went to the cppcheck javadoc here 
>>> https://javadoc.jenkins.io/plugin/cppcheck/ 
>>>  and did some trial and error 
>>> so I can get some values of my report and then do something else with them 
>>> something, so I had something like this in my pipeline:
>>> ```
>>> pipeline {
>>> agent any
>>> 
>>> stages {
>>>   stage('analysis') {
>>> steps {
>>>   script{
>>> bat'cppcheck "E:/My_project/Source/" --xml --xml-version=2 . 2> 
>>> cppcheck.xml'
>>>   }
>>>}
>>> }
>>> stage('Test'){
>>>   steps {
>>> script {
>>>   publishCppcheck pattern:'cppcheck.xml'
>>>   for (action in currentBuild.rawBuild.getActions()) {
>>> def name = action.getClass().getName()
>>> if (name == 'org.jenkinsci.plugins.cppcheck.CppcheckBuildAction') {
>>>def cppcheckaction = action
>>>def totalErrors = cppcheckaction.getResult().report.getNumberTotal()
>>>println totalErrors
>>>def warnings = 
>>> cppcheckaction.getResult().statistics.getNumberWarningSeverity()
>>>println warnings
>>>   }
>>> }
>>>   }
>>> }
>>> }
>>> }
>>> 
>>> }
>>> ```
>>> which output is:
>>> ```
>>> [Pipeline] echo
>>> 102
>>> [Pipeline] echo
>>> 4
>>> ```
>>> 
>>> My logic (wrongly) tells me that if I can access to the report and 
>>> statistics classes like that and uses their methods getNumberTotal() and 
>>> getNumberWarningSeverity() respectively, therefore I should be able to also 
>>> access the ```DiffState``` class in the same way and use the 
>>> ```valueOf()``` method to get an enum of the new errors. But adding this to 
>>> my pipeline:
>>> ```
>>> def nueva = cppcheckaction.getResult().diffState.valueOf(NEW)
>>> println nueva
>>> ```
>>> Gives me an error:
>>> ```
>>> org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: No 
>>> such field found: field org.jenkinsci.plugins.cppcheck.CppcheckBuildAction 
>>> diffState
>>> at 
>>> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.unclassifiedField(SandboxInterceptor.java:425
>>>  )
>>> at 
>>> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:409
>>>  )
>>> ...
>>> ```
>>> 
>> 
>>> -- 
>>> 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/ca24b1f9-b0a8-4e81-8101-0b25f8267602n%40googlegroups.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-use...@googlegroups.com 
>> .
> 
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/9c65acbc-f199-4d99-8d96-0b37a44a4f2an%40googlegroups.com
>>  
>> .
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this 

Re: how to access all classes and methods of a plugin in jenkins pipeline?

[Ullrich Hafner]

In the source code in GitHub?

You can also look for methods annotated with ExportedBean.

> Am 12.04.2021 um 10:16 schrieb jesus fernandez :
> 
> 
> where can I see that? in the javadoc I do not see any method with that 
> annotation, thoug I could use the getResults() with no problems
> El domingo, 11 de abril de 2021 a las 21:43:06 UTC+2, ullrich...@gmail.com 
> escribió:
> Due to security considerations only methods marked with @Whitelisted are 
> accessible in Groovy scripts. Does your getter have such an annotation?
> 
> 
>> Am 11.04.2021 um 19:02 schrieb jesus fernandez > >:
>> 
> 
>> I am a junior dev trying to lear about Jenkins, I have been learning on my 
>> own for a couple of months. Currently I have a pipeline (just for learning 
>> purposes) which runs static analysis on a folder, and then publish it, I 
>> have been able to send a report through email using jelly templates, from 
>> there I realized it is posbile to instantiate the classes of a plugin to use 
>> its methods so I went to the cppcheck javadoc here 
>> https://javadoc.jenkins.io/plugin/cppcheck/ 
>>  and did some trial and error 
>> so I can get some values of my report and then do something else with them 
>> something, so I had something like this in my pipeline:
>> ```
>> pipeline {
>> agent any
>> 
>> stages {
>>   stage('analysis') {
>> steps {
>>   script{
>> bat'cppcheck "E:/My_project/Source/" --xml --xml-version=2 . 2> 
>> cppcheck.xml'
>>   }
>>}
>> }
>> stage('Test'){
>>   steps {
>> script {
>>   publishCppcheck pattern:'cppcheck.xml'
>>   for (action in currentBuild.rawBuild.getActions()) {
>> def name = action.getClass().getName()
>> if (name == 'org.jenkinsci.plugins.cppcheck.CppcheckBuildAction') {
>>def cppcheckaction = action
>>def totalErrors = cppcheckaction.getResult().report.getNumberTotal()
>>println totalErrors
>>def warnings = 
>> cppcheckaction.getResult().statistics.getNumberWarningSeverity()
>>println warnings
>>   }
>> }
>>   }
>> }
>> }
>> }
>> 
>> }
>> ```
>> which output is:
>> ```
>> [Pipeline] echo
>> 102
>> [Pipeline] echo
>> 4
>> ```
>> 
>> My logic (wrongly) tells me that if I can access to the report and 
>> statistics classes like that and uses their methods getNumberTotal() and 
>> getNumberWarningSeverity() respectively, therefore I should be able to also 
>> access the ```DiffState``` class in the same way and use the ```valueOf()``` 
>> method to get an enum of the new errors. But adding this to my pipeline:
>> ```
>> def nueva = cppcheckaction.getResult().diffState.valueOf(NEW)
>> println nueva
>> ```
>> Gives me an error:
>> ```
>> org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: No 
>> such field found: field org.jenkinsci.plugins.cppcheck.CppcheckBuildAction 
>> diffState
>> at 
>> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.unclassifiedField(SandboxInterceptor.java:425
>>  )
>> at 
>> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:409
>>  )
>> ...
>> ```
>> 
> 
>> -- 
>> 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/ca24b1f9-b0a8-4e81-8101-0b25f8267602n%40googlegroups.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/9c65acbc-f199-4d99-8d96-0b37a44a4f2an%40googlegroups.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/AB50-0B55-4A65-9095-CB657D802B4F%40gmail.com.

Re: how to access all classes and methods of a plugin in jenkins pipeline?

[Ullrich Hafner]

Due to security considerations only methods marked with @Whitelisted are 
accessible in Groovy scripts. Does your getter have such an annotation?

> Am 11.04.2021 um 19:02 schrieb jesus fernandez :
> 
> I am a junior dev trying to lear about Jenkins, I have been learning on my 
> own for a couple of months. Currently I have a pipeline (just for learning 
> purposes) which runs static analysis on a folder, and then publish it, I have 
> been able to send a report through email using jelly templates, from there I 
> realized it is posbile to instantiate the classes of a plugin to use its 
> methods so I went to the cppcheck javadoc here 
> https://javadoc.jenkins.io/plugin/cppcheck/ 
>  and did some trial and error so 
> I can get some values of my report and then do something else with them 
> something, so I had something like this in my pipeline:
> ```
> pipeline {
> agent any
> 
> stages {
>   stage('analysis') {
> steps {
>   script{
> bat'cppcheck "E:/My_project/Source/" --xml --xml-version=2 . 2> 
> cppcheck.xml'
>   }
>}
> }
> stage('Test'){
>   steps {
> script {
>   publishCppcheck pattern:'cppcheck.xml'
>   for (action in currentBuild.rawBuild.getActions()) {
> def name = action.getClass().getName()
> if (name == 'org.jenkinsci.plugins.cppcheck.CppcheckBuildAction') {
>def cppcheckaction = action
>def totalErrors = cppcheckaction.getResult().report.getNumberTotal()
>println totalErrors
>def warnings = 
> cppcheckaction.getResult().statistics.getNumberWarningSeverity()
>println warnings
>   }
> }
>   }
> }
> }
> }
> 
> }
> ```
> which output is:
> ```
> [Pipeline] echo
> 102
> [Pipeline] echo
> 4
> ```
> 
> My logic (wrongly) tells me that if I can access to the report and statistics 
> classes like that and uses their methods getNumberTotal() and 
> getNumberWarningSeverity() respectively, therefore I should be able to also 
> access the ```DiffState``` class in the same way and use the ```valueOf()``` 
> method to get an enum of the new errors. But adding this to my pipeline:
> ```
> def nueva = cppcheckaction.getResult().diffState.valueOf(NEW)
> println nueva
> ```
> Gives me an error:
> ```
> org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: No such 
> field found: field org.jenkinsci.plugins.cppcheck.CppcheckBuildAction 
> diffState
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.unclassifiedField(SandboxInterceptor.java:425
>  )
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:409
>  )
> ...
> ```
> 
> -- 
> 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/ca24b1f9-b0a8-4e81-8101-0b25f8267602n%40googlegroups.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/E399BE39-02DE-44AC-9851-7BC0CA0A9456%40gmail.com.

Re: is there a way to see all the available methods of a plugin in Jenkins?

[Ullrich Hafner]

> 
> 
> I actually have tried both to publish the result,

But the object model of both is different, you need to choose the correct one 
in the email template!

> have not decided which one to use yet, any suggestion?

I am biased as I am the author of the warnings plugin ;-)

> I like the dashboard of the warnings-ng better, but I ilke from the 
> publushcpp that you can see the line where the error is right from Jenkins 
> without need to open the editor and look for the line...

This could be done in the warnings plugin as well.
Example: 
https://ci.jenkins.io/job/Plugins/job/analysis-model/job/master/1150/pmd/source.6e8cd82c-d953-4e48-9163-87d374ee6241/#32
 



> El viernes, 9 de abril de 2021 a las 14:40:34 UTC+2, ullrich...@gmail.com 
> escribió:
> First of all: are you using the warnings-ng plugin or the cppcheck plugin in 
> your build? They use different models. 
> 
> I’m not sure if there is an easy way to debug email ext templates in the 
> meantime, I am not using it actively. 
> But you can simply start with a subset of the script below and check which 
> values produce a result and which not. 
> 
> 
>> Am 09.04.2021 um 14:32 schrieb jesus fernandez > >:
>> 
> 
>> my projects are in Perforce. What if I want to acces to one of those 
>> properties which I know are available from looking at the jelly template, 
>> for instance ${cppcheckResult.getDiff().getNumberNoCategorySeverity()} I 
>> tried to echo that property but I get an error how could I access to it?
>> this is the jelly template I am using (I took it from SO)
>> > xmlns:d="jelly:define">
>> 
>>   
>> > value="${it.getAction('org.jenkinsci.plugins.cppcheck.CppcheckBuildAction')}"
>>  />
>> 
>> > value="${cppcheckAction.getResult()}" />
>> 
>>   Summary
>> 
>> #cppcheckStatistics { width: auto; }
>> #cppcheckStatistics .number { text-align: right; }
>> 
>> 
>>   
>> 
>>   Severity
>>   Count
>>   Delta
>> 
>>   
>>   
>> 
>>   Error
>>   ${cppcheckResult.statistics.getNumberErrorSeverity()}
>>   ${cppcheckResult.getDiff().getNumberErrorSeverity()}
>> 
>> 
>>   Warning
>>   ${cppcheckResult.statistics.getNumberWarningSeverity()}
>>   ${cppcheckResult.getDiff().getNumberWarningSeverity()}
>> 
>> 
>>   Style
>>   ${cppcheckResult.statistics.getNumberStyleSeverity()}
>>   ${cppcheckResult.getDiff().getNumberStyleSeverity()}
>> 
>> 
>>   Performance
>>   ${cppcheckResult.statistics.getNumberPerformanceSeverity()}
>>   ${cppcheckResult.getDiff().getNumberPerformanceSeverity()}
>> 
>> 
>>   Portability
>>   ${cppcheckResult.statistics.getNumberPortabilitySeverity()}
>>   ${cppcheckResult.getDiff().getNumberPortabilitySeverity()}
>> 
>> 
>>   Information
>>   ${cppcheckResult.statistics.getNumberInformationSeverity()}
>>   ${cppcheckResult.getDiff().getNumberInformationSeverity()}
>> 
>> 
>>   No category
>>   ${cppcheckResult.statistics.getNumberNoCategorySeverity()}
>>   ${cppcheckResult.getDiff().getNumberNoCategorySeverity()}
>> 
>>   
>>   
>> 
>>   Total
>>   > href="${rooturl}${build.url}cppcheckResult">${cppcheckResult.report.getNumberTotal()}
>>   > href="${rooturl}${build.url}cppcheckResult/source.all/?before=5after=5states=new">${cppcheckResult.getDiff().getNumberTotal()}
>> 
>>   
>> 
>>   
>> 
>>  
>>  
>> 
>> 
>> El viernes, 9 de abril de 2021 a las 14:27:16 UTC+2, ullrich...@gmail.com 
>>  escribió:
>> Are your projects located in GitHub? Then it would be quite easy to report 
>> results automatically using the GitHub checks plugin. Email is quite 
>> old-school when it comes to build result reporting... 
>> 
>> 
>>> Am 09.04.2021 um 13:58 schrieb jesus fernandez >:
>>> 
>> 
>>> Thanks for asering. I have 

Re: is there a way to see all the available methods of a plugin in Jenkins?

[Ullrich Hafner]

First of all: are you using the warnings-ng plugin or the cppcheck plugin in 
your build? They use different models. 

I’m not sure if there is an easy way to debug email ext templates in the 
meantime, I am not using it actively. 
But you can simply start with a subset of the script below and check which 
values produce a result and which not. 

> Am 09.04.2021 um 14:32 schrieb jesus fernandez :
> 
> my projects are in Perforce. What if I want to acces to one of those 
> properties which I know are available from looking at the jelly template, for 
> instance ${cppcheckResult.getDiff().getNumberNoCategorySeverity()} I tried to 
> echo that property but I get an error how could I access to it?
> this is the jelly template I am using (I took it from SO)
> 
> 
>   
>  value="${it.getAction('org.jenkinsci.plugins.cppcheck.CppcheckBuildAction')}" 
> />
> 
>  />
> 
>   Summary
> 
> #cppcheckStatistics { width: auto; }
> #cppcheckStatistics .number { text-align: right; }
> 
> 
>   
> 
>   Severity
>   Count
>   Delta
> 
>   
>   
> 
>   Error
>   ${cppcheckResult.statistics.getNumberErrorSeverity()}
>   ${cppcheckResult.getDiff().getNumberErrorSeverity()}
> 
> 
>   Warning
>   ${cppcheckResult.statistics.getNumberWarningSeverity()}
>   ${cppcheckResult.getDiff().getNumberWarningSeverity()}
> 
> 
>   Style
>   ${cppcheckResult.statistics.getNumberStyleSeverity()}
>   ${cppcheckResult.getDiff().getNumberStyleSeverity()}
> 
> 
>   Performance
>   ${cppcheckResult.statistics.getNumberPerformanceSeverity()}
>   ${cppcheckResult.getDiff().getNumberPerformanceSeverity()}
> 
> 
>   Portability
>   ${cppcheckResult.statistics.getNumberPortabilitySeverity()}
>   ${cppcheckResult.getDiff().getNumberPortabilitySeverity()}
> 
> 
>   Information
>   ${cppcheckResult.statistics.getNumberInformationSeverity()}
>   ${cppcheckResult.getDiff().getNumberInformationSeverity()}
> 
> 
>   No category
>   ${cppcheckResult.statistics.getNumberNoCategorySeverity()}
>   ${cppcheckResult.getDiff().getNumberNoCategorySeverity()}
> 
>   
>   
> 
>   Total
>href="${rooturl}${build.url}cppcheckResult">${cppcheckResult.report.getNumberTotal()}
>href="${rooturl}${build.url}cppcheckResult/source.all/?before=5after=5states=new">${cppcheckResult.getDiff().getNumberTotal()}
> 
>   
> 
>   
> 
>  
>  
> 
> 
> El viernes, 9 de abril de 2021 a las 14:27:16 UTC+2, ullrich...@gmail.com 
> escribió:
> Are your projects located in GitHub? Then it would be quite easy to report 
> results automatically using the GitHub checks plugin. Email is quite 
> old-school when it comes to build result reporting... 
> 
> 
>> Am 09.04.2021 um 13:58 schrieb jesus fernandez > >:
>> 
> 
>> Thanks for asering. I have been checking the javadoc of the plugin 
>> https://javadoc.jenkins.io/plugin/email-ext/ 
>>  but my java knowledge is 
>> super basic and I do not get to see where the methods available to Jenkins 
>> are. So I guess this is too advanced for me ATM
>> 
>> El viernes, 9 de abril de 2021 a las 13:48:03 UTC+2, ullrich...@gmail.com 
>>  escribió:
>> You need to read the code of the plugin. I.e., the model of the producer 
>> plugin.
>> 
>> 
>> 
>>> Am 09.04.2021 um 13:08 schrieb jesus fernandez >:
>>> 
>> 
>>> I am learning Jenkins on my own and I am trying to learn about plugins. I 
>>> have a stage to send an email with the cppcheck results with a template I 
>>> found 
>>> https://stackoverflow.com/questions/13888338/sending-cppcheck-result-report-on-email-from-jenkins-using-email-ext-plugin
>>>  
>>> 
>>>  the template instantiate the ```CppcheckBuildAction``` and access its 
>>> 

Re: is there a way to see all the available methods of a plugin in Jenkins?

[Ullrich Hafner]

Are your projects located in GitHub? Then it would be quite easy to report 
results automatically using the GitHub checks plugin. Email is quite old-school 
when it comes to build result reporting... 

> Am 09.04.2021 um 13:58 schrieb jesus fernandez :
> 
> Thanks for asering. I have been checking the javadoc of the plugin 
> https://javadoc.jenkins.io/plugin/email-ext/ but my java knowledge is super 
> basic and I do not get to see where the methods available to Jenkins are. So 
> I guess this is too advanced for me ATM
> 
> El viernes, 9 de abril de 2021 a las 13:48:03 UTC+2, ullrich...@gmail.com 
> escribió:
> You need to read the code of the plugin. I.e., the model of the producer 
> plugin.
> 
> 
> 
>> Am 09.04.2021 um 13:08 schrieb jesus fernandez > >:
>> 
> 
>> I am learning Jenkins on my own and I am trying to learn about plugins. I 
>> have a stage to send an email with the cppcheck results with a template I 
>> found 
>> https://stackoverflow.com/questions/13888338/sending-cppcheck-result-report-on-email-from-jenkins-using-email-ext-plugin
>>  
>> 
>>  the template instantiate the ```CppcheckBuildAction``` and access its 
>> methods, what I would like to know if is possible to check what methods are 
>> avaialable for that instance and if possible how / where I can see them.
>> Also how could I for example echo / println one of them. For instance in the 
>> template provided in the link above it acces the total number of errors with 
>> ${cppcheckResult.report.getNumberTotal()} but if I echo it I get an error 
>> ```groovy.lang.MissingPropertyException: No such property: cppcheckResult 
>> for class: groovy.lang.Binding```, this is what I tried
>> stage('Email') {
>> steps {
>> script{
>> publishCppcheck pattern:'cppcheck.xml'
>> emailext( subject: 'foo', to: 'ma...@mail.net 
>> ', body: 
>> '${JELLY_SCRIPT, template="custom"}')
>> }
>> echo "${cppcheckResult.report.getNumberTotal()}"
>> }
>> }
>> my final goal actually is to send the email just when the report find a new 
>> error so I was thinking to save the total number of errors in an external 
>> file and compare it with each build and if the number is bigger send the 
>> email, is there any native / easier way to do 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-use...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/901e41a0-e2ec-466c-87a9-23d6082897e1n%40googlegroups.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/48090815-12d1-4f8a-a15b-2d0c0185b830n%40googlegroups.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/AFDA6FF8-B7DF-4DAA-A046-7E063DC41E53%40gmail.com.

Re: Can I send cppcheck results through slack in a jenkins pipeline?

[Ullrich Hafner]

https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#token-macro-support

> Am 09.04.2021 um 13:59 schrieb jesus fernandez :
> 
> Thanks for replying, any documentation or link to guide me in the right 
> direction on how to do it? I am quite Junior and have been learning Jenkins 
> on my own
> 
> El viernes, 9 de abril de 2021 a las 13:46:48 UTC+2, ullrich...@gmail.com 
> escribió:
> Exporting results from one plugin into another plugin is definitely possible. 
> You typically have two steps:
> 1) Export the data from a producer plugin
> a) using Tokens
> b) using API methods of the plugin
> 2) Import the data (or reformat and aggregate it) into a consumer plugin
> 
> For step 1 I can say this works for the warnings plugin, it can export the 
> results of CppCheck either into tokens or into objects (that you can process 
> using your pipeline). 
> 
> I have no idea if the slack plugin is capable of doing step 2 though, but I 
> would assume that it works in that way...
> 
> 
>> Am 09.04.2021 um 08:39 schrieb jesus fernandez > >:
>> 
> 
>> I just started using cppcheck, and I was wondering if there is any way to 
>> access to the report values (for instance number of total errors) and send 
>> it to slack. I have been searching in the documentation and here in SO but I 
>> have found nothing, as I just have been using Jenkins for a couple of months 
>> ( I am a junior dev) I was wondering if somebody know if this is possible 
>> and could drive me in the right direction.
>> 
> 
>> -- 
>> 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/d3aee90e-5331-480f-84d7-4df7c3ebcf6fn%40googlegroups.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/abdfdbec-e2cf-4f69-a089-1cb93dcef30en%40googlegroups.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/2AD3D6C2-F648-4CCC-8CB3-8672EB614ECA%40gmail.com.

Re: is there a way to see all the available methods of a plugin in Jenkins?

[Ullrich Hafner]

You need to read the code of the plugin. I.e., the model of the producer plugin.


> Am 09.04.2021 um 13:08 schrieb jesus fernandez :
> 
> I am learning Jenkins on my own and I am trying to learn about plugins. I 
> have a stage to send an email with the cppcheck results with a template I 
> found 
> https://stackoverflow.com/questions/13888338/sending-cppcheck-result-report-on-email-from-jenkins-using-email-ext-plugin
>  
> 
>  the template instantiate the ```CppcheckBuildAction``` and access its 
> methods, what I would like to know if is possible to check what methods are 
> avaialable for that instance and if possible how / where I can see them.
> Also how could I for example echo / println one of them. For instance in the 
> template provided in the link above it acces the total number of errors with 
> ${cppcheckResult.report.getNumberTotal()} but if I echo it I get an error 
> ```groovy.lang.MissingPropertyException: No such property: cppcheckResult for 
> class: groovy.lang.Binding```, this is what I tried
> stage('Email') {
> steps {
> script{
> publishCppcheck pattern:'cppcheck.xml'
> emailext( subject: 'foo', to: 'm...@mail.net', body: '${JELLY_SCRIPT, 
> template="custom"}')
> }
> echo "${cppcheckResult.report.getNumberTotal()}"
> }
> }
> my final goal actually is to send the email just when the report find a new 
> error so I was thinking to save the total number of errors in an external 
> file and compare it with each build and if the number is bigger send the 
> email, is there any native / easier way to do 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/901e41a0-e2ec-466c-87a9-23d6082897e1n%40googlegroups.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/DE30733C-EF0D-4D21-B61C-BC6137A2CDF4%40gmail.com.

Re: Can I send cppcheck results through slack in a jenkins pipeline?

[Ullrich Hafner]

Exporting results from one plugin into another plugin is definitely possible. 
You typically have two steps:
1) Export the data from a producer plugin
a) using Tokens
b) using API methods of the plugin
2) Import the data (or reformat and aggregate it) into a consumer plugin

For step 1 I can say this works for the warnings plugin, it can export the 
results of CppCheck either into tokens or into objects (that you can process 
using your pipeline). 

I have no idea if the slack plugin is capable of doing step 2 though, but I 
would assume that it works in that way...

> Am 09.04.2021 um 08:39 schrieb jesus fernandez :
> 
> I just started using cppcheck, and I was wondering if there is any way to 
> access to the report values (for instance number of total errors) and send it 
> to slack. I have been searching in the documentation and here in SO but I 
> have found nothing, as I just have been using Jenkins for a couple of months 
> ( I am a junior dev) I was wondering if somebody know if this is possible and 
> could drive me in the right direction.
> 
> -- 
> 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/d3aee90e-5331-480f-84d7-4df7c3ebcf6fn%40googlegroups.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/C816645C-24B7-4FEC-830F-7312BA7E6153%40gmail.com.

Re: How to publish cppcheck results in a pipeline?

[Ullrich Hafner]

I don’t know. Don’t you have a dedicated forum to ask cppcheck questions? 

I still do not understand why you are redirecting stdout or stderr. I would 
assume that every tool that creates XML files automatically creates the file in 
your workspace. Did you check the workspace if there is a file if you omit the 
redirect (>)?
 

> Am 26.03.2021 um 11:28 schrieb jesus fernandez :
> 
> Thanks for the replies but how woud the command be then? something like this 
> cppcheck "E:/Source" --force — enable=all — inconclusive — xml — 
> xml-version=2 . > cppcheck.xm
> 
> El jueves, 25 de marzo de 2021 a las 21:49:15 UTC+1, ullrich...@gmail.com 
> escribió:
> Yes, this is definitely not XML :-)
> This is the stderr of your program! 
> 
> 2 > cppcheck.xml pipes your stderr to a file. You do not need this part. 
> 
> 
>> Am 25.03.2021 um 20:08 schrieb jesus fernandez > >:
>> 
> 
>> so it seems like if it basically is writting all the outputs the cmd throws
>> 
>> El jueves, 25 de marzo de 2021 a las 20:07:20 UTC+1, jesus fernandez 
>> escribió:
>> the supposely .xml does not have any format, these are the first 5 lines:
>> Checking E:\Source\Game\AchievementManager.cpp ...
>> Checking E:\Source\Game\AchievementManager.cpp: 
>> APP_STEAM;FINAL_RELEASE;_DEBUG...
>> Checking E:\Source\Game\AchievementManager.cpp: 
>> APP_STEAM;NEED_AOE1DE_ACHIEVEMENT_TEST;_DEBUG...
>> Checking E:\Source\Game\AchievementManager.cpp: 
>> APP_STEAM;NEED_AOE3DE_ACHIEVEMENT_TEST;_DEBUG...
>> Checking E:\Source\Game\AchievementManager.cpp: APP_STEAM;_DEBUG...
>> 
>> El jueves, 25 de marzo de 2021 a las 19:47:22 UTC+1, ullrich...@gmail.com <> 
>> escribió:
>> If you can’t check on your own if the file contains valid XML can you please 
>> show the first 5 lines of the XML file here?
>> 
>> 
>>> Am 25.03.2021 um 19:36 schrieb jesus fernandez >:
>>> 
>> 
>>> I thought the  ```bat'cppcheck "E:/Source" --force — enable=all — 
>>> inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'``` command does 
>>> genearate a valid xml. is it a matter of missing parameters or a matter of 
>>> having to parse the output? in the documentation and the SO link I attached 
>>> it is supposed to be done like that... what am I missing here?
>>> 
>>> El jueves, 25 de marzo de 2021 a las 18:21:38 UTC+1, ullrich...@gmail.com 
>>>  escribió:
>>> The exception says it is not a valid XML file. Is it a valid XML file? 
>>> Seems that there is content before the fir XML tag. Can you open it in an 
>>> editor that can validate the XML?
>>> 
>>> 
 Am 25.03.2021 um 17:57 schrieb jesus fernandez >:
 
>>> 
 Thanks for replying, I have opened and it has 2000 lines of code but I do 
 not know if it is valid or not as I have never used cppcheck before, and 
 if it is not valid is it because I am not using the right parameters when 
 calling cppcheck or how?
 
 
 
 El jueves, 25 de marzo de 2021 a las 17:44:44 UTC+1, ullrich...@gmail.com 
  escribió:
 It look like your create XML is not valid. Can you please open the XML 
 file and check? 
 
 
> Am 25.03.2021 um 17:40 schrieb jesus fernandez  <>>:
> 
 
> I am learning about Jenkins on my own, and I wanted to try the cppcheck 
> plugin, I have setup the following sample pipeline:
> ```
> pipeline {
> agent any
> 
> stages {
> stage('analysis') {
> steps {
> script{
> bat'cppcheck "E:/Source" --force — enable=all — 
> inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'
> }
> }
> }
> }
> post {
> always {
> // scanForIssues tool: cppCheck(pattern: 'cppcheck.xml')
> publishCppcheck pattern:'cppcheck.xml'
> }
> }
> }
> ```
> 
> But I get an error in the post step which I do not know if it is related 
> to my projecto or if I am doing something wrong. I have follow the 
> instructions on this thread [cppcheck][1]but it does not seem to work, 
> wehther I use ```publushCppcheck``` :
> ```
> [Pipeline] { (Declarative: Post Actions)
> [Pipeline] publishCppcheck (hide)
> [Cppcheck] Starting the cppcheck analysis.
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
> [Cppcheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
>  - with linked exception:
> [org.xml.sax.SAXParseException; systemId: 
> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
> columnNumber: 1; El contenido no está permitido en el prólogo.]
> [Cppcheck] java.io.IOException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [org.xml.sax.SAXParseException; systemId: 
> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
> columnNumber: 1; El 

Re: How to publish cppcheck results in a pipeline?

[Ullrich Hafner]

Yes, this is definitely not XML :-)
This is the stderr of your program! 

2 > cppcheck.xml pipes your stderr to a file. You do not need this part. 

> Am 25.03.2021 um 20:08 schrieb jesus fernandez :
> 
> so it seems like if it basically is writting all the outputs the cmd throws
> 
> El jueves, 25 de marzo de 2021 a las 20:07:20 UTC+1, jesus fernandez escribió:
> the supposely .xml does not have any format, these are the first 5 lines:
> Checking E:\Source\Game\AchievementManager.cpp ...
> Checking E:\Source\Game\AchievementManager.cpp: 
> APP_STEAM;FINAL_RELEASE;_DEBUG...
> Checking E:\Source\Game\AchievementManager.cpp: 
> APP_STEAM;NEED_AOE1DE_ACHIEVEMENT_TEST;_DEBUG...
> Checking E:\Source\Game\AchievementManager.cpp: 
> APP_STEAM;NEED_AOE3DE_ACHIEVEMENT_TEST;_DEBUG...
> Checking E:\Source\Game\AchievementManager.cpp: APP_STEAM;_DEBUG...
> 
> El jueves, 25 de marzo de 2021 a las 19:47:22 UTC+1, ullrich...@gmail.com 
>  escribió:
> If you can’t check on your own if the file contains valid XML can you please 
> show the first 5 lines of the XML file here?
> 
> 
>> Am 25.03.2021 um 19:36 schrieb jesus fernandez >:
>> 
> 
>> I thought the  ```bat'cppcheck "E:/Source" --force — enable=all — 
>> inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'``` command does 
>> genearate a valid xml. is it a matter of missing parameters or a matter of 
>> having to parse the output? in the documentation and the SO link I attached 
>> it is supposed to be done like that... what am I missing here?
>> 
>> El jueves, 25 de marzo de 2021 a las 18:21:38 UTC+1, ullrich...@gmail.com 
>>  escribió:
>> The exception says it is not a valid XML file. Is it a valid XML file? Seems 
>> that there is content before the fir XML tag. Can you open it in an editor 
>> that can validate the XML?
>> 
>> 
>>> Am 25.03.2021 um 17:57 schrieb jesus fernandez >:
>>> 
>> 
>>> Thanks for replying, I have opened and it has 2000 lines of code but I do 
>>> not know if it is valid or not as I have never used cppcheck before, and if 
>>> it is not valid is it because I am not using the right parameters when 
>>> calling cppcheck or how?
>>> 
>>> 
>>> 
>>> El jueves, 25 de marzo de 2021 a las 17:44:44 UTC+1, ullrich...@gmail.com 
>>>  escribió:
>>> It look like your create XML is not valid. Can you please open the XML file 
>>> and check? 
>>> 
>>> 
 Am 25.03.2021 um 17:40 schrieb jesus fernandez >:
 
>>> 
 I am learning about Jenkins on my own, and I wanted to try the cppcheck 
 plugin, I have setup the following sample pipeline:
 ```
 pipeline {
 agent any
 
 stages {
 stage('analysis') {
 steps {
 script{
 bat'cppcheck "E:/Source" --force — enable=all — 
 inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'
 }
 }
 }
 }
 post {
 always {
 // scanForIssues tool: cppCheck(pattern: 'cppcheck.xml')
 publishCppcheck pattern:'cppcheck.xml'
 }
 }
 }
 ```
 
 But I get an error in the post step which I do not know if it is related 
 to my projecto or if I am doing something wrong. I have follow the 
 instructions on this thread [cppcheck][1]but it does not seem to work, 
 wehther I use ```publushCppcheck``` :
 ```
 [Pipeline] { (Declarative: Post Actions)
 [Pipeline] publishCppcheck (hide)
 [Cppcheck] Starting the cppcheck analysis.
 [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
 [Cppcheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
  - with linked exception:
 [org.xml.sax.SAXParseException; systemId: 
 file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
 columnNumber: 1; El contenido no está permitido en el prólogo.]
 [Cppcheck] java.io.IOException: javax.xml.bind.UnmarshalException
  - with linked exception:
 [org.xml.sax.SAXParseException; systemId: 
 file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
 columnNumber: 1; El contenido no está permitido en el prólogo.]
 at 
 org.jenkinsci.plugins.cppcheck.parser.CppcheckParser.parse(CppcheckParser.java:67)
 at 
 org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:69)
 at 
 org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:24)
 at hudson.FilePath.act(FilePath.java:1164)
 at hudson.FilePath.act(FilePath.java:1147)
 at 
 org.jenkinsci.plugins.cppcheck.CppcheckPublisher.perform(CppcheckPublisher.java:337)
 at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
 at 
 org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
 at 
 

Re: How to publish cppcheck results in a pipeline?

[Ullrich Hafner]

If you can’t check on your own if the file contains valid XML can you please 
show the first 5 lines of the XML file here?

> Am 25.03.2021 um 19:36 schrieb jesus fernandez :
> 
> I thought the  ```bat'cppcheck "E:/Source" --force — enable=all — 
> inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'``` command does 
> genearate a valid xml. is it a matter of missing parameters or a matter of 
> having to parse the output? in the documentation and the SO link I attached 
> it is supposed to be done like that... what am I missing here?
> 
> El jueves, 25 de marzo de 2021 a las 18:21:38 UTC+1, ullrich...@gmail.com 
> escribió:
> The exception says it is not a valid XML file. Is it a valid XML file? Seems 
> that there is content before the fir XML tag. Can you open it in an editor 
> that can validate the XML?
> 
> 
>> Am 25.03.2021 um 17:57 schrieb jesus fernandez > >:
>> 
> 
>> Thanks for replying, I have opened and it has 2000 lines of code but I do 
>> not know if it is valid or not as I have never used cppcheck before, and if 
>> it is not valid is it because I am not using the right parameters when 
>> calling cppcheck or how?
>> 
>> 
>> 
>> El jueves, 25 de marzo de 2021 a las 17:44:44 UTC+1, ullrich...@gmail.com 
>>  escribió:
>> It look like your create XML is not valid. Can you please open the XML file 
>> and check? 
>> 
>> 
>>> Am 25.03.2021 um 17:40 schrieb jesus fernandez >:
>>> 
>> 
>>> I am learning about Jenkins on my own, and I wanted to try the cppcheck 
>>> plugin, I have setup the following sample pipeline:
>>> ```
>>> pipeline {
>>> agent any
>>> 
>>> stages {
>>> stage('analysis') {
>>> steps {
>>> script{
>>> bat'cppcheck "E:/Source" --force — enable=all — 
>>> inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'
>>> }
>>> }
>>> }
>>> }
>>> post {
>>> always {
>>> // scanForIssues tool: cppCheck(pattern: 'cppcheck.xml')
>>> publishCppcheck pattern:'cppcheck.xml'
>>> }
>>> }
>>> }
>>> ```
>>> 
>>> But I get an error in the post step which I do not know if it is related to 
>>> my projecto or if I am doing something wrong. I have follow the 
>>> instructions on this thread [cppcheck][1]but it does not seem to work, 
>>> wehther I use ```publushCppcheck``` :
>>> ```
>>> [Pipeline] { (Declarative: Post Actions)
>>> [Pipeline] publishCppcheck (hide)
>>> [Cppcheck] Starting the cppcheck analysis.
>>> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
>>> [Cppcheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
>>>  - with linked exception:
>>> [org.xml.sax.SAXParseException; systemId: 
>>> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
>>> columnNumber: 1; El contenido no está permitido en el prólogo.]
>>> [Cppcheck] java.io.IOException: javax.xml.bind.UnmarshalException
>>>  - with linked exception:
>>> [org.xml.sax.SAXParseException; systemId: 
>>> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
>>> columnNumber: 1; El contenido no está permitido en el prólogo.]
>>> at 
>>> org.jenkinsci.plugins.cppcheck.parser.CppcheckParser.parse(CppcheckParser.java:67)
>>> at 
>>> org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:69)
>>> at 
>>> org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:24)
>>> at hudson.FilePath.act(FilePath.java:1164)
>>> at hudson.FilePath.act(FilePath.java:1147)
>>> at 
>>> org.jenkinsci.plugins.cppcheck.CppcheckPublisher.perform(CppcheckPublisher.java:337)
>>> at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
>>> at 
>>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
>>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>>> at java.util.concurrent.FutureTask.run(Unknown Source)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>> at java.lang.Thread.run(Unknown Source)
>>> Caused by: javax.xml.bind.UnmarshalException
>>> ```
>>> 
>>> or ```scanforIssues``` from warnings ng plugin::
>>> ```
>>> [Pipeline] { (Declarative: Post Actions)
>>> [Pipeline] scanForIssues
>>> [CPPCheck] [-ERROR-] Parsing of file 
>>> 'C:\Users\anton\.jenkins\workspace\JOB4\cppcheck.xml' failed due to an 
>>> exception:
>>> [CPPCheck] [-ERROR-] com.ctc.wstx.exc.WstxUnexpectedCharException: 
>>> Unexpected character 'C' (code 67) in prolog; expected '<'
>>>  at [row,col {unknown-source}]: [1,1]
>>> [CPPCheck] [-ERROR-]  at [row,col {unknown-source}]: [1,1]
>>> [CPPCheck] [-ERROR-]  at 

Re: How to publish cppcheck results in a pipeline?

[Ullrich Hafner]

The exception says it is not a valid XML file. Is it a valid XML file? Seems 
that there is content before the fir XML tag. Can you open it in an editor that 
can validate the XML?

> Am 25.03.2021 um 17:57 schrieb jesus fernandez :
> 
> Thanks for replying, I have opened and it has 2000 lines of code but I do not 
> know if it is valid or not as I have never used cppcheck before, and if it is 
> not valid is it because I am not using the right parameters when calling 
> cppcheck or how?
> 
> 
> 
> El jueves, 25 de marzo de 2021 a las 17:44:44 UTC+1, ullrich...@gmail.com 
> escribió:
> It look like your create XML is not valid. Can you please open the XML file 
> and check? 
> 
> 
>> Am 25.03.2021 um 17:40 schrieb jesus fernandez > >:
>> 
> 
>> I am learning about Jenkins on my own, and I wanted to try the cppcheck 
>> plugin, I have setup the following sample pipeline:
>> ```
>> pipeline {
>> agent any
>> 
>> stages {
>> stage('analysis') {
>> steps {
>> script{
>> bat'cppcheck "E:/Source" --force — enable=all — 
>> inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'
>> }
>> }
>> }
>> }
>> post {
>> always {
>> // scanForIssues tool: cppCheck(pattern: 'cppcheck.xml')
>> publishCppcheck pattern:'cppcheck.xml'
>> }
>> }
>> }
>> ```
>> 
>> But I get an error in the post step which I do not know if it is related to 
>> my projecto or if I am doing something wrong. I have follow the instructions 
>> on this thread [cppcheck][1]but it does not seem to work, wehther I use 
>> ```publushCppcheck``` :
>> ```
>> [Pipeline] { (Declarative: Post Actions)
>> [Pipeline] publishCppcheck (hide)
>> [Cppcheck] Starting the cppcheck analysis.
>> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
>> [Cppcheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
>>  - with linked exception:
>> [org.xml.sax.SAXParseException; systemId: 
>> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
>> columnNumber: 1; El contenido no está permitido en el prólogo.]
>> [Cppcheck] java.io.IOException: javax.xml.bind.UnmarshalException
>>  - with linked exception:
>> [org.xml.sax.SAXParseException; systemId: 
>> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
>> columnNumber: 1; El contenido no está permitido en el prólogo.]
>> at 
>> org.jenkinsci.plugins.cppcheck.parser.CppcheckParser.parse(CppcheckParser.java:67)
>> at 
>> org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:69)
>> at 
>> org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:24)
>> at hudson.FilePath.act(FilePath.java:1164)
>> at hudson.FilePath.act(FilePath.java:1147)
>> at 
>> org.jenkinsci.plugins.cppcheck.CppcheckPublisher.perform(CppcheckPublisher.java:337)
>> at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
>> at 
>> org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
>> at 
>> org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
>> at 
>> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>> at java.util.concurrent.FutureTask.run(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> at java.lang.Thread.run(Unknown Source)
>> Caused by: javax.xml.bind.UnmarshalException
>> ```
>> 
>> or ```scanforIssues``` from warnings ng plugin::
>> ```
>> [Pipeline] { (Declarative: Post Actions)
>> [Pipeline] scanForIssues
>> [CPPCheck] [-ERROR-] Parsing of file 
>> 'C:\Users\anton\.jenkins\workspace\JOB4\cppcheck.xml' failed due to an 
>> exception:
>> [CPPCheck] [-ERROR-] com.ctc.wstx.exc.WstxUnexpectedCharException: 
>> Unexpected character 'C' (code 67) in prolog; expected '<'
>>  at [row,col {unknown-source}]: [1,1]
>> [CPPCheck] [-ERROR-]  at [row,col {unknown-source}]: [1,1]
>> [CPPCheck] [-ERROR-]  at 
>> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
>> [CPPCheck] [-ERROR-]  at 
>> com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)
>> [CPPCheck] [-ERROR-]  at 
>> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
>> [CPPCheck] [-ERROR-]  at 
>> se.bjurr.violations.lib.parsers.CPPCheckParser.parseReportOutput(CPPCheckParser.java:43)
>> [CPPCheck] [-ERROR-]  at 
>> edu.hm.hafner.analysis.parser.violations.AbstractViolationAdapter.parse(AbstractViolationAdapter.java:35)
>> [CPPCheck] [-ERROR-]  at 
>> io.jenkins.plugins.analysis.core.model.FilesScanner.aggregateIssuesOfFile(FilesScanner.java:105)
>> [CPPCheck] [-ERROR-]  at 
>> 

Re: How to publish cppcheck results in a pipeline?

[Ullrich Hafner]

It look like your create XML is not valid. Can you please open the XML file and 
check? 

> Am 25.03.2021 um 17:40 schrieb jesus fernandez :
> 
> I am learning about Jenkins on my own, and I wanted to try the cppcheck 
> plugin, I have setup the following sample pipeline:
> ```
> pipeline {
> agent any
> 
> stages {
> stage('analysis') {
> steps {
> script{
> bat'cppcheck "E:/Source" --force — enable=all — 
> inconclusive — xml — xml-version=2 . 2 > cppcheck.xml'
> }
> }
> }
> }
> post {
> always {
> // scanForIssues tool: cppCheck(pattern: 'cppcheck.xml')
> publishCppcheck pattern:'cppcheck.xml'
> }
> }
> }
> ```
> 
> But I get an error in the post step which I do not know if it is related to 
> my projecto or if I am doing something wrong. I have follow the instructions 
> on this thread [cppcheck][1]but it does not seem to work, wehther I use 
> ```publushCppcheck``` :
> ```
> [Pipeline] { (Declarative: Post Actions)
> [Pipeline] publishCppcheck (hide)
> [Cppcheck] Starting the cppcheck analysis.
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
> [Cppcheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
>  - with linked exception:
> [org.xml.sax.SAXParseException; systemId: 
> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
> columnNumber: 1; El contenido no está permitido en el prólogo.]
> [Cppcheck] java.io.IOException: javax.xml.bind.UnmarshalException
>  - with linked exception:
> [org.xml.sax.SAXParseException; systemId: 
> file:/C:/Users/anton/.jenkins/workspace/JOB4/cppcheck.xml; lineNumber: 1; 
> columnNumber: 1; El contenido no está permitido en el prólogo.]
> at 
> org.jenkinsci.plugins.cppcheck.parser.CppcheckParser.parse(CppcheckParser.java:67)
> at 
> org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:69)
> at 
> org.jenkinsci.plugins.cppcheck.CppcheckParserResult.invoke(CppcheckParserResult.java:24)
> at hudson.FilePath.act(FilePath.java:1164)
> at hudson.FilePath.act(FilePath.java:1147)
> at 
> org.jenkinsci.plugins.cppcheck.CppcheckPublisher.perform(CppcheckPublisher.java:337)
> at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
> at 
> org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
> at 
> org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
> at 
> org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: javax.xml.bind.UnmarshalException
> ```
> 
> or ```scanforIssues``` from warnings ng plugin::
> ```
> [Pipeline] { (Declarative: Post Actions)
> [Pipeline] scanForIssues
> [CPPCheck] [-ERROR-] Parsing of file 
> 'C:\Users\anton\.jenkins\workspace\JOB4\cppcheck.xml' failed due to an 
> exception:
> [CPPCheck] [-ERROR-] com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected 
> character 'C' (code 67) in prolog; expected '<'
>  at [row,col {unknown-source}]: [1,1]
> [CPPCheck] [-ERROR-]  at [row,col {unknown-source}]: [1,1]
> [CPPCheck] [-ERROR-]  at 
> com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
> [CPPCheck] [-ERROR-]  at 
> com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047)
> [CPPCheck] [-ERROR-]  at 
> com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069)
> [CPPCheck] [-ERROR-]  at 
> se.bjurr.violations.lib.parsers.CPPCheckParser.parseReportOutput(CPPCheckParser.java:43)
> [CPPCheck] [-ERROR-]  at 
> edu.hm.hafner.analysis.parser.violations.AbstractViolationAdapter.parse(AbstractViolationAdapter.java:35)
> [CPPCheck] [-ERROR-]  at 
> io.jenkins.plugins.analysis.core.model.FilesScanner.aggregateIssuesOfFile(FilesScanner.java:105)
> [CPPCheck] [-ERROR-]  at 
> io.jenkins.plugins.analysis.core.model.FilesScanner.scanFiles(FilesScanner.java:89)
> [CPPCheck] [-ERROR-]  at 
> io.jenkins.plugins.analysis.core.model.FilesScanner.invoke(FilesScanner.java:72)
> [CPPCheck] [-ERROR-]  at 
> io.jenkins.plugins.analysis.core.model.FilesScanner.invoke(FilesScanner.java:30)
> [CPPCheck] [-ERROR-]  at hudson.FilePath.act(FilePath.java:1164)
> [CPPCheck] [-ERROR-]  at hudson.FilePath.act(FilePath.java:1147)
> [CPPCheck] [-ERROR-]  at 
> io.jenkins.plugins.analysis.core.model.ReportScanningTool.scanInWorkspace(ReportScanningTool.java:152)
> [CPPCheck] [-ERROR-]  at 
> io.jenkins.plugins.analysis.core.model.ReportScanningTool.scan(ReportScanningTool.java:134)
> [CPPCheck] [-ERROR-]  at 
> 

Re: Jenkins Plugins Versions and their compatible versions

[Ullrich Hafner]

You can have a look here:
https://github.com/jenkinsci/bom 


> Am 11.02.2021 um 15:52 schrieb Balu Balaji :
> 
> Hi All, 
> I am trying to find the Jenkins plugins list and their compatibility to the 
> Jenkins version 2.222.4 version. 
> 
> Could you please help me with the Jenkins 2.222.4 compatible below Plugins 
> versions?
> 
> LDAP
> ssh-agent
> apache-httpcomponents-client-4-api
> bouncycastle-api
> branch-api
> pipeline-model-declarative-agent
> pipeline-rest-api
> pipeline-stage-view
> token-macro
> variant
> workflow-basic-steps
> workflow-durable-task-step
> workflow-scm-step
> 
> For all the above plugins, what are the compatible versions with Jenkins 
> 2.222.4 version?
> For example, what is the branch-api plugin version which is compatible with 
> Jenkins 2.222.4 version? and so on.
> 
> 
> Thanks
> Balaji Sivaramagari
> 
> -- 
> 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/2bfb3baf-0f5a-44b0-996f-90a031b457f6n%40googlegroups.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/7F518375-2B08-4778-94CA-CDD95502A867%40gmail.com.

Re: How to set limits for Checkstyles, findsbugs and PMD

[Ullrich Hafner]

See quality gates:
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md
 



> Am 09.02.2021 um 19:06 schrieb Ashok reddy :
> 
> Hello Folks,
> 
> Below is the my pipeline script, How can I set the warnings limit for check 
> style warning 
> 
> stage('Build') {
> options {
> timeout(time: 30, unit: "MINUTES")
> }
> steps {
> 
> withMaven(maven: 'Maven-3.5.2') {
> 
> sh 'mvn clean install'
> }
> }
> }
> }
> post {
> always {
> 
> junit testResults: '**/target/surefire-reports/TEST-*.xml'
> recordIssues enabledForFailure: true, tool: checkStyle()
> recordIssues enabledForFailure: true, tool: spotBugs()
> recordIssues enabledForFailure: true, tool: pmdParser(pattern: 
> '**/target/pmd.xml')
> 
> jacoco(
> exclusionPattern: '**/*Test*.class',
> inclusionPattern: '**/*.class',
> sourceInclusionPattern: '**/*.java'
> )
> }
> 
> -- 
> 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/c349b6a4-f3bf-4464-a4bf-d84a6fc5b0f7n%40googlegroups.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/992E82E5-51E7-40D6-96B0-EAFB3F7EAEB7%40gmail.com.

Re: How to Hide findbug graphs

[Ullrich Hafner]

Which version of the warnings plugin are you using?
Since https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/v8.8.0 
 empty 
trend charts are hidden.

You can also hide the charts using the property `trendChartType`.
See 
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#build-trend
 



> Am 09.02.2021 um 18:48 schrieb Ashok reddy :
> 
> multiple empty findbug trend graphs are creating How to hide them from 
> summery? 
> 
> 
> On Tuesday, February 9, 2021 at 10:48:07 PM UTC+5:30 Ashok reddy wrote:
> Hello Team
> 
> I am working on maven pipeline project, below is the pipeline script. I am 
> getting multiple find bug graphs How to Hide them 
> 
> stage('Build') {
> options {
> timeout(time: 30, unit: "MINUTES")
> }
> steps {
> 
> withMaven(maven: 'Maven-3.5.2') {
> 
> sh 'mvn clean install'
> }
> }
> }
> }
> post {
> always {
> 
> junit testResults: '**/target/surefire-reports/TEST-*.xml'
> recordIssues enabledForFailure: true, tool: checkStyle()
> recordIssues enabledForFailure: true, tool: spotBugs()
> recordIssues enabledForFailure: true, tool: pmdParser(pattern: 
> '**/target/pmd.xml')
> 
> jacoco(
> exclusionPattern: '**/*Test*.class',
> inclusionPattern: '**/*.class',
> sourceInclusionPattern: '**/*.java'
> )
> }
> 
> 
> 
> 
> 
> 
> -- 
> 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/40a80df4-3c39-47ac-a30f-d1d6f5c153fan%40googlegroups.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/D666FB7A-F1C1-44B1-BDFD-9B2386E98750%40gmail.com.

Re: Unable to list Warnings Next Generation plugin

[Ullrich Hafner]

I added the new plugin as a dependency to the deprecated warnings plugin so 
users automatically have the new plugin installed.

> Am 20.09.2020 um 06:41 schrieb Praveen Kumar K S :
> 
> Hello,
> 
> Today I have upgraded Jenkins to 2.249.1. After the upgrade, Jenkins 
> suggested removing deprecated plugins. I visited the plugins home page and 
> got to know that All functionality has been integrated into the Warnings Next 
> Generation Plugin  and the 
> Static Analysis Model and Parsers Library 
> .
> So I have uninstalled those deprecated plugins, restarted Jenkins and tried 
> to install Warnings Next Generation Plugin 
>  and the Static Analysis 
> Model and Parsers Library .
> But those are not getting listed under Available plugins. Please help.
> 
> -- 
> Regards,
> 
> K S Praveen Kumar
> 
> 
> -- 
> 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/CANSiNp5P2ax%2B_JfaFuxPuLFaKyagYesXQNVm%3DadLvsGsACmJdQ%40mail.gmail.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/429B0EC8-E528-42D9-AC3C-23A7A471EB4E%40gmail.com.

Re: Vulnerability in JQuery on Jenkins

[Ullrich Hafner]

You cannot update this specific version. There are still some plugins (and 
maybe some old core scripts as well) that use jQuery 1, so we cannot remove 
that dependency. If a new plugin wants to use jQuery then there is an 
additional plugin available: https://github.com/jenkinsci/jquery3-api-plugin 


> Am 26.08.2020 um 16:38 schrieb eric@gmail.com :
> 
> Hi All,
> 
> Just got gigged by our security team for a vulnerability in Jenkins with the 
> version of JQuery installed.  How do I go about updating the version of 
> JQuery Jenkins runs?  Here's the specifics of the vulnerability:
> 
> Plugin Output: 
>   URL   : http://myMachine:8081/js/jquery-1.11.1.min.js
>   Installed version : 1.11.1
>   Fixed version : 3.5.0
> 
> I'm running version 2.235.5 of Jenkins.
> 
> Thanks,
> Eric
> 
> -- 
> 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/13c921b1-02f4-4f00-a474-266fe766ced0n%40googlegroups.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/C41FF017-77FB-4726-93B4-264011284A0E%40gmail.com.

Re: Available plugins are hidden

[Ullrich Hafner]

> Am 30.06.2020 um 22:33 schrieb BarraS :
> 
> I find it somewhat unintuitive, but I guess I should have read the manual.

Well, you never should be required to read a manual to understand on how to use 
the search field :-) I also think this is not intuitive, it also has been 
discussed in the PR but as far as I remember it will be addressed some time in 
the future when we hopefully improve the UI experience of tables in Jenkins. 
Maybe it would be a good thing if you bring up this topic in the UX Gitter 
channel: https://gitter.im/jenkinsci/ux-sig 


-- 
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/84D4B4D1-6B21-4C58-9964-558BBC8B3470%40gmail.com.

Re: NoSuchMethodError in BFA-plugin

[Ullrich Hafner]

In my workspace 1.0.19 version of jfreechart is used. Seems that the plugin 
uses a method that is not there anymore because of an outdated library 
reference.
Please file a bug report for the plugin in Jira.

 

> Am 16.06.2020 um 09:14 schrieb Torsten Reinhard :
> 
> Hi, 
> 
> I´m running Jenkins 2.204.5 and the Build-failure-analyzer plugin 1.26.0
> 
> When hitting 
> https://mycompany/jenkins/failure-cause-management/detailedgraphs 
>  I see 
> some empty graphs (missing img) which probably is caused by exceptions like 
> the below:
> 
> Error while serving 
> https://mycompany/jenkins/failure-cause-management/graph/png
> java.lang.NoSuchMethodError: 
> org.jfree.data.time.TimeTableXYDataset.add(Lorg/jfree/data/time/TimePeriod;DLjava/lang/String;)V
> at 
> com.sonyericsson.jenkins.plugins.bfa.graphs.TimeSeriesUnkownFailuresChart.createDataset(TimeSeriesUnkownFailuresChart.java:106)
> at 
> com.sonyericsson.jenkins.plugins.bfa.graphs.TimeSeriesUnkownFailuresChart.createGraph(TimeSeriesUnkownFailuresChart.java:73)
> at hudson.util.Graph.render(Graph.java:93)
> at hudson.util.Graph.doPng(Graph.java:120)
> at 
> java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
> at 
> org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
> Caused: java.lang.reflect.InvocationTargetException
> at 
> org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400)
> at 
> org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
> at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
> at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)
> at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:249)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)
> at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623)
> at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)
> at org.jenkinsci.plugins.RefreshFilter.doFilter(RefreshFilter.java:96)
> at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
> at 
> jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76)
> at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
> at 
> net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:239)
> at 
> net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:215)
> at 
> net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88)
> at 
> org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114)
> at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
> at 
> jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128)
> at 
> hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
> at 
> hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
> at 
> hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118)
> at 
> 

Re: Warnings Next Generation Plugin: git rev-parse HEAD^{commit} takes a (too) long time

[Ullrich Hafner]

You can disable that part, see 
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#source-code-blames-for-git-projects
 



> Am 04.06.2020 um 08:31 schrieb Amedee Van Gasse :
> 
> Warnings Next Generation Plugin provides a build step `recordIssues`.
> 
> I found that it hangs for several minutes on
> 
> /usr/bin/git rev-parse HEAD^{commit}
> 
> Before I knew which Jenkins plugin was responsible, I asked on Stack Overflow 
> 10 days ago, but of course didn't get (nor expect) a useful answer.
> 
> https://stackoverflow.com/questions/61973411/jenkins-pipeline-during-recordissues-for-checkstyle-pmd-spotbugs-git-rev-pars
>  
> 
> 
> This is the relevant part of the Jenkinsfile:
> 
> stage('Static Code Analysis') {
> options {
> timeout(time: 1, unit: 'HOURS')
> }
> steps {
> withMaven(jdk: "${JDK_VERSION}", maven: 'M3', mavenLocalRepo: 
> '.repository') {
> sh 'mvn --no-transfer-progress verify --activate-profiles qa 
> -Dpmd.analysisCache=true'
> }
> recordIssues(tools: [
> checkStyle(),
> pmdParser(),
> spotBugs(useRankAsPriority: true)
> ])
> dependencyCheckPublisher pattern: 'target/dependency-check-report.xml'
> }
> }
> This is an excerpt from the Jenkins console log:
> 
> 00:10:26.471  [CheckStyle] Successfully parsed file 
> /home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop/target/checkstyle-result.xml
> 00:10:26.471  [CheckStyle] -> found 0 issues (skipped 0 duplicates)
> 00:10:26.847  using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:27.322  using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:26.896   > /usr/bin/git rev-parse HEAD^{commit} # timeout=10
> 00:10:27.699  using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:28.173  using credential bd100583-6d56-496a-89c0-67e640c2f80e
> 00:10:27.748   > /usr/bin/git rev-parse HEAD^{commit} # timeout=10
> 00:12:10.218   > /usr/bin/git rev-parse HEAD^{commit} # timeout=10
> 00:25:35.352  [CheckStyle] Post processing issues on 'jenkins-node-aws' with 
> source code encoding 'UTF-8'
> 00:25:35.352  [CheckStyle] Creating SCM blamer to obtain author and commit 
> information for affected files
> 00:25:35.352  [CheckStyle] -> Git blamer successfully created in working tree 
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352  [CheckStyle] Creating SCM miner to obtain statistics for 
> affected repository files
> 00:25:35.352  [CheckStyle] -> Git miner successfully created in working tree 
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352  [CheckStyle] Resolving file names for all issues in source 
> directory '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352  [CheckStyle] -> resolved paths in source directory (1238 found, 
> 0 not found)
> 00:25:35.352  [CheckStyle] Resolving module names from module definitions 
> (build.xml, pom.xml, or Manifest.mf files)
> 00:25:35.352  [CheckStyle] -> resolved module names for 85004 issues
> 00:25:35.352  [CheckStyle] Resolving package names (or namespaces) by parsing 
> the affected files
> 00:25:35.352  [CheckStyle] -> resolved package names of 1238 affected files
> 00:25:35.352  [CheckStyle] No filter has been set, publishing all 85004 issues
> 00:25:35.352  [CheckStyle] Creating fingerprints for all affected code blocks 
> to track issues over different builds
> 00:25:35.352  [CheckStyle] -> created fingerprints for 85004 issues (skipped 
> 0 issues)
> 00:25:35.352  [CheckStyle] Invoking Git blamer to create author and commit 
> information for 1238 affected files
> 00:25:35.352  [CheckStyle] GIT_COMMIT env = 'HEAD'
> 00:25:35.352  [CheckStyle] Git commit ID = 
> '62d4a2abfda51f58acac8f4ce8e799dffcdbfb0a'
> 00:25:35.352  [CheckStyle] Git working tree = 
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352  [CheckStyle] -> blamed authors of issues in 1238 files
> 00:25:35.352  [CheckStyle] Blaming of authors took 498 seconds
> 00:25:35.352  [CheckStyle] Analyzing the commit log of the Git repository 
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352  [CheckStyle] Invoking Git miner to create statistics for all 
> available files
> 00:25:35.352  [CheckStyle] Git working tree = 
> '/home/ubuntu/jenkins/workspace/iText_7_Java_itextcore_develop'
> 00:25:35.352  [CheckStyle] -> created statistics for 1238 files
> 00:25:35.352  [CheckStyle] -> created report for 1238 files in 69 seconds
> 00:25:35.352  [CheckStyle] Copying affected files to Jenkins' build folder 
> 

Re: CppCheck(XML parsing) with Warning-Next-Generation plugins

[Ullrich Hafner]

> Am 03.04.2020 um 09:07 schrieb 'Christoph Fetzer' via Jenkins Users 
> :
> 
> For me that looks like an issue of your shell command and not of the plugin. 

Exactly!

> [CPPCheck] Skipping execution of recorder since overall result is 'FAILURE'
> Finished: FAILURE
> 

The log indicates that my plugin does not even run since the build already 
failed. (You can change that behavior but I think it makes more sense to 
correct your build.) 

If you want to test the plugin I can recommend the plugin 
https://github.com/jenkinsci/file-operations-plugin 
<https://github.com/jenkinsci/file-operations-plugin>
I’m using that in my testing courses to create manual integration tests that 
use fake input files for my warning plugin.
With this plugin you can create an example file for cppcheck in the workspace.

> 
> On Thu, Apr 2, 2020 at 8:19 PM Ullrich Hafner gmail.com 
> <http://gmail.com/>> wrote:
> 
> 
>> Am 02.04.2020 um 13:06 schrieb Hakan Rafik gmail.com 
>> <http://gmail.com/>>:
>> 
>> I'm using the next generation plugins to represent the CppCheck warnings and 
>> errors. 
>> But the plugins is not parsing Carriage return:  or Line feed: . 
>> I've tried to feed the plugins with the given example 
>> (https://github.com/jenkinsci/warnings-ng-plugin/blob/master/plugin/src/test/resources/io/jenkins/plugins/analysis/warnings/cppcheck.xml
>>  
>> <https://github.com/jenkinsci/warnings-ng-plugin/blob/master/plugin/src/test/resources/io/jenkins/plugins/analysis/warnings/cppcheck.xml>)
>>  generates error and didn't produces any formatted string.
>> 
>> Any help in this regards is highly appreciated. 
>> 
> 
> When you don’t show error messages or log messages we cannot help. Just 
> writing that it does not work is not enough information.
> 
>> Regards,
>> 
>> 
>> -- 
>> 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 jenkins...@ <>googlegroups.com <http://googlegroups.com/>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/4ef79c27-73bf-4062-a240-65f9b38f9341%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/4ef79c27-73bf-4062-a240-65f9b38f9341%40googlegroups.com?utm_medium=email_source=footer>.
> 
> 
> -- 
> 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 jenkins...@ <>googlegroups.com <http://googlegroups.com/>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/0A40A6D1-60D0-477B-B000-430235D6808E%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/0A40A6D1-60D0-477B-B000-430235D6808E%40gmail.com?utm_medium=email_source=footer>.
> 
> -- 
> 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 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/a976054d-bd91-4643-96fe-927270bf5019%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/a976054d-bd91-4643-96fe-927270bf5019%40googlegroups.com?utm_medium=email_source=footer>.

-- 
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/E593C47E-EAF9-40A2-9E7D-11B2D4BA7F9A%40gmail.com.

Re: CppCheck(XML parsing) with Warning-Next-Generation plugins

[Ullrich Hafner]

> Am 02.04.2020 um 13:06 schrieb Hakan Rafik :
> 
> I'm using the next generation plugins to represent the CppCheck warnings and 
> errors. 
> But the plugins is not parsing Carriage return:  or Line feed: . 
> I've tried to feed the plugins with the given example 
> (https://github.com/jenkinsci/warnings-ng-plugin/blob/master/plugin/src/test/resources/io/jenkins/plugins/analysis/warnings/cppcheck.xml)
>  generates error and didn't produces any formatted string.
> 
> Any help in this regards is highly appreciated. 
> 

When you don’t show error messages or log messages we cannot help. Just writing 
that it does not work is not enough information.

> Regards,
> 
> 
> -- 
> 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/4ef79c27-73bf-4062-a240-65f9b38f9341%40googlegroups.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/0A40A6D1-60D0-477B-B000-430235D6808E%40gmail.com.

Re: Coverage API: jacoco instead of jacocoAdapter

[Ullrich Hafner]

It simply means that you can use the symboled `jacoco` in your pipeline if you 
do not have the jacoco-plugin installed. Otherwise you need to use the name 
`jacocoAdapter` (both symbols refer to the same thing). Since the jacoco plugin 
also provides a step with the symbol `jacoco` your pipeline will have a syntax 
error (name clash) because you use a symbol that is located in multiple 
plugins. To be on the save side: always use jacocoAdapter.

> Am 06.03.2020 um 09:52 schrieb Sverre Moe :
> 
> Publish Coverage from JaCoCo using the new Coverage API:
> https://jenkins.io/blog/2018/08/17/code-coverage-api-plugin-1/
> 
> It makes a statement in this blog:
> publishCoverage adapters: [jacocoAdapter('target/site/jacoco/jacoco.xml')]
> You can also use jacoco instead of jacocoAdapter if you didn't install 
> Jacoco-Plugin.
> 
> What does this mean? That I could use the jacoco pipeline within 
> publishCoverage:
> jacoco classPattern: 'build/classes', execPattern: 'build/jacoco/*.exec'
> 
> In order to use the JaCoCo Adapter, I would need to run jacoco to generate 
> the test report as part of my build with Gradle.
> ./gradlew jacocoTestReport
> 
> Then use the output from it in publishCoverage:
> publishCoverage adapters: 
> [jacocoAdapter('build/reports/jacoco/test/jacocoTestReport.xml')]
> 
> But if the implication of the statement made in the blog is what I think it 
> means, I would not need to run jacocoTestReport.
> However the Snippet generator does not allow for it, so I am not sure.
> 
> 
> 
> -- 
> 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/67662343-72e7-4c65-9e51-833bab959a71%40googlegroups.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/6D414CE2-C5CB-45E5-8AA0-0E70BDED356B%40gmail.com.

Re: How to report a affected Jehnkins/polugin version for an already existing JIRA ticket

[Ullrich Hafner]

> What I don't understand:How do I correctly report: "I've found this existing 
> issue in this not yet mentioned Jenkins (plugin, ...) version"
> Do I just add a comment to an existing ticket referring to the version 
> affected too ?

Yes, that would make sense. 

> I've checked https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue, 
> but can't see this issue addressed and unfortunately can't comment there any 
> longer.
> 
> My intentions here are:
> I would like to report the issue for this version
> I would like to see, if this issue got addressed for this line (e.g. LTS here)
> AFAIK, the issue is currently not addressed in the successor 2.204.4
> If I report a blocker to https://jenkins.io/changelog-stable/, I get asked 
> for a JIRA ticket
Since we are migrating our wiki to GitHub and so to our web page we need to 
migrate this topic as well. We would appreciate it if you are interested in 
helping us with this tremendous task. E.g. here is an example pull request:
https://github.com/jenkins-infra/jenkins.io/pull/2642 
. I think the report an 
issue document can be supported in a similar way...


> Regards
> 
> Martin
> 
> 
> -- 
> 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/f155270c-319e-4808-84b8-4857cdcd60da%40googlegroups.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/17783C9F-CBF7-4849-96F9-71DBA63F2034%40gmail.com.

Re: Jenkins 2.204.3 -> java.lang.IllegalStateException: Form is larger than max length 200000

[Ullrich Hafner]

2.204.4 is on its way, see 
https://groups.google.com/d/msg/jenkinsci-dev/M_RtDuDXtbU/AZTw8LtvHAAJ 



> Am 03.03.2020 um 11:10 schrieb Martin Jost :
> 
> Hello,
> 
> I'm getting - on trying to [Save] a change to a view configuration:
> java.lang.IllegalStateException: Form is larger than max length 20
>   at 
> org.eclipse.jetty.server.Request.extractFormParameters(Request.java:562)
>   at 
> org.eclipse.jetty.server.Request.extractContentParameters(Request.java:519)
>   at org.eclipse.jetty.server.Request.getParameters(Request.java:430)
> Caused: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form 
> content
>   at org.eclipse.jetty.server.Request.getParameters(Request.java:434)
>   at org.eclipse.jetty.server.Request.getParameter(Request.java:1059)
>   at 
> javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:194)
>   at 
> javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:194)
>   at org.kohsuke.stapler.RequestImpl.getParameter(RequestImpl.java:174)
>   at 
> org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:1002)
>   at 
> hudson.plugins.sectioned_view.SectionedView.submit(SectionedView.java:153)
>   at hudson.model.View.doConfigSubmit(View.java:1004)
>   at 
> java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
>   at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
>   at 
> org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
>   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
>   at 
> org.kohsuke.stapler.SelectionInterceptedFunction$Adapter.invoke(SelectionInterceptedFunction.java:36)
>   at 
> org.kohsuke.stapler.verb.HttpVerbInterceptor.invoke(HttpVerbInterceptor.java:48)
>   at 
> org.kohsuke.stapler.SelectionInterceptedFunction.bindAndInvoke(SelectionInterceptedFunction.java:26)
>   at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
>   at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)
>   at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
>   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
> [Full stack trace below]
> 
> This seems to happen, since the update to 2.204.3.
> 
> IIRC we've had that at some time in the past, where there was a WA by handing 
> some option to Jenkins start to increase the size.
> Does someone have me a pointer to that ?
> I'll open a bug report on that one.
> 
> Thanks
> 
> Martin
> 
> Full stack trace:
> Stack trace
> 
> java.lang.IllegalStateException: Form is larger than max length 20 at 
> org.eclipse.jetty.server.Request.extractFormParameters(Request.java:562) at 
> org.eclipse.jetty.server.Request.extractContentParameters(Request.java:519) 
> at org.eclipse.jetty.server.Request.getParameters(Request.java:430) Caused: 
> org.eclipse.jetty.http.BadMessageException: 400: Unable to parse form content 
> at org.eclipse.jetty.server.Request.getParameters(Request.java:434) at 
> org.eclipse.jetty.server.Request.getParameter(Request.java:1059) at 
> javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:194)
>  at 
> javax.servlet.ServletRequestWrapper.getParameter(ServletRequestWrapper.java:194)
>  at org.kohsuke.stapler.RequestImpl.getParameter(RequestImpl.java:174) at 
> org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:1002) at 
> hudson.plugins.sectioned_view.SectionedView.submit(SectionedView.java:153) at 
> hudson.model.View.doConfigSubmit(View.java:1004) at 
> java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at 
> org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at 
> org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at 
> org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at 
> org.kohsuke.stapler.SelectionInterceptedFunction$Adapter.invoke(SelectionInterceptedFunction.java:36)
>  at 
> org.kohsuke.stapler.verb.HttpVerbInterceptor.invoke(HttpVerbInterceptor.java:48)
>  at 
> org.kohsuke.stapler.SelectionInterceptedFunction.bindAndInvoke(SelectionInterceptedFunction.java:26)
>  at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) 
> at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: 
> javax.servlet.ServletException at 
> org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at 
> org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at 
> org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) 
> at 

Re: how to parse the console log of jenkins pipeline using groovy and search for a string and get the line which contains the string

[Ullrich Hafner]

https://github.com/jenkinsci/warnings-ng-plugin

> Am 27.02.2020 um 07:35 schrieb Aditya Varma :
> 
> Can you please help me with this -- > how to parse the console log of jenkins 
> pipeline using groovy and search for a string and get the line which contains 
> the string
> 
> -- 
> 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/3cab5a17-cd05-4886-8330-bead4f8b070f%40googlegroups.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/87215AF1-00E9-46B9-8A3B-B25C526B04F6%40gmail.com.

Re: Client side validation in Jenkins Plugin using jelly

[Ullrich Hafner]

Did you look into the https://plugins.jenkins.io/ui-samples-plugin? 
 There are a lot of Jenkins UI 
elements explained there...

> Am 16.01.2020 um 11:51 schrieb vinita sanghi :
> 
> I am using jelly controls for UI design in my Jenkins plugin. I need to 
> enable a textbox based on radio button selection. Cannot use radio blocks 
> here . Is this requirement achievable ?
> 
> -- 
> 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/ae71dde2-164f-487a-a7ee-0b8f2c4ff075%40googlegroups.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/DAB75EDD-EB79-412B-A4A8-A041CE8C6901%40gmail.com.

Re: Inject Test issue while plugin genration

[Ullrich Hafner]

The messages already tells you what to do:

>  is missing in 
> file:/Users/selva-5820/plugin/sprints-jenkins-plugin/target/classes/io/jenkins/plugins/jenkinswork/buildstepaction/FeedStatus/config.jelly

Using a web search engine will lead to the following page:
https://wiki.jenkins.io/display/JENKINS/Jelly+and+XSS+prevention 


> Am 12.12.2019 um 08:40 schrieb selva vignesh :
> 
> Hi Team,
> I've developed plugin for my team. While generating the hpi file using mvn 
> clean package. I am getting below error. Kindly assist me get rid of this 
> issue.
> [ERROR] Tests run: 165, Failures: 100, Errors: 0, Skipped: 0, Time elapsed: 
> 17.734 s <<< FAILURE! - in InjectedTest
> [ERROR] 
> io/jenkins/plugins/jenkinswork/buildstepaction/FeedStatus/config.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck)
>   Time elapsed: 0.184 s  <<< FAILURE!
> java.lang.AssertionError:  is missing in 
> file:/Users/selva-5820/plugin/sprints-jenkins-plugin/target/classes/io/jenkins/plugins/jenkinswork/buildstepaction/FeedStatus/config.jelly
> 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 jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/b5bc7ce8-54b2-4b1a-8954-ccbf975b8802%40googlegroups.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/2E405E59-7E4C-483A-8F31-7ABC0BF97776%40gmail.com.

Re: How to enable "recordIssues tool: pyLint"

[Ullrich Hafner]

You need to install the warnings-ng plugin: 
https://github.com/jenkinsci/warnings-ng-plugin 


For more details please ask in our Gitter channel: 
https://gitter.im/jenkinsci/warnings-plugin 


> Am 24.10.2019 um 10:31 schrieb tOmMy Lau :
> 
> Hi,
> I'm a new fish on Jenkins, I saw one of this pipeline code
> recordIssues tool: pyLint(pattern: '.test_reports/pylint.out'), 
> enabledForFailure: true
> 
> I found it's interesting and added into my Jenkinsfile, however, when my job 
> runs at this line, it throws error as below:
> java.lang.NoSuchMethodError: No such DSL method 'pyLint' found among steps
> ..
> 
> 
> So, my question is: is there any plugins need to be installed? I searched 
> plugins but not find pyLint plugin.
> 
> Thanks.
> tOmMy
> 
> -- 
> 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/c3a1504d-f597-4037-a3e9-bd9539acabc2%40googlegroups.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/6D7DDF7D-79D6-40E6-91E8-64A59579DA6E%40gmail.com.

Re: JUnit Results not parsing in Jenkinsfile-based Pipeline Build

[Ullrich Hafner]

Shoudn’t the command use ’testResults’ as parameter name?

junit testResults: '**/build/pytest.xml'


> Am 18.08.2019 um 06:42 schrieb Matt Hollingsworth :
> 
> Hi everyone,
> 
> I ran into a weird issue that I thought you might be able to help 
> troubleshoot. I'm using Jenkinsfile-based Pipelines with python, and I use 
> pytest to produce JUnit-compatible reports after the tests are run. The 
> problem is that I get an error when I try to parse the results with the junit 
> step: "No test report files were found. Configuration error?" Here are the 
> relevant parts of the Jenkinsfile:
> 
> stage("Unit tests") {
>   steps {
> sh "runtests.sh" // This produces build/pytest.xml
> sh "cat build/pytest.xml"
> junit 'build/pytest.xml'
>   }
> }
> 
> The sh’s cat command runs properly and prints out a properly formatted junit 
> xml file--I can parse it with junit-viewer, for example. But I still get the 
> error. Any idea what's going on, or how I could debug this properly?
> 
> Thanks for the help!
> 
> Best,
> Matt
> 
> -- 
> 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/8e1eae66-4c8b-4de0-9d9e-e0474a7ab93c%40googlegroups.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/D0E7E558-57F6-4B92-8724-3D7156A5EA96%40gmail.com.

Re: Programmatically searching the artifacts from multiple jobs

[Ullrich Hafner]

Or you can use the https://wiki.jenkins.io/display/JENKINS/Text-finder+Plugin 
 
It provides already a way to grep files for a pattern and set the build status 
accordingly.

> Am 12.08.2019 um 06:49 schrieb 'Björn Pedersen' via Jenkins Users 
> :
> 
> Hi, 
> 
> I think the best solution would be to use warnings-ng  and set up  suitable 
> custom parser (I assume that none of the many available parsers fit your 
> use-case). Possibly in combination with the Build Failure Analyzer plugin 
> your jobs will show the correct status and where the errors happed.
> 
> Björn
> 
> -- 
> 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/ccdab323-3894-4635-a06f-5f7a74c3b3ec%40googlegroups.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/3F83F7A5-5C3D-4786-8770-83B26B85DEC8%40gmail.com.

Re: Updates to the Blue Ocean plugin and a new Pipeline sub-project

[Ullrich Hafner]

> Am 17.06.2019 um 13:17 schrieb Jeremy Hartley :
> 
> Hello fellow Jenkins users and developers,
> 
> I am a product manager at CloudBees and have taken over responsibility for 
> the Jenkins Blue Ocean sub-project. Over the last year, the teams working on 
> Jenkins at CloudBees have looked at the initiative of overhauling the Jenkins 
> user experience. This analysis led us to conclude that Blue Ocean is a great 
> way to work with Jenkins Pipelines but that it’s not the best way to achieve 
> the larger goal of overhauling the entire Jenkins user experience. 
> 
Does this mean that blue ocean is dead and a new - even bigger - project will 
come? Wouldn’t it make more sense to start with smaller UI refactoring steps in 
the current UI rather than another large overall approach that may fail in the 
end? There is so much potential in the current UI that could be leveraged with 
small effort. (An overall approach still can be started in parallel. But now we 
have the problem that almost nobody is improving the classic UI side anymore 
because of the announcement of blue ocean.)

>  Christina Noren's blog post on CloudBees and Jenkins 
>  gives a good 
> update of the work we are doing at CloudBees on Jenkins overall. The 
> CloudBees teams working on Jenkins are currently engaged in a discovery 
> process to start a large project to modernize the overall user experience in 
> Jenkins. This research goes beyond simple user interface updates and focuses 
> on usability in addition to  modern aesthetics. 


Maybe it would also make sense if you could run such a discussions in public 
(dev list?) so that non-Cloudbees contributors can participate? At least during 
the initialization of blue ocean we had a lot of discussions with plugin 
authors about requirements for a new UI.

> 
> I believe that Pipeline is THE way that continuous integration and continuous 
> delivery are best done in Jenkins. Therefore, I am proposing that we raise 
> Pipeline to become a top-level sub-project within Jenkins.
> 
> Making Pipeline a top-level sub-project will:
> Clearly tie Jenkins to CI/CD for new and existing Jenkins users
> Make it easier for everyone to find documentation for using CI/CD Pipelines 
> in Jenkins
> Help the community and CloudBees to continue to improve and build out new 
> features for Pipeline and to improve documentation and examples
> Help clarify that Blue Ocean is a feature of Jenkins Pipeline
> 
> I look forward to getting your feedback. Thank you for your time.
> 
> Regards
> 
> Jeremy Hartley
> Senior Product Manager
> CloudBees, Inc.
> 
> -- 
> 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/264C1702-896E-485B-8630-8B4616607AE3%40cloudbees.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/7D410C5E-5A40-4D3C-8D5E-6C92A8D00DF9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: The sh step does not show all output

[Ullrich Hafner]

Would a workaround as shown in 
https://issues.jenkins-ci.org/browse/JENKINS-54832 
 help?

> Am 27.05.2019 um 12:51 schrieb Sverre Moe :
> 
> I found a way to ouput both stdout and stderr, but then I didn't get either 
> in Jenkins Console.
> sh("make 2>&1 | tee buildOutputFile.txt")
> 
> mandag 27. mai 2019 12.20.17 UTC+2 skrev Sverre Moe følgende:
> The standard output from the sh-step does not show all the output:
> final def output = sh(returnStdout: true, label: "Build and Package", script: 
> "make")
> writeFile(file: 'buildOutputFile.txt', text: output)
> 
> The Blue Ocean log output from a single Node shows all the warnings, but the 
> output from the sh step does not:
> https://JENKINS_URL/blue/rest/organizations/jenkins/pipelines/PROJECT/branches/BRANCH/runs/2/nodes/56/log/?start=0
>  
> 
> 
> Could it be that the actual output is not stdout, but stderr? Unfortunately 
> sh does not have an returnStderr.
> 
> I am using this output for the Warnings Plugin, since I want warning for each 
> build node, and the plugin default reads the entire console output.
> recordIssues(tools: [gcc4(id: "gcc-${buildHost}", name: "${buildHost}", 
> pattern: "buildOutputFile.txt")])
> 
> -- 
> 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/5efbb0ab-54e9-462c-86f6-2ff0593a88fa%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/C70314E1-145F-4C34-AFB6-B9813F209629%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings Next Generation Plugin: Keep its history after discard builds

[Ullrich Hafner]

The trend charts are created dynamically using the available build results. So 
if you delete builds, then those results are also not available anymore. (This 
concept should be similar for all Jenkins plugins, or are e.g. test results 
shown for deleted builds?). 

One workaround would be to delete unused data in the build folders (e.g. 
artifacts, etc.), but not the build.xml files. 

An alternative approach would be 
a) Store the data of the visible trend information in the current build as 
well. Then you cannot remove builds with broken warning results anymore from 
the charts. I’m not sure if that is something we should consider?
b) Create a new Jenkins Visualizer App - independent of the Jenkins UI, that 
renders the results of various plugins. The shown data could be stored in an 
associated build artifacts database. Then we could have a headless Jenkins on 
the one side and a modern UI app on the other side. 
 
> Am 27.05.2019 um 10:38 schrieb Sverre Moe :
> 
> The "Warnings Trend" graphs are empty.
> 
> From out last build:
> sles15.0-x86_64: No warnings
> No warnings for 28 builds, i.e. since build 3
> 
> This might be because we delete old builds. We keep only the last 10 builds.
> In this case build #3 has been deleted.
> 
> Is there a workaround for this? We do not want to keep all builds in Build 
> History. As it requires much more disk space and (perhaps could slow down 
> Jenkins ((a guess)).
> 
> -- 
> 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/1edbe937-2d9a-4dba-9a72-d4b567299bab%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/8C298C1F-B433-473A-9674-5DFBDA405D85%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins JUnit Plugin - Unstable issues

[Ullrich Hafner]

Yes: the plugin sets the status to UNSTABLE or SUCCESS. But never to FAILED.

> Am 06.05.2019 um 22:17 schrieb cliffhanger...@gmail.com:
> 
> Yes: it sets the status to UNSTABLE or SUCCESS. But never to FAILED.

-- 
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/F749CAB6-9308-44CF-89F9-A5294FE1EDE0%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings Next Generation Plugin With GCC C++

[Ullrich Hafner]

> Am 06.05.2019 um 14:47 schrieb Sverre Moe :
> 
> mandag 6. mai 2019 13.23.02 UTC+2 skrev Ullrich Hafner følgende:
> There are some open issues about that:
> https://issues.jenkins-ci.org/browse/JENKINS-44450 
> <https://issues.jenkins-ci.org/browse/JENKINS-44450>
> https://issues.jenkins-ci.org/browse/JENKINS-55258 
> <https://issues.jenkins-ci.org/browse/JENKINS-55258>
> 
> As a workaround you should pipe the log to a file.
>  
> How so, is there a pipeline step to do this?

No.

> Or do I need to take the output from sh step?

Yes.

> 
> -- 
> 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 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/7290124c-0624-4822-8595-16fb82a6774f%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/7290124c-0624-4822-8595-16fb82a6774f%40googlegroups.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/01BE5B84-065A-4A7E-9945-5AE9B184A5F8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings Next Generation Plugin With GCC C++

[Ullrich Hafner]

There are some open issues about that:
https://issues.jenkins-ci.org/browse/JENKINS-44450 

https://issues.jenkins-ci.org/browse/JENKINS-55258 


As a workaround you should pipe the log to a file.

> Am 06.05.2019 um 13:12 schrieb Sverre Moe :
> 
> I think the tool
> Reads the complete output (where all 4 nodes are intermingled).
> It would be better if it could read only for the one node it is executed 
> within.
> 
> Still I find it odd that it showed the same issues for all nodes. It should 
> at least show the ones from the node itself
> sles12.3 output showed none of the sles12.3 warnings.
> 
> mandag 6. mai 2019 13.01.22 UTC+2 skrev Sverre Moe følgende:
> It seems to be very confused.
> I am bulding on 4 nodes
> opensuse42.3
> opensuse15.0
> sles12.3
> sles15.0
> 
> They have each their own gcc4 ID, but they have the same result, showing the 
> same 4 entries for each.
> Total 5 
> /dev/shm/rpmroot-build-opensuse42.3_x86_64/projectA/BUILD/projectA-1.3.2/something/some_thing_file
> Total 6 
> /dev/shm/rpmroot-build-opensuse15.0_x86_64/projectA/BUILD/projectA-1.3.2/src/dirA
> Total 2 
> /dev/shm/rpmroot-build-opensuse15.0_x86_64/projectA/BUILD/projectA-1.3.2/src/dirB
> Total 10 
> /dev/shm/rpmroot-build-opensuse15.0_x86_64/projectA/BUILD/projectA-1.3.2/something/some_thing_file
> 
> None from the sles nodes are shown.
> 
> mandag 6. mai 2019 12.27.29 UTC+2 skrev Sverre Moe følgende:
> How do I use this plugin to record and show C/C++ Warnings/Errors from GCC?
> 
> There is two tools available GNU C Compiler (gcc3) and GNU C Compiler (gcc4), 
> but are those for C?
> We are using a much newer version of GCC.
> 
> Otherwise I could only find these for C++
> recordIssues(tools: [cppCheck()])
> recordIssues(tools: [cppLint()])
> 
> Neither found no warnings, but there where plenty of warnings when running 
> GCC.
> 
> [50/107] Building CXX object src/CMakeFiles/some.dir/thing/file.cpp.o 
> src/thing/file.cpp: In member function ‘std::__cxx11::string 
> file::method(const string&, const string&)’:
> src/thing/file.cpp:141:31: warning: unused variable ‘id’ [-Wunused-variable]
>  for (const auto & [ id, m ] : _id_to_var)
> 
> 
> I tried with the gcc4, and it spewed out some errors with stacktrace in the 
> recording. Looks like it tried to run some git commands, and I do not have a 
> git repository at hand, just a stashed archive.
> However it seems at least it did find some Warnings. The warning above was 
> detected by gcc4.
> Is there any way I can stop it from accessing Git when it is trying to record?
> 
> -- 
> 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/86e41f89-fdc6-499d-8cad-3403128bad04%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/AB18F045-B5CD-41E0-B46F-37B4B0EBB963%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings Next Generation Plugin With GCC C++

[Ullrich Hafner]

> Am 06.05.2019 um 12:27 schrieb Sverre Moe :
> 
> How do I use this plugin to record and show C/C++ Warnings/Errors from GCC?
> 
> There is two tools available GNU C Compiler (gcc3) and GNU C Compiler (gcc4), 
> but are those for C?
> We are using a much newer version of GCC.
> 

I think I should rename the Tools

GNU C Compiler (gcc4) -> GNU C Compiler 
GNU C Compiler (gcc3) -> GNU C Compiler (3 and older)

And the ID to gcc. 

Would that make sense?

> Otherwise I could only find these for C++
> recordIssues(tools: [cppCheck()])
> recordIssues(tools: [cppLint()])
> 
> Neither found no warnings, but there where plenty of warnings when running 
> GCC.
> 
> [50/107] Building CXX object src/CMakeFiles/some.dir/thing/file.cpp.o 
> src/thing/file.cpp: In member function ‘std::__cxx11::string 
> file::method(const string&, const string&)’:
> src/thing/file.cpp:141:31: warning: unused variable ‘id’ [-Wunused-variable]
>  for (const auto & [ id, m ] : _id_to_var)
> 

I’m not sure if your log is different but the parser gcc4 should work. 

> 
> I tried with the gcc4, and it spewed out some errors with stacktrace in the 
> recording. Looks like it tried to run some git commands, and I do not have a 
> git repository at hand, just a stashed archive.
> However it seems at least it did find some Warnings. The warning above was 
> detected by gcc4.
> Is there any way I can stop it from accessing Git when it is trying to record?
> 

Yes, use 

recordIssues blameDisabled: true, …

BTW: there is also a Gitter channel available: 
https://gitter.im/jenkinsci/warnings-plugin 

> -- 
> 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/db195bc3-2907-4dee-8a4b-a9a1bf2c6734%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/1BE0FEAF-0244-499D-B497-CC1E1E80D4F8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins JUnit Plugin - Unstable issues

[Ullrich Hafner]

> Am 29.04.2019 um 22:25 schrieb cliffhanger...@gmail.com:
> 
> JUnit is defintiely setting the build status to UNSTABLE when the only test 
> which got executed failed:
> 
> Erorr output: 
> "Build step 'Publish JUnit test result report' changed 
> build result to UNSTABLE"
> 
> I am guessing that means there is something in JUnit reporter which can set 
> the build status to pass or fail.
> 

Yes: it sets the status to UNSTABLE or SUCCESS. But never to FAILED.
> --Ishan
> 
> On Saturday, April 27, 2019 at 6:32:53 AM UTC-7, Ullrich Hafner wrote:
> The JUnit plugin cannot set the build result to failed. The unstable state is 
> a feature of Jenkins.
> 
> (If you need to set the build to failed you can do this with your build tool, 
> but I would not recommend to do it)
> 
>> Am 27.04.2019 um 00:27 schrieb cliffha...@gmail.com <>:
>> 
>> Hi,
>> 
>> So I am using the Jenknis JUnit plugin to parse the test results. I have a 
>> job which has just one test and it fails all the time however, the JUnit 
>> plugin marks the job as unstable and not failed. Any reasons why? I have 
>> tried to set the Health report amplification factor to 1, 0.1, 0.0 but no 
>> luck. 
>> 
>> How can I get the JUnit to fail the build?
>> 
>> Thanks,
>> --Ishan
>> 
>> -- 
>> 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 jenkins...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/907f0d07-ed2d-427e-9649-ddb1caebb457%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/907f0d07-ed2d-427e-9649-ddb1caebb457%40googlegroups.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/1835afb9-ee4e-46c9-8d12-03c5b9b5a920%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/1835afb9-ee4e-46c9-8d12-03c5b9b5a920%40googlegroups.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/092AED53-5A4A-4CA5-BCBA-C6F5152C167D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins JUnit Plugin - Unstable issues

[Ullrich Hafner]

The JUnit plugin cannot set the build result to failed. The unstable state is a 
feature of Jenkins.

(If you need to set the build to failed you can do this with your build tool, 
but I would not recommend to do it)

> Am 27.04.2019 um 00:27 schrieb cliffhanger...@gmail.com:
> 
> Hi,
> 
> So I am using the Jenknis JUnit plugin to parse the test results. I have a 
> job which has just one test and it fails all the time however, the JUnit 
> plugin marks the job as unstable and not failed. Any reasons why? I have 
> tried to set the Health report amplification factor to 1, 0.1, 0.0 but no 
> luck. 
> 
> How can I get the JUnit to fail the build?
> 
> Thanks,
> --Ishan
> 
> -- 
> 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/907f0d07-ed2d-427e-9649-ddb1caebb457%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/CA1191AE-7409-441F-800B-5FC3DB265E90%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publisher 'Publish JUnit test result report' failed: None of the test reports contained any result

[Ullrich Hafner]

Please use text when showing text output, images are not helpful. 

The error message indicates that your report has not been found. I.e. the 
pattern is wrong.


> Am 03.04.2019 um 14:31 schrieb yash sharma :
> 
> 

-- 
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/D15F3792-295A-4604-8F47-3C836BC36381%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Publisher 'Publish JUnit test result report' failed: None of the test reports contained any result

[Ullrich Hafner]

JaCoCo is a code coverage tool. The report you pasted is the code coverage 
result. This can visualized in Jenkins using the 
https://plugins.jenkins.io/code-coverage-api 
 plugin. The JUnit plugin can’t 
read those reports.

In order to visualize JUnit results you need to run JUnit (without coverage) 
and provide a link to these results. 

> Am 01.04.2019 um 16:32 schrieb yash sharma :
> 
> Hi All,
> 
> In my Jenkins I am doing a post build action which will display Junit test 
> result report. PFB the snip for the configuration of Junit xmls
> 
> 
> I am doing an Ant(jacoco) build to generate Junit results. 
> Post a successful build I get an error message like 
> 
> I could see the xml generated and even the HTML file displaying the results
> 
> 
> My Junit Plugin version is 1.2.
> 
> PFA the attached JUNIT xml.
> 
> Any help is appreciated.
> Thanks and regards
> 
> 
> -- 
> 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/fd0fc17a-9b36-43b6-b08a-65013b552776%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
>  2.png>

-- 
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/7EEBC97E-C800-47A2-86EF-0DB78601D6BC%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings Next Generation Plugin with CodeWarrior

[Ullrich Hafner]

> Am 07.03.2019 um 13:10 schrieb Gavin Nottage :
> 
> I started to work on adding the help text as suggested, but have got very 
> confused. I'm an embedded C programmer and while Java is mostly 
> understandable, I haven't found a suitable guide for contributing to existing 
> plugins. I have some experience with git, but Maven is all new to me. 
> Whatever I try to do I get errors that mean nothing to me like:
> 
> mvn hpi:run
> [INFO] Scanning for projects...
> [WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:2.7 is 
> missing, no dependency information available
> [WARNING] Failed to build parent project for 
> io.jenkins.plugins:warnings-ng:hpi:4.0.0-SNAPSHOT


I’ll add something to the Contributing document. I’m currently preparing a 
docker-based development environment for my plugin for one of my university 
courses. Hopefully, this will work for contributors as well.
  
> 
> I think I know the code change to make, but cannot build or test it. The 
> addition I think is needed is as below, and I've attached the complete file. 
> If this is good then it can be added...
> 
> Thanks for all the efforts of the developers, if a good webpage could walk 
> though going from nothing to building and testing a plugin, that would be 
> really helpful.
> 
> @Override
> public String getHelp() {
> return "Ensure that the output from the CodeWarrior build 
> tools is in the expected format. If there are warnings present, but they are 
> not found, then it is likely that the format is incorrect. The mwccarm 
> compiler and mwldarm linker tools may support a configurable message style. 
> This can be used to enforce the expected output format, which may be 
> different from Metrowerks CodeWarrior (and thus require a different tool). 
> For example the following could be appended to the build flags:"
> + "-msgstyle gcc -nowraplines";
> }
> 

Thank!

Committed as 
https://github.com/jenkinsci/warnings-ng-plugin/commit/2d3c402fc477fea0b0e95ea5ba0ecc3e633fb8e9

> 
> -- 
> 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/580f12cb-1ded-4ea8-8b90-fec5f27cbc1c%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/55A5F975-1CBC-4A29-AD47-506F4132A07D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Warnings Next Generation Plugin with CodeWarrior

[Ullrich Hafner]

If you are interested then you could also create a small PR that describes your 
approach in the help of the parser:
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/warnings/MetrowerksCodeWarrior.java
 


You can use plain text or HTML in the help text, here is an example:
https://github.com/jenkinsci/warnings-ng-plugin/blob/master/src/main/java/io/jenkins/plugins/analysis/warnings/Eclipse.java#L48
 


Then it is always visible for users of code warrior.

> Am 04.03.2019 um 17:38 schrieb 'Gavin Nottage' via Jenkins Users 
> :
> 
> Thanks for your advice Ullrich.Digging into the project options I have 
> managed to get it to output the warnings in gcc format, which are picked up!
> 
> For anyone reading this in the years to come (which could be me, or a member 
> of my team), I needed to define -msgstyle gcc -nowraplines as other flags in 
> the mwccarm compiler and again for the mwldarm linker. This overwrites the 
> default parseable msgstyle in each .args file (which is generated from the 
> project for each source file). This is using the console log rather than a 
> file for reporting.
> 
> --
> 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/b71f6abc-441a-4bc0-bc0f-4230890becb1%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/65984E07-5DCE-4B1C-8A63-F0A7395863A1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Warnings Next Generation Plugin with CodeWarrior

[Ullrich Hafner]

Seems that your warning output format looks totally different. The tests of the 
parser use:

https://github.com/jenkinsci/analysis-model/blob/master/src/test/resources/edu/hm/hafner/analysis/parser/MetrowerksCWCompiler.txt
 


Are there options to change the output format?

> Am 01.03.2019 um 15:09 schrieb 'Gavin Nottage' via Jenkins Users 
> :
> 
> C:/Freescale/CW MCU 
> v10.2/MCU/ARM_Tools/Command_Line_Tools/mwccarm|Compiler|Warning
> (C:\jenkins\workspace\PointColourWindowsBuild\point-colour\Sources\port\mqx\MqxUsbDescriptor.c|432|19|1|16759|1)
> = uint_32 handle,
> >variable / argument 'handle' is not used in function
> C:/Freescale/CW MCU 
> v10.2/MCU/ARM_Tools/Command_Line_Tools/mwccarm|Compiler|Warning
> (C:\jenkins\workspace\PointColourWindowsBuild\point-colour\Sources\port\mqx\MqxI2C.c|163|15|1|4665|1)
> =  return(error);
> >implicit arithmetic conversion from 'unsigned long' to 'unsigned char'
> C:/Freescale/CW MCU 
> v10.2/MCU/ARM_Tools/Command_Line_Tools/mwccarm|Compiler|Warning
> (C:\jenkins\workspace\PointColourWindowsBuild\point-colour\Sources\port\mqx\MqxI2C.c|176|15|1|4977|1)
> =  return(error);
> >implicit arithmetic conversion from 'unsigned long' to 'unsigned char'

-- 
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/9F719AB3-F1C9-48B2-94CF-D8589A075DA8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: What should be used instead of the various Deprecated plugins?

[Ullrich Hafner]

https://github.com/jenkinsci/warnings-ng-plugin 


There should be a upgrade notice in your system configuration if you have not 
installed the new plugin.

> Am 06.02.2019 um 18:18 schrieb John Lussmyer :
> 
> I've noticed that our builds now have a list of Deprecated plugins:
> [Deprecated] Publish Findbugs Analysis results
> [Deprecated] Scan for Compiler warnings
> [Deprecated] Publish combined static analysis results
> 
> What are the replacements for those?
> 
> 
> --
> 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/e03a7353-5c31-4713-816f-ae0727fc71ff%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/15C1F504-9DC6-4FB6-8FF6-06CD1B23A410%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: warnings-ng plug-in in a matrix job

[Ullrich Hafner]

Does the plugin fail the job for the other axes? Or can’t you just pick a file 
that is empty for the other axes? 

Currently there is no way to configure different properties for different axes.

> Am 21.01.2019 um 19:49 schrieb Braden McDaniel :
> 
> I have a matrix job that builds on multiple compilers/platforms. One of those 
> compilers is clang with static analysis.
> 
> I have recently discovered the warnings-ng plug-in; and while it seems quite 
> clever, because it operates as a post-build action (and the conditional step 
> plug-in does not provide conditional steps in post-build), I do not see how 
> to enable it only for the portion of the matrix where clang's static analysis 
> is run.
> 
> Is there a way to get this sort of result within the matrix job?
> 
> -- 
> 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/14213f8f-251d-4544-b190-f4c71651a1f6%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/034B5AD4-8CD4-4879-B42C-19EC7C7F67B4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Building Jenkins in Eclipse

[Ullrich Hafner]

Building is quite easy:-) Just importing it into an IDE is complex since 
Jenkins uses a lot of hacks around the maven infrastructure so it does not work 
out of the box. 

E.g., the compile error in IntelliJ is due to missing generated resource files. 
These generated sources are not picked up automatically. You need to make sure 
that the folder target/generated-sources/localizer is recognized as source 
folder. 

> Am 03.01.2019 um 21:19 schrieb Gerry Storm :
> 
> I'm a bit surprised. jenkins is widely used and it looks looks like there are 
> tons of contributors. I assumed it would be a breeze to build it from the 
> source. I wonder if this is just my bad luck? 
> 
> On Thu, Jan 3, 2019 at 12:08 PM Gerry Storm  > wrote:
> I have tried inlelliji and still got one error when building projects:
> Error:(26, 25) java: package hudson.cli.client does not exist
> 
> in cli/src/main/java/hudson/cli/CLI.java at "import 
> hudson.cli.client.Messages;"
> 
> 
> 
> On Thu, Jan 3, 2019 at 8:56 AM Jan Monterrubio  > wrote:
> I personally use intellij idea, since it lets you import a project ( and if 
> it is maven it will wire things up on its own). 
> https://blog.jetbrains.com/idea/2008/03/opening-maven-projects-is-easy-as-pie/
>  
> 
> 
> 
> On Thu, Jan 3, 2019 at 10:55 AM Gerry Storm  > wrote:
> Thank you all very much. I am not particularly fond of Eclipse per se. I have 
> used it in the past and it was my first choice. If you think Apache NetBeans 
> or IntelliJ IDEA are better I will switch to one of those. Which one would 
> you recommend and are there instructions available I could follow? 
> 
> On Thu, Jan 3, 2019 at 5:17 AM Steffen Elste  > wrote:
> Hi,
> after i modified the pom.xml of the cli project to include
> 
> 
>  org.codehaus.mojo
>  build-helper-maven-plugin
>  3.0.0
>  
>  
>  add-source
>  generate-sources
>  
>  add-source
>  
>  
>  
>  
> ${project.build.directory}/generated-sources/localizer
>  
>  
>  
>  
>   
> 
> 
> and re-imported everything the build path is set up correctly.
> Cheers,
> 
> Steffen
> 
> -- 
> 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/46b79a6d-78d1-48f5-b1dd-8798eb82a9bc%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/CA%2BQZycn1-AO%2BrC5KhRi_QJwfJtxXzZdjrvs9-9kcjf5p2rjbNw%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/CADgiF9LAebb%2B-0tXsf2Vx5uCeKO0c7Rj4Ze8-uNiZCGpDtoS0A%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 

Re: Building Jenkins in Eclipse

[Ullrich Hafner]

I’m not sure if one of the developers is still using Eclipse. Did you try in 
IntelliJ (or is that not an option)?

BTW: I think your questing is better suited for the dev list, see Jenkins 
Developers .


> Am 31.12.2018 um 18:52 schrieb Gerry Storm :
> 
> I have tried to follow instructions in 
> https://wiki.jenkins.io/display/JENKINS/Building+Jenkins:
> 
> // check out the workspace
> $ git clone https://github.com/jenkinsci/jenkins.git
> // Download dependencies and build with Maven
> // Note: mvn install may be a prerequisite for other mvn targets
> $ cd jenkins
> $ mvn -Plight-test install
> 
> All went fine.
> 
> After that I followed instructions in 
> https://wiki.jenkins.io/display/JENKINS/Setting+up+Eclipse+to+build+Jenkins.
> 
> 
> I tried several times and Eclipse ALWAYS finds errors after it imports the 
> projects. (see attached screenshot).
> I am a newbie so maybe the instructions imply stuff I am not familiar with.
> 
> My goals are:
> Build Jenkins from source in Eclipse
> Run it under a debugger so that I can make myself familiar with the flow.
> 
> Please help.
> 
> -- 
> 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/a00369ef-2bd3-470e-a787-e7a9bfaca2f4%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/9C623046-BA74-45F2-8C99-1D977947EA9A%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[Ullrich Hafner]

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=planning=JENKINS-54398
 
<https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=421=planning=JENKINS-54398>
The plugin should rather report a helpful text...

> Am 01.11.2018 um 12:22 schrieb dean warren :
> 
> 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  <mailto:ullrich.haf...@gmail.com>> 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 > <mailto:dean.warren...@gmail.com>>:
>> 
>> 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 > <mailto:ullrich.haf...@gmail.com>> wrote:
>> and one additional question: how is the checkstyle file created?
>> 
>>> Am 30.10.2018 um 15:30 schrieb Ullrich Hafner >> <mailto:ullrich.haf...@gmail.com>>:
>>> 
>>> 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 >>> <mailto:dean.warren...@gmail.com>>:
>>>> 
>>>> 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)
>>>>  

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[Ullrich Hafner]

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 :
> 
> 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  <mailto:ullrich.haf...@gmail.com>> wrote:
> and one additional question: how is the checkstyle file created?
> 
>> Am 30.10.2018 um 15:30 schrieb Ullrich Hafner > <mailto:ullrich.haf...@gmail.com>>:
>> 
>> 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 >> <mailto:dean.warren...@gmail.com>>:
>>> 
>>> 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.impersona

Re: Warning Plugin 5.0 Release - Beta Testing

[Ullrich Hafner]

The next beta release is available for download!

In order to simplify the upgrade process I moved all new reporters and steps to 
a completely new plugin: Warnings Next Generation Plugin (warnings-ng).
That means the old plugins (warnings, checkstyle, findbugs, analysis-core etc.) 
are not required anymore if you have converted your jobs.

You need to install the following plugins (from the experimental update center):
• analysis-model-api: 1.0.0-beta9
• warnings-ng (Warnings Next Generation Plugin): 1.0.0-beta1


> Am 10.09.2018 um 10:05 schrieb Ullrich Hafner :
> 
> A new major release of the static analysis suite is about to come. Since 
> there are a lot of changes (see [1]) I decided to start with a public beta. 
> I.e., the new release is currently only available at the experimental update 
> center.
> 
> Important changes at a glance:
> - All plug-ins have been merged into the Warning Plug-in, i.e. there is only 
> a single entry point for all static analysis tools now. That means that the 
> plugins android-lint, ccm, checkstyle, dry, pmd, findbugs, analysis-core, 
> analysis-collector, task-scanner are at end-of-life. You do not need them 
> anymore after a (manual) migration of your existing jobs.
> - New UI using modern frameworks (charts, tables, etc.). See documentation 
> [1] for some screenshots and details about the user experience.
> - New API for pipelines to combine and filter reports.
> 
> Since the wiki is not reliable in the moment I published the new 
> documentation directly in GitHub [1].
> 
> HOW CAN YOU HELP?
> - Convert some of your jobs to the new API and test the new (and old) 
> features (based on your requirements).
> - Read all labels carefully, I’m not a native speaker so some descriptions 
> might be misleading or incorrect.
> - Check the new URLs and names of the parsers, see list of supported formats 
> [2].
> 
> If you find a problem, incorrect phrase, typo, etc. please report a bug in 
> Jira (or even better: file a PR in GitHub).
> 
> [1] 
> https://github.com/jenkinsci/warnings-plugin/blob/master/doc/Documentation.md
> [2] 
> https://github.com/jenkinsci/warnings-plugin/blob/master/SUPPORTED-FORMATS.md
> 

-- 
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/9141891F-F88A-43C7-8FA0-EFDDB3F2424E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Warnings reports in BlueOcean

[Ullrich Hafner]

No. Providing a UI for blue ocean is still blocked by JEP-203 and JEP-204 :-(

See
- https://github.com/jenkinsci/jep/blob/master/jep/203/README.adoc 

- https://github.com/jenkinsci/jep/blob/master/jep/204/README.adoc 



> Am 31.10.2018 um 11:19 schrieb 'Kamil Wójcik' via Jenkins Users 
> :
> 
> Hi,
> I'm using warnings plugin link  
> to publish static analysis reports (findbugs, codenarc). In old UI those 
> reports are visible on the left side. However in BlueOcean I'm not able to 
> find it anywhere.
> 
> Is there any way to make it visible in BlueOcean ?
> 
> Regards Kamil
> 
> --
> 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/a147586d-e694-478e-954e-cc679d8de1a2%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/68F460E5-0BB3-4151-909E-499337324BE3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[Ullrich Hafner]

and one additional question: how is the checkstyle file created?

> Am 30.10.2018 um 15:30 schrieb Ullrich Hafner :
> 
> 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 > <mailto:dean.warren...@gmail.com>>:
>> 
>> 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 
&

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[Ullrich Hafner]

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  <mailto:ullrich.haf...@gmail.com>> 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 > <mailto:dean.warren...@gmail.com>>:
>> 
>> 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 > <mailto:dean.warren...@gmail.com>> 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.
>> 
>> But on the failed build the icons have dissappeared.
>> 
>> How do I view the checkstyle warnings/errors in Jenksin?
>> 
>> On Tue, Oct 30, 2018 at 10:57 AM Ullrich Hafner > <mailto:ullrich.haf...@gmail.com>> 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 >> <mailto:dean.warren...@gmail.com>>:
>>> 
>>> 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 >> <mailto:dean.warren...@gmail.com>> 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-experi

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[Ullrich Hafner]

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 :
> 
> 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  <mailto:dean.warren...@gmail.com>> 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.
> 
> But on the failed build the icons have dissappeared.
> 
> How do I view the checkstyle warnings/errors in Jenksin?
> 
> On Tue, Oct 30, 2018 at 10:57 AM Ullrich Hafner  <mailto:ullrich.haf...@gmail.com>> 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 > <mailto:dean.warren...@gmail.com>>:
>> 
>> 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 > <mailto:dean.warren...@gmail.com>> 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 >:
>> 
>>> 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 > 
>>> 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 > wrote:
>>> OK, from here:
>>> https://github.com/jenkinsci/warnings-plugin/tree/5.0 
>>> <https://github.

Re: java.lang.NoSuchMethodError: No such DSL method 'scanForIssues' found among steps

[Ullrich Hafner]

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).

Is your file called checkstyle-result.xml or checkstyle-result*s*.xml?

> Am 30.10.2018 um 11:48 schrieb dean warren :
> 
> 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  <mailto:dean.warren...@gmail.com>> 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 >:
> 
>> 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 > 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 > 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 > wrote:
>> 
>> 
>> Von meinem iPad gesendet
>> 
>> Am 26.10.2018 um 09:50 schrieb dean warren >:
>> 
>>> 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',

Re: Configuration as code and preservation of credentials

[Ullrich Hafner]

> Am 25.09.2018 um 22:27 schrieb nicolas de loof :
> 
> A feature we'd like to investigate for JCasC is to make the web UI read-only 
> once configured from yaml
> The specific sample of credentials could be adapted to support "preserve 
> existing entries" but we have no way to support this in a generic way
> Also, JCasC is designed to support re-creating an equivalent jenkins master 
> from scratch, so from this point of view this would make no sense.
> 

Shouldn’t it be possible to use the same configuration to create multiple 
master instances that handle different jobs with different views? This seems to 
be not possible now.

> Le mar. 25 sept. 2018 à 22:07,  > a écrit :
> But many things are otherwise preserved. I feel the implementation of the 
> credentials configuration is doing a none vs. all approach, not taking into 
> account existing entries:
> 
> In SystemCredentialsProviderConfigurator:
> 
> target.setDomainCredentialsMap(DomainCredentials.asMap(value))
> 
> Maybe this code could be replaced to preserve existing entries.
> 
> 
> On Tuesday, September 25, 2018 at 10:03:00 PM UTC+2, damien.c...@collibra.com 
>  wrote:
> I've created the PR at 
> https://github.com/jenkinsci/configuration-as-code-plugin/pull/556 
>  to show 
> an unit test reproducing the issue.
> 
> On Tuesday, September 25, 2018 at 9:04:31 PM UTC+2, damien.c...@collibra.com 
> <> wrote:
> Hi,
> 
> We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is a 
> list of credentials (some SSH keys, some user/passwords, etc.) common to all 
> our instances but we let also the administrators of a Jenkins instance define 
> their own credential entries.
> 
> However, when the Jenkins instance is restarted, only the credential entries 
> defined by the CasC files are kept, and all the ones which were added 
> manually are lost.
> 
> Is there a way to prevent this?
> 
> Thanks,
> Damien Coraboeuf
> 
> --
> 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/fb5e1d2b-4df3-4950-902d-5f18490b2ea5%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> --
> Nicolas De Loof
> 
> --
> 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/CANMVJzn_LpJBVQbjHKGLmF51oAsyWW7E%2BNxng9sB-KCHKtb%2BWQ%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/39087A77-F84E-4EA3-92E0-74AB71B470C9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Configuration as code and preservation of credentials

[Ullrich Hafner]

This is one of the drawbacks of JCasC of the current version.
You can’t change anything in the UI anymore if you enable JCasC. Everything 
will be lost after restart.
It would make sense to have a way to use both JCasC and the manual UI 
configuration together somehow.

> Am 25.09.2018 um 21:04 schrieb damien.corabo...@collibra.com:
> 
> Hi,
> 
> We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is a 
> list of credentials (some SSH keys, some user/passwords, etc.) common to all 
> our instances but we let also the administrators of a Jenkins instance define 
> their own credential entries.
> 
> However, when the Jenkins instance is restarted, only the credential entries 
> defined by the CasC files are kept, and all the ones which were added 
> manually are lost.
> 
> Is there a way to prevent this?
> 
> Thanks,
> Damien Coraboeuf
> 
> --
> 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/2ab722d3-c851-4764-89a3-733d6cbb5391%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/32379F33-4158-412F-92DD-215AAA30DEE5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: CppCheck plugin fails on Ubuntu 18.04

[Ullrich Hafner]

The beta release of the warnings plug-in has also support for CPPcheck now. You 
can try if your file works here.

https://jenkins.io/blog/2018/09/11/speaker-blog-warnings-plugin/

> Am 20.09.2018 um 14:29 schrieb Fabian Cenedese :
> 
> Hi
> 
> I have a job that among other things uses cppcheck to examine the code.
> This has worked on several systems (Ubuntu, Debian, Windows). However
> I have a problem using the same job on the last Ubuntu 18.04. Here's a
> snippet from a working build:
> 
> (Ubuntu 16.04, CppCheck 1.72)
> [Cppcheck] Starting the cppcheck analysis.
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
> [Cppcheck] Not changing build status, since no threshold has been exceeded.
> [Cppcheck] Ending the cppcheck analysis.
> 
> And this is what happens on Ubuntu 18.04
> 
> (Ubuntu 18.04, CppCheck 1.82)
> [Cppcheck] Starting the cppcheck analysis.
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
> [Cppcheck] Error on cppcheck analysis: java.io.IOException: remote file 
> operation failed: 
> /var/lib/jenkins/workspace/inos_unittest_desktop/INOSTYPE/600205020 
> Linux/OPT/Debug/OS/linux/label/inos_desktop at 
> hudson.remoting.Channel@282557ba:Ub18-04-64: java.io.IOException: Remote call 
> on Ub18-04-64 failed
> Build step 'Publish Cppcheck results' changed build result to FAILURE
> Build step 'Publish Cppcheck results' marked build as failure
> 
> The cppcheck logfile looks the same, xml with version 2. So what else
> could be the reason for this exception? Is there a log file on the slave
> that has more information? Or can I tell the slave to output more information
> to the master?
> 
> Thanks
> 
> bye  Fabi
> 
> --
> 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/20180920122925.855C736B177E%40macserver.private.
> 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/0AD00919-3BF6-40E1-97CE-E5E1C37A92C7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Warning Plugin 5.0 Release - Beta Testing

[Ullrich Hafner]

A new major release of the static analysis suite is about to come. Since there 
are a lot of changes (see [1]) I decided to start with a public beta. I.e., the 
new release is currently only available at the experimental update center. 

Important changes at a glance:
- All plug-ins have been merged into the Warning Plug-in, i.e. there is only a 
single entry point for all static analysis tools now. That means that the 
plugins android-lint, ccm, checkstyle, dry, pmd, findbugs, analysis-core, 
analysis-collector, task-scanner are at end-of-life. You do not need them 
anymore after a (manual) migration of your existing jobs. 
- New UI using modern frameworks (charts, tables, etc.). See documentation [1] 
for some screenshots and details about the user experience.
- New API for pipelines to combine and filter reports. 

Since the wiki is not reliable in the moment I published the new documentation 
directly in GitHub [1].

HOW CAN YOU HELP?
- Convert some of your jobs to the new API and test the new (and old) features 
(based on your requirements). 
- Read all labels carefully, I’m not a native speaker so some descriptions 
might be misleading or incorrect.
- Check the new URLs and names of the parsers, see list of supported formats 
[2]. 

If you find a problem, incorrect phrase, typo, etc. please report a bug in Jira 
(or even better: file a PR in GitHub).

[1] 
https://github.com/jenkinsci/warnings-plugin/blob/master/doc/Documentation.md
[2] 
https://github.com/jenkinsci/warnings-plugin/blob/master/SUPPORTED-FORMATS.md 

-- 
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/CE2AE646-04C8-44F4-930D-A493A2FF3359%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help staff the Contributors Corner at DevOps World | Jenkins World 2018

[Ullrich Hafner]

I will be attending in San Francisco.

> Am 24.08.2018 um 05:07 schrieb Mark Waite :
> 
> Thanks Ulli!  Will you be attending in San Francisco, or Nice, or both?
> 
> On Thu, Aug 23, 2018 at 4:41 PM Ullrich Hafner  <mailto:ullrich.haf...@gmail.com>> wrote:
>> Am 21.08.2018 um 02:56 schrieb Mark Waite > <mailto:mark.earl.wa...@gmail.com>>:
>> 
>> We want more people to help the Jenkins project in many different ways.  The 
>> Contributors Corner at DevOps World | Jenkins World 2018 is your chance to 
>> help others as they learn how to help the Jenkins project.
>> 
>> If you're attending DevOps World | Jenkins World 2018 in either San 
>> Francisco or Nice, and would be willing to give 30 minutes or an hour to 
>> assist at the Contributor's Corner table, we'd love to have your help.
>> 
>> We've assigned themes to different time slots during the conference.  We'll 
>> staff the table with people experienced in that theme.  The experienced 
>> people will help others contribute and become more experienced in that 
>> specific area.  You can help new contributors as they learn how to help the 
>> Jenkins project.
>> 
>> Themes we've chosen:
>> Answer Jenkins Questions
>> Promoting Jenkins in Your Company
>> Documenting Jenkins
>> Localizing Jenkins
>> Testing Jenkins Plugins (PRs and more)
>> Reviewing Jenkins Bugs
>> Testing Jenkins
>> Supporting Jenkins Platforms
>> Organizing a Jenkins Area Meetup
>> Helping Jenkins Infrastructure
>> Adopt a Jenkins Plugin
>> If you're willing to assist new contributors as they learn how to help 
>> within one or more of those themes during the conference, reply to this 
>> message and I'll include you in the list.
> 
> I can help with these themes:
>   • Testing Jenkins Plugins (PRs and more)
>   • Reviewing Jenkins Bugs
>   • Testing Jenkins
>   • Adopt a Jenkins Plugin
> 
> Ulli
> 
> 
>> 
>> If you have suggestions for additional themes, send them to me.
>> 
>> Thanks,
>> Mark Waite
>> 
>> --
>> 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 
>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/81D378D8-D5E3-4BFE-8678-9D93473A328B%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/81D378D8-D5E3-4BFE-8678-9D93473A328B%40gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEtEFSsS6KsSdBi3pFDH_Q1OTx5ZX0fDMcG9N_TZZCFYQ%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEtEFSsS6KsSdBi3pFDH_Q1OTx5ZX0fDMcG9N_TZZCFYQ%40mail.gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/552F47A2-1CCF-4F08-816A-EEF28B297948%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Help staff the Contributors Corner at DevOps World | Jenkins World 2018

[Ullrich Hafner]

> Am 21.08.2018 um 02:56 schrieb Mark Waite :
> 
> We want more people to help the Jenkins project in many different ways.  The 
> Contributors Corner at DevOps World | Jenkins World 2018 is your chance to 
> help others as they learn how to help the Jenkins project.
> 
> If you're attending DevOps World | Jenkins World 2018 in either San Francisco 
> or Nice, and would be willing to give 30 minutes or an hour to assist at the 
> Contributor's Corner table, we'd love to have your help.
> 
> We've assigned themes to different time slots during the conference.  We'll 
> staff the table with people experienced in that theme.  The experienced 
> people will help others contribute and become more experienced in that 
> specific area.  You can help new contributors as they learn how to help the 
> Jenkins project.
> 
> Themes we've chosen:
> Answer Jenkins Questions
> Promoting Jenkins in Your Company
> Documenting Jenkins
> Localizing Jenkins
> Testing Jenkins Plugins (PRs and more)
> Reviewing Jenkins Bugs
> Testing Jenkins
> Supporting Jenkins Platforms
> Organizing a Jenkins Area Meetup
> Helping Jenkins Infrastructure
> Adopt a Jenkins Plugin
> If you're willing to assist new contributors as they learn how to help within 
> one or more of those themes during the conference, reply to this message and 
> I'll include you in the list.

I can help with these themes:
• Testing Jenkins Plugins (PRs and more)
• Reviewing Jenkins Bugs
• Testing Jenkins
• Adopt a Jenkins Plugin

Ulli

> 
> If you have suggestions for additional themes, send them to me.
> 
> Thanks,
> Mark Waite
> 
> --
> 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/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%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/81D378D8-D5E3-4BFE-8678-9D93473A328B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: How to integrate stylecop with Jenkins?

[Ullrich Hafner]

Or install the warnings plugin, add the corresponding post build step and 
configure the path to the report file.

> Am 01.08.2018 um 13:52 schrieb girish kumar :
> 
> how to integrate stylecop with Jenkins? specify the path in Jenkins violation 
> plugin and publish the report?
> 
> --
> 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/0c17775b-dade-4568-9a70-a155ecae3a7c%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/7FDB2326-0804-40B0-82C9-EE358AB29EAC%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Contribute

[Ullrich Hafner]

Did you write the mail to the dev-list and the current maintainer?

> Am 08.05.2018 um 22:53 schrieb Orlando Burli <orlando.bu...@gmail.com>:
> 
> Yes, i wish to adopt this plugin:
> 
> https://wiki.jenkins.io/display/JENKINS/Backup+Plugin 
> <https://wiki.jenkins.io/display/JENKINS/Backup+Plugin>
> 
> I have a few modifications made on it, and like to share.
> 
> There is a problem of using him in docker, and i like to fix it.
> 
> 2018-05-08 16:50 GMT-04:00 Ullrich Hafner <ullrich.haf...@gmail.com 
> <mailto:ullrich.haf...@gmail.com>>:
> For what? How to adapt a plugin?
> See 
> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess
>  
> <https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess>
> 
> 
>> Am 08.05.2018 um 22:25 schrieb Orlando Burli <orlando.bu...@gmail.com 
>> <mailto:orlando.bu...@gmail.com>>:
>> 
>> Sorry, was my mistake.
>> 
>> Anyway, i still don't understando how is the processo for it.
>> 
>> 2018-05-08 16:21 GMT-04:00 Ullrich Hafner <ullrich.haf...@gmail.com 
>> <mailto:ullrich.haf...@gmail.com>>:
>> What do you mean with the mail is returning? Did you subscribe to the dev 
>> list?
>> 
>> From the web page:
>> 
>> Due to heavy spam volume, we have enabled moderation of a user’s first post 
>> on some of these lists. This may result in delays in delivering your first 
>> email to these lists. For this reason, you should not re-send your email if 
>> it doesn’t appear on the list straight away.
>> Maybe you just need to wait a little bit longer.
>> 
>> Your approach to participate is correctly! Here some additional information: 
>> https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing 
>> <https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing>
>> 
>> 
>>> Am 08.05.2018 um 18:19 schrieb Orlando Burli <orlando.bu...@gmail.com 
>>> <mailto:orlando.bu...@gmail.com>>:
>>> 
>>> Hi guys,
>>> 
>>> Anyone knows how to contribute to the project? I follow the steps on the 
>>> page to adopt a plugin, but the mail is returning...
>>> 
>>> jenkinsci-...@googlegroups.com <mailto:jenkinsci-...@googlegroups.com>
>>> 
>>> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin 
>>> <https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin>
>>> 
>>> 
>>> Orlando Burli
>>> 
>>> --
>>> 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 
>>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/5339a963-6ae6-4a32-9687-3ac5cba5f92f%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/5339a963-6ae6-4a32-9687-3ac5cba5f92f%40googlegroups.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/06B5E563-9E89-423F-9B3B-0BB643048E38%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/06B5E563-9E89-423F-9B3B-0BB643048E38%40gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/CABAnctpTzyg2BzkpfWFb0cYLV7DLxzyYXg-QvSYN5ceGkpk3VQ%40mail.gmail.com
&g

Re: Contribute

[Ullrich Hafner]

For what? How to adapt a plugin?
See 
https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess


> Am 08.05.2018 um 22:25 schrieb Orlando Burli <orlando.bu...@gmail.com>:
> 
> Sorry, was my mistake.
> 
> Anyway, i still don't understando how is the processo for it.
> 
> 2018-05-08 16:21 GMT-04:00 Ullrich Hafner <ullrich.haf...@gmail.com 
> <mailto:ullrich.haf...@gmail.com>>:
> What do you mean with the mail is returning? Did you subscribe to the dev 
> list?
> 
> From the web page:
> 
> Due to heavy spam volume, we have enabled moderation of a user’s first post 
> on some of these lists. This may result in delays in delivering your first 
> email to these lists. For this reason, you should not re-send your email if 
> it doesn’t appear on the list straight away.
> Maybe you just need to wait a little bit longer.
> 
> Your approach to participate is correctly! Here some additional information: 
> https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing 
> <https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing>
> 
> 
>> Am 08.05.2018 um 18:19 schrieb Orlando Burli <orlando.bu...@gmail.com 
>> <mailto:orlando.bu...@gmail.com>>:
>> 
>> Hi guys,
>> 
>> Anyone knows how to contribute to the project? I follow the steps on the 
>> page to adopt a plugin, but the mail is returning...
>> 
>> jenkinsci-...@googlegroups.com <mailto:jenkinsci-...@googlegroups.com>
>> 
>> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin 
>> <https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin>
>> 
>> 
>> Orlando Burli
>> 
>> --
>> 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 
>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/5339a963-6ae6-4a32-9687-3ac5cba5f92f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/5339a963-6ae6-4a32-9687-3ac5cba5f92f%40googlegroups.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/06B5E563-9E89-423F-9B3B-0BB643048E38%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/06B5E563-9E89-423F-9B3B-0BB643048E38%40gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CABAnctpTzyg2BzkpfWFb0cYLV7DLxzyYXg-QvSYN5ceGkpk3VQ%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/CABAnctpTzyg2BzkpfWFb0cYLV7DLxzyYXg-QvSYN5ceGkpk3VQ%40mail.gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/D594871A-D5A4-495F-9E03-B8D96C60D917%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Contribute

[Ullrich Hafner]

What do you mean with the mail is returning? Did you subscribe to the dev list?

>From the web page:

Due to heavy spam volume, we have enabled moderation of a user’s first post on 
some of these lists. This may result in delays in delivering your first email 
to these lists. For this reason, you should not re-send your email if it 
doesn’t appear on the list straight away.
Maybe you just need to wait a little bit longer.

Your approach to participate is correctly! Here some additional information: 
https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing 



> Am 08.05.2018 um 18:19 schrieb Orlando Burli :
> 
> Hi guys,
> 
> Anyone knows how to contribute to the project? I follow the steps on the page 
> to adopt a plugin, but the mail is returning...
> 
> jenkinsci-...@googlegroups.com
> 
> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin
> 
> 
> Orlando Burli
> 
> --
> 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/5339a963-6ae6-4a32-9687-3ac5cba5f92f%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/06B5E563-9E89-423F-9B3B-0BB643048E38%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Create iOS Warnings and Errors report in Jenkins

[Ullrich Hafner]

It would help us all if you would use a search engine before you ask questions.

> Am 25.04.2018 um 07:24 schrieb mManage mail <mmanagem...@gmail.com>:
> 
> By JENKINS-22700 what do you mean? I couldn't get it.
> 
> On Wed, Apr 25, 2018 at 10:51 AM, mManage mail <mmanagem...@gmail.com 
> <mailto:mmanagem...@gmail.com>> wrote:
> Thanks for the reply. I am unaware of the Jenkins remote API. Can you please 
> let me know what it is? Also can you please let me know the path where to 
> find the xml warnings file. I could find it inside my build folder.
> 
> On Wed, Apr 25, 2018 at 1:35 AM, Ullrich Hafner <ullrich.haf...@gmail.com 
> <mailto:ullrich.haf...@gmail.com>> wrote:
> You can use Jenkins remote API. (Or use the xml warnings file in the build 
> folder of Jenkins)
> 
> Errors are not yet reported, see JENKINS-22700.
> 
>> Am 24.04.2018 um 14:20 schrieb mManage mail <mmanagem...@gmail.com 
>> <mailto:mmanagem...@gmail.com>>:
>> 
>> I solved the issue. There is no need of Clang scan build step. It requires 
>> only the post build action "Scan for compiler warnings" to capture the 
>> warnings. I have selected the parser type as "Clang LLVM" and got a trend 
>> graph for each build. But is there a way to get this in a json or xml file 
>> saved in workspace? Also this is only for warnings. If there is any compiler 
>> error, will we be able to get the report similar to this?
>> 
>> 
>> 
>> On Tue, Apr 24, 2018 at 4:20 PM, Ullrich Hafner <ullrich.haf...@gmail.com 
>> <mailto:ullrich.haf...@gmail.com>> wrote:
>> I can’t help with xcode but there is again a hint from the tool, did you try 
>> that? This message is printed with purpose!
>> 
>>> xcodebuild: error: The flag -scheme or -xctestrun is required when 
>>> specifying -derivedDataPath.
>> 
>> 
>>> Am 24.04.2018 um 12:45 schrieb mManage mail <mmanagem...@gmail.com 
>>> <mailto:mmanagem...@gmail.com>>:
>>> 
>>> Ok i got it, I installed clang and configured the path in Jenkins->Manage 
>>> but getting the below error now while running the job, attaching the 
>>> screenshot. Could you please help?
>>> 
>>> xcodebuild: error: The flag -scheme or -xctestrun is required when 
>>> specifying -derivedDataPath.
>>> scan-build: Removing directory 
>>> '/Users/soe-admin/.jenkins/workspace/iOSTemplateJob/clangScanBuildReports/2018-04-24-161113-47610-1'
>>>  because it contains no reports.
>>> scan-build: No bugs found.
>>> XCODEBUILD ERROR
>>> Build step 'Clang Scan-Build' marked build as failure
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Tue, Apr 24, 2018 at 3:43 PM, mManage mail <mmanagem...@gmail.com 
>>> <mailto:mmanagem...@gmail.com>> wrote:
>>> I installed warnings plugin and clang scan-build plugin. I added clang 
>>> scan-build as a build step and entered the target and output folder as 
>>> clangScanBuildReports. Then i added a post build action to scan compiler 
>>> warnings. Please refer to the attached screenshot.  I am getting the 
>>> following error
>>> "
>>> FATAL: Unable to locate the clang scan-build installation named 'null'.  
>>> Please confirm a clang installation named 'null' is defined in the jenkins 
>>> global config and on each slave if the location is different than the 
>>> master.
>>> Build step 'Clang Scan-Build' marked build as failure
>>> [WARNINGS] Skipping publisher since build result is FAILURE
>>> 
>>> "
>>> 
>>> On Tue, Apr 24, 2018 at 1:58 PM, Ullrich Hafner <ullrich.haf...@gmail.com 
>>> <mailto:ullrich.haf...@gmail.com>> wrote:
>>> What did you try so far? Did you read the description in the wiki?
>>> 
>>> 
>>>> Am 24.04.2018 um 09:44 schrieb Vidhya Sri Soundararajan 
>>>> <yaali@gmail.com <mailto:yaali@gmail.com>>:
>>>> 
>>>> Thank you so much for the reply. Can you please elaborate your answer? I 
>>>> have installed warnings plugin in jenkins. How to use it for my job and 
>>>> how to parse the result using Clang?
>>>> 
>>>> On Monday, April 23, 2018 at 2:21:50 PM UTC+5:30, mmana...@gmail.com 
>>>> <http://gmail.com/> wrote:
>>>> How to generate report for Warnings and Errors generated from Xcode in 
>>>> Jenkins? Is there any API that would give me the count of warnings, errors 
>>&g

Re: Create iOS Warnings and Errors report in Jenkins

[Ullrich Hafner]

You can use Jenkins remote API. (Or use the xml warnings file in the build 
folder of Jenkins)

Errors are not yet reported, see JENKINS-22700.

> Am 24.04.2018 um 14:20 schrieb mManage mail <mmanagem...@gmail.com>:
> 
> I solved the issue. There is no need of Clang scan build step. It requires 
> only the post build action "Scan for compiler warnings" to capture the 
> warnings. I have selected the parser type as "Clang LLVM" and got a trend 
> graph for each build. But is there a way to get this in a json or xml file 
> saved in workspace? Also this is only for warnings. If there is any compiler 
> error, will we be able to get the report similar to this?
> 
> 
> 
> On Tue, Apr 24, 2018 at 4:20 PM, Ullrich Hafner <ullrich.haf...@gmail.com 
> <mailto:ullrich.haf...@gmail.com>> wrote:
> I can’t help with xcode but there is again a hint from the tool, did you try 
> that? This message is printed with purpose!
> 
>> xcodebuild: error: The flag -scheme or -xctestrun is required when 
>> specifying -derivedDataPath.
> 
> 
>> Am 24.04.2018 um 12:45 schrieb mManage mail <mmanagem...@gmail.com 
>> <mailto:mmanagem...@gmail.com>>:
>> 
>> Ok i got it, I installed clang and configured the path in Jenkins->Manage 
>> but getting the below error now while running the job, attaching the 
>> screenshot. Could you please help?
>> 
>> xcodebuild: error: The flag -scheme or -xctestrun is required when 
>> specifying -derivedDataPath.
>> scan-build: Removing directory 
>> '/Users/soe-admin/.jenkins/workspace/iOSTemplateJob/clangScanBuildReports/2018-04-24-161113-47610-1'
>>  because it contains no reports.
>> scan-build: No bugs found.
>> XCODEBUILD ERROR
>> Build step 'Clang Scan-Build' marked build as failure
>> 
>> 
>> 
>> 
>> 
>> 
>> On Tue, Apr 24, 2018 at 3:43 PM, mManage mail <mmanagem...@gmail.com 
>> <mailto:mmanagem...@gmail.com>> wrote:
>> I installed warnings plugin and clang scan-build plugin. I added clang 
>> scan-build as a build step and entered the target and output folder as 
>> clangScanBuildReports. Then i added a post build action to scan compiler 
>> warnings. Please refer to the attached screenshot.  I am getting the 
>> following error
>> "
>> FATAL: Unable to locate the clang scan-build installation named 'null'.  
>> Please confirm a clang installation named 'null' is defined in the jenkins 
>> global config and on each slave if the location is different than the master.
>> Build step 'Clang Scan-Build' marked build as failure
>> [WARNINGS] Skipping publisher since build result is FAILURE
>> 
>> "
>> 
>> On Tue, Apr 24, 2018 at 1:58 PM, Ullrich Hafner <ullrich.haf...@gmail.com 
>> <mailto:ullrich.haf...@gmail.com>> wrote:
>> What did you try so far? Did you read the description in the wiki?
>> 
>> 
>>> Am 24.04.2018 um 09:44 schrieb Vidhya Sri Soundararajan 
>>> <yaali@gmail.com <mailto:yaali@gmail.com>>:
>>> 
>>> Thank you so much for the reply. Can you please elaborate your answer? I 
>>> have installed warnings plugin in jenkins. How to use it for my job and how 
>>> to parse the result using Clang?
>>> 
>>> On Monday, April 23, 2018 at 2:21:50 PM UTC+5:30, mmana...@gmail.com 
>>> <http://gmail.com/> wrote:
>>> How to generate report for Warnings and Errors generated from Xcode in 
>>> Jenkins? Is there any API that would give me the count of warnings, errors 
>>> that I could use of?
>>> 
>>> --
>>> 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 
>>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/24cc293a-245a-40bc-8b0f-3391ffa34bd4%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-users/24cc293a-245a-40bc-8b0f-3391ffa34bd4%40googlegroups.com?utm_medium=email_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 fro

Re: Create iOS Warnings and Errors report in Jenkins

[Ullrich Hafner]

I can’t help with xcode but there is again a hint from the tool, did you try 
that? This message is printed with purpose!

> xcodebuild: error: The flag -scheme or -xctestrun is required when specifying 
> -derivedDataPath.


> Am 24.04.2018 um 12:45 schrieb mManage mail <mmanagem...@gmail.com>:
> 
> Ok i got it, I installed clang and configured the path in Jenkins->Manage but 
> getting the below error now while running the job, attaching the screenshot. 
> Could you please help?
> 
> xcodebuild: error: The flag -scheme or -xctestrun is required when specifying 
> -derivedDataPath.
> scan-build: Removing directory 
> '/Users/soe-admin/.jenkins/workspace/iOSTemplateJob/clangScanBuildReports/2018-04-24-161113-47610-1'
>  because it contains no reports.
> scan-build: No bugs found.
> XCODEBUILD ERROR
> Build step 'Clang Scan-Build' marked build as failure
> 
> 
> 
> 
> 
> 
> On Tue, Apr 24, 2018 at 3:43 PM, mManage mail <mmanagem...@gmail.com 
> <mailto:mmanagem...@gmail.com>> wrote:
> I installed warnings plugin and clang scan-build plugin. I added clang 
> scan-build as a build step and entered the target and output folder as 
> clangScanBuildReports. Then i added a post build action to scan compiler 
> warnings. Please refer to the attached screenshot.  I am getting the 
> following error
> "
> FATAL: Unable to locate the clang scan-build installation named 'null'.  
> Please confirm a clang installation named 'null' is defined in the jenkins 
> global config and on each slave if the location is different than the master.
> Build step 'Clang Scan-Build' marked build as failure
> [WARNINGS] Skipping publisher since build result is FAILURE
> 
> "
> 
> On Tue, Apr 24, 2018 at 1:58 PM, Ullrich Hafner <ullrich.haf...@gmail.com 
> <mailto:ullrich.haf...@gmail.com>> wrote:
> What did you try so far? Did you read the description in the wiki?
> 
> 
>> Am 24.04.2018 um 09:44 schrieb Vidhya Sri Soundararajan <yaali@gmail.com 
>> <mailto:yaali@gmail.com>>:
>> 
>> Thank you so much for the reply. Can you please elaborate your answer? I 
>> have installed warnings plugin in jenkins. How to use it for my job and how 
>> to parse the result using Clang?
>> 
>> On Monday, April 23, 2018 at 2:21:50 PM UTC+5:30, mmana...@gmail.com 
>> <http://gmail.com/> wrote:
>> How to generate report for Warnings and Errors generated from Xcode in 
>> Jenkins? Is there any API that would give me the count of warnings, errors 
>> that I could use of?
>> 
>> --
>> 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 
>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/24cc293a-245a-40bc-8b0f-3391ffa34bd4%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/24cc293a-245a-40bc-8b0f-3391ffa34bd4%40googlegroups.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/7B2A5F3F-21F7-48DE-B882-027034A1FC7B%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/7B2A5F3F-21F7-48DE-B882-027034A1FC7B%40gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CAABnZ92HZdvdK8XikEnEY5Ozf8cr6rOOfMmRWOKJ7SKNBHpkHg%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/CAABnZ92HZdvdK8XikEnEY5Ozf8cr6rOOfMmRWOKJ7SKNBHpkHg%40mail.gmail.com?utm_medium=email_so

Re: Create iOS Warnings and Errors report in Jenkins

[Ullrich Hafner]

Did you do what the error message suggest?

> Please confirm a clang installation named 'null' is defined in the jenkins 
> global config and on each slave if the location is different than the master.



> Am 24.04.2018 um 12:13 schrieb mManage mail <mmanagem...@gmail.com>:
> 
> I installed warnings plugin and clang scan-build plugin. I added clang 
> scan-build as a build step and entered the target and output folder as 
> clangScanBuildReports. Then i added a post build action to scan compiler 
> warnings. Please refer to the attached screenshot.  I am getting the 
> following error
> "
> FATAL: Unable to locate the clang scan-build installation named 'null'.  
> Please confirm a clang installation named 'null' is defined in the jenkins 
> global config and on each slave if the location is different than the master.
> Build step 'Clang Scan-Build' marked build as failure
> [WARNINGS] Skipping publisher since build result is FAILURE
> 
> "
> 
> On Tue, Apr 24, 2018 at 1:58 PM, Ullrich Hafner <ullrich.haf...@gmail.com 
> <mailto:ullrich.haf...@gmail.com>> wrote:
> What did you try so far? Did you read the description in the wiki?
> 
> 
>> Am 24.04.2018 um 09:44 schrieb Vidhya Sri Soundararajan <yaali@gmail.com 
>> <mailto:yaali@gmail.com>>:
>> 
>> Thank you so much for the reply. Can you please elaborate your answer? I 
>> have installed warnings plugin in jenkins. How to use it for my job and how 
>> to parse the result using Clang?
>> 
>> On Monday, April 23, 2018 at 2:21:50 PM UTC+5:30, mmana...@gmail.com 
>> <http://gmail.com/> wrote:
>> How to generate report for Warnings and Errors generated from Xcode in 
>> Jenkins? Is there any API that would give me the count of warnings, errors 
>> that I could use of?
>> 
>> --
>> 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 
>> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/24cc293a-245a-40bc-8b0f-3391ffa34bd4%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/24cc293a-245a-40bc-8b0f-3391ffa34bd4%40googlegroups.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/7B2A5F3F-21F7-48DE-B882-027034A1FC7B%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/7B2A5F3F-21F7-48DE-B882-027034A1FC7B%40gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-users+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CAABnZ91EGk7%3DZrS%2BsAG6r0h_QsE7hJz9Vmkf_sJAjCN9cO6pzw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-users/CAABnZ91EGk7%3DZrS%2BsAG6r0h_QsE7hJz9Vmkf_sJAjCN9cO6pzw%40mail.gmail.com?utm_medium=email_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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/B83C9D9E-7E78-411F-BBF2-F72D6E02BF8F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Create iOS Warnings and Errors report in Jenkins

[Ullrich Hafner]

What did you try so far? Did you read the description in the wiki?

> Am 24.04.2018 um 09:44 schrieb Vidhya Sri Soundararajan :
> 
> Thank you so much for the reply. Can you please elaborate your answer? I have 
> installed warnings plugin in jenkins. How to use it for my job and how to 
> parse the result using Clang?
> 
> On Monday, April 23, 2018 at 2:21:50 PM UTC+5:30, mmana...@gmail.com wrote:
> How to generate report for Warnings and Errors generated from Xcode in 
> Jenkins? Is there any API that would give me the count of warnings, errors 
> that I could use of?
> 
> --
> 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/24cc293a-245a-40bc-8b0f-3391ffa34bd4%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/7B2A5F3F-21F7-48DE-B882-027034A1FC7B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Create iOS Warnings and Errors report in Jenkins

[Ullrich Hafner]

You can use the warnings plugin to show compiler warnings. There is an parser 
for Clang (LLVM) available.

> Am 23.04.2018 um 08:45 schrieb mmanagem...@gmail.com:
> 
> How to generate report for Warnings and Errors generated from Xcode in 
> Jenkins? Is there any API that would give me the count of warnings, errors 
> that I could use of?
> 
> --
> 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/0aa7a601-8691-4b9a-8b2c-8af1cc8128fc%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/21560CED-B37C-410C-A263-F525D6414804%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Trend Graph

[Ullrich Hafner]

I this a general advice or are you using the warnings plugin in a different way 
that requires that the old behavior should be retained?

BTW: the corresponding issue is 
https://issues.jenkins-ci.org/browse/JENKINS-50551

> Am 05.04.2018 um 13:13 schrieb Artur Szostak <aszos...@partner.eso.org>:
> 
> Unless you want to make a lot of people angry, or unless there is a 
> fundamentally good reason, always make the existing behaviour the default. 
> New behaviour should be explicitly selected. If there is a good reason to 
> make new behaviour the default, there should at the very least be a 
> transition period over several plugin versions, and clear deprecation 
> warnings / mechanisms to allow for a sensible update / transition strategy.
> 
> Cheers
> 
> Artur
> 
> From: jenkinsci-users@googlegroups.com 
> <mailto:jenkinsci-users@googlegroups.com> <jenkinsci-users@googlegroups.com 
> <mailto:jenkinsci-users@googlegroups.com>> on behalf of Dan 
> <daniel.faie...@remcom.com <mailto:daniel.faie...@remcom.com>>
> Sent: 30 March 2018 15:29:25
> To: Jenkins Users
> Subject: Re: Trend Graph
> 
> Maybe I should change that so that the first build always has no new 
> warnings. What do you think? I’m not sure if I break something from other 
> peoples’ jobs if I change that…
> 
> This would solve my problem, so I'm all for it!
> For people who want existing functionality, you could add a checkbox in 
> "Configure the trend graph". Although it seems my usage makes more sense, 
> there's probably someone who disagrees. Something like:
> 
> 
> Suppress reference build
> If set warnings for the reference build are not displayed as 'new' for the 
> graph type 'Distribution of new and fixed warnings'.
> 
> 
> 
> Or you could reverse it and have
> 
> Display reference build
> 
> 
> On Thursday, March 29, 2018 at 7:43:19 PM UTC-4, Ullrich Hafner wrote:
> I think this will not work. If no previous result is found, then an empty set 
> of warnings is used as baseline, so we still get a large number of new 
> warnings. I wonder if it would make sense to change the current behavior of 
> my plugin. I must admit that marking all warnings of the first build as new 
> is not a conscious decision. Maybe I should change that so that the first 
> build always has no new warnings. What do you think? I’m not sure if I break 
> something from other peoples’ jobs if I change that…
> 
> The other suggestions about changing the graphs: this is currently not 
> supported will will never be supported with the current chart implementation. 
> In the future (*), I would like to replace the png server side rendered 
> charts with client side rendered JS charts. Then it should be easy to 
> configure these graphs on the client side.
> 
> (*) Currently this is blocked by an integration of an old Prototype.JS 
> library in Jenkins core, see 
> https://issues.jenkins-ci.org/browse/JENKINS-49319 for details
> 
> Am 29.03.2018 um 21:42 schrieb Mark Waite <mark.ea...@gmail.com 
> <http://gmail.com/>>:
> 
> What if the first build on a branch were run without calculating warnings 
> (since you intend to ignore warnings from the first build, you could choose 
> not to compute those warnings and not to report them.
> 
> After first build is complete, reconfigure the job (Jenkins UI or in the 
> Jenkinsfile if Pipeline) to report warnings.
> 
> Mark Waite
> 
> On Thu, Mar 29, 2018 at 12:26 PM Dan <daniel@remcom.com 
> <http://remcom.com/>> wrote:
> Jenkins uses a trend graph to display things like failed unit tests or 
> compilation warnings as a function of build number. Is there a way to 
> suppress only the first build OR to limit the height of the y-axis?
> 
> My company's workflow
> - create a copy of a Jenkins job for your particular branch
> - Build the branch without changes. This gives a baseline for the # of 
> warnings in the code (it has very old code, so there are a LOT)
> - The branch then automatically builds daily. New warnings introduced by the 
> developer show up in the Trend Graph.
> 
> The Trend Graph is configured to show only new or fixed warnings.
> The problem is that the 1st build introduces a ton of "new" warnings. This 
> pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after 
> that are not visible.
> 
> Solution
> If we could somehow suppress showing just that first build, while still 
> showing all subsequent builds, this would be fixed. Or, if the +Y-axis could 
> be limited to show numbers from 0-100, this would be fixed.
> 
> Is this possible?
> 
> --
> You received this message b

Re: Trend Graph

[Ullrich Hafner]

I think this will not work. If no previous result is found, then an empty set 
of warnings is used as baseline, so we still get a large number of new 
warnings. I wonder if it would make sense to change the current behavior of my 
plugin. I must admit that marking all warnings of the first build as new is not 
a conscious decision. Maybe I should change that so that the first build always 
has no new warnings. What do you think? I’m not sure if I break something from 
other peoples’ jobs if I change that…

The other suggestions about changing the graphs: this is currently not 
supported will will never be supported with the current chart implementation. 
In the future (*), I would like to replace the png server side rendered charts 
with client side rendered JS charts. Then it should be easy to configure these 
graphs on the client side.

(*) Currently this is blocked by an integration of an old Prototype.JS library 
in Jenkins core, see https://issues.jenkins-ci.org/browse/JENKINS-49319 for 
details

> Am 29.03.2018 um 21:42 schrieb Mark Waite :
> 
> What if the first build on a branch were run without calculating warnings 
> (since you intend to ignore warnings from the first build, you could choose 
> not to compute those warnings and not to report them.
> 
> After first build is complete, reconfigure the job (Jenkins UI or in the 
> Jenkinsfile if Pipeline) to report warnings.
> 
> Mark Waite
> 
> On Thu, Mar 29, 2018 at 12:26 PM Dan  > wrote:
> Jenkins uses a trend graph to display things like failed unit tests or 
> compilation warnings as a function of build number. Is there a way to 
> suppress only the first build OR to limit the height of the y-axis?
> 
> My company's workflow
> - create a copy of a Jenkins job for your particular branch
> - Build the branch without changes. This gives a baseline for the # of 
> warnings in the code (it has very old code, so there are a LOT)
> - The branch then automatically builds daily. New warnings introduced by the 
> developer show up in the Trend Graph.
> 
> The Trend Graph is configured to show only new or fixed warnings.
> The problem is that the 1st build introduces a ton of "new" warnings. This 
> pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after 
> that are not visible.
> 
> Solution
> If we could somehow suppress showing just that first build, while still 
> showing all subsequent builds, this would be fixed. Or, if the +Y-axis could 
> be limited to show numbers from 0-100, this would be fixed.
> 
> Is this possible?
> 
> --
> 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/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%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/CAO49JtGfLMfX6P_ampCegh1aKTs5uU%3D9Lt67Ag97fQApE%2BaheQ%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/80A72BD9-B8BB-46C1-B747-CC1EF297ADC8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Stage View for Freestyle Job

[Ullrich Hafner]

Which information is missing? A freestyle job already has a page for each build 
with all important post steps.

> Am 16.03.2018 um 14:36 schrieb StickSto :
> 
> Hello All,
> 
> Is it possible to get Stage View kind of Result Window to Jenkins's Freestyle 
> Job?
> 
> Or what kind of Result Windows it's possible to get into Freestyle Job?
> 
> I would like to use Freestyle Job in my case but it's normal basic Result 
> Window should contain information
> of it's Builds and Post Build Actions.
> 
> Can anyone help how to get them, thanks
> 
> Best Regards,
> 
> JH
> 
> 
> --
> 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/8c5df05a-91aa-4956-a899-883a2a4f8d6a%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/5A0510B9-E1E8-4977-BCA1-8EEC37637D5B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Java heap space

[Ullrich Hafner]

These are too many warnings for the current architecture of the plug-in, see 
https://issues.jenkins-ci.org/browse/JENKINS-1960 
<https://issues.jenkins-ci.org/browse/JENKINS-1960>.

Once the refactoring to the new analysis-model is finished, I think it would be 
possible to add an option to just count the number of warnings rather then 
creating and persisting them.

BTW: what is the reason that you are interested in tracking so many warnings?

> Am 09.02.2018 um 12:39 schrieb Consult Hyperion * <chyp...@gmail.com>:
> 
> At the last count:
> 
> 42938 Warning(s)
> 
> I did wonder if that was just too many and it was overloading something.  Is 
> that the problem?
> 
> 
> On Thursday, February 8, 2018 at 5:16:52 PM UTC, Ullrich Hafner wrote:
> How many warnings do you have?
> 
>> Am 08.02.2018 um 18:01 schrieb Consult Hyperion * <chy...@gmail.com <>>:
>> 
>> I keep getting this on a job - the worker is fine with other jobs:
>> 
>> [WARNINGS] Parsing warnings in console log with parser MSBuild
>> Skipping warnings blame since Git is the only supported SCM up to now.%n
>> FATAL: Java heap space
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.HashMap.resize(Unknown Source)
>> at java.util.HashMap.putVal(Unknown Source)
>> at java.util.HashMap.put(Unknown Source)
>> at java.util.HashSet.add(Unknown Source)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addCategory(AnnotationContainer.java:285)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:250)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAuthorName(AnnotationContainer.java:393)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:267)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addModule(AnnotationContainer.java:319)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:256)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
>> at 
>> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotations(AnnotationContainer.java:376)
>> at hudson.plugins.analysis.core.BuildResult.initialize(BuildResult.java:307)
>> at hudson.plugins.analysis.core.BuildResult.(BuildResult.java:222)
>> at hudson.plugins.warnings.WarningsResult.(WarningsResult.java:52)
>> at hudson.plugins.warnings.WarningsResult.(WarningsResult.java:46)
>> at 
>> hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:434)
>> at 
>> hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:378)
>> at 
>> hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:312)
>> at 
>> hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69)
>> at 
>> hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298)
>> at 
>> hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
>> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
>> at hudson.model.Build$BuildExecution.post2(Build.java:186)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
>> at hudson.model.Run.execute(Run.java:1749)
>> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>> at hudson.model.ResourceController.execute(ResourceController.java:97)
>> 
>> I've tried increasing the heap space (I think) with -Xmx2048M on the worker 
>> but it's not helping.  I'm wondering if the problem might be on the server 
>> instead?  It seems to start parsing warnings, get some of the way through 
>> then fall over.  Any useful suggestions gratefully received.
>> 
>> 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-use...@googlegroups.com <>.
>> To view this discussion on the 

Re: Java heap space

[Ullrich Hafner]

How many warnings do you have?

> Am 08.02.2018 um 18:01 schrieb Consult Hyperion * :
> 
> I keep getting this on a job - the worker is fine with other jobs:
> 
> [WARNINGS] Parsing warnings in console log with parser MSBuild
> Skipping warnings blame since Git is the only supported SCM up to now.%n
> FATAL: Java heap space
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.resize(Unknown Source)
> at java.util.HashMap.putVal(Unknown Source)
> at java.util.HashMap.put(Unknown Source)
> at java.util.HashSet.add(Unknown Source)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.addCategory(AnnotationContainer.java:285)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:250)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.addAuthorName(AnnotationContainer.java:393)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:267)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.addModule(AnnotationContainer.java:319)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.updateMappings(AnnotationContainer.java:256)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotation(AnnotationContainer.java:366)
> at 
> hudson.plugins.analysis.util.model.AnnotationContainer.addAnnotations(AnnotationContainer.java:376)
> at hudson.plugins.analysis.core.BuildResult.initialize(BuildResult.java:307)
> at hudson.plugins.analysis.core.BuildResult.(BuildResult.java:222)
> at hudson.plugins.warnings.WarningsResult.(WarningsResult.java:52)
> at hudson.plugins.warnings.WarningsResult.(WarningsResult.java:46)
> at 
> hudson.plugins.warnings.WarningsPublisher.annotate(WarningsPublisher.java:434)
> at 
> hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:378)
> at 
> hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:312)
> at 
> hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69)
> at 
> hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298)
> at 
> hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81)
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
> at hudson.model.Build$BuildExecution.post2(Build.java:186)
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
> at hudson.model.Run.execute(Run.java:1749)
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> at hudson.model.ResourceController.execute(ResourceController.java:97)
> 
> I've tried increasing the heap space (I think) with -Xmx2048M on the worker 
> but it's not helping.  I'm wondering if the problem might be on the server 
> instead?  It seems to start parsing warnings, get some of the way through 
> then fall over.  Any useful suggestions gratefully received.
> 
> 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/f079111d-0efb-4cff-a304-b4b6db3252d8%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/121FC146-E1FC-4798-97E1-F73BBE1E1F7B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP