date:20130802
















































SCM/JIRA link daemon
 resolved  JENKINS-18677 as Fixed


Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers
















Change By:


SCM/JIRA link daemon
(03/Aug/13 5:32 AM)




Status:


Open
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/groups/opt_out.

[JIRA] [core] (JENKINS-18677) Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers

SCM/JIRA link daemon
commented on JENKINS-18677

Some jobs not loaded after jenkins restart: java.lang.NoSuchFieldError: triggers

Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
changelog.html
core/pom.xml
core/src/main/java/hudson/ClassicPluginStrategy.java
core/src/main/java/hudson/PluginManager.java
core/src/main/java/hudson/model/AbstractProject.java
pom.xml
http://jenkins-ci.org/commit/jenkins/47de54d070f67af95b4fefb6d006a72bb31a5cb8
Log:
[FIXED JENKINS-18677]

Integrated bytecode-compatibility-transformer that allows core to
do signature changes on properties that plugins might depend on.

The library performs necessary bytecode transformation to achieve this.

The first use of this is to fix plugins that looks for List
AbstractProject.triggers, thereby resolving JENKINS-18677.

For the time being, I'm not loading such compatibility annotations from
plugins, but I did code that in PluginManager. Let's see how this
feature work out for a while in the core, and if it looks stable and
solid, we'll open it up to plugins at that point.

Compare: https://github.com/jenkinsci/jenkins/compare/2135a17552fd...47de54d070f6

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/groups/opt_out.

[no subject]

2013-08-02 Thread Michael K Larson

you are a winner of a big sum pay out of 750,00.00. To claim prize send info to 
: (free.r...@outlook.com)

-- 
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/groups/opt_out.

[JIRA] [maven2] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration

2013-08-02 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-10539


windows path separators not correctly escaped in Maven properties configuration















Integrated in  jenkins_main_trunk #2779
 [FIXED JENKINS-10539] Noting that #841 was merged. (Revision 8e08d2dcddc1ca3c36d7e570da7a35bd0950b8f2)

 Result = SUCCESS
Jesse Glick : 8e08d2dcddc1ca3c36d7e570da7a35bd0950b8f2
Files : 

	changelog.html





























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/groups/opt_out.

[JIRA] [environment-script] (JENKINS-19056) Environment variables are not available in post-build steps if the build is a matrix job

2013-08-02 Thread o...@nerdnetworks.org (JIRA)
















































owenmehegan
 assigned  JENKINS-19056 to owenmehegan



Environment variables are not available in post-build steps if the build is a matrix job
















Change By:


owenmehegan
(02/Aug/13 9:31 PM)




Assignee:


Jørgen Tjernø
owenmehegan



























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/groups/opt_out.

[JIRA] [environment-script] (JENKINS-19056) Environment variables are not available in post-build steps if the build is a matrix job

2013-08-02 Thread o...@nerdnetworks.org (JIRA)















































owenmehegan
 commented on  JENKINS-19056


Environment variables are not available in post-build steps if the build is a matrix job















Hmm, Jørgen doesn't maintain this plugin anymore. I will see if I can fix this bug, unless someone else wants to take it on.



























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/groups/opt_out.

[JIRA] [vagrant] (JENKINS-14682) Vagrant Plugin Doesn't Install

2013-08-02 Thread ever...@free.fr (JIRA)















































evernat
 updated  JENKINS-14682


Vagrant Plugin Doesn't Install
















Change By:


evernat
(02/Aug/13 8:38 PM)




Component/s:


vagrant





Component/s:


plugin



























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/groups/opt_out.

[JIRA] [environment-script] (JENKINS-19056) Environment variables are not available in post-build steps if the build is a matrix job

2013-08-02 Thread o...@nerdnetworks.org (JIRA)

owenmehegan
created JENKINS-19056

Environment variables are not available in post-build steps if the build is a matrix job

Issue Type:

Bug

Affects Versions:

current

Assignee:

Jørgen Tjernø

Components:

environment-script

Created:

02/Aug/13 8:39 PM

Description:

If I create a regular freestyle job and use this plugin, I can set an env var and access it in a post-build step (for example, with the parameterized trigger plugin). But if I use it in a matrix job, the variable is visible in build steps, but in post-build it is not.

Repro steps:

1. Create a new matrix job
2. Use 'Generate environment variables from script' and set e.g. TEST=foo
3. Add a shell script build step and echo $TEST
4. Add a 'Trigger parameterized build' post-build step, choose another test job which is parameterized, use 'Predefined parameters' and pass something like PARAMETER=$TEST

In the downstream job, parameter will be set to the literal string $TEST. If the upstream job is just a regular freestyle project, when the downstream job triggers the parameter will actually be set to 'foo.'

Environment:

Linux

Project:

Jenkins

Priority:

Major

Reporter:

owenmehegan

[JIRA] [remote-terminal-access] (JENKINS-16600) NullPointerException Exception in AuthorizationMatrixProperty when saving job config
















































SCM/JIRA link daemon
 resolved  JENKINS-16600 as Fixed


NullPointerException Exception in  AuthorizationMatrixProperty when saving job config
















Change By:


SCM/JIRA link daemon
(02/Aug/13 8:27 PM)




Status:


Open
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/groups/opt_out.

[JIRA] [remote-terminal-access] (JENKINS-16600) NullPointerException Exception in AuthorizationMatrixProperty when saving job config















































SCM/JIRA link daemon
 commented on  JENKINS-16600


NullPointerException Exception in  AuthorizationMatrixProperty when saving job config















Code changed in jenkins
User: Stefan Wolf
Path:
 src/main/java/org/jenkinsci/plugins/remote_terminal_access/TerminalSessionAction.java
http://jenkins-ci.org/commit/remote-terminal-access-plugin/e4fa8fcd85d76d2c80f3956b664cb1fc380c7d73
Log:
  [FIXED JENKINS-16600] Use existing PermissionGroup






























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/groups/opt_out.

[JIRA] [remote-terminal-access] (JENKINS-16600) NullPointerException Exception in AuthorizationMatrixProperty when saving job config

2013-08-02 Thread wo...@java.net (JIRA)















































wolfs
 commented on  JENKINS-16600


NullPointerException Exception in  AuthorizationMatrixProperty when saving job config















The RemoteTerminalAccess Plugin calls new PermissionGroup(Run.class,...). This replaces the old Permission Group from Run in a Map (containing Delete and Update)... Trying to get the Permission for the PermissionGroup then yields the null, since the old Permission is not in the new group...



























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/groups/opt_out.

[JIRA] [maven2] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration















































Jesse Glick
 commented on  JENKINS-10539


windows path separators not correctly escaped in Maven properties configuration















(Actually not merged as such; closed and rebased as 72901837dbbb554ec3d66ecd6b9949f1d794312c.)



























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/groups/opt_out.

[JIRA] [maven2] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration















































SCM/JIRA link daemon
 commented on  JENKINS-10539


windows path separators not correctly escaped in Maven properties configuration















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/8e08d2dcddc1ca3c36d7e570da7a35bd0950b8f2
Log:
  [FIXED JENKINS-10539] Noting that #841 was merged.






























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/groups/opt_out.

[JIRA] [maven2] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration
















































SCM/JIRA link daemon
 resolved  JENKINS-10539 as Fixed


windows path separators not correctly escaped in Maven properties configuration
















Change By:


SCM/JIRA link daemon
(02/Aug/13 8:17 PM)




Status:


Open
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/groups/opt_out.

[JIRA] [subversion] (JENKINS-9613) Builds are occurring twice for each commit

2013-08-02 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-9613


Builds are occurring twice for each commit















Is this reproducable in current Jenkins and subversion plugin versions?



























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/groups/opt_out.

[JIRA] [plugin] (JENKINS-17158) Quiet subversion checkout?

2013-08-02 Thread ku...@gmx.de (JIRA)
















































kutzi
 resolved  JENKINS-17158 as Duplicate


Quiet subversion checkout?
















Change By:


kutzi
(02/Aug/13 8:04 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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/groups/opt_out.

[JIRA] [core] (JENKINS-19000) Something broken in 1.525 (issue loading maven plugin?)

2013-08-02 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-19000


Something broken in 1.525 (issue loading maven plugin?)















Did you disable the Maven plugin? It's a non-optional dependency of Job Config History and the bug JENKINS-18654 probably hid that in unsupported configurations before.



























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/groups/opt_out.

[JIRA] [mercurial] (JENKINS-18252) Push notifications on Windows and a local repository















































SCM/JIRA link daemon
 commented on  JENKINS-18252


Push notifications on Windows and a local repository















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/hudson/plugins/mercurial/HgExe.java
 src/main/java/hudson/plugins/mercurial/MercurialStatus.java
 src/test/java/hudson/plugins/mercurial/HgExeTest.java
 src/test/java/hudson/plugins/mercurial/MercurialStatusTest.java
http://jenkins-ci.org/commit/mercurial-plugin/9d41ba0b7ad66b6ddefd87711195c0c3e7843124
Log:
  Merge pull request #41 from thomedw/path-equal

[FIXED JENKINS-18252] Added ability to recognize non-URL file paths in /notifyCommit


Compare: https://github.com/jenkinsci/mercurial-plugin/compare/fc8a1a73b312...9d41ba0b7ad6




























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/groups/opt_out.

[JIRA] [mercurial] (JENKINS-18252) Push notifications on Windows and a local repository
















































SCM/JIRA link daemon
 resolved  JENKINS-18252 as Fixed


Push notifications on Windows and a local repository
















Change By:


SCM/JIRA link daemon
(02/Aug/13 7:02 PM)




Status:


Open
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/groups/opt_out.

[JIRA] [mercurial] (JENKINS-18807) Mercurial plugin cannot ignore post commit hooks















































SCM/JIRA link daemon
 commented on  JENKINS-18807


Mercurial plugin cannot ignore post commit hooks















Code changed in jenkins
User: Jesse Glick
Path:
 pom.xml
 src/main/java/hudson/plugins/mercurial/MercurialStatus.java
http://jenkins-ci.org/commit/mercurial-plugin/c0c4bd98dd8f3e1aab161f3ecb562b0b96f4a520
Log:
  [FIXED JENKINS-18807] Ignore SCM triggers which ask to suppress post-commit hooks.
Requires 1.493+, so just update to 1.509.x already.





























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/groups/opt_out.

[JIRA] [build-pipeline] (JENKINS-18490) Run button not work

2013-08-02 Thread jdb...@diversit.eu (JIRA)















































Joost den Boer
 commented on  JENKINS-18490


Run button not work















We don't have any parameters and Run button still doesn't work, so that's not the cause.



























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/groups/opt_out.

[JIRA] [core] (JENKINS-19055) In case of connection loss, slave JVM should restart itself if it can

2013-08-02 Thread k...@kohsuke.org (JIRA)















































Kohsuke Kawaguchi
 commented on  JENKINS-19055


In case of connection loss, slave JVM should restart itself if it can















I think this would address some of the root cause in a blanket issue like JENKINS-5413.



























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/groups/opt_out.

[JIRA] [core] (JENKINS-19055) In case of connection loss, slave JVM should restart itself if it can

2013-08-02 Thread k...@kohsuke.org (JIRA)















































Kohsuke Kawaguchi
 created  JENKINS-19055


In case of connection loss, slave JVM should restart itself if it can















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


core



Created:


02/Aug/13 6:27 PM



Description:


"java -jar slave.jar" currently has a logic that keeps on reconnecting if a connection is dropped. This is good, but over a long run, if any memory leak happens during a connection, it'll slowly clog up the JVM.

On Unix, it is better to exec to itself to start clean in case of a connection loss. On slaves managed as a Windows service, it is better to just terminate the process and let Windows SCM launch a new one.

Slaves should do this kind of intelligent reconnection, much like how Jenkins master restarts itself.





Project:


Jenkins



Priority:


Major



Reporter:


Kohsuke Kawaguchi

























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/groups/opt_out.

[JIRA] [sitemonitor] (JENKINS-19054) Improvement adding basic auth url feature with Site Montor plugin

2013-08-02 Thread prithish.cha...@gmail.com (JIRA)















































prithish chanda
 created  JENKINS-19054


Improvement adding basic auth url feature with Site Montor plugin















Issue Type:


Improvement



Affects Versions:


current



Assignee:


cliffano



Components:


sitemonitor



Created:


02/Aug/13 5:42 PM



Description:


I am using site monitor plug to access lower qa envs (https://wiki.jenkins-ci.org/display/JENKINS/SiteMonitor+Plugin)

I would like to extend this plug in to access some of the url with basic auth for eg:- http://username:password@http://yoursite.com

Went through the source code and made the change @ https://github.com/jenkinsci/sitemonitor-plugin/pull/4

I had a discussion with the author (jieryn), and he confirmed that he is no more associated with the project .

Can you please review the code once and give me commit access, my changes can be found @https://github.com/jenkinsci/sitemonitor-plugin/pull/4





Project:


Jenkins



Priority:


Major



Reporter:


prithish chanda

























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/groups/opt_out.

[JIRA] [core] (JENKINS-19046) ClassCastException: cannot assign instance of hudson.remoting.ProxyOutputStream$Chunk to field java.lang.Throwable.suppressedExceptions of type java.util.List in instance















































SCM/JIRA link daemon
 commented on  JENKINS-19046


ClassCastException: cannot assign instance of hudson.remoting.ProxyOutputStream$Chunk to field java.lang.Throwable.suppressedExceptions of type java.util.List in instance of hudson.remoting.Command$Source















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/hudson/remoting/ClassicCommandTransport.java
http://jenkins-ci.org/commit/remoting/8c9064025fb341237c1411e4c2d1602868d9c585
Log:
  JENKINS-19046

Improving the stream diagnosis to report the actual contents of the stream.





























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/groups/opt_out.

[JIRA] [promoted-builds] (JENKINS-17243) Cannot access Global Passwords

2013-08-02 Thread smad...@java.net (JIRA)















































smadden
 commented on  JENKINS-17243


Cannot access Global Passwords















I noticed the same thing when working with a Free Style Project and using the "Execute Windows Batch Command" build step. I also have the latest envinject-plugin installed. Maybe it's related to that?

System:
Windows Server 2008
Jenkins Version 1.525
envinject-plugin Version 1.88



























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/groups/opt_out.

[JIRA] [publish-over-ssh] (JENKINS-19053) FATAL: HTML Publisher failure

2013-08-02 Thread brian.min...@colorado.edu (JIRA)















































Brian Mingus
 created  JENKINS-19053


FATAL: HTML Publisher failure















Issue Type:


Bug



Assignee:


bap



Components:


publish-over-ssh



Created:


02/Aug/13 4:26 PM



Description:


The master is OSX 10.8.3 running Jenkins 1.5.11, and the slave is Ubuntu 10.04.4 LTS Lucid Lynx. When trying to publish HTML reports, it freezes permanently. After killing the job the following stack trace is produced:

BUILD SUCCESSFUL
Total time: 29 minutes 48 seconds
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at BUILD level /home/builder/jenkins/workspace/sre-build-test-linux/branches/mingus/vcloud/sonic/.build/Debug/coverage_report to /Users/Shared/Jenkins/Home/jobs/sre-build-test-linux/builds/2013-08-01_17-04-54/htmlreports/Test_Coverage
FATAL: HTML Publisher failure
hudson.util.IOException2: hudson.util.IOException2: Failed to extract /home/builder/jenkins/workspace/sre-build-test-linux/branches/mingus/vcloud/sonic/.build/Debug/coverage_report/*/
	at hudson.FilePath.readFromTar(FilePath.java:2014)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1926)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1831)
	at htmlpublisher.HtmlPublisher.perform(HtmlPublisher.java:212)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)
	at hudson.model.Run.execute(Run.java:1600)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
Caused by: java.io.IOException
	at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175)
	at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61)
	at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:221)
	at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141)
	at java.util.zip.GZIPInputStream.read(GZIPInputStream.java:90)
	at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)
	at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223)
	at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228)
	at hudson.FilePath.readFromTar(FilePath.java:1992)
	... 12 more

	at hudson.FilePath.copyRecursiveTo(FilePath.java:1933)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1831)
	at htmlpublisher.HtmlPublisher.perform(HtmlPublisher.java:212)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)
	at hudson.model.Run.execute(Run.java:1600)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
Caused by: java.util.concurrent.ExecutionException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.Request$1.get(Request.java:278)
	at hudson.remoting.Request$1.get(Request.java:210)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1929)
	... 11 more
Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.Request.abort(Request.java:299)
	at hudson.remoting.Channel.terminate(Channel.java:732)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
Caused by: java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.SynchronousCommandTrans

[JIRA] [publish-over-ssh] (JENKINS-19053) FATAL: HTML Publisher failure

2013-08-02 Thread brian.min...@colorado.edu (JIRA)















































Brian Mingus
 updated  JENKINS-19053


FATAL: HTML Publisher failure
















Change By:


Brian Mingus
(02/Aug/13 4:27 PM)




Description:


The master is OSX 10.8.3 running Jenkins 1.
5.11
511
, and the slave is Ubuntu 10.04.4 LTS Lucid Lynx. When trying to publish HTML reports, it freezes permanently. After killing the job the following stack trace is produced:BUILD SUCCESSFULTotal time: 29 minutes 48 seconds[htmlpublisher] Archiving HTML reports...[htmlpublisher] Archiving at BUILD level /home/builder/jenkins/workspace/sre-build-test-linux/branches/mingus/vcloud/sonic/.build/Debug/coverage_report to /Users/Shared/Jenkins/Home/jobs/sre-build-test-linux/builds/2013-08-01_17-04-54/htmlreports/Test_CoverageFATAL: HTML Publisher failurehudson.util.IOException2: hudson.util.IOException2: Failed to extract /home/builder/jenkins/workspace/sre-build-test-linux/branches/mingus/vcloud/sonic/.build/Debug/coverage_report/**/*	at hudson.FilePath.readFromTar(FilePath.java:2014)	at hudson.FilePath.copyRecursiveTo(FilePath.java:1926)	at hudson.FilePath.copyRecursiveTo(FilePath.java:1831)	at htmlpublisher.HtmlPublisher.perform(HtmlPublisher.java:212)	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)	at hudson.model.Build$BuildExecution.post2(Build.java:183)	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)	at hudson.model.Run.execute(Run.java:1600)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.java:237)Caused by: java.io.IOException	at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175)	at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61)	at java.util.zip.InflaterInputStream.fill(InflaterInputStream.java:221)	at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:141)	at java.util.zip.GZIPInputStream.read(GZIPInputStream.java:90)	at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)	at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223)	at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228)	at hudson.FilePath.readFromTar(FilePath.java:1992)	... 12 more	at hudson.FilePath.copyRecursiveTo(FilePath.java:1933)	at hudson.FilePath.copyRecursiveTo(FilePath.java:1831)	at htmlpublisher.HtmlPublisher.perform(HtmlPublisher.java:212)	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)	at hudson.model.Build$BuildExecution.post2(Build.java:183)	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)	at hudson.model.Run.execute(Run.java:1600)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.java:237)Caused by: java.util.concurrent.ExecutionException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel	at hudson.remoting.Request$1.get(Request.java:278)	at hudson.remoting.Request$1.get(Request.java:210)	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)	at hudson.FilePath.copyRecursiveTo(FilePath.java:1929)	... 11 moreCaused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel	at hudson.remoting.Request.abort(Request.java:299)	at hudson.remoting.Channel.terminate(Channel.java:732)	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)Caused by: java.io.IOException: Unexpected termination of the channel	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)Caused by: java.io.EOFException	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2576)	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1295)

[JIRA] [core] (JENKINS-19052) upgrading from 1.523 to 1.524 or 1.525 breaks jenkins

2013-08-02 Thread mmostt...@harryanddavid.com (JIRA)















































Marcus Mosttler
 created  JENKINS-19052


upgrading from 1.523 to 1.524 or 1.525 breaks jenkins















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


02/Aug/13 4:12 PM



Description:


After upgrading from 1.523 to 1.524 or 1.525 The jenkins webapp is broken and shows the following on the page:

org.jvnet.hudson.reactor.ReactorException: java.lang.AssertionError: class hudson.plugins.active_directory.ActiveDirectorySecurityRealm is missing its descriptor
	at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
	at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
	at jenkins.model.Jenkins.executeReactor(Jenkins.java:906)
	at jenkins.model.Jenkins.(Jenkins.java:806)
	at hudson.model.Hudson.(Hudson.java:81)
	at hudson.model.Hudson.(Hudson.java:77)
	at hudson.WebAppMain$2.run(WebAppMain.java:214)
Caused by: java.lang.AssertionError: class hudson.plugins.active_directory.ActiveDirectorySecurityRealm is missing its descriptor
	at jenkins.model.Jenkins.getDescriptorOrDie(Jenkins.java:1175)
	at hudson.model.AbstractDescribableImpl.getDescriptor(AbstractDescribableImpl.java:35)
	at hudson.security.SecurityRealm.getDescriptor(SecurityRealm.java:178)
	at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.getDescriptor(ActiveDirectorySecurityRealm.java:154)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
	at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
	at groovy.lang.MetaClassImpl$GetBeanMethodMetaProperty.getProperty(MetaClassImpl.java:3457)
	at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:61)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227)
	at Script1.run(Script1.groovy:12)
	at hudson.util.spring.BeanBuilder.parse(BeanBuilder.java:135)
	at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.createSecurityComponents(ActiveDirectorySecurityRealm.java:130)
	at hudson.security.SecurityRealm.getSecurityComponents(SecurityRealm.java:398)
	at hudson.security.HudsonFilter.reset(HudsonFilter.java:134)
	at jenkins.model.Jenkins.setSecurityRealm(Jenkins.java:2041)
	at jenkins.model.Jenkins$20.run(Jenkins.java:2609)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:895)
	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$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

I copied by jenkins.war.bak to jenkins.war and restarted and am able to work again but I can't seem to upgrade Jenkins.  I was trying to upgrade since a fix for the buildresult trigger pluggin says it requires Jenkins 1.524.




Environment:


Windows 7 Server




Project:


Jenkins



Priority:


Major



Reporter:


Marcus Mosttler

























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







--

[JIRA] [configurationslicing] (JENKINS-19051) The configuration slicing crashes whenever I try to change an SCM Timer

2013-08-02 Thread julianpa...@fr.ibm.com (JIRA)















































Julian Payne
 created  JENKINS-19051


The configuration slicing crashes whenever I try to change an SCM Timer















Issue Type:


Bug



Affects Versions:


current



Assignee:


mdonohue



Components:


configurationslicing



Created:


02/Aug/13 3:44 PM



Description:


Whenever I try to change any SCM Timer entries I get a crash like this:

Stack trace

javax.servlet.ServletException: java.lang.UnsupportedOperationException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:217)
	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 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:118)
	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:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at winstone.FilterConfigurati

[JIRA] [core] (JENKINS-18800) Jenkins selects channel to wrong node for build job

2013-08-02 Thread martin.h.schroe...@intel.com (JIRA)















































Martin Schröder
 commented on  JENKINS-18800


Jenkins selects channel to wrong node for build job















Hello everyone.

Is there any update on this bug report? Because we currently see this issue occurring every few days on our heavily loaded main servers. The fact that the issue first shows itself by causing random-looking build failures only increases the problems raised by this bug.


Best regards,

Martin Schröder
 Intel Mobile Communications GmbH.



























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/groups/opt_out.

[JIRA] [envinject] (JENKINS-18411) Use RunAction2 from EnvInjectPluginAction















































Jesse Glick
 commented on  JENKINS-18411


Use RunAction2 from EnvInjectPluginAction















https://github.com/olivergondza/jenkins/commit/cf2bea4e58d86ef096fecafbf1395cd4b588e923 is proposed for backport so it may be available in 1.509.3 as well.



























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/groups/opt_out.

[JIRA] [buildresult-trigger] (JENKINS-18716) build is triggering to early

2013-08-02 Thread gregory.boissi...@gmail.com (JIRA)















































Gregory Boissinot
 updated  JENKINS-18716


build is triggering to early
















Change By:


Gregory Boissinot
(02/Aug/13 3:42 PM)




Component/s:


buildresult-trigger





Component/s:


buildresulttrigger



























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/groups/opt_out.

[JIRA] [rebuild] (JENKINS-18923) NPE when trying to rebuild last configuration from inside a View or trying triggering specific Matrix build

2013-08-02 Thread gregory.boissi...@gmail.com (JIRA)















































Gregory Boissinot
 commented on  JENKINS-18923


NPE when trying to rebuild last configuration from inside a View or trying triggering specific Matrix build















ScriptTrigger 0.30 fixes the second NPE.



























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/groups/opt_out.

[JIRA] [buildresult-trigger] (JENKINS-13793) Build isn't triggered after reboot

2013-08-02 Thread gregory.boissi...@gmail.com (JIRA)















































Gregory Boissinot
 updated  JENKINS-13793


Build isn't triggered after reboot
















Change By:


Gregory Boissinot
(02/Aug/13 3:11 PM)




Issue Type:


Bug
Improvement



























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/groups/opt_out.

[JIRA] [buildresult-trigger] (JENKINS-18889) BuildResultTrigger should not need to check for available nodes

2013-08-02 Thread gregory.boissi...@gmail.com (JIRA)
















































Gregory Boissinot
 resolved  JENKINS-18889 as Fixed


BuildResultTrigger should not need to check for available nodes
















Change By:


Gregory Boissinot
(02/Aug/13 3:07 PM)




Status:


Open
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/groups/opt_out.

[JIRA] [buildresult-trigger] (JENKINS-18889) BuildResultTrigger should not need to check for available nodes















































SCM/JIRA link daemon
 commented on  JENKINS-18889


BuildResultTrigger should not need to check for available nodes















Code changed in jenkins
User: Gregory Boissinot
Path:
 pom.xml
 src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java
http://jenkins-ci.org/commit/buildresult-trigger-plugin/e3e29b92c57f57a120cc0afa3a7da13b844f7c50
Log:
  Fix JENKINS-18889





























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/groups/opt_out.

[JIRA] [core] (JENKINS-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive
















































Jesse Glick
 resolved  JENKINS-18660 as Fixed


10,000+ jobs tied to a label make Node index page unusably unresponsive
















Yes, probably the JIRA link daemon was malfunctioning at the time of commit.





Change By:


Jesse Glick
(02/Aug/13 2:44 PM)




Status:


Open
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/groups/opt_out.

[JIRA] [plugin] (JENKINS-4543) Manually uploaded plugins are incorrectly unpacked















































Jesse Glick
 commented on  JENKINS-4543


Manually uploaded plugins are incorrectly unpacked















@danielbeck: that would be a reasonable RFE, though much lower priority I think since if you are manually rearranging the plugins directory it is assumed you know what you are doing.



























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/groups/opt_out.

[JIRA] [ec2] (JENKINS-18854) EC2 Plugin unable to connect to Eucalyptus 3.x

2013-08-02 Thread co...@pobox.com (JIRA)















































Colby Dyess
 commented on  JENKINS-18854


EC2 Plugin unable to connect to Eucalyptus 3.x















Cosmo, simply adding "/" to the end of the URLs will do the trick.




























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/groups/opt_out.

[JIRA] [teamconcert] (JENKINS-19050) RTC plugin is not recognizing Jazz 4.0.3

2013-08-02 Thread julianpa...@fr.ibm.com (JIRA)















































Julian Payne
 created  JENKINS-19050


RTC plugin is not recognizing Jazz 4.0.3















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


teamconcert



Created:


02/Aug/13 2:08 PM



Description:


When trying to use Jazz 4.0.3 the plugin is not recognizing the toolkit. The same job works fine with Jazz 3.0.1.6

This is the message that I get from the plugin:

Started by user julianpa...@fr.ibm.com
Building remotely on ncedemeter01 in workspace /data/jenkins/workspace/BackupReleaseAssetRepository
RTC : checkout...
FATAL: RTC : checkout failure: Built toolkit directory not found at: /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit 
java.lang.IllegalArgumentException: Built toolkit directory not found at: /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit 
	at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory.newFacade(RTCFacadeFactory.java:149)
	at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory.getFacade(RTCFacadeFactory.java:67)
	at com.ibm.team.build.internal.hjplugin.RTCScm.checkout(RTCScm.java:727)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1394)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
	at hudson.model.Run.execute(Run.java:1593)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:247)
ERROR: RTC : checkout failure: Built toolkit directory not found at: /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit 

If I go to the machine "ncedemeter01" and do "ls -l /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit" I get this:

ncedemeter01.francelab.fr.ibm.com% ls -l /data/tools/RTC-BuildSystem-4/jazz/buildsystem/buildtoolkit
total 39556
-rwxrwxrwx 1 jenkins solver  345035 May 18 01:37 apache-mime4j-0.6.jar
-rwxrwxrwx 1 jenkins solver4254 May 18 01:37 BuildToolkitTaskDefs.xml
-rwxrwxrwx 1 jenkins solver 6451214 May 18 01:37 com.ibm.icu_4.2.1.v20100412.jar
-rwxrwxrwx 1 jenkins solver  125529 May 18 01:37 com.ibm.team.build.client_3.0.500.v20130315_0142.jar
-rwxrwxrwx 1 jenkins solver   33873 May 18 01:37 com.ibm.team.build.client.nl1_3.0.4.v201305091351.jar
-rwxrwxrwx 1 jenkins solver   15034 May 18 01:37 com.ibm.team.build.client.nl2_3.0.3.v201211091526.jar
-rwxrwxrwx 1 jenkins solver  705908 May 18 01:37 com.ibm.team.build.common_3.1.400.v20130415_0257.jar
-rwxrwxrwx 1 jenkins solver   57437 May 18 01:37 com.ibm.team.build.common.nl1_3.1.2.v201305091351.jar
-rwxrwxrwx 1 jenkins solver   25873 May 18 01:37 com.ibm.team.build.common.nl2_3.1.2.v201305091343.jar
-rwxrwxrwx 1 jenkins solver  282616 May 18 01:37 com.ibm.team.build.toolkit_3.0.500.v20130428_0234.jar
-rwxrwxrwx 1 jenkins solver   98538 May 18 01:37 com.ibm.team.build.toolkit.nl1_3.0.5.v201305091352.jar
-rwxrwxrwx 1 jenkins solver   42498 May 18 01:37 com.ibm.team.build.toolkit.nl2_3.0.5.v201305091343.jar
-rwxrwxrwx 1 jenkins solver   50586 May 18 01:37 com.ibm.team.calm.foundation.client_3.1.200.v20120924_1445.jar
-rwxrwxrwx 1 jenkins solver   26751 May 18 01:37 com.ibm.team.calm.foundation.client.nl1_3.1.2.v201305091352.jar
-rwxrwxrwx 1 jenkins solver   12261 May 18 01:37 com.ibm.team.calm.foundation.client.nl2_3.1.1.v201305091343.jar
-rwxrwxrwx 1 jenkins solver  290464 May 18 01:37 com.ibm.team.calm.foundation.common_3.1.300.v20130509_0147.jar
-rwxrwxrwx 1 jenkins solver   48849 May 18 01:37 com.ibm.team.calm.foundation.common.nl1_3.1.2.v201305091352.jar
-rwxrwxrwx 1 jenkins solver   21678 May 18 01:37 com.ibm.team.calm.foundation.common.nl2_3.1.2.v201305091343.jar
-rwxrwxrwx 1 jenkins solver9346 May 18 01:37 com.ibm.team.dev.jdojo.runtime.common_3.0.500.v20130415_0257.jar
-rwxrwxrwx 1 jenkins solver   62036 May 18 01:37 com.ibm.team.enterprise.automation.common_3.1.200.v20120924_1445.jar
-rwxrwxrwx 1 jenkins

[JIRA] [jenkins-multijob-plugin] (JENKINS-19015) jenkins-multijob-plugin - Multijob plugin throws CancellationException

2013-08-02 Thread jacekkowalczy...@gmail.com (JIRA)















































Jacek Kowalczyk
 updated  JENKINS-19015


jenkins-multijob-plugin - Multijob plugin throws CancellationException
















proposed patch for issue JENKINS-19015





Change By:


Jacek Kowalczyk
(02/Aug/13 2:10 PM)




Attachment:


0001-proposed-solution-for-issue-JENKINS-19015.patch



























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/groups/opt_out.

[JIRA] [maven] (JENKINS-18183) After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.

2013-08-02 Thread ho...@se-rwth.de (JIRA)















































Andreas Horst
 commented on  JENKINS-18183


After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.















I can confirm this on 1.522.



























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/groups/opt_out.

[JIRA] [git] (JENKINS-4418) do shallow clone by default

2013-08-02 Thread peter.gerstm...@gmail.com (JIRA)















































Peter Gerstmann
 commented on  JENKINS-4418


do shallow clone by default















Limiting disk space footprint is key for automated builds, as are speedier checkout times. If this enhancement can deliver both, it should be a no-brainer.
So default or optional, either way is fine; this is very much a desired feature.



























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/groups/opt_out.

[JIRA] [git] (JENKINS-4418) do shallow clone by default

2013-08-02 Thread ope...@gmail.com (JIRA)















































Nathan Baker
 commented on  JENKINS-4418


do shallow clone by default















I would see this as a nice feature that could speed up the build process and make network admins happier from moving large project over the network.



























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/groups/opt_out.

[JIRA] [buildresult-trigger] (JENKINS-18889) BuildResultTrigger should not need to check for available nodes















































SCM/JIRA link daemon
 commented on  JENKINS-18889


BuildResultTrigger should not need to check for available nodes















Code changed in jenkins
User: Gregory Boissinot
Path:
 src/main/java/org/jenkinsci/lib/xtrigger/AbstractTrigger.java
 src/main/java/org/jenkinsci/lib/xtrigger/AbstractTriggerByFullContext.java
http://jenkins-ci.org/commit/xtrigger-lib/f35d4f8a610eefafc3fc99925b6b1c304f5367d2
Log:
  Add functionality: Enable to not require a polling node.
Fix JENKINS-18889





























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/groups/opt_out.

[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space

2013-08-02 Thread david.is...@gmail.com (JIRA)















































David Ishee
 commented on  JENKINS-18929


OutOfMemoryError: PermGen space















After a few more days:


jmap -heap 32633
Attaching to process ID 32633, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 14.3-b01

using thread-local object allocation.
Parallel GC with 4 thread(s)

Heap Configuration:
   MinHeapFreeRatio = 40
   MaxHeapFreeRatio = 70
   MaxHeapSize  = 1572864000 (1500.0MB)
   NewSize  = 2686976 (2.5625MB)
   MaxNewSize   = 17592186044415 MB
   OldSize  = 5439488 (5.1875MB)
   NewRatio = 2
   SurvivorRatio= 8
   PermSize = 21757952 (20.75MB)
   MaxPermSize  = 268435456 (256.0MB)

Heap Usage:
PS Young Generation
Eden Space:
   capacity = 47382528 (45.1875MB)
   used = 4997064 (4.765571594238281MB)
   free = 42385464 (40.42192840576172MB)
   10.546216529434647% used
>From Space:
   capacity = 6291456 (6.0MB)
   used = 1802240 (1.71875MB)
   free = 4489216 (4.28125MB)
   28.6458332% used
To Space:
   capacity = 7077888 (6.75MB)
   used = 0 (0.0MB)
   free = 7077888 (6.75MB)
   0.0% used
PS Old Generation
   capacity = 202375168 (193.0MB)
   used = 142506192 (135.9044952392578MB)
   free = 59868976 (57.09550476074219MB)
   70.41683691153254% used
PS Perm Generation
   capacity = 98893824 (94.3125MB)
   used = 91663704 (87.41732025146484MB)
   free = 7230120 (6.895179748535156MB)
   92.68900755622515% used





























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/groups/opt_out.

[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters

2013-08-02 Thread angela.bauer....@rohde-schwarz.com (JIRA)















































Andrejs Šitals
 commented on  JENKINS-18534


Cannot add new build to queue from same project with different parameters















Shannon Kerr, good job on isolating this. I'm also waiting for a fix, but I didn't know how to reproduce the problem (tried with string parameters, but they worked fine).

As for workarounds, I think BUILD_NUMBER could be passed to a downstream job as a parameter by using "Predefined parameters" in "Trigger parameterized build on other projects" step - that should solve the problem with merged downstream jobs.



























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/groups/opt_out.

[JIRA] [maven] (JENKINS-18895) MavenModuleSetBuild.getResult is expensive

2013-08-02 Thread te...@java.net (JIRA)















































teilo
 updated  JENKINS-18895


MavenModuleSetBuild.getResult is expensive
















Change By:


teilo
(02/Aug/13 12:15 PM)




Labels:


lazy-loading
 lts-candidate
 performance



























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/groups/opt_out.

[JIRA] [core] (JENKINS-19049) java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson

2013-08-02 Thread jie...@java.net (JIRA)















































jieryn
 updated  JENKINS-19049


java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson
















Change By:


jieryn
(02/Aug/13 12:12 PM)




Assignee:


jieryn





Component/s:


core





Component/s:


configure-job-column



























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/groups/opt_out.

[JIRA] [configure-job-column] (JENKINS-19049) java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson

Angela Bauer
created JENKINS-19049

java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson

Issue Type:

Bug

Affects Versions:

current

Assignee:

jieryn

Attachments:

JavaException.TXT

Components:

configure-job-column

Created:

02/Aug/13 12:09 PM

Description:

javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
...

occurred in the following context:
I made a new job, edit view, selected the new job to enhance the view, SAVE, then the above exception occurred. Coming back to the view, the new job was integrated.

The same happened to a colleague, when saving new roles.

The issue is not blocking us, but I think it should be corrected ...

About two weeks ago, I installed Jenkins 1522.

Due Date:

30/Aug/13 12:00 AM

Environment:

Windows XP Professional, Version 2002, SP3

Intel(R)Xeon(R) CPU

X5670 @ 2.93 GHz

2,67 GHz, 2,00 GB of RAM

Physical Address Extension

Fix Versions:

current

Project:

Jenkins

Priority:

Major

Reporter:

Angela Bauer

[JIRA] [join] (JENKINS-16922) Join plugin does not trigger when the downstream builds are complete















































Andrejs Šitals
 commented on  JENKINS-16922


Join plugin does not trigger when the downstream builds are complete















Similar issues here - join trigger often does not work. We have a "starter job" that prepares some files, some "platform jobs" that do the stuff on multiple platforms, and a "collector job" that collects artifacts from the "platform jobs" - the collector often fails to start.



























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/groups/opt_out.

[JIRA] [join] (JENKINS-16922) Join plugin does not trigger when the downstream builds are complete













































  
Andrejs Šitals
 edited a comment on  JENKINS-16922


Join plugin does not trigger when the downstream builds are complete
















Similar issues here - join trigger often does not work. We have a "starter job" that prepares some files, some "platform jobs" that do the stuff on multiple platforms, and a "collector job" that collects artifacts from the "platform jobs" - the collector often fails to start.

Using 1.523 currently, but the same issue was with older Jenkins versions.



























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/groups/opt_out.

[JIRA] [rebuild] (JENKINS-18923) NPE when trying to rebuild last configuration from inside a View or trying triggering specific Matrix build

2013-08-02 Thread deyan.pav...@microfocus.com (JIRA)















































deyan pavlov
 commented on  JENKINS-18923


NPE when trying to rebuild last configuration from inside a View or trying triggering specific Matrix build















I have solved very similar issue, just a bit different NPE, by updating the plug-in ScriptTrigger to 0.30 Prior to that version can't work together with recent verions of Jenkins.



























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/groups/opt_out.

[JIRA] [global-build-stats] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs













































  
John Waitforit
 edited a comment on  JENKINS-15969


Build Stats Plugin Returns so much data it hangs
















I am experiencing this problem.

Jenkins version: 1.473
Global Stats Plugin version: 1.3
Chrome version, if relevant: 28.0.1500.71

The course of events:

	installed the plugin, restarted jenkins
	created 4 graphs, then edited their dimensions, range, etc.
	reordered the graphs on the page - worked for most of them, but when I tried to move the last one up I got some error (in an alert window)
	reloaded page - then reloading took so long it crashed the page
	using task manager in chrome I observed that the memory usage went over 1GB for just that page
	the developer tools showed a very large json file downloaded for /global-build-stats/api/json?depth=2
	when that finished, it spawned a huge number of requests to obtain the graph images - those actually killed the page
	somewhere in between I investigated the files on the server
	I tried to remove the file global-build-stats.xml, no luck - it gets regenerated
	I tried to edit it and leave only a few  nodes (note that there are literally thousands of  nodes having the following template , where {number} seem to be random numbers (up to or over 125), with 7 and 2 being probably the most frequent (not sure if relevant)
	editing that file didn't seem to fix it (file got regenerated and overwritten)
	I also tried to clear the data in global-build-stats/jobresults, but nothing changed (the data for the last month seems to be regenerated)



Note that the json returned by global/build-stats/api/json?depth=2 returns that large json which actually contains mostly the same two graphs repeated over and over again (hundreds, maybe thousands of times). Also, I requested, as suggested, that deleteConfiguration resource - which returned "ok" (whatever, some short json with "ok" in it), but the chart generation resource still returns the chart image for that same id.



























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/groups/opt_out.

[JIRA] [subversion] (JENKINS-17867) Allow manual builds of different branches













































  
Andrejs Šitals
 edited a comment on  JENKINS-17867


Allow manual builds of different branches
















This was unexpected to us as well. Additionally, few days ago the job somehow switched back to "trunk" few minutes after it was run manually to test a branch. Later, both "chains" of builds mixed together, i.e., triggered a single downstream build from two different upstream builds. Upstream builds had different parameters which are passed to downstream jobs, therefore there had to be 2 downstream builds to test both branch and trunk.

Possible workaround for polling issue - remove SCM polling from your "starter job" and add 2 new jobs - one for polling (set depths to "empty"), another for running it manually. Then, use "Trigger parameterized build on other projects" to run your current "starter job".



























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/groups/opt_out.

[JIRA] [plugin] (JENKINS-17158) Quiet subversion checkout?















































Andrejs Šitals
 commented on  JENKINS-17158


Quiet subversion checkout?















If you only want to detect that there are changes without actually downloading them, then you can set "Repository depth option" to "empty". This will still trigger new builds on CSM changes, but won't download any files.



























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/groups/opt_out.

[JIRA] [global-build-stats] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs















































John Waitforit
 updated  JENKINS-15969


Build Stats Plugin Returns so much data it hangs
















Change By:


John Waitforit
(02/Aug/13 10:42 AM)




Priority:


Minor
Critical



























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/groups/opt_out.

[JIRA] [plot] (JENKINS-18644) Loading Overlay

2013-08-02 Thread ogon...@gmail.com (JIRA)
















































Oliver Gondža
 resolved  JENKINS-18644 as Duplicate


Loading Overlay
















Original issue is fixed





Change By:


Oliver Gondža
(02/Aug/13 10:38 AM)




Status:


Open
Resolved





Resolution:


Duplicate



























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/groups/opt_out.

[JIRA] [subversion] (JENKINS-17867) Allow manual builds of different branches













































  
Andrejs Šitals
 edited a comment on  JENKINS-17867


Allow manual builds of different branches
















This was unexpected to us as well. Additionally, few days ago the job somehow switched back to "trunk" few minutes after it was run manually to test a branch. Later, both "chains" of builds mixed together, i.e., triggered a single downstream build from two different upstream builds. Upstream builds had different parameters which are passed to downstream jobs, therefore there had to be 2 downstream builds to test both branch and trunk.

Possible workaround for polling issue - remove SCM polling from your "starter job" and add 2 new jobs - one for polling, another for running it manually. Then, use "Trigger parameterized build on other projects" to run your current "starter job".



























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/groups/opt_out.

[JIRA] [subversion] (JENKINS-17867) Allow manual builds of different branches















































Andrejs Šitals
 commented on  JENKINS-17867


Allow manual builds of different branches















This was unexpected to us as well. Additionally, few days ago the job somehow switched back to "trunk" few minutes after it was run manually to test a branch. Later, both "chains" of builds mixed together, i.e., triggered a single downstream build from two different upstream builds. Upstream builds had different parameters which are passed to downstream jobs, therefore there had to be 2 downstream builds to test both branch and trunk.

Possible workaround - remove SCM polling from your "starter job" and add 2 new jobs - one for polling, another for running it manually. Then, use "Trigger parameterized build on other projects" to run your current "starter job".



























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/groups/opt_out.

[JIRA] [ssh-slaves] (JENKINS-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel

2013-08-02 Thread steve.ossel...@gmail.com (JIRA)















































Steve Osselton
 commented on  JENKINS-18706


ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel















Am seeing exact same stack trace for Jenkins 1.525 with a Solaris slave. This slave was working
fine with an older release (not sure of the version). Have a variety of Linux slaves that are all
still working fine. On trying to re-launch slave:

java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
	at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2595)
	at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)
	at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
	at hudson.remoting.Command.readFrom(Command.java:92)
	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)




























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/groups/opt_out.

[JIRA] [core] (JENKINS-18674) TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened

2013-08-02 Thread ogon...@gmail.com (JIRA)
















































Oliver Gondža
 resolved  JENKINS-18674 as Fixed


TypeError: registry is undefined in prototype.js:5621 when plot plugin publisher configuration reopened
















I have created reproducing selenium test[1] that works on master so I am resolving the issue. Fixed by https://github.com/jenkinsci/jenkins/commit/12c3efc02d42e30ab6a7018cf0f89e5e0b881d07. It is present in rc branch so I assume it will be in 1.526 (the build is broken so I have not verified the fix against rc branch).

[1] https://github.com/jenkinsci/selenium-tests/commit/5cc84aa2b0a369030e9cea3ea875f99821480028





Change By:


Oliver Gondža
(02/Aug/13 10:25 AM)




Status:


Open
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/groups/opt_out.

[JIRA] [global-build-stats] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs













































  
John Waitforit
 edited a comment on  JENKINS-15969


Build Stats Plugin Returns so much data it hangs
















I am experiencing this problem.

Jenkins version: 1.473
Global Stats Plugin version: 1.3
Chrome versions, if relevant: 28.0.1500.71

The course of events:

	installed the plugin, restarted jenkins
	created 4 graphs, then edited their dimensions, range, etc.
	reordered the graphs on the page - worked for most of them, but when I tried to move the last one up I got some error (in an alert window)
	reloaded page - then reloading took so long it crashed the page
	using task manager in chrome I observed that the memory usage went over 1GB for just that page
	the developer tools showed a very large json file downloaded for /global-build-stats/api/json?depth=2
	when that finished, it spawned a huge number of requests to obtain the graph images - those actually killed the page
	somewhere in between I investigated the files on the server
	I tried to remove the file global-build-stats.xml, no luck - it gets regenerated
	I tried to edit it and leave only a few  nodes (note that there are literally thousands of  nodes having the following template , where {number} seem to be random numbers (up to or over 125), with 7 and 2 being probably the most frequent (not sure if relevant)
	editing that file didn't seem to fix it (file got regenerated and overwritten)
	I also tried to clear the data in global-build-stats/jobresults, but nothing changed (the data for the last month seems to be regenerated)



Note that the json returned by global/build-stats/api/json?depth=2 returns that large json which actually contains mostly the same two graphs repeated over and over again (hundreds, maybe thousands of times). Also, I requested, as suggested, that deleteConfiguration resource - which returned "ok" (whatever, some short json with "ok" in it), but the chart generation resource still returns the chart image for that same id.



























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/groups/opt_out.

[JIRA] [global-build-stats] (JENKINS-15969) Build Stats Plugin Returns so much data it hangs















































John Waitforit
 reopened  JENKINS-15969


Build Stats Plugin Returns so much data it hangs
















I am experiencing this problem.

Jenkins version: 1.473
Global Stats Plugin version: 1.3
Chrome versions, if relevant: 28.0.1500.71

The course of events:

	installed the plugin, restarted jenkins
	created 4 graphs, then edited their dimensions, range, etc.
	reordered the graphs on the page - worked for most of them, but when I tried to move the last one up I got some error (in an alert window)
	reloaded page - then reloading took so long it crashed the page
	using task manager in chrome I observed that the memory usage went over 1GB for just that page
	the developer tools showed a very large json file downloaded for /global-build-stats/api/json?depth=2
	when that finished, it spawned a huge number of requests to obtain the graph images - those actually killed the page
	somewhere in between I investigated the files on the server
	I tried to remove the file global-build-stats.xml, no luck - it gets regenerated
	I tried to edit it and leave only a few  nodes (note that there are literally thousands of  nodes having the following template , where {number} seem to be random numbers (up to or over 125), with 7 and 2 being probably the most frequent (not sure if relevant)
	editing that file didn't seem to fix it (file got regenerated and overwritten)
	I also tried to clear the data in global-build-stats/jobresults, but nothing changed (the data for the last month seems to be regenerated)



Note that the json returned by global/build-stats/api/json?depth=2 returns that large json which actually contains the same two tables repeated over and over again (hundreds, maybe thousands of times). Also, I requested, as suggested, that deleteConfiguration resource - which returned "ok" (whatever, some short json with "ok" in it), but the chart generation resource still returns the chart image for that same id.





Change By:


John Waitforit
(02/Aug/13 10:17 AM)




Resolution:


Fixed





Status:


Closed
Reopened



























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/groups/opt_out.

[JIRA] [findbugs] (JENKINS-15049) New column: Number of FindBugs issues

2013-08-02 Thread sschube...@gmail.com (JIRA)















































Sebastian Schuberth
 commented on  JENKINS-15049


New column: Number of FindBugs issues















I'm sorry but I probably won't find the time to implement this any time soon.



























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/groups/opt_out.

[JIRA] [cobertura] (JENKINS-12640) Cobertura plugin should not fail maven build for maven release

2013-08-02 Thread croesusk...@gmail.com (JIRA)















































Croesus Kall
 commented on  JENKINS-12640


Cobertura plugin should not fail maven build for maven release















Just in case someone runs into this again.

In version 1.8 of the cobertura plugin an option was added in the "Publish Cobertura Coverage Report" configuration:

	Advanced -> Fail if no reports
Leave it unchecked in order to make the maven release plugin play nice.



ref: https://github.com/jenkinsci/cobertura-plugin/commit/46f5af5abf7750f751231fd32239fce7bd982fc4, JENKINS-14552





























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/groups/opt_out.

[JIRA] [clearcase-ucm] (JENKINS-18281) Possibility to remove the contributing activities from the change set of the build, case 9488

2013-08-02 Thread mdeb...@gmail.com (JIRA)















































Marc De Boeck
 commented on  JENKINS-18281


Possibility to remove the contributing activities from the change set of the build, case 9488















For me, the best solution that would cover all possible cases would be to have three options. This way, we can choose when configuring the plugin. 

option 1:  like it is now (with all change sets of the contributing activities visible)
option 2: show only the change set from the stream itself, but show also the list of contributing activities (without further details about the changes per activity).
option 3: show only the change set from the stream itself (sorted per activity).




























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/groups/opt_out.

[JIRA] [git] (JENKINS-18328) GitLab repoisitory browser creates defective file link















































SCM/JIRA link daemon
 commented on  JENKINS-18328


GitLab repoisitory browser creates defective file link















Code changed in jenkins
User: Nicolas De loof
Path:
 src/main/java/hudson/plugins/git/browser/GitLab.java
http://jenkins-ci.org/commit/git-plugin/58997a88a07fb64c173c8e7148b8d28ac8a92da5
Log:
  Merge pull request #164 from olafmandel/JENKINS-18328

[FIXED JENKINS-18328] Defective file link for GitLab browsers


Compare: https://github.com/jenkinsci/git-plugin/compare/c5b127f98ebc...58997a88a07f




























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/groups/opt_out.

[JIRA] [git] (JENKINS-18328) GitLab repoisitory browser creates defective file link
















































SCM/JIRA link daemon
 resolved  JENKINS-18328 as Fixed


GitLab repoisitory browser creates defective file link
















Change By:


SCM/JIRA link daemon
(02/Aug/13 8:50 AM)




Status:


Open
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/groups/opt_out.

[JIRA] [git] (JENKINS-18328) GitLab repoisitory browser creates defective file link















































SCM/JIRA link daemon
 commented on  JENKINS-18328


GitLab repoisitory browser creates defective file link















Code changed in jenkins
User: Olaf Mandel
Path:
 src/main/java/hudson/plugins/git/browser/GitLab.java
http://jenkins-ci.org/commit/git-plugin/73249eeac564567f86d8e7d70cf85efa5e5f0b5b
Log:
  Adapt file link for GitLab 5.2

Fix the defective file link for GitLab browsers:

For older GitLab versions, there was a duplicate slash and for
newer versions the link is completely wrong. Fix both:

Old:   http://urlbase//0123456789...01234567/tree/file.name
<5.2:  http://urlbase/0123456789...01234567/tree/file.name
>=5.2: http://urlbase/blob/0123456789...01234567/file.name

Note: I do not know at which version of GitLab the new link
  format was introduced. This patch assumes 5.2.0, but it
  may be that older versions already need the new format.

Closes #JENKINS-18328





























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/groups/opt_out.

[JIRA] [core] (JENKINS-18879) Collecting finbugs analysis results randomly fails with exception

2013-08-02 Thread baradari.ra...@googlemail.com (JIRA)















































Ramin Baradari
 commented on  JENKINS-18879


Collecting finbugs analysis results randomly fails with exception















I'll try to downgrade to the LTS monday morning as I can't change it during the day.



























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/groups/opt_out.

[JIRA] [analysis-core] (JENKINS-18954) add console log line for reason that the build is marked as unstable when thresholds are exceeded















































Ulli Hafner
 commented on  JENKINS-18954


add console log line for reason that the build is marked as unstable when thresholds are exceeded















I see. I'll append that information to the console log.



























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/groups/opt_out.

[JIRA] [analysis-core] (JENKINS-18954) add console log line for reason that the build is marked as unstable when thresholds are exceeded













































  
Ulli Hafner
 edited a comment on  JENKINS-18954


add console log line for reason that the build is marked as unstable when thresholds are exceeded
















I see. I'll append the status information to the console log.



























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/groups/opt_out.

[JIRA] [analysis-core] (JENKINS-19047) Incorrect compareTo method















































Ulli Hafner
 commented on  JENKINS-19047


Incorrect compareTo method















It would be good if also all existing parsers would be checked to see if they correctly assign the column number for 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/groups/opt_out.

[JIRA] [core] (JENKINS-18879) Collecting finbugs analysis results randomly fails with exception















































Ulli Hafner
 commented on  JENKINS-18879


Collecting finbugs analysis results randomly fails with exception















Can you please check if this happens with the LTS Jenkins version, too?



























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/groups/opt_out.

[JIRA] [jenkins-tracker] (JENKINS-19048) Better place for "Delete project" link in the lefthand menu

2013-08-02 Thread deyan.pav...@microfocus.com (JIRA)















































deyan pavlov
 created  JENKINS-19048


Better place for "Delete project" link in the lefthand menu















Issue Type:


Improvement



Assignee:


Unassigned


Components:


jenkins-tracker



Created:


02/Aug/13 7:59 AM



Description:


I'd like to ask for another place of the link "Delete project" which currently is just between "Build project" and "Configure", which are the most used probably and having in between an option to delete the work, although with a confirmation dialog (which saved me) could be improved. I'd suggest the lowest possible.




Project:


Jenkins



Labels:


gui




Priority:


Minor



Reporter:


deyan pavlov

























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/groups/opt_out.

[JIRA] [rebuild] (JENKINS-18923) NPE when trying to rebuild last configuration from inside a View or trying triggering specific Matrix build

2013-08-02 Thread deyan.pav...@microfocus.com (JIRA)















































deyan pavlov
 commented on  JENKINS-18923


NPE when trying to rebuild last configuration from inside a View or trying triggering specific Matrix build















If I want to change a configuration setting or even without any change, just clicking Save, shows similar problem with the Oops! page and different NPE in the backgrond: at org.jenkinsci.plugins.scripttrigger.ScriptTrigger.getLogFile(ScriptTrigger.java:66)
This is intermittent, at least so far I can't give exact steps to reproduce but happens every now and then.
The web link that it tries to load is %JENKINS_URL%/view/myView/job/myJob/configSubmit
If I click "Apply", then an empty error dialog appears and that same Oops page opens in a different tab.
It's not browser specific.


javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:726)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:217)
	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:206)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
	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:118)
	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:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.sec

[JIRA] [findbugs] (JENKINS-15049) New column: Number of FindBugs issues