[JIRA] (JENKINS-13382) Support multimodule sloccount report
Brice Beard created JENKINS-13382: - Summary: Support multimodule sloccount report Key: JENKINS-13382 URL: https://issues.jenkins-ci.org/browse/JENKINS-13382 Project: Jenkins Issue Type: New Feature Components: sloccount Reporter: Brice Beard Assignee: npiguet atm the plugin only supports the --details format of sloccount report whereas sloc2html (http://www.dwheeler.com/sloccount/sloc2html-example.html) supports --multimodule. I would be great if the plugin could also support multiproject. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13308) Build action Sauce OnDemand report link links to a page with a bad iframe
[ https://issues.jenkins-ci.org/browse/JENKINS-13308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161382#comment-161382 ] Ross Rowe commented on JENKINS-13308: - I can see the Sauce Job results correctly when I navigate to the specific test result page, but I'm not seeing the 'Sauce OnDemand report' link appear at all for my job results. I'll keep having a look into this, but could you let me know what version of Jenkins you're using? Cheers, Ross Build action Sauce OnDemand report link links to a page with a bad iframe --- Key: JENKINS-13308 URL: https://issues.jenkins-ci.org/browse/JENKINS-13308 Project: Jenkins Issue Type: Bug Components: sauce-ondemand Reporter: R. Tyler Croy Assignee: Ross Rowe Attachments: ondemand-embedding-fail-first-link.png, ondemand-embedding-fail.png See the two attached screenshots. Basically, despite being logged in inside my browser, when I click on the Sauce OnDemand report link, I get an iframe with the login screen, instead of the actual report. This might be something on saucelabs.com as opposed to the plugin though :/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11498) ConcurrentModificationException in continuous integration game
[ https://issues.jenkins-ci.org/browse/JENKINS-11498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161383#comment-161383 ] SCM/JIRA link daemon commented on JENKINS-11498: Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/plugins/cigame/model/ScoreCard.java http://jenkins-ci.org/commit/ci-game-plugin/e12f121b9681c28f2bc2c0bda324c817e2cc9195 Log: [FIXED JENKINS-11498] ConcurrentModificationException when recording scores for matrix build Compare: https://github.com/jenkinsci/ci-game-plugin/compare/b55d92b...e12f121 ConcurrentModificationException in continuous integration game -- Key: JENKINS-11498 URL: https://issues.jenkins-ci.org/browse/JENKINS-11498 Project: Jenkins Issue Type: Bug Components: ci-game Environment: Jenkins on linux 64 bit, version 1.435 Plugin version is 1.18 Reporter: Johannes Wienke Assignee: kutzi I just received a ConcurrentModificationException in the ci game plugin for a matrix job which builds in parallel in several nodes: [ci-game] evaluating rule: Build result [ci-game] scored: 1.0 ERROR: Publisher hudson.plugins.cigame.GamePublisher aborted due to exception java.util.ConcurrentModificationException at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:761) at java.util.LinkedList$ListItr.next(LinkedList.java:696) at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:110) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:60) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:45) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:694) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:669) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:647) at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171) at hudson.model.Run.run(Run.java:1448) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11538) Jenkins serves existing files regardless of security
[ https://issues.jenkins-ci.org/browse/JENKINS-11538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161384#comment-161384 ] Steve Betts commented on JENKINS-11538: --- These changes are a good step and remove the vulnerability for WEB-INF and META-INF attacks, but this does nothing for the https://server/scripts./behavior.js attack. Please don't forget that facet too. Jenkins serves existing files regardless of security Key: JENKINS-11538 URL: https://issues.jenkins-ci.org/browse/JENKINS-11538 Project: Jenkins Issue Type: Bug Components: security, www Affects Versions: current Environment: Jenkins 1.436, Windows 7 64-bit SP1, build-in Winstone servlet engine 0.9.10 Reporter: Steve Betts Priority: Critical an url of the form (note the dot): https:/server/WEB-INF./web.xml will return the file, even with security turned on and the client unauthenticated. As will any other url that references a valid filename with a '.' after the first directory name, such as https://server/scripts./behavior.js. these behaviors are considered culnerabilites by our large corporation. http://xforce.iss.net/xforce/xfdb/9446 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1858 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11902) On reconnect the Expose presence option is ignored.
[ https://issues.jenkins-ci.org/browse/JENKINS-11902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kutzi resolved JENKINS-11902. - Resolution: Cannot Reproduce Cannot reproduce nor fix without more information On reconnect the Expose presence option is ignored. - Key: JENKINS-11902 URL: https://issues.jenkins-ci.org/browse/JENKINS-11902 Project: Jenkins Issue Type: Bug Components: jabber Affects Versions: current Reporter: Mathias K Assignee: kutzi Labels: plugin On reconnect the groupchat is available with jenkins inside but the presence is not send to the private user list. I can't see jenkins in my userlist after a reconnect. Restart jenkins will fix this issue but this should work on the fly. Log: Nov 28, 2011 9:41:52 AM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test. Returning 403. Nov 28, 2011 9:41:52 AM hudson.security.csrf.CrumbFilter doFilter WARNING: Found invalid crumb hidden. Will check remaining parameters for a valid one... Nov 28, 2011 9:41:31 AM hudson.plugins.jabber.im.transport.JabberIMConnection connect INFO: Joined groupchat hidden.jabber.ccc.de Nov 28, 2011 9:41:31 AM hudson.plugins.jabber.im.transport.JabberIMConnection connect INFO: Connected to XMPP on jabber.ccc.de:5222/jabber.ccc.de using TLS Nov 28, 2011 9:41:30 AM hudson.plugins.jabber.im.transport.JabberIMConnection setupSubscriptionMode INFO: Subscription requests must be handled manually Nov 28, 2011 9:41:29 AM hudson.plugins.jabber.im.transport.JabberIMConnection createConnection INFO: Trying to connect to XMPP on jabber.ccc.de:5222/jabber.ccc.de with SASL Nov 28, 2011 9:41:26 AM hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run INFO: Trying to reconnect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13383) Support matrix jobs
Pablo Saavedra created JENKINS-13383: Summary: Support matrix jobs Key: JENKINS-13383 URL: https://issues.jenkins-ci.org/browse/JENKINS-13383 Project: Jenkins Issue Type: Improvement Components: performance-plugin Affects Versions: current Reporter: Pablo Saavedra Assignee: Manuel Carrasco I have a matrix configuration build specifically for testing an application with different numbers of concurrent users (threads), and a separate regular build with a fixed number of concurrent users. In the regular build, I can see the performance trend graph. However, in the matrix build I don't see a performance trend graph, neither in the main build page, nor in the individual configurations pages. It'd be very useful to be able to see the performance trend in each individual configuration page in a matrix job. Is it at all possible? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13384) Cannot archive artifact - NTFS symlink
Ben Golding created JENKINS-13384: - Summary: Cannot archive artifact - NTFS symlink Key: JENKINS-13384 URL: https://issues.jenkins-ci.org/browse/JENKINS-13384 Project: Jenkins Issue Type: Bug Components: artifactory Environment: Windows Slave: - Windows Server 2008 R2 SP1 64 bit - C: is NTFS filesystem - Sun Java 1.6.0_20 Master: - Jenkins 1.457 - Red Hat Enterprise Linux 4.8 64 bit - Sun Java 1.6.0_20 Reporter: Ben Golding Assignee: yossis Attachments: artifact_exception.log Steps to reproduce: # Open slave command prompt mkdir C:\test cd /d C:\test notepad file.txt # Write something, save mklink linked.txt file.txt # Note linked.txt is an NTFS symlink # Open Jenkins web interface # New Job # Name 'test' # 'Build a free-style software project' # OK button # Check 'Restrict where this project can be run', enter Windows slave name # Check 'Use custom workspace', enter Directory: C:\test # Check 'Archive the artifacts', enter Files to archive: file.txt,linked.txt # Save button # Build Now link # When complete, click the link for Build #1 # Note 'linked.txt' appears with a size 0, while file.txt is size 15 bytes # Click 'Console Output' link, errors seen: (artifact_exception.log is attached) - Expected behaviour is: make a copy of the symlinked file as a regular file - Below are some types of link you may wish to consider for MS Windows. Jenkins does not necessarily need to support all. Should be transparent to applications: * NTFS file and directory symlinks (Win Vista and later) * junction points (also supported on Win XP, ...) Non-transparent: * Windows Explorer shortcuts (.lnk) ? * Cygwin symlinks ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13384) Cannot archive artifact - NTFS symlink
[ https://issues.jenkins-ci.org/browse/JENKINS-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ben Golding updated JENKINS-13384: -- Priority: Minor (was: Major) Cannot archive artifact - NTFS symlink -- Key: JENKINS-13384 URL: https://issues.jenkins-ci.org/browse/JENKINS-13384 Project: Jenkins Issue Type: Bug Components: artifactory Environment: Windows Slave: - Windows Server 2008 R2 SP1 64 bit - C: is NTFS filesystem - Sun Java 1.6.0_20 Master: - Jenkins 1.457 - Red Hat Enterprise Linux 4.8 64 bit - Sun Java 1.6.0_20 Reporter: Ben Golding Assignee: yossis Priority: Minor Attachments: artifact_exception.log Steps to reproduce: # Open slave command prompt mkdir C:\test cd /d C:\test notepad file.txt # Write something, save mklink linked.txt file.txt # Note linked.txt is an NTFS symlink # Open Jenkins web interface # New Job # Name 'test' # 'Build a free-style software project' # OK button # Check 'Restrict where this project can be run', enter Windows slave name # Check 'Use custom workspace', enter Directory: C:\test # Check 'Archive the artifacts', enter Files to archive: file.txt,linked.txt # Save button # Build Now link # When complete, click the link for Build #1 # Note 'linked.txt' appears with a size 0, while file.txt is size 15 bytes # Click 'Console Output' link, errors seen: (artifact_exception.log is attached) - Expected behaviour is: make a copy of the symlinked file as a regular file - Below are some types of link you may wish to consider for MS Windows. Jenkins does not necessarily need to support all. Should be transparent to applications: * NTFS file and directory symlinks (Win Vista and later) * junction points (also supported on Win XP, ...) Non-transparent: * Windows Explorer shortcuts (.lnk) ? * Cygwin symlinks ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11362) Strange delay during a maven job build
[
https://issues.jenkins-ci.org/browse/JENKINS-11362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161386#comment-161386
]
Gustavo Chaves commented on JENKINS-11362:
--
Last week we upgraded our instance to Jenkins 1.458 and confirmed that the
problem persists.
So far we are still managing this by segregating our big maven jobs to an old
Hudson instance in which the problem doesn't happen.
Strange delay during a maven job build
--
Key: JENKINS-11362
URL: https://issues.jenkins-ci.org/browse/JENKINS-11362
Project: Jenkins
Issue Type: Bug
Components: maven2
Environment: We're running Jenkins on a RHEL 5.2, 32 bits box, with
Java 1.6.0_04. The build agent runs on a RHEL 5.4, 64 bits box, with Java
1.6.0_23.
Reporter: Gustavo Chaves
Assignee: kutzi
Attachments: config.xml, etics-6.1.x-es_76_Console.html,
fine-stack-traces.zip, JENKINS-11362_stack-traces.zip, m3.log.gz,
simplificado-config.xml, simplificado.zip, System_Information_Jenkins.html
Hi. We upgraded our old Hudson server to Jenkins 1.409.2 on Sep, 20th. Since
then we're facing bigger build times, like twice the time it used to take
with Hudson.
We're running Jenkins on a RHEL 5.2, 32 bits box, with Java 1.6.0_04. The
build agent runs on a RHEL 5.4, 64 bits box, with Java 1.6.0_23.
I'm attaching the [^System_Information_Jenkins.html] page which contains the
configuration of our Jenkins server.
I'm also attaching the [^config.xml] file of a particular job which shows the
problem well.
I'm also attaching the [^etics-6.1.x-es_76_Console.html] file with the
Console output of a particular build. The output lines are prefixed with the
time of day (via the timestamper plugin) so that we can see where most of the
time was spent. As you can see, the build started at 10:47:17 and ended at
11:26:36, having taken 39 minutes and 19 seconds in the whole. However, as
you can see at the end of the log, maven tells us that the build took only 11
minutes and 3 seconds. Most of the remaining 28 minutes and 16 seconds was
spent between the lines prefixed with times 10:47:54 and 11:15:21.
I don't know what the Jenkins server or the agent were doing during this
quiet period. I tried to see which processes were busy during this period and
the only strange thing I noticed was that there was a process in the agent
machine very busy, which was this:
{noformat}
/l/disk0/ipscate/tools/java/jdk1.6.0_23/bin/java -jar slave.jar
{noformat}
I straced it during a few seconds and saw that it was busy opening lots of
files under the /l/disk0/ipscate/ip/nexus/.m2/repository/br/com/cpqd
directory. In fact, in a short period of about 15 or 20 seconds it opened
more than 4 files, some of them being repeatedly opened thousands of
times. These were the most often opened ones:
{noformat}
# sort /tmp/trace | uniq -c | sort -n | tail -5
3502 32319
open(/l/disk0/ipscate/ip/nexus/.m2/repository/br/com/cpqd/public/cpqd-public-bom/6.5.2/_maven.repositories,
O_RDONLY) = 16
3502 32319
stat(/l/disk0/ipscate/ip/nexus/.m2/repository/br/com/cpqd/public/cpqd-public-bom/6.5.2/cpqd-public-bom-6.5.2.pom,
{st_mode=S_IFREG|0644, st_size=45211, ...}) = 0
3793 32319
open(/l/disk0/ipscate/ip/nexus/.m2/repository/br/com/cpqd/parent/cpqd-super-parent/6.5.2/cpqd-super-parent-6.5.2.pom,
O_RDONLY) = 16
3793 32319
stat(/l/disk0/ipscate/ip/nexus/.m2/repository/br/com/cpqd/parent/cpqd-super-parent/6.5.2/cpqd-super-parent-6.5.2.pom,
{st_mode=S_IFREG|0644, st_size=14792, ...}) = 0
7004 32319
stat(/l/disk0/ipscate/ip/nexus/.m2/repository/br/com/cpqd/public/cpqd-public-bom/6.5.2/_maven.repositories,
{st_mode=S_IFREG|0644, st_size=163, ...}) = 0
{noformat}
I'm not sure this behaviour is directly related with the delay I was seeing
in the build, but it doesn't seem right to me.
Do you have any suggestion as to how can I go about investigating this?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup
[
https://issues.jenkins-ci.org/browse/JENKINS-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161387#comment-161387
]
Kanstantsin Shautsou commented on JENKINS-12970:
plugins]# cat ../hudson.plugins.disk_usage.DiskUsageProperty.xml
?xml version='1.0' encoding='UTF-8'?
hudson.plugins.disk__usage.DiskUsageProperty_-DiskUsageDescriptor
helpRedirect/
showGraphfalse/showGraph
convertedtrue/converted
/hudson.plugins.disk__usage.DiskUsageProperty_-DiskUsageDescriptor
Jenkins 1.458
NPE in disk-usage during jenkins startup
Key: JENKINS-12970
URL: https://issues.jenkins-ci.org/browse/JENKINS-12970
Project: Jenkins
Issue Type: Bug
Components: disk-usage
Affects Versions: current
Environment: Jenkins ver. 1.452
java version 1.7.0
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
Reporter: Maciej Olędzki
Assignee: vjuranek
After updating disk-usage plugin to version 0.15 I can't start jenkins
anymore. During statup process following error appears:
{code}
org.jvnet.hudson.reactor.ReactorException: java.lang.Error:
java.lang.reflect.InvocationTargetException
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:824)
at jenkins.model.Jenkins.init(Jenkins.java:736)
at hudson.model.Hudson.init(Hudson.java:81)
at hudson.model.Hudson.init(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
at
hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:813)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
... 8 more
Caused by: java.lang.NullPointerException
at
hudson.plugins.disk_usage.DiskUsageProperty$DiskUsageDescriptor.access$000(DiskUsageProperty.java:46)
at
hudson.plugins.disk_usage.DiskUsageProperty.transitionAuth(DiskUsageProperty.java:36)
... 13 more
{code}
Previous version of disk-usage (0.14) plugin works ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup
[
https://issues.jenkins-ci.org/browse/JENKINS-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161387#comment-161387
]
Kanstantsin Shautsou edited comment on JENKINS-12970 at 4/9/12 2:38 PM:
{code:title=hudson.plugins.disk_usage.DiskUsageProperty.xml}
?xml version='1.0' encoding='UTF-8'?
hudson.plugins.disk__usage.DiskUsageProperty_-DiskUsageDescriptor
helpRedirect/
showGraphfalse/showGraph
convertedtrue/converted
/hudson.plugins.disk__usage.DiskUsageProperty_-DiskUsageDescriptor
{code}
Jenkins 1.458
was (Author: integer):
plugins]# cat ../hudson.plugins.disk_usage.DiskUsageProperty.xml
?xml version='1.0' encoding='UTF-8'?
hudson.plugins.disk__usage.DiskUsageProperty_-DiskUsageDescriptor
helpRedirect/
showGraphfalse/showGraph
convertedtrue/converted
/hudson.plugins.disk__usage.DiskUsageProperty_-DiskUsageDescriptor
Jenkins 1.458
NPE in disk-usage during jenkins startup
Key: JENKINS-12970
URL: https://issues.jenkins-ci.org/browse/JENKINS-12970
Project: Jenkins
Issue Type: Bug
Components: disk-usage
Affects Versions: current
Environment: Jenkins ver. 1.452
java version 1.7.0
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
Reporter: Maciej Olędzki
Assignee: vjuranek
After updating disk-usage plugin to version 0.15 I can't start jenkins
anymore. During statup process following error appears:
{code}
org.jvnet.hudson.reactor.ReactorException: java.lang.Error:
java.lang.reflect.InvocationTargetException
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:824)
at jenkins.model.Jenkins.init(Jenkins.java:736)
at hudson.model.Hudson.init(Hudson.java:81)
at hudson.model.Hudson.init(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
at
hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:813)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
... 8 more
Caused by: java.lang.NullPointerException
at
hudson.plugins.disk_usage.DiskUsageProperty$DiskUsageDescriptor.access$000(DiskUsageProperty.java:46)
at
hudson.plugins.disk_usage.DiskUsageProperty.transitionAuth(DiskUsageProperty.java:36)
... 13 more
{code}
Previous version of disk-usage (0.14) plugin works ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161388#comment-161388 ] Jay Beeckman commented on JENKINS-11381: This is according to SVNKit's web page (http://svnkit.com/download.php): Lastest stable version of SVNKit (1.3.7) is not compatible with Subversion 1.7 working copy format. However, SVNKit 1.7 is under development now and we plan to release it in 12th of April 2012. We plan to publish first Release Candidate build till the end of February 2012. This is in three days, when could we reasonably expect this to be rolled into the plugin if they do indeed release on the 12th? Subversion Plugin does not support Subversion 1.7 - Key: JENKINS-11381 URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 Project: Jenkins Issue Type: Improvement Components: subversion Reporter: soundworker Priority: Blocker -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13373) Job in quiet period blocks other jobs even if executors are available
[ https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161391#comment-161391 ] Kohsuke Kawaguchi commented on JENKINS-13373: - This appears to be a bug, although without more description I can't really interpret the screenshot. Job in quiet period blocks other jobs even if executors are available - Key: JENKINS-13373 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: johno Attachments: queue.png If there is a job in quiet period other jobs which do not depend on its completion will block even if executors are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11538) Jenkins serves existing files regardless of security
[ https://issues.jenkins-ci.org/browse/JENKINS-11538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-11538. Resolution: Fixed Jenkins serves existing files regardless of security Key: JENKINS-11538 URL: https://issues.jenkins-ci.org/browse/JENKINS-11538 Project: Jenkins Issue Type: Bug Components: security, www Affects Versions: current Environment: Jenkins 1.436, Windows 7 64-bit SP1, build-in Winstone servlet engine 0.9.10 Reporter: Steve Betts Priority: Critical an url of the form (note the dot): https:/server/WEB-INF./web.xml will return the file, even with security turned on and the client unauthenticated. As will any other url that references a valid filename with a '.' after the first directory name, such as https://server/scripts./behavior.js. these behaviors are considered culnerabilites by our large corporation. http://xforce.iss.net/xforce/xfdb/9446 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1858 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11538) Jenkins serves existing files regardless of security
[ https://issues.jenkins-ci.org/browse/JENKINS-11538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161390#comment-161390 ] SCM/JIRA link daemon commented on JENKINS-11538: Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/9acf12f7976bd97bfa125e4b715ae340be8c1715 Log: [FIXED JENKINS-11538] integrated Stapler 1.187 that contains the fix. Jenkins serves existing files regardless of security Key: JENKINS-11538 URL: https://issues.jenkins-ci.org/browse/JENKINS-11538 Project: Jenkins Issue Type: Bug Components: security, www Affects Versions: current Environment: Jenkins 1.436, Windows 7 64-bit SP1, build-in Winstone servlet engine 0.9.10 Reporter: Steve Betts Priority: Critical an url of the form (note the dot): https:/server/WEB-INF./web.xml will return the file, even with security turned on and the client unauthenticated. As will any other url that references a valid filename with a '.' after the first directory name, such as https://server/scripts./behavior.js. these behaviors are considered culnerabilites by our large corporation. http://xforce.iss.net/xforce/xfdb/9446 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1858 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13373) Job in quiet period blocks other jobs even if executors are available
[ https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161392#comment-161392 ] johno commented on JENKINS-13373: - Basically there are a few independent jobs, job a completes, goes into quiet period, job b is triggered, and won't start (even though executors are available) until job a quiet period is over. Job in quiet period blocks other jobs even if executors are available - Key: JENKINS-13373 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: johno Attachments: queue.png If there is a job in quiet period other jobs which do not depend on its completion will block even if executors are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11538) Jenkins serves existing files regardless of security
[ https://issues.jenkins-ci.org/browse/JENKINS-11538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161393#comment-161393 ] dogfood commented on JENKINS-11538: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png! [jenkins_main_trunk #1649|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1649/] [FIXED JENKINS-11538] integrated Stapler 1.187 that contains the fix. (Revision 9acf12f7976bd97bfa125e4b715ae340be8c1715) Result = UNSTABLE Kohsuke Kawaguchi : [9acf12f7976bd97bfa125e4b715ae340be8c1715|https://github.com/jenkinsci/jenkins/commit/9acf12f7976bd97bfa125e4b715ae340be8c1715] Files : * core/pom.xml Jenkins serves existing files regardless of security Key: JENKINS-11538 URL: https://issues.jenkins-ci.org/browse/JENKINS-11538 Project: Jenkins Issue Type: Bug Components: security, www Affects Versions: current Environment: Jenkins 1.436, Windows 7 64-bit SP1, build-in Winstone servlet engine 0.9.10 Reporter: Steve Betts Priority: Critical an url of the form (note the dot): https:/server/WEB-INF./web.xml will return the file, even with security turned on and the client unauthenticated. As will any other url that references a valid filename with a '.' after the first directory name, such as https://server/scripts./behavior.js. these behaviors are considered culnerabilites by our large corporation. http://xforce.iss.net/xforce/xfdb/9446 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2002-1858 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13381) Jenkins stopped after updating plugins
[ https://issues.jenkins-ci.org/browse/JENKINS-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161394#comment-161394 ] Rafael Tavares commented on JENKINS-13381: -- Well I removed git plugin manually and It works again. Then I tried reinstalling git plugin and It stops jenkins again. I didn't try disable or remove analysis-collector yet. Jenkins stopped after updating plugins -- Key: JENKINS-13381 URL: https://issues.jenkins-ci.org/browse/JENKINS-13381 Project: Jenkins Issue Type: Bug Components: core, git Affects Versions: current Environment: Ubuntu Server 64 bits Reporter: Rafael Tavares Assignee: Nicolas De Loof Labels: git, jenkins, plugins Hi, I was updating my plugins then after update I can't access anymore my jenkins. I get the following error: [!] Erro org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:849) at jenkins.model.Jenkins.init(Jenkins.java:761) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: java.lang.NullPointerException at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) ... 13 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13381) Jenkins stopped after updating plugins
[ https://issues.jenkins-ci.org/browse/JENKINS-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael Tavares updated JENKINS-13381: - Component/s: analysis-collector Jenkins stopped after updating plugins -- Key: JENKINS-13381 URL: https://issues.jenkins-ci.org/browse/JENKINS-13381 Project: Jenkins Issue Type: Bug Components: analysis-collector, core, git Affects Versions: current Environment: Ubuntu Server 64 bits Reporter: Rafael Tavares Assignee: Nicolas De Loof Labels: git, jenkins, plugins Hi, I was updating my plugins then after update I can't access anymore my jenkins. I get the following error: [!] Erro org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) at jenkins.model.Jenkins.executeReactor(Jenkins.java:849) at jenkins.model.Jenkins.init(Jenkins.java:761) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) ... 8 more Caused by: java.lang.NullPointerException at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) ... 13 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13111) Plugin activation cause a NullPointerException
[ https://issues.jenkins-ci.org/browse/JENKINS-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13111. Resolution: Fixed Plugin activation cause a NullPointerException -- Key: JENKINS-13111 URL: https://issues.jenkins-ci.org/browse/JENKINS-13111 Project: Jenkins Issue Type: Bug Components: pegdown-formatter-plugin Affects Versions: current Environment: Debian x64 Reporter: Sébastien Heurtematte Assignee: bap Attachments: stacktrace-monitoring.log, stacktrace-without-monitoring.log NullPointerException in the jenkins 1.455 I have different stacktrace depends on monitoring plugin or not -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
wernight created JENKINS-13385: -- Summary: Jenkins stop working after upgrade Key: JENKINS-13385 URL: https://issues.jenkins-ci.org/browse/JENKINS-13385 Project: Jenkins Issue Type: Bug Components: git Reporter: wernight Assignee: Nicolas De Loof Priority: Blocker After upgrading Jenkins to 1.459 I got this exception which is removed as soon as I disable Git plugin: SEVERE: Failed to create Guice container from all the plugins com.google.common.collect.ComputationException: java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) at com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) at com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:94) at com.google.inject.Guice.createInjector(Guice.java:71) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) at hudson.ExtensionFinder._find(ExtensionFinder.java:149) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wernight updated JENKINS-13385: --- Affects Version/s: current Description: After upgrading Jenkins to 1.459 I got this exception which is removed as soon as I disable Git plugin 1.1.16: SEVERE: Failed to create Guice container from all the plugins com.google.common.collect.ComputationException: java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) at com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) at com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:94) at com.google.inject.Guice.createInjector(Guice.java:71) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) at hudson.ExtensionFinder._find(ExtensionFinder.java:149) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) at
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161396#comment-161396 ] wernight commented on JENKINS-13385: Installing *Dashboard View* plugin seem to solve this issue. Jenkins stop working after upgrade -- Key: JENKINS-13385 URL: https://issues.jenkins-ci.org/browse/JENKINS-13385 Project: Jenkins Issue Type: Bug Components: git Affects Versions: current Reporter: wernight Assignee: Nicolas De Loof Priority: Blocker After upgrading Jenkins to 1.459 I got this exception which is removed as soon as I disable Git plugin 1.1.16: SEVERE: Failed to create Guice container from all the plugins com.google.common.collect.ComputationException: java.lang.TypeNotPresentException: Type hudson.plugins.view.dashboard.DashboardPortlet not present at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) at com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) at com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) at com.google.inject.internal.FailableCache.get(FailableCache.java:49) at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) at com.google.inject.Guice.createInjector(Guice.java:94) at com.google.inject.Guice.createInjector(Guice.java:71) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:280) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at java.lang.Class.newInstance0(Class.java:372) at java.lang.Class.newInstance(Class.java:325) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) at hudson.ExtensionFinder._find(ExtensionFinder.java:149) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) at hudson.ExtensionList.load(ExtensionList.java:278) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
[JIRA] (JENKINS-13360) Envinject fails with UnsupportedMediaException
[ https://issues.jenkins-ci.org/browse/JENKINS-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161397#comment-161397 ] gbois commented on JENKINS-13360: - I don't reproduce it. Envinject fails with UnsupportedMediaException -- Key: JENKINS-13360 URL: https://issues.jenkins-ci.org/browse/JENKINS-13360 Project: Jenkins Issue Type: Bug Components: envinject Environment: JBOSS 7.1.1, FreeBSD 8.2, openjdk 6 Reporter: Radim Kolar Assignee: gbois Priority: Critical Attachments: 1.zip It does this in all cases, even if property file does not exists. [EnvInject] - Preparing an environment for the build. [EnvInject] - [ERROR] - SEVERE ERROR occurs: com/sun/xml/internal/ws/server/UnsupportedMediaException Archiving artifacts EnvInject 1.44 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13256) JDK 5 Compatibility
[ https://issues.jenkins-ci.org/browse/JENKINS-13256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161398#comment-161398 ] Jordan Grant commented on JENKINS-13256: My projects are using JDK 5 and I think I'm experiencing this as well in our Gradle/Artifactory build: * Where: Initialization script 'C:\temp\init-artifactory9203926068238878954gradle' line: 19 * What went wrong: Failed to notify build listener. Failed to notify build listener. Bad version number in .class file * Try: Run with --info or --debug option to get more log output. * Exception is: org.gradle.listener.ListenerNotificationException: Failed to notify build listener. at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:97) at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:75) at $Proxy8.projectsLoaded(Unknown Source) at org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:136) at org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:110) at org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:78) at org.gradle.launcher.cli.RunBuildAction.execute(RunBuildAction.java:42) at org.gradle.launcher.cli.RunBuildAction.execute(RunBuildAction.java:28) at org.gradle.launcher.exec.ExceptionReportingAction.execute(ExceptionReportingAction.java:32) at org.gradle.launcher.exec.ExceptionReportingAction.execute(ExceptionReportingAction.java:21) at org.gradle.launcher.cli.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:238) at org.gradle.launcher.cli.CommandLineActionFactory$WithLoggingAction.execute(CommandLineActionFactory.java:222) at org.gradle.launcher.Main.doAction(Main.java:48) at org.gradle.launcher.exec.EntryPoint$1.execute(EntryPoint.java:53) at org.gradle.launcher.exec.EntryPoint$1.execute(EntryPoint.java:51) at org.gradle.launcher.exec.Execution.execute(Execution.java:28) at org.gradle.launcher.exec.EntryPoint.run(EntryPoint.java:39) at org.gradle.launcher.Main.main(Main.java:39) at org.gradle.launcher.ProcessBootstrap.runNoExit(ProcessBootstrap.java:51) at org.gradle.launcher.ProcessBootstrap.run(ProcessBootstrap.java:33) at org.gradle.launcher.GradleMain.main(GradleMain.java:24) Caused by: org.gradle.listener.ListenerNotificationException: Failed to notify build listener. at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:97) at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:32) at org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:75) at $Proxy8.projectsLoaded(Unknown Source) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) at org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:88) ... 21 more Caused by: org.gradle.listener.ListenerNotificationException: Failed to notify build listener. at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:97) at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:32) at org.gradle.messaging.dispatch.BroadcastDispatch.dispatch(BroadcastDispatch.java:88) ... 27 more Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at org.jfrog.gradle.plugin.artifactory.ArtifactoryPlugin.$getStaticMetaClass(ArtifactoryPlugin.groovy) at org.jfrog.gradle.plugin.artifactory.ArtifactoryPlugin.init(ArtifactoryPlugin.groovy) at org.gradle.api.internal.plugins.DefaultPluginRegistry.loadPlugin(DefaultPluginRegistry.java:63) at org.gradle.api.internal.plugins.DefaultPluginRegistry.loadPlugin(DefaultPluginRegistry.java:54) at org.gradle.api.internal.plugins.DefaultProjectsPluginContainer.providePlugin(DefaultProjectsPluginContainer.java:106) at org.gradle.api.internal.plugins.DefaultProjectsPluginContainer.addPluginInternal(DefaultProjectsPluginContainer.java:71) at org.gradle.api.internal.plugins.DefaultProjectsPluginContainer.apply(DefaultProjectsPluginContainer.java:41) at org.gradle.api.internal.plugins.DefaultObjectConfigurationAction.applyPlugin(DefaultObjectConfigurationAction.java:90) at
[JIRA] (JENKINS-13373) Job in quiet period blocks other jobs even if executors are available
[ https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161392#comment-161392 ] johno edited comment on JENKINS-13373 at 4/9/12 9:21 PM: - This can be reproduced by configuring three jobs, two jobs job-A and job-B which are chained, job-B has a quiet period, and an independent job job-C, when job-A completes and job-B is in its quiet period, job-C won't start (even though executors are available) until job a quiet period is over. was (Author: johno): Basically there are a few independent jobs, job a completes, goes into quiet period, job b is triggered, and won't start (even though executors are available) until job a quiet period is over. Job in quiet period blocks other jobs even if executors are available - Key: JENKINS-13373 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: johno Attachments: queue.png If there is a job in quiet period other jobs which do not depend on its completion will block even if executors are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13373) Job in quiet period blocks other jobs even if executors are available
[ https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] johno updated JENKINS-13373: Attachment: jobs.zip Please find attached job configs which can be used to reproduce the bug. Job in quiet period blocks other jobs even if executors are available - Key: JENKINS-13373 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: johno Attachments: jobs.zip, queue.png If there is a job in quiet period other jobs which do not depend on its completion will block even if executors are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13373) Job in quiet period blocks other jobs even if executors are available
[ https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161392#comment-161392 ] johno edited comment on JENKINS-13373 at 4/9/12 9:23 PM: - This can be reproduced by configuring three jobs, two jobs job-A and job-B which are chained, job-B has a quiet period, and an independent job job-C, when job-A completes and job-B is in its quiet period, job-C won't start (even though executors are available) until the quiet period is over. was (Author: johno): This can be reproduced by configuring three jobs, two jobs job-A and job-B which are chained, job-B has a quiet period, and an independent job job-C, when job-A completes and job-B is in its quiet period, job-C won't start (even though executors are available) until job a quiet period is over. Job in quiet period blocks other jobs even if executors are available - Key: JENKINS-13373 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: johno Attachments: jobs.zip, queue.png If there is a job in quiet period other jobs which do not depend on its completion will block even if executors are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13360) Envinject fails with UnsupportedMediaException
[ https://issues.jenkins-ci.org/browse/JENKINS-13360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161397#comment-161397 ] gbois edited comment on JENKINS-13360 at 4/9/12 9:25 PM: - I don't reproduce it. Is it possible for you to test your use case in another environment? was (Author: gbois): I don't reproduce it. Envinject fails with UnsupportedMediaException -- Key: JENKINS-13360 URL: https://issues.jenkins-ci.org/browse/JENKINS-13360 Project: Jenkins Issue Type: Bug Components: envinject Environment: JBOSS 7.1.1, FreeBSD 8.2, openjdk 6 Reporter: Radim Kolar Assignee: gbois Priority: Critical Attachments: 1.zip It does this in all cases, even if property file does not exists. [EnvInject] - Preparing an environment for the build. [EnvInject] - [ERROR] - SEVERE ERROR occurs: com/sun/xml/internal/ws/server/UnsupportedMediaException Archiving artifacts EnvInject 1.44 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13373) Job in quiet period blocks other jobs even if executors are available
[ https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] johno updated JENKINS-13373: Attachment: queue.png Job in quiet period blocks other jobs even if executors are available - Key: JENKINS-13373 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: johno Attachments: jobs.zip, queue.png, queue.png If there is a job in quiet period other jobs which do not depend on its completion will block even if executors are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13386) New Warnings and Fixed Static Analysis Warnings
Srinivasa Prasad Sunnapu created JENKINS-13386: -- Summary: New Warnings and Fixed Static Analysis Warnings Key: JENKINS-13386 URL: https://issues.jenkins-ci.org/browse/JENKINS-13386 Project: Jenkins Issue Type: Improvement Components: email-ext Environment: OS X, Snow Leopard Reporter: Srinivasa Prasad Sunnapu I have a requirement to share static analysis warnings, like FindBugs, PMD, etc., in build notifications without need to go to job's Jenkins page. Basically need options to configure email notifications to share - new warnings introduced in this build - fixed warnings in the build - All High priorities warnings - Source files and last committer ids Any alternatives that satisfy the above requirements at least for FindBugs will be appreciable. Thanks, Srini -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10735) Failed to import results from Non-server Klocwork Run
[ https://issues.jenkins-ci.org/browse/JENKINS-10735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-10735. - Resolution: Fixed Failed to import results from Non-server Klocwork Run - Key: JENKINS-10735 URL: https://issues.jenkins-ci.org/browse/JENKINS-10735 Project: Jenkins Issue Type: Bug Components: klocwork Affects Versions: current Environment: Windows XP Pro, Klocwork 9.2, C# Reporter: John Werner Assignee: gbois Attachments: 0001-Fixed-JENKINS-1073.patch, klocwork-plugin-err.txt, klocwork_result.xml The output file from running Klocwork analysis on a locally on my machine as opposed to remotely does not get properly parsed. The plugin throws an error because of missing fields. The errors generated are attached along with the actual Klocwork output xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10379) Allowed statuses for Klocwork report are incorrect
[ https://issues.jenkins-ci.org/browse/JENKINS-10379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-10379. - Resolution: Fixed Allowed statuses for Klocwork report are incorrect -- Key: JENKINS-10379 URL: https://issues.jenkins-ci.org/browse/JENKINS-10379 Project: Jenkins Issue Type: Bug Components: klocwork Environment: Jenkins 1.421 on RHEL 5.2, Klocwork 9.2.2, Klocwork plugin Reporter: Krzysztof Malinowski Assignee: gbois Attachments: out.xml When trying to parse Klocwork 9.2.2 report, an error is raised: At line 25 of file:/tmp/workspace/job1/kwreport.xml:cvc-enumeration-valid: Value 'Not a Problem' is not facet-valid with respect to enumeration '[Analyze, Ignore, Not a problem, Fix, Fix in Next Release, Fix in Later Release, Defer, Filter]'. It must be a value from the enumeration. kwreport.xml comes straight from kwinspectreport 9.2.2. [I know it's not a core issue, but there's no klocwork component] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10776) No Klokwork Results even if there is a unstable build
[ https://issues.jenkins-ci.org/browse/JENKINS-10776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-10776. - Resolution: Fixed No Klokwork Results even if there is a unstable build - Key: JENKINS-10776 URL: https://issues.jenkins-ci.org/browse/JENKINS-10776 Project: Jenkins Issue Type: Bug Components: klocwork Affects Versions: current Environment: Jenkins 1.424 Klocwork Plugin 1.2 Reporter: Hans-Juergen Hafner Assignee: gbois Priority: Minor Attachments: kw1.jpg, kw2.jpg, kw2.jpg klicking on Klocwork Results leads to page myjob/kloResult/nodata even if ther was an unstable build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13373) Job in quiet period blocks other jobs even if executors are available
[ https://issues.jenkins-ci.org/browse/JENKINS-13373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] johno resolved JENKINS-13373. - Resolution: Duplicate Verified JENKINS-12994 fix with attached test job configs. Job in quiet period blocks other jobs even if executors are available - Key: JENKINS-13373 URL: https://issues.jenkins-ci.org/browse/JENKINS-13373 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: johno Attachments: jobs.zip, queue.png, queue.png If there is a job in quiet period other jobs which do not depend on its completion will block even if executors are available. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert Delete this build buttons into links in the sidepanel
[ https://issues.jenkins-ci.org/browse/JENKINS-13387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13387 started by Fred G. Convert Delete this build buttons into links in the sidepanel --- Key: JENKINS-13387 URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Assignee: Fred G Labels: gui Attachments: DeleteBuildButtons_MatrixBuild.png, DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, DeleteBuildLinks_MatrixConfig.png The Delete this build buttons on build pages and also the Delete this build and all configurations of this build buttons on matrix build pages should be converted to links in the sidepanel of the respective pages (see Screenshots). This simplifies the user experience of deleting an object (see the Delete Project link in the sidepanel of project pages). Having the links in the sidepanel also makes them accessible through the newly added context menus that came with the breadcrumbs. Recent discussion about this topic: https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13387) Convert Delete this build buttons into links in the sidepanel
Fred G created JENKINS-13387: Summary: Convert Delete this build buttons into links in the sidepanel Key: JENKINS-13387 URL: https://issues.jenkins-ci.org/browse/JENKINS-13387 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Assignee: Fred G Attachments: DeleteBuildButtons_MatrixBuild.png, DeleteBuildButtons_MatrixConfig.png, DeleteBuildLinks_MatrixBuild.png, DeleteBuildLinks_MatrixConfig.png The Delete this build buttons on build pages and also the Delete this build and all configurations of this build buttons on matrix build pages should be converted to links in the sidepanel of the respective pages (see Screenshots). This simplifies the user experience of deleting an object (see the Delete Project link in the sidepanel of project pages). Having the links in the sidepanel also makes them accessible through the newly added context menus that came with the breadcrumbs. Recent discussion about this topic: https://github.com/jenkinsci/jenkins/pull/403 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13388) Add option to delete existing artifacts before copy
[ https://issues.jenkins-ci.org/browse/JENKINS-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Davidson updated JENKINS-13388: Summary: Add option to delete existing artifacts before copy (was: Add option to delete existing artifacts before copyc) Add option to delete existing artifacts before copy --- Key: JENKINS-13388 URL: https://issues.jenkins-ci.org/browse/JENKINS-13388 Project: Jenkins Issue Type: New Feature Components: copyartifact Reporter: Josh Davidson Assignee: Alan Harder It would be nice if the copy artifact build step would allow users to specify that the plugin should delete artifacts from a prior run before copying. With the current behavior, the only way to prevent renamed or deleted artifacts from making there way into a job is to manually add a build step to remove the copied artifacts in each job that uses this plugin. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12122) Coverity plugin console output is not human friendly
[ https://issues.jenkins-ci.org/browse/JENKINS-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Vinson reassigned JENKINS-12122: - Assignee: Josh Vinson (was: James Croall) Coverity plugin console output is not human friendly Key: JENKINS-12122 URL: https://issues.jenkins-ci.org/browse/JENKINS-12122 Project: Jenkins Issue Type: Bug Components: coverity Affects Versions: current Reporter: James Croall Assignee: Josh Vinson Priority: Minor Attachments: cpoutput.txt The console output provided by the Coverity plugin includes raw XML and is generally not very human readable/friendly, especially when included in a failed build report to a developer. Notifications like this should be clear and actionable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move View as plain text link on console output page from top right to the sidepanel.
Fred G created JENKINS-13389: Summary: Move View as plain text link on console output page from top right to the sidepanel. Key: JENKINS-13389 URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Priority: Minor Attachments: ViewAsPlainText_Link.png To clean up the Jenkins UI, all actions should be links in the sidepanel menu on the right side of the screen. In this case, the View as plain text link that appears on the top right corner of the console output page should be moved to the sidepanel (see screenshot). The link should only appear when the Console Output page is shown (similiar to the Wipe out workspace-link which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move View as plain text link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13389 started by Fred G. Move View as plain text link on console output page from top right to the sidepanel. -- Key: JENKINS-13389 URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Assignee: Fred G Priority: Minor Labels: gui Attachments: ViewAsPlainText_Link.png To clean up the Jenkins UI, all actions should be links in the sidepanel menu on the left side of the screen. The View as plain text link that appears on the top right corner of the console output page should be moved to the sidepanel (see screenshot). The link should only appear when the console output page is shown (similiar to the Wipe out workspace-link which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move View as plain text link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred G reassigned JENKINS-13389: Assignee: Fred G Move View as plain text link on console output page from top right to the sidepanel. -- Key: JENKINS-13389 URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Assignee: Fred G Priority: Minor Labels: gui Attachments: ViewAsPlainText_Link.png To clean up the Jenkins UI, all actions should be links in the sidepanel menu on the left side of the screen. The View as plain text link that appears on the top right corner of the console output page should be moved to the sidepanel (see screenshot). The link should only appear when the console output page is shown (similiar to the Wipe out workspace-link which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13389) Move View as plain text link on console output page from top right to the sidepanel.
[ https://issues.jenkins-ci.org/browse/JENKINS-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161402#comment-161402 ] Fred G commented on JENKINS-13389: -- Pull request: https://github.com/jenkinsci/jenkins/pull/432 Move View as plain text link on console output page from top right to the sidepanel. -- Key: JENKINS-13389 URL: https://issues.jenkins-ci.org/browse/JENKINS-13389 Project: Jenkins Issue Type: Improvement Components: gui, ui-changes Reporter: Fred G Assignee: Fred G Priority: Minor Labels: gui Attachments: ViewAsPlainText_Link.png To clean up the Jenkins UI, all actions should be links in the sidepanel menu on the left side of the screen. The View as plain text link that appears on the top right corner of the console output page should be moved to the sidepanel (see screenshot). The link should only appear when the console output page is shown (similiar to the Wipe out workspace-link which only appears when the workspace is selected). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup
[
https://issues.jenkins-ci.org/browse/JENKINS-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161403#comment-161403
]
Matthew Jones edited comment on JENKINS-12970 at 4/10/12 12:40 AM:
---
Appears to be a problem with the Analysis Collector plugin. Disabling that
makes a lot of other plugins start working again.
Comment referenced on the git plugin:
https://issues.jenkins-ci.org/browse/JENKINS-12966
https://issues.jenkins-ci.org/browse/JENKINS-13381
was (Author: jonespm):
Appears to be a problem with the Analysis Collector plugin. Disabling that
makes a lot of other plugins start working again.
Comment referenced on the git plugin:
https://issues.jenkins-ci.org/browse/JENKINS-12966
NPE in disk-usage during jenkins startup
Key: JENKINS-12970
URL: https://issues.jenkins-ci.org/browse/JENKINS-12970
Project: Jenkins
Issue Type: Bug
Components: disk-usage
Affects Versions: current
Environment: Jenkins ver. 1.452
java version 1.7.0
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
Reporter: Maciej Olędzki
Assignee: vjuranek
After updating disk-usage plugin to version 0.15 I can't start jenkins
anymore. During statup process following error appears:
{code}
org.jvnet.hudson.reactor.ReactorException: java.lang.Error:
java.lang.reflect.InvocationTargetException
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:824)
at jenkins.model.Jenkins.init(Jenkins.java:736)
at hudson.model.Hudson.init(Hudson.java:81)
at hudson.model.Hudson.init(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
at
hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:813)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
... 8 more
Caused by: java.lang.NullPointerException
at
hudson.plugins.disk_usage.DiskUsageProperty$DiskUsageDescriptor.access$000(DiskUsageProperty.java:46)
at
hudson.plugins.disk_usage.DiskUsageProperty.transitionAuth(DiskUsageProperty.java:36)
... 13 more
{code}
Previous version of disk-usage (0.14) plugin works ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12970) NPE in disk-usage during jenkins startup
[
https://issues.jenkins-ci.org/browse/JENKINS-12970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161403#comment-161403
]
Matthew Jones commented on JENKINS-12970:
-
Appears to be a problem with the Analysis Collector plugin. Disabling that
makes a lot of other plugins start working again.
Comment referenced on the git plugin:
https://issues.jenkins-ci.org/browse/JENKINS-12966
NPE in disk-usage during jenkins startup
Key: JENKINS-12970
URL: https://issues.jenkins-ci.org/browse/JENKINS-12970
Project: Jenkins
Issue Type: Bug
Components: disk-usage
Affects Versions: current
Environment: Jenkins ver. 1.452
java version 1.7.0
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
Reporter: Maciej Olędzki
Assignee: vjuranek
After updating disk-usage plugin to version 0.15 I can't start jenkins
anymore. During statup process following error appears:
{code}
org.jvnet.hudson.reactor.ReactorException: java.lang.Error:
java.lang.reflect.InvocationTargetException
at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
at jenkins.model.Jenkins.executeReactor(Jenkins.java:824)
at jenkins.model.Jenkins.init(Jenkins.java:736)
at hudson.model.Hudson.init(Hudson.java:81)
at hudson.model.Hudson.init(Hudson.java:77)
at hudson.WebAppMain$2.run(WebAppMain.java:217)
Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
at
hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:813)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
... 8 more
Caused by: java.lang.NullPointerException
at
hudson.plugins.disk_usage.DiskUsageProperty$DiskUsageDescriptor.access$000(DiskUsageProperty.java:46)
at
hudson.plugins.disk_usage.DiskUsageProperty.transitionAuth(DiskUsageProperty.java:36)
... 13 more
{code}
Previous version of disk-usage (0.14) plugin works ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13296) Changelists that include excluded files and files outside of the client view will trigger a build.
[ https://issues.jenkins-ci.org/browse/JENKINS-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161404#comment-161404 ] Patrick McKeown commented on JENKINS-13296: --- Will do thanks a lot! Changelists that include excluded files and files outside of the client view will trigger a build. -- Key: JENKINS-13296 URL: https://issues.jenkins-ci.org/browse/JENKINS-13296 Project: Jenkins Issue Type: Improvement Components: perforce Reporter: Patrick McKeown Assignee: Rob Petti Priority: Minor If there is already a way to handle this I apologize, looked around but didn't find anything. Given a client spec //depot/test/... //client/test/... with an exclude list such as //depot/test/exclude/... and polling turned on- if someone submits a changelist with an excluded file and a file outside the client spec such as changelist 1234 //depot/test/exclude/example.txt#1 //depot/test2/example2.txt#1 then //depot/test2/example2.txt#1 will trigger the build as it does not match anything in the exclude list. I would like a way to consider any files outside of the client spec as excluded files without actually having to specify them. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-31) new test feature
[ https://issues.jenkins-ci.org/browse/TEST-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved TEST-31. - Resolution: Fixed new test feature Key: TEST-31 URL: https://issues.jenkins-ci.org/browse/TEST-31 Project: test Issue Type: New Feature Components: test1 Reporter: OHTAKE Tomohiro Assignee: Kohsuke Kawaguchi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (TEST-31) new test feature
OHTAKE Tomohiro created TEST-31: --- Summary: new test feature Key: TEST-31 URL: https://issues.jenkins-ci.org/browse/TEST-31 Project: test Issue Type: New Feature Components: test1 Reporter: OHTAKE Tomohiro Assignee: Kohsuke Kawaguchi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
