> Am 21.08.2020 um 12:02 schrieb 'christop...@googlemail.com' via Jenkins Users
> :
>
>
> I have two different kinds of jobs:
> one is installing all the requirements for a job from a storage, building one
> package and collecting warnings and cppcheck results with warnings ng. Here
> everyt
To: jenkinsci-users@googlegroups.com
> Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN)
> At: Jun 11 2013 16:39:53
> How? I've had a short email conversation with the warnings plugin maintainer,
> Ulli Hafner, and he said it only does warnings: "For javac, only warnings are
>
Hi Martin, this looks like the same problem as
https://github.com/jenkinsci/findbugs-plugin/pull/3
I'm using the findbugs library to read the XML file. The library seems to
ignore the values from the XML file in custom rules.
Ulli
PS: please use the mailing lists for such question so other us
Maybe it would be good to create a bug report for FindBugs so that they will
hopefully fix that problem, soon…
Ulli
Am 14.06.2013 um 13:45 schrieb Martin :
> Ulli, I believe you are right. What obviously puzzled me was that it goes
> into the XML file with the correct rank and that it goes int
Well, you mean writing another parser that replaces the existing parser from
the Findbugs library rather than fixing it? I don't think that this is simpler
(not invented here syndrome), but if you are interested to provide a pull
request please go ahead…
I would suggest that the best thing is
Are you already using the email-ext plug-in? There you can define triggers and
jelly scripts that navigate on Jenkins's object model.
BTW: with the warnings plug-in you can define that a build is set to unstable
if there are new JSLint warnings.
Ulli
Am 17.06.2013 um 10:59 schrieb Sebastian :
What exactly is the problem or question? From the log I see that PMD is already
running and reporting 0 warnings.
If there are no warnings then you also can't navigate to the warnings.
Ulli
Am 26.06.2013 um 11:44 schrieb Tan Chen :
> Hello,
> I am really new to Jenkins. In fact I have installe
If you need to collect the test results then this is not possible.
Am 02.07.2013 um 12:59 schrieb orima...@gmail.com:
> anyone?
>
> I want to mark test in jenkins as not making build unstable if failed
>
> On Thursday, June 27, 2013 8:23:30 AM UTC+3, orim...@gmail.com wrote:
>
>
> --
> You r
Actually the analysis plugs-in expose the number of new warnings as token or
via the REST API. Can't you just use that information to trigger the email?
Ulli
Am 08.07.2013 um 17:13 schrieb Slide :
> I don't have specific knowledge of the Warnings plugin, so I don't know what
> is available.
>
That why I recommend using the *new* warnings (and not the totals). Then you
find all new warnings regardless of the total number of warnings.
These warnings are shown in the REST report:
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-remote
Hi Jean Louis,
seems that the source code still is hosted in Subversion. Or is there already a
git repository set up?
Ulli
Am 13.07.2013 um 13:40 schrieb Jean-Louis Boudart :
> Hi there,
>
> A few time ago i started EasyAnt plugin [1] for hudson/jenkins.
>
> I would like to update the plugi
> https://github.com/jenkinsci/easyant-plugin/
>
>
> 2013/7/13 Ulli Hafner
> Hi Jean Louis,
>
> seems that the source code still is hosted in Subversion. Or is there already
> a git repository set up?
>
> Ulli
>
> Am 13.07.2013 um 13:40 schrieb Jean-Lo
Can you please check if there is already an issue in Jira? If not please create
a new one. Does the problem occur in Jenkins 1.522?
Ulli
Am 13.07.2013 um 18:25 schrieb Maurice van der Pot :
> We're experiencing failures in all our builds with the below error in console
> output.
> I've been lo
See my answer in the dev-list:
> Von: Ulli Hafner
> Betreff: Aw: EasyAnt plugin
> Datum: 14. Juli 2013 12:16:53 MESZ
> An: "jenkinsci-...@googlegroups.com"
>
> It might work if you would use an LTS release as parent pom. I'm using 1.424
> for my plug-ins a
You can use the unit plug-in, it uses a similar approach:
https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin
Here you need to define a stylesheet that converts the format to a JUnit format.
Ulli
Am 19.07.2013 um 10:39 schrieb Pawel Jasinski :
> hi
>
> I am looking for a way to capture n
Am 23.07.2013 um 12:02 schrieb Roland Schulz :
> Hi,
>
> I would like to define a custom multi-line warnings parser. Searching for the
> question I have found that screenshots show a "Multi-line support" checkbox.
> Both with versions 4.27 and 418 I don't see that option. I tried a multi-line
Is your maven plugin installed and enabled?
Am 06.08.2013 um 15:06 schrieb fREW Schmidt :
> Hey guys,
>
> All of my projects are showing stack traces on the Post-build Actions.
> If I uninstall Checkstyle the problem goes away. Here is the Stack
> trace:
>
> javax.servlet.ServletException: org
I think the root cause is https://issues.jenkins-ci.org/browse/JENKINS-18654
It is already fixed in Jenkins core.
Ulli
Am 07.08.2013 um 00:43 schrieb fREW Schmidt :
> Right, I have not instaled Maven, though I'll try it tomorrow and see
> if it fixes the problem I guess.
>
> On Tue, Aug 06, 20
Good to see.
I fixed the bug in the meantime, too.
Ulli
Am 14.08.2013 um 21:37 schrieb fREW Schmidt :
> That did fix it, but it is a bug I believe.
>
> On Wed, Aug 14, 2013 at 02:29:50PM -0500, fREW Schmidt wrote:
>> I'll do it now, but it is marked as an optional dep, so this is
>> certainly
Did you restart Jenkins?
Ulli
Am 20.08.2013 um 13:01 schrieb Marek Marzec :
> Hello,
>
>
> Jenkins 1.519.
>
> In plugin I manager i switched off (untick checkbox) : Jenkins JIRA plugin
> vers 1.37 - still JIRA issues are being commented.
>
>
> Any ideas how to disable this plugin?
>
> How
The warnings plug-in does not scan js files using the JSLint scanner. It only
visualizes the results from JSLint. I.e., you need to run JSLInt in your build.
And then the plug-in will pick up these results and visualizes these on the
build page.
Ulli
Am 29.08.2013 um 11:00 schrieb Giovanni Tor
Is your maven plug-in enabled?
Ulli
Am 10.09.2013 um 10:14 schrieb amityr :
>
> Hi,
>
> I am new to jenkins.
> I installed 1.529 with a few plugins :
> AnsiColor 0.3.1
> Ant Plugin 1.2
> Build Failure Analyzer 1.5.0
> Build View Column Plugin 0.2
> built-on-column 1.1
> Configure Job
https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking
Am 13.09.2013 um 14:11 schrieb Selva Kumar :
> ERROR: Publisher JiraTestResultReporter.JiraReporter aborted due to exception
> java.lang.NullPointerException
> at JiraTestResultReporter.JiraReporter.perform(JiraReporter.java:106)
>
The missing class is part of Xerces, a required library in my plug-in. This
class should be transferred automatically to the slave by Jenkins.
Does the same job work on the master? Is the slave.jar file up to date?
Ulli
Am 13.09.2013 um 08:45 schrieb Mikael Arvids :
> Hi,
>
> I’m currently
What values are in your Java Version list box in you job configuration? Which
Java Versions are visible in Jenkins global configuration? Please use the UI
only...
Am 20.09.2013 um 15:39 schrieb Farrukh Najmi :
> Hi Guys,
>
> Initially all was well and my Jenkins config.xml was configured for j
What job type are you using? I have a JDK Listbox right above the advanced
project options section…
Am 20.09.2013 um 16:01 schrieb Farrukh Najmi :
> I do not see a Java Version list box in my job config page in UI. I have
> expanded varios Advanced section in the page but still do not see Java
om/files/tmp/screenshot.png
>
> BTW, what determines whether the java command during build uses fully
> qualified path or not?
>
> Thanks very much for your help Ulli!
>
> On 09/20/2013 10:22 AM, Ulli Hafner wrote:
>> What job type are you using? I have a JDK Listb
> On 09/20/2013 11:30 AM, Ulli Hafner wrote:
>> Hmm, I have such a list box, for maven and freestyle builds.
>>
>>
>> Am 20.09.2013 um 16:32 schrieb Farrukh Najmi :
>>
>>> I am using job type of a maven multi-module project. There is no such JDK
>&g
Jenkins can read the file but the contents are broken:
hudson.security.csrf.DefaultCrumbIssuer.PROXY_HEADER
This field cannot be set from the XML file (is missing, etc.)
Which plug-in are you using for security?
Ulli
Am 25.09.2013 um 19:00 schrieb Boris Kurktchiev :
> i keep getting org.jvn
kspace
> ${ITEM_ROOTDIR}/builds
>
> false
>
>
>
>
>
>
> 5
> 0
>
>
>
> All
> false
> false
>
>
>
> All
> 0
Thanks Johannes!
Interested in adding a small explanation in our wiki so that other users will
find that information more easily?
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-email
Ulli
Am 26.09.2013 um 17:34 schrieb Johannes Wienke
:
>
This is not possible in the moment. There is already a quite similar feature
request: https://issues.jenkins-ci.org/browse/JENKINS-18884. (We think this is
a security problem not only for anonymous users but also for users with a valid
account: these users also see the login names of other users
I'm using the repeatable to select the parsers in the warnings plug-in:
Here the the whole UI:
https://github.com/jenkinsci/warnings-plugin/blob/master/src/main/resources/hudson/plugins/warnings/WarningsPublisher/config.jelly
Is your selectable package a Describable?
Example:
https://g
What did you specify as file pattern?
Ulli
Am 22.10.2013 um 12:07 schrieb Dmitry S :
> I'm using pytest to run pep8 check:
>
> py.test --pep8 --junitxml=reports\pep8.log
>
> I setup a job to look for pep8.log file in reports\pep8.log
>
> But when i run the job I see that the path where violat
Seems that something is broken there. Please create a bug report in our issue
tracker.
Can you please check if the pep8 parser in the warnings plug-in works for your
file? If the same exceptions appears there too then maybe your input file is
somehow corrupt?
Ulli
Am 22.10.2013 um 12:37 s
I'm not sure if this is related but it seems that 1.536 changed the JSON
binding (Jenkins core) which also breaks my plug-ins:
https://issues.jenkins-ci.org/browse/JENKINS-20199
Ulli
Am 22.10.2013 um 16:41 schrieb Slide :
> Seems like something from the form is not making it through to the pos
What is in your console log? Is there no side panel link?
Ulli
Am 23.10.2013 um 10:19 schrieb Maneesh M P :
> Ok finally I am able to figure out the regular expression -> ^.*(err:)
> (.*)at(.*\.pp):(\d+)$
> But I had to change the order of mapping script strings the way it is
> assigned, that
Did you enable the collection of compiler warnings in your job?
Am 24.10.2013 um 02:23 schrieb Maneesh M P :
> I did not get that question, there was nothing in the console output. I am
> attaching the images, please take a look
>
> Thanks
> M
>
> On Wednesday, October 23, 2013 2:59:15 PM UTC
And are there messages in the console log from the warnings plugin? They start
with [WARNINGS] in the console log.
And what is shown if you select the page of a build (not the job)?
Ulli
Am 24.10.2013 um 22:11 schrieb Maneesh M P :
> Yes, I did enable the post build option for compiler warnings
Am 25.10.2013 um 00:42 schrieb Maneesh M P :
> Yes, there is a [WARNINGS] line in the console
>
> 13:36:20 Validating ./modules/xyxz/tests/init.pp ...
> 13:36:20 [WARNINGS] Parsing warnings in console log with parser
> Puppet-Error-Parser
>
I see, i.e. the parser is running. Seems that no ma
Am 30.10.2013 um 16:47 schrieb Ruben van Staveren :
> Hi,
>
> I am a Jenkins administrator for a site with not that many jobs, but these
> jobs keep a constant rate of massive compiler warnings (~9000 - 1).
> For a particular job for a software with multiple versions the per build
> build.
You can write a simple plug-in that does the job. It requires just one simple
class that gathers the information from the SCM and shows the result. (Or you
add that column class to the mercurial plug-in and create a pull request).
Ulli
Am 05.11.2013 um 07:58 schrieb Andreas Schilling
:
> Hi
Which job types are your using? Maven or Freestyle?
Did you enable the plug-in in your job?
What ist the plug-in writing in the console log?
Am 08.11.2013 um 18:47 schrieb SamL :
> Hello Folks,
>
> We have two Maven Jenkins Jobs that are not displaying the results generated
> by the findbugs
Am 13.11.2013 um 10:04 schrieb zou zy :
> Hi, All
>
> Just like said in 2.1.6 of attached file, for HelloWordBuilder plugin source
> code, the @Extension is at the inner class DescriptorImpl, rather than at the
> outer class HelloWorldBuilder itself, Why? i cannot find the answer from the
> w
All UI elements that are introduced by Jenkins-plugins can be removed by
disabling (or removing) the corresponding plugin.
I.e., the maven project type can be removed by disabling the maven plug-in.
Elements that are part of Jenkins core cannot be removed. Also, you can only
remove all the opti
This seems to be a bug in the JobConfigurationHistory Plugin. Are you using the
latest version? Then please create a new bug report.
Am 13.11.2013 um 18:43 schrieb SamL :
> Hello Folks,
>
> We are getting the following WARNING.
> Has anyone seen this issue?
> Any help would be very much appreci
Yes this is possible. Have a look at the ui examples plug-in.
BTW: please use the developer mailing list for such questions:
jenkinsci-...@googlegroups.com
Am 14.11.2013 um 11:19 schrieb Kishore RP :
> In Jenkins, Is there a way to change the value dynamically in a child combo
> box based on t
It should be quite easy to write such a column (one new simple class), maybe it
would be a good candidate for the
https://wiki.jenkins-ci.org/display/JENKINS/Extra+Columns+Plugin
I think Fred would be happy to integrate such a feature if you provide a pull
request.
Ulli
Am 14.11.2013 um 23:02
Hmm, yes, seems that http://updates.jenkins-ci.org/download/plugins/ is
outdated.
Here are all versions:
http://maven.jenkins-ci.org/content/repositories/releases/org/jvnet/hudson/plugins/warnings/
Ulli
Am 19.11.2013 um 16:20 schrieb James Howe :
> Has this stopped being maintained? I'm lo
For Maven jobs, the file name is automatically derived from the pom.
For Freestyle jobs, you can enter the filename in the advanced section.
Ulli
Am 21.11.2013 um 19:52 schrieb John D. Ament :
> All,
>
> Is it possible to tell Jenkins where to find the findbugs xml file after
> running a buil
Can you please check if the findbugs build is enabled as post build step?
Normally the plug-in should show at least one [FINDBUGS] message in the console
log. Did you look into the console log of the submodule or the whole job?
Ulli
Am 22.11.2013 um 13:17 schrieb John D. Ament :
> My results
I would suggest that you pipe the output of the pclint command through a small
script that removes the Z: from the filenames.
(Or you can use a custom parser that basically does the same as the pclint
parser and remove the Z: prefix there)
Ulli
Am 15.01.2014 um 15:51 schrieb Stijn :
> Hi,
>
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
nature 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.
>>
>> Ulli
>>
>> Am
The analysis plug-ins log their results in the console log. Is there something
printed out?
E.g. [FINDBUGS] Parsing...
Does your build produce the artifacts (e.g. FindBugs results XML file) that are
read as input by the plugins?
Ulli
Am 03.10.2012 um 17:05 schrieb Rob Withers :
> I have the
Is there a Findbugs action in your job's config.xml file?
Ulli
Am 03.10.2012 um 19:00 schrieb Rob Withers :
> There are no logs for analysis tools in the console log.
>
> Rob
>
> -Original Message----- From: Ulli Hafner
> Sent: Wednesday, October 03, 2012 12:47 P
r-events
>
> The one inside the modules directory does not have the analysis reporters
> section.
>
> Rob
>
> -Original Message- From: Ulli Hafner
> Sent: Wednesday, October 03, 2012 5:51 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis
r-events
>
> The one inside the modules directory does not have the analysis reporters
> section.
>
> Rob
>
> -Original Message- From: Ulli Hafner
> Sent: Wednesday, October 03, 2012 5:51 PM
> To: jenkinsci-users@googlegroups.com
> Subject: Re: no code analysis
e I want to call them on the
> verify step. Do you have a good link or description on how to have maven
> invoke these?
>
> Thanks,
> Rob
>
>
> -Original Message- From: Ulli Hafner
> Sent: Thursday, October 04, 2012 2:40 AM
> To: jenkinsci-users@googlegro
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 experience a massive slo
Can you please post your environment as comment in Jira:
https://issues.jenkins-ci.org/browse/JENKINS-15490
Ulli
Am Freitag, 27. Juli 2012 14:34:14 UTC+2 schrieb Kjetil Ødegaard:
>
> I'm trying to upgrade Jenkins and the PMD plugin, but I keep getting an
> exception [1] on certain Maven jobs wh
Did you enable Checkstyle and Findbugs in your build? The plug-ins only
visualize the results.
Ulli
Am 19.10.2012 um 16:26 schrieb Matt :
> Hi
> i installed plugins checkstyle and findbugs in Jenkins but nothing shows in
> dashboard.
> in the configure menu > Build Settings i check "Publish
Please create a new Jira issue and attach the whole stack trace. Does the same
error occur if your build is started on the master? Did you ensure that your
slaves are connected to the master using the latest slave.jar? What setup is
your slave using?
Ulli
Am 22.10.2012 um 02:58 schrieb bball
Monday, October 22, 2012 4:20:38 AM UTC-4, Ulli Hafner wrote:
> Please create a new Jira issue and attach the whole stack trace. Does the
> same error occur if your build is started on the master? Did you ensure that
> your slaves are connected to the master using the latest sl
I don't know how to cancel sending an email so my answer is only for the
warnings part of your mail. Maybe slide knows how to cancel the sending.
In your script you basically need a reference to one of the warnings result
actions (there is one action per parser). There is no TOKEN yet that expos
Does it work when you call 'mvn install'?
BTW: please direct development questions to the developer list…
Ulli
Am 02.11.2012 um 12:48 schrieb makiselev :
> Hi all.
>
> I tried compile Jenkins for eclipse as described in
> https://wiki.jenkins-ci.org/display/JENKINS/Building+Jenkins. But after
The warnings plug-in should pick up warnings from every compiler version.
Ulli
Am 10.12.2012 um 01:33 schrieb zw :
> Hi
>
> We installed our own java jdk and .net framework and configured them in
> Jenkins.
> When selecting compiler warning type from the drop down menu, is Jenkins
> smart eno
The violations plug-in is not part of the static analysis suite. Or are you
referring to the analysis collector plug-in? You can try to downgrade the
violations plug-in only. Does that help?
Ulli
Am 10.12.2012 um 21:37 schrieb Ryan Shoemaker :
> I updated Jenkins and all my plugins last week t
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
us
>
>
> Am 13.12.2012 um 16:02 schrieb Ulli Hafner :
>
>> 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 schne
parser configuration page is:
> file name: src\test.c
> line number: 199
> category: #550-D
>
> Project configuration uses "Scan workspace files" with pattern **/*.log
>
>
> From warnings.xml:
>
> src/test.c
> src
>
>
> -> path is not ex
The value is a regular expression that matches the actual filename (as it
appears in the console log). Note, that all paths use the unix file separator.
Can you please post one of your warnings if that does not work?
Ulli
Am 17.12.2012 um 23:00 schrieb Z W :
> Hi All
>
> We are trying to us
has removed the relative path
>>> section.
>>> However, there is no concatenation with the workspace path:
>>>> C:\programme\Jenkins\test-ci\workspace
>>>
>>>
>>> Can I do some debugging? Which class is appending the complete path?
>&
Please use the user mailing list for such emails. (And don't reply to another
unrelated mail, using a correct header will help to get more attention;-)
Did you enable PMD to report the full path of the warnings?
Ulli
Am 27.12.2012 um 19:01 schrieb punit jain :
> Hello all,
> I apologies if i
https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin
There is a GitHub link in the plug-in section..
Am 07.01.2013 um 09:24 schrieb "Levin, Ilya" :
> Hello,
>
> I was wondering where can I find ldap plugin src code?
>
> Thanks
> Why does the Checkstyle page viewer need the full paths? All it needs to do
> is output the given file name (regardless of whether it exists or not) and
> the warnings/errors for those files.
>
> If it wants to use the paths to display samples of the code, how does that
> work for old builds
:
>
> On Jan 16, 2013, at 6:31 PM, Ulli Hafner wrote:
>
>>
>>> Why does the Checkstyle page viewer need the full paths? All it needs to do
>>> is output the given file name (regardless of whether it exists or not) and
>>> the warnings/errors for those files
"Violations" in the Jenkins job as type "checkstyle"
>
> -- Tem
>
>
> On Jan 17, 2013, at 11:20 AM, Ulli Hafner wrote:
>
>> Just to make sure that we are talking about the same plug-ins:
>> Are you using the jslint and checkstyle plug-in? Or
Which plug-in/jenkins versions are you using? Which job type? Please use the
issue tracker for reporting defects.
Ulli
Am 28.01.2013 um 20:06 schrieb Z W :
> Hi All
>
> We ran a build and we got this error after successful build.
> Would the experts share their workaround to this issue ?
>
>
Hi Christoph,
I haven't changed the plug-ins for quite a while now… From which versions did
you upgrade? What Jenkins version are you using? Are the missing summaries in
maven or freestyle jobs? Are there any exceptions on the console? (Or messages
that Jenkins cannot assign some values from XM
ge are still there.
> It's just the summary which is gone.
>
> cheers
> Christoph
>
> Gesendet: Dienstag, 29. Januar 2013 um 10:38 Uhr
> Von: "Ulli Hafner"
> An: jenkinsci-users@googlegroups.com
> Betreff: Re: Checkstyle/FindBugs plugin: warning summary
ug-in, so the warnings plug-in
and the freestyle jobs should work…
Can you please file a bug report?
Ulli
Am 29.01.2013 um 11:30 schrieb Christoph Kutzinski :
> No, it neither shows for old nor for new builds.
>
> Christoph
>
> Gesendet: Dienstag, 29. Januar 2013 um 11:26 Uhr
gt;
> https://issues.jenkins-ci.org/browse/JENKINS-16518
>
> thanks
> Christoph
>
>
>
> Gesendet: Dienstag, 29. Januar 2013 um 11:55 Uhr
> Von: "Ulli Hafner"
> An: jenkinsci-users@googlegroups.com
> Betreff: Re: Checkstyle/FindBugs plugin: warning summa
Hi Gabriel,
this is not possible yet. You need to run PMD and findbugs in two different
jobs.
Ulli
Am 01.02.2013 um 10:22 schrieb "Lukacs, Gabriel" :
> Hello,
> is it possible to configure more than one PMD (Publish Pmd analysis
> results) or Findbugs (Publish Findbugs analysis results)
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 to to use the Warnings Plugin
> (http
Am 12.02.2013 um 13:23 schrieb Jan Goyvaerts :
> On Tue, Feb 12, 2013 at 1:19 PM, Ulli Hafner wrote:
> Is there no entry in the "Add post build action" drop down list that is
> called "scan for compiler warnings"?
>
> Discovered it finally - but
Am 12.02.2013 um 14:45 schrieb Jan Goyvaerts :
>
>
> On Tue, Feb 12, 2013 at 1:39 PM, Ulli Hafner wrote:
>
> Am 12.02.2013 um 13:23 schrieb Jan Goyvaerts :
>
>> On Tue, Feb 12, 2013 at 1:19 PM, Ulli Hafner
>> wrote:
>> Is there no entry in the "A
>
>
> Ok, thanks! I did't update the documentation after changing the
> visualization… (It only looks different for Java 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 see
Yes, please. If there is something what helps to describe the plugin
configuration then go ahead :-)
Thanks, Ulli
Am 13.02.2013 um 12:48 schrieb Jan Goyvaerts :
> just modify this page then ?
>
> On Tue, Feb 12, 2013 at 5:29 PM, Ulli Hafner wrote:
>>
>>
>> Ok,
i.org/browse/JENKINS-16826
>
> Thanks !
>
> On Wed, Feb 13, 2013 at 1:23 PM, Ulli Hafner wrote:
> Yes, please. If there is something what helps to describe the plugin
> configuration then go ahead :-)
>
> Thanks, Ulli
>
> Am 13.02.2013 um 12:48 schrieb Jan Goyvaerts
You can try to use use the warnings plug-in, it can scan the console log for
jslint warnings.
Ulli
Am 06.03.2013 um 18:05 schrieb John Smith :
> Hi,
>
> I'm trying to validate some Java Script as part of my Jenkins build jobs.
> I've got to the point where:
>
> 1. I've installed and configu
Seems that for one of the old builds the result file could not be not found (or
read).
What is the reason that that failure occurs now? Did you upgrade the plug-in?
Did your remove some files or builds? Or did you change some file permissions?
You can check whether every build folder contains a
You can't define the ranks on your own. Rank is a kind of "new priority"
introduced by the FindBugs team. So each bug has a constant priority and rank.
What I'm doing in my plug-in is to map either each bug rank (if the check boy
is set) or priority to one of the three plug-in priorities LOW, NO
Didn't the answer to your previous thread help?
http://jenkins.361315.n4.nabble.com/Q-How-to-use-Maven-JSLint-plugin-with-Jenkins-Violation-Plugin-tp4658337p4658374.html
Am 08.03.2013 um 10:57 schrieb John Smith :
> Hi,
>
> Does anybody know how to integrate the "jslint-maven-plugin" from
> "o
; My fault
>
>
>
> I this looks like a viable workaround. I was hoping to use the Violations
> plug in simply because I'm already using it for Java Code in the same
> project. That said, there is no particular reason why I have to use the
> Violations plugin
>
&
;
>
> Paulo
>
>
>
>
>
> On Thu, Mar 7, 2013 at 6:08 PM, Ulli Hafner wrote:
> You can't define the ranks on your own. Rank is a kind of "new priority"
> introduced by the FindBugs team. So each bug has a constant priority and
> rank. What I&#
:46:58:['classCode'] is better written in dot notation.
> My guess is that the warnings plug-in hasn't noticed the errors.
>
>
>
> On Fri, Mar 8, 2013 at 5:12 PM, Ulli Hafner wrote:
> Hmm, seems that the messages of the maven JSLint plug-in use a different
> wa
Normally, we try to use extension points for such requirements. If there is no
such extension point yet, it would be good to introduce one. Interested in
providing a corresponding pull request?
Ulli
Am 13.03.2013 um 12:37 schrieb david barker :
> Hello,
>
> I was wondering if it's possible
;
> Any idea what the problem is?
>
> Thanks
>
>
>
>
>
> On Tue, Mar 12, 2013 at 5:02 PM, John Smith
> wrote:
> Thanks for getting back to me.
>
> I'll probably go with option 3 as the quickest option ;-)
>
>
> On Tue, Mar 12, 2013 a
You can change the ordinal:
@Extension(ordinal = 100)
See JavaDoc of Extension for details.
BTW: Please use the dev list for such questions…
Ulli
Am 09.04.2013 um 14:48 schrieb Bharathi Ramalingam
:
> Hi All,
> I'm developing a build wrapper plugin which depends on the Builds user
> v
1 - 100 of 138 matches
Mail list logo
