/parser/Messages.properties for
the paths, but I also tried the exact paths you suggested.
I tried adding my code to the warnings-plugin source and building that.
This approach worked: my new parser shows up and works.
Simon
On Thursday, June 8, 2017 at 7:05:32 AM UTC-7, slide wrote:
>
>
7, slide wrote:
>
>> They are defined by creating a properties file with the messages. See
>> https://github.com/jenkinsci/warnings-plugin/blob/c5db29ed729c201e37e553521f4daf099ff36a52/src/main/resources/hudson/plugins/warnings/parser/Messages.properties#L87
>> for
>> examp
s file with the messages. See
> https://github.com/jenkinsci/warnings-plugin/blob/c5db29ed729c201e37e553521f4daf099ff36a52/src/main/resources/hudson/plugins/warnings/parser/Messages.properties#L87
> for
> examples.
>
> On Wed, Jun 7, 2017 at 5:22 PM Simon M > wrote:
>
>&g
They are defined by creating a properties file with the messages. See
https://github.com/jenkinsci/warnings-plugin/blob/c5db29ed729c201e37e553521f4daf099ff36a52/src/main/resources/hudson/plugins/warnings/parser/Messages.properties#L87
for
examples.
On Wed, Jun 7, 2017 at 5:22 PM Simon M wrote
2 PM
> org.springframework.beans.factory.support.DefaultListableBeanFactory
> preInstantiateSingletons
> INFO: Pre-instantiating singletons in
> org.springframework.beans.factory.support.DefaultListableBeanFactory@1847c74a:
>
>
> defining beans [filter,legacy]; root of fac
ugin and restarting Jenkins. I
>> checked the source and it looked like you added the @Extension to your
>> parser, so it should get pulled in once the plugin is installed. What do you
>> mean by #2? Are you asking how to use the warnings plugin in general?
>>
>> On T
at do
> you mean by #2? Are you asking how to use the warnings plugin in general?
>
>
I realized my misunderstanding which resulted in question #2.
Simon
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe fro
wrote:
> It should show up after installing your plugin and restarting Jenkins. I
> checked the source and it looked like you added the @Extension to your
> parser, so it should get pulled in once the plugin is installed. What do
> you mean by #2? Are you asking how to use the warnings
It should show up after installing your plugin and restarting Jenkins. I
checked the source and it looked like you added the @Extension to your
parser, so it should get pulled in once the plugin is installed. What do
you mean by #2? Are you asking how to use the warnings plugin in general?
On Tue
So, after getting my own log parser written and built, my next questions
are:
1. How to get it to show up when adding a new parser? What needs to be
defined for this?
2. How the input file to the parser is defined.
I would very much appreciate any advice on these topics. My present current
v
te:
>>
>> This might not be too helpful, but have you looked at the other parsers
>> that come with the plugin:
>> https://github.com/jenkinsci/warnings-plugin/tree/master/src
>> /main/java/hudson/plugins/warnings/parser
>> a good start might be the LintParser.java
&g
more examples.
Simon
On Wednesday, May 31, 2017 at 1:43:23 AM UTC-7, Knurek wrote:
>
> This might not be too helpful, but have you looked at the other parsers
> that come with the plugin:
>
> https://github.com/jenkinsci/warnings-plugin/tree/master/src/main/java/hudson/plugins/warn
This might not be too helpful, but have you looked at the other parsers
that come with the plugin:
https://github.com/jenkinsci/warnings-plugin/tree/master/src/main/java/hudson/plugins/warnings/parser
a good start might be the LintParser.java
On Wednesday, May 31, 2017 at 2:31:36 AM UTC+2
I am trying to understand how to write a new "parser" to work with the
Warnings plugin. The "parser" cannot be written by extending the
RegexpDocumentParser or RegexpLineParser because I need it to open and read
a SQLite3 database.
I have been able to write a basic plug
I have been having an issue as of late with custom parsers executing and
not being able to run the groovy script.
Groovy sandbox rejected the parsing script for parser Custom Parser:
Scripts not permitted to use method java.util.regex.MatchResult group int.
You will need to manually approve the
Hi all,
I am trying to do a user defined parser using the gui for
https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
According to documentation, it should be easy to understand, but It is not
so straight forward to me to understand what should i do.
I am far to be familiar with that
dd the parser with it:
>
> warningDesc.addGroovyParser(RuboCop)
>
> Although I'm not 100% sure :) let me know when if you try that
>
>
> On Wednesday, March 22, 2017 at 6:39:18 PM UTC+1, Alex wrote:
>>
>> Hello,
>>
>> I am trying to automate the creation of
ch 22, 2017 at 6:39:18 PM UTC+1, Alex wrote:
>
> Hello,
>
> I am trying to automate the creation of a parser for the warnings plugin.
>
> So far I have this groovy code
>
>
> import hudson.plugins.warnings.*;
> def rubocop_name = 'Rubocop'
Hello,
I am trying to automate the creation of a parser for the warnings plugin.
So far I have this groovy code
import hudson.plugins.warnings.*;
def rubocop_name = 'Rubocop';
def rubocop_regexp = "^([^:]+):(\\d+):\\d+: ([^:]): ([^:]+)\$";
def rubocop
Hi,
I still have problems using the warnings plugin for pipeline jobs.
1)
I can not use pipeline syntax wizard. It simply crashes if I add the name of my
file to scan (Scan workspace file) and get a java exception:
javax.servlet.ServletException: java.lang.NullPointerException
at
Hey!
I hope I'm posting this in the correct place, it's my first request here,
usually I can find the answers to my questions somewhere on the Web...
I'm currently trying to define a Compiler Warning with the provided Jenkins
plugin UI. I've done it several times in the past with basic regular
Hi,
Piping to a file works, but I don't want to do that, because I want the
output to appear
in the normal Jenkins job console output screen. Your guess was right, in
that the output
doesn't seem to be fully available to the warnings plugin at the time that
I called it.
I seemed to
AM, Ullrich Hafner <mailto:ullrich.haf...@gmail.com>> wrote:
> The warnings should be parsed correctly by the parser. Maybe the input is not
> yet accessible when the warnings plugin runs.
>
> Why is your log (or output) in two different files? (consoleText.txt and no
Hi,
I installed:
workflow-plugin 1.12
warnings plugin 4.51
jenkins 1.641
I used the workflow snipper generator to generate code to
invoke the warnings plugin.
I came up with the following example:
node {
writeFile(file: "a.c", text: '''
#include
#
Please, find attached a screenshot.
2015-10-13 14:39 GMT+02:00 Manuel Jesús Recena Soto :
> Maybe these examples are interesting for you:
> https://github.com/jenkinsci/warnings-plugin/pull/63
>
> The snippet generator seems work fine. Remember, you'll find the option
> under
Thank you very much.
--
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
htt
Maybe these examples are interesting for you:
https://github.com/jenkinsci/warnings-plugin/pull/63
The snippet generator seems work fine. Remember, you'll find the option
under "General Build Step".
By the way, Log Parser Plugin is not still compatible with Workflow.
Regards,
E
I already check the source code of the plugins.
But I dont know yet how to use it in the workflow. Can you please help me
with that ?
--
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
> Am 13.10.2015 um 12:27 schrieb Leon Leon :
>
> Dear Jenkins Users,
>
> I am trying to use the Warnings plugin in a Workflow job. However, since it
> is not available in the snippet generator. I am using it this way:
> step([$class: 'WarningsPublisher'
Dear Jenkins Users,
I am trying to use the Warnings plugin in a Workflow job. However, since it
is not available in the snippet generator. I am using it this way:
step([$class: 'WarningsPublisher', consoleParsers: [[parserName: 'myParser']
]])
How can I add more options to t
https://github.com/jenkinsci/analysis-core-plugin/pull/30
Użytkownik "Ullrich Hafner" napisał(a):
> Temat: Re: warnings plugin. Filtering builds for trend graph and differences
> by parameter.
> Data: 2015-05-20 0:15
> Nadawca: "Ullrich Hafner"
> Adresa
No, this is not possible.
> Am 19.05.2015 um 14:42 schrieb Jacek Tomaka :
>
> Hi,
> Does warnings plugin allow to filter builds that appear on the warning trends
> graph?
>
> We do incremental builds during the day and only full builds (in clear
> workspace) nightly.
Hi,
Does warnings plugin allow to filter builds that appear on the warning trends
graph?
We do incremental builds during the day and only full builds (in clear
workspace) nightly.
These builds differ by value of parameter BUILD_TYPE. It is either FULL or CI.
It makes little sense to
Hello,
I've just installed the nice warnings plugin for an avr-gcc project, and
configured it to scan the source as well as the console for warnings.
I've put an unused variable on purpose and in the console I have:
lambda.c: In function ‘display’:
lambda.c:59:6: warning: unuse
is-core-plugin/blob/master/src/main/java/hudson/plugins/analysis/core/AnnotationDifferencer.java>
>
> On Monday, January 19, 2015 at 1:57:59 PM UTC-5, Trinition wrote:
> We're using the Warnings Plugin
> <https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin> in our C
is-core-plugin/blob/master/src/main/java/hudson/plugins/analysis/core/AnnotationDifferencer.java>
>
> On Monday, January 19, 2015 at 1:57:59 PM UTC-5, Trinition wrote:
> We're using the Warnings Plugin
> <https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin> in our C
1:57:59 PM UTC-5, Trinition wrote:
>
> We're using the Warnings Plugin
> <https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin> in our CI
> build, and doing some time-stamp logging in our build, I've found that 1
> miunte of our 13 minute build is spent he
We're using the Warnings Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin> in our CI
build, and doing some time-stamp logging in our build, I've found that 1
miunte of our 13 minute build is spent here:
11:13.1 00:10.6 [WARNINGS] Parsing warnings in console
This functionality is already built in: you can flag a build as failed if there
are new warnings.
Am 09.05.2014 um 02:01 schrieb C dev :
> Hi,
>
> Currently we are using warnings plugin to list out all the new warnings and
> results. It looks good,
> but as the warnings kee
tokens? If not, then you
would need to enhance that plugin to support expansion of tokens from the
Token Macro plugin. It is not automatic.
On Fri, May 9, 2014 at 3:37 PM, C dev wrote:
> Hi Slide,
>
> I have my warnings plugin place and i thought these token plugins would
> extract the
Hi Slide,
I have my warnings plugin place and i thought these token plugins would
extract the info from the Warnings plugin so we can use it the way we want,
Also thought these tokens are currently available as per the document, (it
specifies to use it with the plugin name as below) If i am
The token macro plugin would need to know about the tokens you are
mentioning. They would have to be implemented as token macros in some
plugin. They aren't part of the token macro plugin by default.
On Thu, May 8, 2014 at 5:01 PM, C dev wrote:
> Hi,
>
> Currently we are using w
Hi,
Currently we are using warnings plugin to list out all the new warnings and
results. It looks good,
but as the warnings keep increasing we wanted to flag those warnings as
errors so they get immediate attention to be fixed.
So tried to install the token macro plugin which I thought would
ETA for a release that will include the change?
--
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.
For more options,
https://issues.jenkins-ci.org/browse/JENKINS-21569
On 30 January 2014 14:48, Ulli Hafner wrote:
> I see, the parsing is delegated to an extra class that does not have this
> method. Can you please add a new feature request in Jira? This is quite easy
> to implement…
>
> Ulli
>
> Am 30.01.2014 u
I see, the parsing is delegated to an extra class that does not have this
method. Can you please add a new feature request in Jira? This is quite easy to
implement…
Ulli
Am 30.01.2014 um 14:52 schrieb James Howe :
> An exception occurred during evaluation of the Groovy script: No
> signature o
An exception occurred during evaluation of the Groovy script: No
signature of method: Script1.getCurrentLine() is applicable for
argument types: () values: []
On 30 January 2014 12:28, Ulli Hafner wrote:
> You can use method getCurrentLine() in your parser when creating the new
> warning.
>
> Ull
You can use method getCurrentLine() in your parser when creating the new
warning.
Ulli
Am 30.01.2014 um 12:45 schrieb James Howe :
> If you construct a Warning() with an empty filename, then this is treated as
> being from the console log (or whichever log file it was parsing).
> How can I als
If you construct a Warning() with an empty filename, then this is treated
as being from the console log (or whichever log file it was parsing).
How can I also set the line number of the warning to the line of the input
that the regex matched?
--
You received this message because you are subscri
On Wednesday, January 15, 2014 9:51:25 AM UTC-5, Stijn wrote:
>
> Hi,
>
> I'm using pclint together with jenkins warnings plugin on linux. However,
> pclint is a windows executable executed by wine. Therefore, the output of
> pclint is something like
> Z:\media\
Hi,
>
> I'm using pclint together with jenkins warnings plugin on linux. However,
> pclint is a windows executable executed by wine. Therefore, the output of
> pclint is something like
> Z:\media\Data\workspace\pr_7315\app\common\logging\src\logger.c(91): Note
> 956: Non
Hi,
I'm using pclint together with jenkins warnings plugin on linux. However,
pclint is a windows executable executed by wine. Therefore, the output of
pclint is something like
Z:\media\Data\workspace\pr_7315\app\common\logging\src\logger.c(91): Note
956: Non const, non volatile stat
bug
> report, it should be quite easy to fix.
>
> Ulli
>
> Am Samstag, 19. Oktober 2013 schrieb Mike Hambidge :
>
>> Does anyone know if the MSBuild parser for the Warnings Plugin is
>> supposed to detection Visual Studio Code Analysis warnings? The reason I
>> ask
Yes, it should work on Visual Studio messages, too. Please file a new bug
report, it should be quite easy to fix.
Ulli
Am Samstag, 19. Oktober 2013 schrieb Mike Hambidge :
> Does anyone know if the MSBuild parser for the Warnings Plugin is supposed
> to detection Visual Studio Code An
Does anyone know if the MSBuild parser for the Warnings Plugin is supposed
to detection Visual Studio Code Analysis warnings? The reason I ask is that
I've encountered a problem where the console output for code analysis
warnings contains an extra space character that causes the regex
Toraldo :
> Hi,
>
> I've setup a new project with the latest version of warnings plugin to scan
> js file with the JsLint integrated scanner.
>
> However, it looks like that the plugin is using the wrong scanner (an XML
> one?), hence I've selected JsLint from
Hi,
I've setup a new project with the latest version of warnings plugin to scan
js file with the JsLint integrated scanner.
However, it looks like that the plugin is using the wrong scanner (an XML
one?), hence I've selected JsLint from the dropdown for files of type **/.js
The st
Hi All--
We're having an issue with one of our builds that uses the MSBuild plugin where
the Warnings plugin gives me new warnings with every build, even though they're
not new. We have a groovy query of the REST API that sends an email when
someone lets a new warning by (using Emai
gt;
> This is not directly related to the Buckminster parser, as it still fails
> with other parsers. I have Jenkins 1.504 and the warnings plugin is 4.23; OS
> is Ubuntu 32 bit.
>
> Should I file a bug report? Can I "reset" the job somehow, because I don't
>
warnings plugin is 4.23;
OS is Ubuntu 32 bit.
Should I file a bug report? Can I "reset" the job somehow, because I don't
want to lose its history?
best regards,
Vlad
[WARNINGS] Parsing warnings in console log with parser Buckminster
ERROR: Publisher hudson.plugins.warnings.WarningsPu
a warnings up to now:-)
>>>
>>> Interested in adding any missing documentation parts in the wiki?
>>>
>>> Sure ! How ? What pages ?
>>> (be aware I just know about this plugin - you seem to have much more code
>>> running out there)
>>
&
gt;
>> Sure ! How ? What pages ?
>> (be aware I just know about this plugin - you seem to have much more code
>> running out there)
>>
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
>>
>> Ulli
>>
>>
>> --
>> You rec
ware I just know about this plugin - you seem to have much more code
>> running out there)
>
> https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
>
> Ulli
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users
any missing documentation parts in the wiki?
>>
>
> Sure ! How ? What pages ?
> (be aware I just know about this plugin - you seem to have much more code
> running out there)
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
>
> Ulli
>
> -
ust know about this plugin - you seem to have much more code
> running out there)
https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
Ulli
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and
nfiguration be required…
>
>
> What's a bit confusing too is the screenshot of the plugin page:
>
>
>
> Which is presume now looks like this:
>
>
>
> Because the picture and text was different I presumed it wasn't from the
> Warnings plugin. :-)
>
>
; would definitely be good to know the user has to add one or more parsers.
>
I see, that is on my issue list for the maven plug-in: ideally there should be
no configuration be required…
>
> What's a bit confusing too is the screenshot of the plugin page:
>
>
>
> Wh
of the plugin page:
[image: Inline image 1]
Which is presume now looks like this:
[image: Inline image 2]
Because the picture and text was different I presumed it wasn't from the
Warnings plugin. :-)
So I think it's just a matter of documentation. The software works all
right ! :-)
&g
ven project, Jenkins 1.500 and Plugin 4.21.
>
>
> Ulli
>
> Am 12.02.2013 um 12:47 schrieb Jan Goyvaerts :
>
>> I'm trying to to use the Warnings Plugin
>> (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) to publish the
>> compilation warni
12.02.2013 um 12:47 schrieb Jan Goyvaerts :
>
> I'm trying to to use the Warnings Plugin (
> https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) to publish
> the compilation warnings - obviously. :-)
>
> The problem is that no warnings show at all. Neither is there
Is there no entry in the "Add post build action" drop down list that is called
"scan for compiler warnings"?
Are you using a maven or freestyle job type? Which Jenkins and warnings version?
Ulli
Am 12.02.2013 um 12:47 schrieb Jan Goyvaerts :
> I'm trying t
I'm trying to to use the Warnings Plugin (
https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) to publish the
compilation warnings - obviously. :-)
The problem is that no warnings show at all. Neither is there an option in
the job configuration to publish those warnings. As it i
>>
>>>>> Where is the src folder located?
>>>>> C:\programme\Jenkins\test-ci\workspace\src?
>>>>>
>>>>> My plug-in concatenates the workspace path and the found path in the
>>>>> warning, which results in yo
i\workspace\src?
>>>>
>>>> My plug-in concatenates the workspace path and the found path in the
>>>> warning, which results in your case to
>>>> C:\programme\Jenkins\test-ci\workspace\..\..\..\src\test.c
>>>> A simple solution would be to strip off the relative
n would be to strip off the relative path section in your
>>> groovy parser so that the concatenation works.
>>>
>>> Ulli
>>>
>>> Am 15.12.2012 um 11:37 schrieb Markus Schneider :
>>>
>>>> Hi Ulli,
>>>>
>>>>
n in your
>> groovy parser so that the concatenation works.
>>
>> Ulli
>>
>> Am 15.12.2012 um 11:37 schrieb Markus Schneider :
>>
>>> Hi Ulli,
>>>
>>>
>>> thanks for your help. Here is some more information:
>>>
>> Hi Ulli,
>>
>>
>> thanks for your help. Here is some more information:
>>
>> Jenkins: V1.493
>> Warnings-Plugin: V4.18
>> Static Analysis Utilities: V1.48
>> OS: Windows XP
>>
>>
>> Workspace Path: C:\programme\Jenkins\t
would be to strip off the relative path section in your
groovy parser so that the concatenation works.
Ulli
Am 15.12.2012 um 11:37 schrieb Markus Schneider :
> Hi Ulli,
>
>
> thanks for your help. Here is some more information:
>
> Jenkins: V1.493
> Warnings-Plugi
Hi Ulli,
thanks for your help. Here is some more information:
Jenkins: V1.493
Warnings-Plugin: V4.18
Static Analysis Utilities: V1.48
OS: Windows XP
Workspace Path: C:\programme\Jenkins\test-ci\workspace
Example Warning: "..\..\..\src\test.c", line 199: warning #550-D: variable
Hmm, I thought that the files should contain at least the exception string.
Can you please provide some more information?
What is your workspace path? Can you provide an example of a warning from the
build console log? What is the corresponding warning result in
warnings-[yourparsername].xml in
I have tried it, but the parser throughs an error not knowing "$JenkinsHome"
string.
Am 13.12.2012 um 04:04 schrieb "Strausser, Barrett"
:
> You could probably do $JenkinsHome + "/jobs/" + $WorkSpace
>
>
>
>
> On Wed, Dec 12, 2012 at 5:58 PM, schneim wrote:
>> Hello,
>>
>>
>> I have cr
Hello Ulli,
Yes the relative path does not work for me. The tmp files are generated, but
are empty.
Do I need a special configuration?
Markus
Am 13.12.2012 um 16:02 schrieb Ulli Hafner :
> Actually, a relative path (starting from the workspace root) should be
> resolved automatically. Doe
Actually, a relative path (starting from the workspace root) should be resolved
automatically. Does this not work in your case?
Ulli
Am 12.12.2012 um 23:58 schrieb schneim :
> Hello,
>
>
> I have created a custom warning parser. This works quite well. However, I
> have trouble to display the
You could probably do $JenkinsHome + "/jobs/" + $WorkSpace
On Wed, Dec 12, 2012 at 5:58 PM, schneim wrote:
> Hello,
>
>
> I have created a custom warning parser. This works quite well. However, I
> have trouble to display the content of the source files.
>
> I found out the path in the warnin
Hello,
I have created a custom warning parser. This works quite well. However, I
have trouble to display the content of the source files.
I found out the path in the warning is only relative to the workspace path,
e.g. $WORKSPACE/src/file.c
But for displaying the source file, the plugin req
Hi All--
We have a project that's behaving inconsistently with the warnings plugin. It's
an Xcode project, using the clang/LLVM parser.
Environment:
Jenkins 1.478
Warnings Plugin: 4.17
Xcode 4.4
What we're running into is that this particular project is marking warnings as
d then look at the API's available for
>> that to get the information you need. If there is a WARNINGS_NEW token, then
>> you could look at how the Java creates that token and go from there.
>>
>> slide
>>
>> On Tue, Oct 30, 2012 at 8:57 AM, Fisher, Allen wrote
a creates that token and go from there.
slide
On Tue, Oct 30, 2012 at 8:57 AM, Fisher, Allen
mailto:afis...@makemusic.com>> wrote:
Hi List--
We're on a tear to clean up warnings in our applications. The Warnings Plugin
has been invaluable in that effort (Thanks, Ulli!). It's goi
, Oct 30, 2012 at 8:57 AM, Fisher, Allen
mailto:afis...@makemusic.com>> wrote:
Hi List--
We're on a tear to clean up warnings in our applications. The Warnings Plugin
has been invaluable in that effort (Thanks, Ulli!). It's going to be a while
until we can turn "Warnings a
t 8:57 AM, Fisher, Allen wrote:
> Hi List--
>
> We're on a tear to clean up warnings in our applications. The Warnings Plugin
> has been invaluable in that effort (Thanks, Ulli!). It's going to be a while
> until we can turn "Warnings as errors" as a global option,
_NEW token, then you could look at how the Java creates that token
and go from there.
slide
On Tue, Oct 30, 2012 at 8:57 AM, Fisher, Allen wrote:
> Hi List--
>
> We're on a tear to clean up warnings in our applications. The Warnings
> Plugin has been invaluable in that effort (Th
Hi List--
We're on a tear to clean up warnings in our applications. The Warnings Plugin
has been invaluable in that effort (Thanks, Ulli!). It's going to be a while
until we can turn "Warnings as errors" as a global option, so in the mean time,
we want to alert the dev t
You can see which changes are in a release in github:
https://github.com/jenkinsci/warnings-plugin/commits/master
The issue you are referring to is part of release warning@4.15 and
analysis-core@1.45.
Ulli
Am 04.10.2012 um 16:01 schrieb Jon Payne :
> Hi all,
>
> We've experi
Hi all,
We've experience a massive slow down in parsing of warnings with a
custom regexp. It appears that the issue was fixed but that this patch
never made it into a release as far as I can tell:
Warnings Plugin: Slow Performance on customized parsing rules with
Regular Expression &
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mark Waite
Sent: 24 August 2012 15:14
To: jenkinsci-users@googlegroups.com
Subject: Re: Warnings plugin; Can I exclude certain warnings?
Couldn't you also exclude the generation of the deprecation warnings from your
compilation command
om: "matthew.web...@diamond.ac.uk"
>To: jenkinsci-users@googlegroups.com
>Sent: Friday, August 24, 2012 8:12 AM
>Subject: RE: Warnings plugin; Can I exclude certain warnings?
>
>Thanks for the comprehensive reply, Ulli.
>
>> -Original Message-
>> From
Thanks for the comprehensive reply, Ulli.
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ullrich
> Hafner
> Sent: 24 August 2012 15:02
> To: jenkinsci-users@googlegroups.com
> Subject: Re: W
On 08/24/2012 11:20 AM, matthew.web...@diamond.ac.uk wrote:
> The Jenkins Warnings plugin
> (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) allows us to
> select (via a regex) which files we want to analyse. However, I could not see
> any way to exclude certain warning
The Jenkins Warnings plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin) allows us to
select (via a regex) which files we want to analyse. However, I could not see
any way to exclude certain warnings we are not interested in. Can this be done?
Use case: We have a large, old
Hi,
Have you checked "Run always" in the advanced configuration?
By default, warnings-plugin collects warnings
only if a build finishes successfully.
So, there are no warnings if a build fails.
akihirox
2012/7/20 rb512
> I installed the warnings plugin and have this configuratio
1 - 100 of 125 matches
Mail list logo
