[JIRA] [svnmerge] (JENKINS-12495) svnmerge fails when running on a Jenkins slave
Indra Gunawan commented on JENKINS-12495 svnmerge fails when running on a Jenkins slave HI Hugues, Rebasing always works. Integration now is failing every time after it failed once regardless of which slave it was executed. The exception appeared pretty quickly as post-build action (integrate to upstream if build is successful). I do not have access to the Apache SVN server logs since it is a centralized corporate SVN Server setup and maintained by the SCMCI IT team. May I know your setup, which version of Jenkins and what slave are you running successfully? May I know the SVN commands used by the integration to upstream (I tried Jigomerge script but it is unreliable). I am hoping the fix for svnmerge will resolve and deliver pre-merge validation between feature and main branch as asked by development team. Here is the list of plugin installed (on Jenkins running version 1.509.4): Plugin Name: mailer Plugin Version: 1.4 Plugin Name: external-monitor-job Plugin Version: 1.1 Plugin Name: ldap Plugin Version: 1.1 Plugin Name: pam-auth Plugin Version: 1.0 Plugin Name: credentials Plugin Version: 1.10 Plugin Name: ssh-credentials Plugin Version: 1.6.1 Plugin Name: scm-api Plugin Version: 0.2 Plugin Name: subversion Plugin Version: 2.2 Plugin Name: javadoc Plugin Version: 1.0 Plugin Name: token-macro Plugin Version: 1.8.1 Plugin Name: maven-plugin Plugin Version: 1.509.4 Plugin Name: ant Plugin Version: 1.1 Plugin Name: cvs Plugin Version: 1.6 Plugin Name: promoted-builds Plugin Version: 1.9 Plugin Name: run-condition Plugin Version: 1.0 Plugin Name: conditional-buildstep Plugin Version: 1.3.1 Plugin Name: parameterized-trigger Plugin Version: 2.21 Plugin Name: copyartifact Plugin Version: 1.21 Plugin Name: promoted-builds-simple Plugin Version: 1.9 Plugin Name: built-on-column Plugin Version: 1.1 Plugin Name: dashboard-view Plugin Version: 1.8.2 Plugin Name: cobertura Plugin Version: 1.3 Plugin Name: email-ext Plugin Version: 2.6 Plugin Name: build-timeout Plugin Version: 1.6 Plugin Name: configurationslicing Plugin Version: 1.28.1 Plugin Name: git Plugin Version: 1.1.6 Plugin Name: m2release Plugin Version: 0.12.0 Plugin Name: workspace-periodic-purge Plugin Version: 0.2.1 Plugin Name: timestamper Plugin Version: 1.5.2 Plugin Name: translation Plugin Version: 1.10 Plugin Name: xvnc Plugin Version: 1.10 Plugin Name: ws-cleanup Plugin Version: 0.20 Plugin Name: envinject Plugin Version: 1.89 Plugin Name: groovy Plugin Version: 1.14 Plugin Name: flexible-publish Plugin Version: 0.12 Plugin Name: any-buildstep Plugin Version: 0.1 Plugin Name: svnmerge Plugin Version: 2.0.4 Plugin Name: ruby Plugin Version: 1.2 Plugin Name: publish-over-ssh Plugin Version: 1.10 Plugin Name: ssh-slaves Plugin Version: 1.5 Plugin Name: extended-read-permission Plugin Version: 1.0 Plugin Name: analysis-core Plugin Version: 1.9 Plugin Name: checkstyle Plugin Version: 3.7 Plugin Name: dry Plugin Version: 2.7 Plugin Name: findbugs Plugin Version: 4.10 Plugin Name: pmd Plugin Version: 3.7 Plugin Name: analysis-collector Plugin Version: 1.6 Plugin Name: audit-trail Plugin Version: 1.4 Plugin Name: dependencyanalyzer Plugin Version: 0.5 Plugin Name: description-setter Plugin Version: 1.6 Plugin Name: disk-usage Plugin Version: 0.11 Plugin Name: downstream-buildview Plugin Version: 1.4 Plugin Name: downstream-ext Plugin Version: 1.6
[JIRA] [findbugs] (JENKINS-21974) Publish pmd analysis results
Ulli Hafner commented on JENKINS-21974 Publish pmd analysis results Hmm, I don't see what I can do here in my plug-in... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-21569) Expose current input line in groovy script
SCM/JIRA link daemon commented on JENKINS-21569 Expose current input line in groovy script Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/GroovyParser.java src/main/java/hudson/plugins/warnings/parser/GroovyExpressionMatcher.java http://jenkins-ci.org/commit/warnings-plugin/14b3ce92f80a51778b37e2eef44687897c14d562 Log: FIXED JENKINS-21569 Expose variable lineNumber also when validating the script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-21569) Expose current input line in groovy script
SCM/JIRA link daemon resolved JENKINS-21569 as Fixed Expose current input line in groovy script Change By: SCM/JIRA link daemon (08/Mar/14 9:38 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-21256) Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
Ulli Hafner commented on JENKINS-21256 Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Hmm, I still can't reproduce this problem. I'm now testing on 1.553: both of my analysis jobs (maven and freestyle) run without problems on Mac OS X (Master) and Ubuntu (Slave). It makes no difference if the job is on master or slave. I will try to shade this library, maybe that helps... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring] (JENKINS-21967) Node monitoring links are broken -- they don't use the proper root URL
evernat assigned JENKINS-21967 to evernat Node monitoring links are broken -- they dont use the proper root URL Change By: evernat (08/Mar/14 10:24 AM) Assignee: evernat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring] (JENKINS-21967) Node monitoring links are broken -- they don't use the proper root URL
evernat commented on JENKINS-21967 Node monitoring links are broken -- they dont use the proper root URL This is probably fixed by the following commit (but after v1.49.0, not yet released) https://github.com/jenkinsci/monitoring-plugin/commit/00a88984d861b347731b36023556d1527555f1db Please test v1.50.0, when it is released some day near end of March, and report here. You may also download a nightly build including the fix, from https://javamelody.ci.cloudbees.com/job/jenkins%20plugin/ws/target/monitoring.hpi Note: This link seems to me simpler than https://jenkins.ci.cloudbees.com/job/plugins/job/monitoring-plugin/org.jvnet.hudson.plugins$monitoring/lastSuccessfulBuild/artifact/org.jvnet.hudson.plugins/monitoring/1.50.0-SNAPSHOT/monitoring-1.50.0-SNAPSHOT.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-18951) Problems with too long paths
Mark Waite commented on JENKINS-18951 Problems with too long paths The msysgit development team has implemented what appears to be a solution in msysgit 1.9.0. It appears that the solution needs to be specifically enabled, but it may allow you to resolve this problem by installing msystgit 1.9.0 and running git config --global core.longpaths true Refer to https://github.com/msysgit/git/commit/c5f98452e98dca292c615000df7973ead63cf29b for more details on the option. You should probably only enable that option if you encounter the problem, since the msysgit people warn that there may be compatibility issues with other tools when longpaths are enabled in core git. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-21256) Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
SCM/JIRA link daemon commented on JENKINS-21256 Findbug: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory Code changed in jenkins User: Ulli Hafner Path: library/library.iml library/pom.xml library/upload-pom.xml library/upload.sh http://jenkins-ci.org/commit/findbugs-plugin/1ba7db7e2eecfe750f4a50cd8d1ba3191ac01132 Log: JENKINS-21256 Integrate dom4j into shaded library. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-21569) Expose current input line in groovy script
SCM/JIRA link daemon commented on JENKINS-21569 Expose current input line in groovy script Code changed in jenkins User: Ulli Hafner Path: warnings http://jenkins-ci.org/commit/analysis-suite-plugin/cb1d3e4b9c59fc693064952ba2c1c8b5dce495b1 Log: FIXED JENKINS-21569 Expose variable lineNumber also when validating the script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22085) git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+)
Sergey P commented on JENKINS-22085 git plugin should allow perform clone with --single-branch parameter to speed up (requires git 1.7.10+) Yes, there should be gain from using --single-branch even when using --reference and it depends on the project history. If there are many heavy-weight branches and the project have long history - then --single-branch option could speed up project cloning significantly. --reference can just minimize network load on loading objects as I understand. I cloned git module source code and took a look at it. My estimate for completing this task (even w/o tests) is many hours, because I'm not familiar with Java and the coding style seems pretty odd for me. That's why I decided to create a task. For some who is familiar with Java and with git module code it could took max few hours (10 minutes of coding, and the rest for debugging, writing tests etc.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I think I fixed the case of exceptions during post-commit notifications (notifyCommit): https://github.com/daniel-beck/subversion-plugin/tree/notify-commit-external-credentials https://github.com/daniel-beck/subversion-plugin/commit/aabd40a550461b08296ff3e971c80915ba22d9e0 Have never seen the specific exception stack trace from the original report, so I don't know whether that is also resolved (but I doubt it). I resolved exceptions during polling by specifying additional credentials. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck
edited a comment on JENKINS-21785
Check for changes in folders linked via svn:externals fails due to missing credentials
I think I fixed the case of exceptions during post-commit notifications (notifyCommit):
https://github.com/daniel-beck/subversion-plugin/tree/notify-commit-external-credentials
https://github.com/daniel-beck/subversion-plugin/commit/aabd40a550461b08296ff3e971c80915ba22d9e0
(not a PR because it's not nice enough; feel free to build on this)
Have never seen the specific exception stack trace from the original report, so I don't know whether that is also resolved (but I doubt it).
To be specific, this is the case I resolved with this change:
1. Set up an SVN repo, anywhere. Can be locally file://...; no auth required.
2. Add an external somewhere that required credentials for access (below I used a repo accessed via HTTPS)
3. Check out the first repo
4. Build once to get the 'WARNING: The following realms could not be authenticated'
5. Configure additional credential for the realm it complains about, build again
6. No warning this time, external gets checked out
7. Script console:
def p = Jenkins.instance.getItemByFullName('jobname')
p.scm.getProjectLocations(p).findAll { it.remote.startsWith('https://') }.each { println it.getUUID(p) }
Result
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/... failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148)
at hudson.scm.SubversionSCM$ModuleLocation.getUUID(SubversionSCM.java:2707)
at (user script)
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32)
at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185)
at hudson.scm.FilterSVNAuthenticationManager.getFirstAuthentication(FilterSVNAuthenticationManager.java:35)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382)
... 89 more
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17363) Ludicrously slow load time [with lazyloading]
SCM/JIRA link daemon commented on JENKINS-17363 Ludicrously slow load time [with lazyloading] Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckResult.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckSourceContainer.java src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/index.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/summary.jelly http://jenkins-ci.org/commit/cppcheck-plugin/5db2c791e4ceb93f5cafce525ddbde5047aa0b97 Log: JENKINS-17363 Ludicrously slow load time with lazyloading JENKINS-19437 Implement load on demand functionality in Cppcheck Lazy loaded details are stored in CppcheckResult member variable and never released by Java garbace collector since a reference to them exists forever. All build.xml files are loaded during Jenkins startup and never released, CppcheckResult objects are part of them. This is kind of a memory leak. The update will cause slight lower performance but releasing of the memory is much more important for long run tasks/daemons/servers. Method lazyLoadSourceContainer() updated to return the data instead of their caching in a member variable. If cached CppcheckSourceContainer object can't be loaded, an empty one will be created. Different constructor used to remove unnecessary exception catches. Recently added related if removed from CppcheckSourceContainer. Condition moved from index.jelly to summary.jelly to be able to reuse the data and remove one unnecessary loading (performance). Construction "key = +key" has no meaning, updated to "+key" to resolve a warning. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-21928) Redesign of results page
SCM/JIRA link daemon
commented on JENKINS-21928
Redesign of results page
Code changed in jenkins
User: Michal Turek
Path:
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckResult.java
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckBuildAction/statistics.jelly
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckBuildAction/summary.jelly
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/details.jelly
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/index.jelly
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/summary.jelly
http://jenkins-ci.org/commit/cppcheck-plugin/9335f6c706ef9afc2887411320bc306fe4d32a32
Log:
JENKINS-21928 Redesign of results page
Table in buildaction/summary.jelly extracted to a separate file and reused in the results page. This table uses rows instead of columns so it is better readable and supports sorting, it also contains more information (delta).
"Errors Trend" removed, it is part of the summary.
"Cppcheck Engine versions" updated from one cell table to a simple paragraph.
summary.jelly renamed to details.jelly, the file contains details and not summary.
Wrapping of long lines is now possible in the details table to remove horizontal scroll bar.
Column headers renamed in the details table to look more like words instead of identifiers.
The tables have their widths instead of 100% width of the page.
Missing support for translations ${%Text} implemented.
Function getNumberNewErrorsFromPreviousBuild() is now unused so it was removed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
SCM/JIRA link daemon commented on JENKINS-17450 warning and performance not counted Code changed in jenkins User: Michal Turek Path: src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckBuildAction.java src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckPublisher.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckBuildAction.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckParserResult.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckProjectAction.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckReport.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckResult.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckStatistics.java src/main/java/org/jenkinsci/plugins/cppcheck/config/CppcheckConfigGraph.java src/main/java/org/jenkinsci/plugins/cppcheck/config/CppcheckConfigSeverityEvaluation.java src/main/java/org/jenkinsci/plugins/cppcheck/parser/CppcheckParser.java src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckBuildAction/statistics.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckProjectAction/floatingBox.jelly src/main/resources/org/jenkinsci/plugins/cppcheck/Messages.properties src/main/resources/util/thresholds.jelly http://jenkins-ci.org/commit/cppcheck-plugin/2bb2ba06bd5b844a192a57b66e41acf7bbb17900 Log: JENKINS-17450 "warning" and "performance" not counted The graph doesn't consider "No Category" and whole plugin doesn't work with "portability" severity at all. "No category" and "portability" severities added at all places in the code where other severities are used. Configuration files now contain these additional values. Align of the displayed severities updated on the configuration page to use 2 rows and 4 columns. CppcheckParser is now able to parse the portability severity correctly, it used incorrect "no category". This is only for report version 2, version 1 doesn't output it. REST API extended to contain portability severity too. Legend "Severity 'SEVERITY'" in the graph updated to equivalent but much shorter "SEVERITY". There is more space for the data in the trend now. Non-parametric constructor added to CppcheckStatistics class to simplify creation of empty instance. Support for localization implemented at many places instead of hardcoded strings. Incorrect @SuppressWarnings anotations removed to fix compiler warnings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-22073) ProjectAction should render graph, optimize build.xml size
SCM/JIRA link daemon commented on JENKINS-22073 ProjectAction should render graph, optimize build.xml size Code changed in jenkins User: Michal Turek Path: src/main/java/org/jenkinsci/plugins/cppcheck/util/CppcheckBuildResultEvaluator.java http://jenkins-ci.org/commit/cppcheck-plugin/229cd1b28a9d795dadffdbc5f9066694e6f48226 Log: JENKINS-22073 ProjectAction should render graph, optimize build.xml size Forgotten unsaved file commited. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-19437) Implement load on demand functionality in Cppcheck
SCM/JIRA link daemon
commented on JENKINS-19437
Implement load on demand functionality in Cppcheck
Code changed in jenkins
User: Michal Turek
Path:
pom.xml
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckBuildAction.java
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckReport.java
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckResult.java
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckSourceContainer.java
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckStatistics.java
src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckSummary.java
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/index.jelly
src/main/resources/tabview/main.jelly
http://jenkins-ci.org/commit/cppcheck-plugin/e9122560bfc6944395c4a72a628310516a90bf5e
Log:
JENKINS-17363 Ludicrously slow load time with lazyloading
JENKINS-19437 Implement load on demand functionality in Cppcheck
All details from Cppcheck report is stored to build.xml which is wrong. The file quickly grows with many findings and causes performance and memory issues.
Storing of the details to external file cppcheck_details.xml and their lazy loading implemented to fix the issue. File build.xml now contains only small statitistics neccessary for trend graph and build summary.
There is no need to store CppcheckReport during the build at all, its content is fully dupplicated in CppcheckSourceContainer. CppcheckStatistics has nearly identical interface so it can be used instead of CppcheckReport most of time.
Incorrect uses of @SuppressWarnings("unused") removed to solve compiler warnings.
Cppcheck tool version is stored to build.xml together with CppcheckStatistics now. This fixes a bug in the details page, the information was expected in CppcheckReport but its field is transient so the information was never stored/loaded and displayed.
Content of tabview/main.jelly moved dirrectly to CppcheckResult/index.jelly, include removed. This was probably only a historical location.
New developer added to pom.xml.
Several TODOs unrelated to this commit added to the code, they will be fixed in future.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-22073) ProjectAction should render graph, optimize build.xml size
Michal Turek closed JENKINS-22073 as Fixed ProjectAction should render graph, optimize build.xml size Change By: Michal Turek (08/Mar/14 12:55 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-21927) Redesign of build summary page
Michal Turek resolved JENKINS-21927 as Fixed Redesign of build summary page Implemented, will be released in version 1.15. Change By: Michal Turek (08/Mar/14 12:58 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-21927) Redesign of build summary page
Michal Turek closed JENKINS-21927 as Fixed Redesign of build summary page Change By: Michal Turek (08/Mar/14 12:59 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-21714) More data from REST API
Michal Turek started work on JENKINS-21714 More data from REST API Change By: Michal Turek (08/Mar/14 1:01 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-21714) More data from REST API
Michal Turek closed JENKINS-21714 as Wont Fix More data from REST API Change By: Michal Turek (08/Mar/14 1:02 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17363) Ludicrously slow load time [with lazyloading]
Michal Turek closed JENKINS-17363 as Fixed Ludicrously slow load time [with lazyloading] Change By: Michal Turek (08/Mar/14 1:10 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17363) Ludicrously slow load time [with lazyloading]
Michal Turek resolved JENKINS-17363 as Fixed Ludicrously slow load time [with lazyloading] Fixed, will be released in version 1.15. Change By: Michal Turek (08/Mar/14 1:10 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-19437) Implement load on demand functionality in Cppcheck
Michal Turek resolved JENKINS-19437 as Fixed Implement load on demand functionality in Cppcheck Fixed, will be released in version 1.15. Change By: Michal Turek (08/Mar/14 1:11 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-19437) Implement load on demand functionality in Cppcheck
Michal Turek closed JENKINS-19437 as Fixed Implement load on demand functionality in Cppcheck Change By: Michal Turek (08/Mar/14 1:11 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
Michal Turek resolved JENKINS-17540 as Fixed ConversionException reading build.xml Impossible to reproduce, probably fixed by JENKINS-12124. Change By: Michal Turek (08/Mar/14 1:28 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
Michal Turek closed JENKINS-17540 as Fixed ConversionException reading build.xml Change By: Michal Turek (08/Mar/14 1:29 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-17450) warning and performance not counted
Michal Turek closed JENKINS-17450 as Fixed warning and performance not counted Change By: Michal Turek (08/Mar/14 1:37 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-14481) [cppcheck] Quickly identify only the new errors
Michal Turek commented on JENKINS-14481 [cppcheck] Quickly identify only the new errors I'm thinking about a similar approach used in TODOs Plugin. There is a screenshot of the Results table on that page. What do you think? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
Michal Turek closed JENKINS-21346 as Fixed Not working with cppcheck 1.63 Change By: Michal Turek (08/Mar/14 2:01 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-16700) [cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
Michal Turek assigned JENKINS-16700 to Michal Turek [cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException Change By: Michal Turek (08/Mar/14 2:18 PM) Assignee: GregoryBoissinot MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-16700) [cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
Michal Turek started work on JENKINS-16700 [cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException Change By: Michal Turek (08/Mar/14 2:18 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22096) Raw HTML Description: Can't use custom URL scheme
Francis Labrie created JENKINS-22096 Raw HTML Description: Cant use custom URL scheme Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 08/Mar/14 3:06 PM Description: When rendered, all custom URL schemes used in a tags are erased. For example, the docs-for-xcode scheme below: pClick to a href="" class="code-quote">"docs-for-xcode://http%3A%2F%2Fcocoadocs.org%2Fdocsets%2FAFNetworking%2Fxcode-docset.atom"add to Xcode/a (via a href="" class="code-quote">"http://documancer.com/xcode/"Docs for Xcode/a)/p It would be useful to allow them to ease some tool interactions. This support could be controlled with a checkbox in the security settings. Environment: OS X 10.9.2 Mavericks Project: Jenkins Priority: Major Reporter: Francis Labrie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22017) Git client: NoClassDefFoundError
Mark Waite commented on JENKINS-22017 Git client: NoClassDefFoundError I'm reasonably confident this is an issue in core, rather than an issue with the git-client plugin. I don't know if it is related to class loading, or to interactions with some other plugin. Could you provide the list of all plugins installed on your system, and show which of the plugins are disabled? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22017) Git client: NoClassDefFoundError
Mark Waite updated JENKINS-22017 Git client: NoClassDefFoundError Change By: Mark Waite (08/Mar/14 3:12 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-18029) Selected line with static analysis violation is hidden because breadcrumb covers it
Michal Turek updated JENKINS-18029 Selected line with static analysis violation is hidden because breadcrumb covers it The task description updated to contain an information. Change By: Michal Turek (08/Mar/14 3:15 PM) Summary: InCppCheckpluginselected Selected linewithstaticanalysisviolationishiddenbecausebreadcrumbcoversit Assignee: GregoryBoissinot MichalTurek Affects Version/s: current Environment: All Description: IfalinenumberinCppcheckResultsisclickedto see self-explained therelatedcode,theresultingpagewillscrollexactlytothisline.Itisthefirstdisplayedlineonthescreen.Everythingiscorrect,butitwouldbebetterifthepagescrollede.g.10linesabovetobeabletoseethecontexttoo.NewerversionsofJenkinsshowabreadcrumbnavigationontopofthescreen,thatevenhidesthehighlightedlinewhichisconfusing.Seetheattached screenshots . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-18029) Selected line with static analysis violation is hidden because breadcrumb covers it
Michal Turek resolved JENKINS-18029 as Fixed Selected line with static analysis violation is hidden because breadcrumb covers it Fixed, will be released in version 1.15. Change By: Michal Turek (08/Mar/14 3:25 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-18029) Selected line with static analysis violation is hidden because breadcrumb covers it
SCM/JIRA link daemon
commented on JENKINS-18029
Selected line with static analysis violation is hidden because breadcrumb covers it
Code changed in jenkins
User: Michal Turek
Path:
src/main/java/com/thalesgroup/hudson/plugins/cppcheck/CppcheckSource.java
src/main/java/com/thalesgroup/hudson/plugins/cppcheck/model/CppcheckFile.java
src/main/resources/org/jenkinsci/plugins/cppcheck/CppcheckResult/details.jelly
http://jenkins-ci.org/commit/cppcheck-plugin/70008f01f202df6f76d068551c2dffaaae0578f2
Log:
JENKINS-18029 Selected line with static analysis violation is hidden because breadcrumb covers it
The page with source code now scrolls 10 lines above the highlighted one to be able to see the context.
@SuppressWarnings("unused") removed to solve compiler warnings.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
SCM/JIRA link daemon commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java http://jenkins-ci.org/commit/email-ext-plugin/6dfefca4438cd5d15f2d3c5cd88a29b2ae2f8556 Log: Fix JENKINS-20078 Added caching to the private macro lookup This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21047) Update XStream 1.4.4. to 1.4.6
martin brook started work on JENKINS-21047 Update XStream 1.4.4. to 1.4.6 Change By: martin brook (08/Mar/14 6:01 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21047) Update XStream 1.4.4. to 1.4.6
martin brook stopped work on JENKINS-21047 Update XStream 1.4.4. to 1.4.6 Change By: martin brook (08/Mar/14 6:01 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21047) Update XStream 1.4.4. to 1.4.6
martin brook commented on JENKINS-21047 Update XStream 1.4.4. to 1.4.6 Pull request added at https://github.com/jenkinsci/xstream/pulls This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22081) XStream deserialization errors at service startup
martin brook commented on JENKINS-22081 XStream deserialization errors at service startup I've added a pull request for https://issues.jenkins-ci.org/browse/JENKINS-21047 which may be related This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Oleg Nenashev assigned JENKINS-13619 to Oleg Nenashev Add ability to throttle number of concurrent builds of matrix configurations per node Change By: Oleg Nenashev (08/Mar/14 6:35 PM) Assignee: abayer OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
SCM/JIRA link daemon commented on JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node Code changed in jenkins User: Oleg Nenashev Path: src/main/java/hudson/plugins/throttleconcurrents/ThrottleJobProperty.java src/main/java/hudson/plugins/throttleconcurrents/ThrottleMatrixProjectOptions.java src/main/resources/hudson/plugins/throttleconcurrents/Messages.properties src/main/resources/hudson/plugins/throttleconcurrents/ThrottleJobProperty/config.jelly src/main/resources/hudson/plugins/throttleconcurrents/ThrottleMatrixProjectOptions/config.jelly src/main/resources/hudson/plugins/throttleconcurrents/ThrottleMatrixProjectOptions/config.properties http://jenkins-ci.org/commit/throttle-concurrent-builds-plugin/c8280ad3ac3c4faf9b69e0401800813a5953dcfa Log: JENKINS-13619 - Added configuration options for Matrix project's throttling Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-13619) Add ability to throttle number of concurrent builds of matrix configurations per node
Oleg Nenashev started work on JENKINS-13619 Add ability to throttle number of concurrent builds of matrix configurations per node Change By: Oleg Nenashev (08/Mar/14 6:47 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Oleg Nenashev started work on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs Change By: Oleg Nenashev (08/Mar/14 6:47 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-22097) Confusing terminology: Global domain vs. global scope
Daniel Beck created JENKINS-22097 Confusing terminology: Global domain vs. global scope Issue Type: Bug Assignee: stephenconnolly Components: credentials Created: 08/Mar/14 7:12 PM Description: Credentials plugin uses the term "global" for two very different concepts: Global scope This credential is available to the object on which the credential is associated and all objects that are children of that object. Typically you would use global-scoped credentials for things that are needed by jobs. Global credentials domain All credentials that are not bound to a specific domain This should be changed by renaming one of them to prevent user confusion. Suggestions: Unbound domain, inheriting scope Project: Jenkins Priority: Major Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
jocelyn fournier commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Same issue here, svn:externals on a local directory inside the same project, and it fails randomly. hudson.util.IOException2: revision check failed on http:///client/application/class at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:738) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:899) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /*/client/application/class failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ... 12 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 30 more Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
jocelyn fournier edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Same issue here on linux debian, svn:externals on a local directory inside the same project (../../client/application/class class) , and it fails randomly. hudson.util.IOException2: revision check failed on http:///client/application/class at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:738) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:899) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /*/client/application/class failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ... 12 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 30 more Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Jocelyn: That particular issue looks like you can resolve it by adding an "additional credentials" entry below the list of module locations with a valid credential. For realm, enter e.g. https://server:443 Subversion Authentication It's the protocol, host, and port of the SVN service. The realm name (Subversion Authentication in my example is what your web browser shows in the password dialog when trying to access that URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-21554) NPE if MavenMailer/recipients is undefined
jsyrjala commented on JENKINS-21554 NPE if MavenMailer/recipients is undefined Sorry for delay. We are not using any DSL. Jobs have been configured manually via UI and then copied to create new jobs. I'll check the our xml config next week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-21554) NPE if MavenMailer/recipients is undefined
Tunde Oduniyi assigned JENKINS-21554 to Unassigned NPE if MavenMailer/recipients is undefined Change By: Tunde Oduniyi (08/Mar/14 11:08 PM) Assignee: TundeOduniyi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-20932) NPE in hudson.plugins.parameterizedtrigger.BuildTriggerConfig#resolveProject when no successful builds
ikedam closed JENKINS-20932 as Fixed NPE in hudson.plugins.parameterizedtrigger.BuildTriggerConfig#resolveProject when no successful builds Released in 2.23. Change By: ikedam (09/Mar/14 1:57 AM) Status: Reopened Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-19990) When load parameters from a properties file which file encoding is UTF-8, parameters‘ value is not right.
ikedam commented on JENKINS-19990 When load parameters from a properties file which file encoding is UTF-8, parameters‘ value is not right. Released in 2.23. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-21013) Matrix project support for Parameters from properties file
ikedam closed JENKINS-21013 as Fixed Matrix project support for Parameters from properties file Released in 2.23. Change By: ikedam (09/Mar/14 1:59 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-20651) File Parameters type causes the encoding of Chinese incorrect and blocks the build
ikedam commented on JENKINS-20651 File Parameters type causes the encoding of Chinese incorrect and blocks the build Parameterized-Trigger 2.23 now handles non-ascii characters. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-19990) When load parameters from a properties file which file encoding is UTF-8, parameters‘ value is not right.
ikedam closed JENKINS-19990 as Fixed When load parameters from a properties file which file encoding is UTF-8, parameters‘ value is not right. Change By: ikedam (09/Mar/14 2:01 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
ikedam commented on JENKINS-21932 Job hangs if one of multiple triggered builds was aborted Jenkins = 1.519 (7b2541d) Queue#doCancelItem Queue#cancel(Item) Item#onCancelled FutureImpl#setAsCancelled Jenkins = 1.520 (513a45b) Queue#doCancelItem Queue#cancel(Item) Item#leave Item#onCancelled is removed in 513a45b. I think it should work in following way: Queue#doCancelItem Queue#cancel(Item) Item#cancel Item#leave FutureImpl#setAsCancelled This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20500) Build queue is not filtered after progress updated
clint axeda commented on JENKINS-20500 Build queue is not filtered after progress updated i definitely voted for it. we have many executors, many views - this bug is really painful for us This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22098) NoClassDefFoundError when viewing git configuration
jpschewe created JENKINS-22098 NoClassDefFoundError when viewing git configuration Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 09/Mar/14 3:59 AM Description: When viewing the configuration for a job using git I now get "ERROR" under the git url and when I click on it I see the following: javax.servlet.ServletException: java.lang.NoClassDefFoundError: org.jenkinsci.plugins.gitclient.GitClient at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
