[JIRA] [core] (JENKINS-26582) Unexpected Executor Death - build already existed - 1.597
Mark Sinclair created JENKINS-26582 Unexpected Executor Death - build already existed - 1.597 Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Jan/15 5:34 AM Description: Jan 23, 2015 11:43:52 PM hudson.model.Executor run SEVERE: Unexpected executor death java.lang.IllegalStateException: /MY_DIR/jenkins/home/jobs/MY_JOB/builds/29 already existed; will not overwite with MY_JOB #29 at hudson.model.RunMap.put(RunMap.java:187) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1001) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1200) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor.run(Executor.java:213) I tried to manually start a job via the run button. I see the Dead indicator in the executor status sidebar. I was able to restart the thread and then manually start the job again. This time it started with #30 and appears to be running OK. Looking at JENKINS_HOME dir in linux, I see that there is a build directory for #29 and the job ran and failed (unrelated). Looking at the Jenkins webpage for the job, the build skips from 28 to (the now running) 30. #29 has no listing. I know some items related to the major enhancement are not closed yet, like JENKINS-23152, so please close this if the behavior I'm seeing is expected until the next release. If this is unexpected - hopefully this report is informative - this issue happened 4x in a row for each job I had put in the build queue. Environment: Jenkins 1.597 Project: Jenkins Priority: Major Reporter: Mark Sinclair This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-19094) HOME Env variable is NOT SET in Build Shell Command
apgray edited a comment on JENKINS-19094 HOME Env variable is NOT SET in Build Shell Command Is there some other workaround for this? Its been open for over a year. I'm trying to get Intern execute JS tests of an angular application in Jenkins and SauceLabs We are running Jenkins as a Windows Service on Windows 2012. /root might work if Jenkins is installed on a *ux boxHow about some love for Windows? What value should I set this HOME environment variable to for a windows box? \root does not work. This is the build output in my Jenkins console: C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example>npm install npm WARN package.json angularjs-intern-example@0.1.0 No repository field. > angularjs-intern-example@0.1.0 postinstall C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example > bower install 'bower' is not recognized as an internal or external command, operable program or batch file. npm ERR! angularjs-intern-example@0.1.0 postinstall: `bower install` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the angularjs-intern-example@0.1.0 postinstall script. npm ERR! This is most likely a problem with the angularjs-intern-example package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! bower install npm ERR! You can get their info via: npm ERR! npm owner ls angularjs-intern-example npm ERR! There is likely additional logging output above. npm ERR! System Windows_NT 6.2.9200 npm ERR! command "C:\\PROGRA~2\\nodejsnode.exe" "C:\\PROGRA~2\\nodejs\\node_modules\\npm\\binnpm-cli.js" "install" npm ERR! cwd C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example npm ERR! node -v v0.10.35 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npmBuild step 'Execute Windows batch command' marked build as failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-19094) HOME Env variable is NOT SET in Build Shell Command
apgray edited a comment on JENKINS-19094 HOME Env variable is NOT SET in Build Shell Command Is there some other workaround for this? Its been open for over a year. I'm trying to get We are running Jenkins as a Windows Service on Windows 2012. /root might work if Jenkins is installed on a *ux boxHow about some love for Windows? What value should I set this HOME environment variable to for a windows box? \root does not work. This is the build output in my Jenkins console: C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example>npm install npm WARN package.json angularjs-intern-example@0.1.0 No repository field. > angularjs-intern-example@0.1.0 postinstall C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example > bower install 'bower' is not recognized as an internal or external command, operable program or batch file. npm ERR! angularjs-intern-example@0.1.0 postinstall: `bower install` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the angularjs-intern-example@0.1.0 postinstall script. npm ERR! This is most likely a problem with the angularjs-intern-example package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! bower install npm ERR! You can get their info via: npm ERR! npm owner ls angularjs-intern-example npm ERR! There is likely additional logging output above. npm ERR! System Windows_NT 6.2.9200 npm ERR! command "C:\\PROGRA~2\\nodejsnode.exe" "C:\\PROGRA~2\\nodejs\\node_modules\\npm\\binnpm-cli.js" "install" npm ERR! cwd C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example npm ERR! node -v v0.10.35 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npmBuild step 'Execute Windows batch command' marked build as failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-19094) HOME Env variable is NOT SET in Build Shell Command
apgray commented on JENKINS-19094 HOME Env variable is NOT SET in Build Shell Command Is there some other workaround for this? Its been open for over a year. I'm trying to get We are running Jenkins as a Windows Service on Windows 2012. /root might work if Jenkins is installed on a *ux boxHow about some love for Windows? What value should I set this HOME environment variable to for a windows box? \root does not work. This is the build output in my Jenkins console: `C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example>npm install npm WARN package.json angularjs-intern-example@0.1.0 No repository field. > angularjs-intern-example@0.1.0 postinstall C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example > bower install 'bower' is not recognized as an internal or external command, operable program or batch file. npm ERR! angularjs-intern-example@0.1.0 postinstall: `bower install` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the angularjs-intern-example@0.1.0 postinstall script. npm ERR! This is most likely a problem with the angularjs-intern-example package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! bower install npm ERR! You can get their info via: npm ERR! npm owner ls angularjs-intern-example npm ERR! There is likely additional logging output above. npm ERR! System Windows_NT 6.2.9200 npm ERR! command "C:\\PROGRA~2\\nodejsnode.exe" "C:\\PROGRA~2\\nodejs\\node_modules\\npm\\binnpm-cli.js" "install" npm ERR! cwd C:\Program Files (x86)\Jenkins\jobs\InternAngularExample\workspace\angularjs-example npm ERR! node -v v0.10.35 npm ERR! npm -v 1.4.28 npm ERR! code ELIFECYCLE npmBuild step 'Execute Windows batch command' marked build as failure` This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Jesse Glick updated JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Change By: Jesse Glick (24/Jan/15 2:26 AM) Labels: jnlp remoting security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
Jesse Glick updated JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Change By: Jesse Glick (24/Jan/15 2:26 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26101) Load entire script from SCM
Jesse Glick resolved JENKINS-26101 as Fixed Load entire script from SCM Change By: Jesse Glick (24/Jan/15 2:21 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26101) Load entire script from SCM
SCM/JIRA link daemon commented on JENKINS-26101 Load entire script from SCM Code changed in jenkins User: Jesse Glick Path: CHANGES.md TUTORIAL.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsScmFlowDefinitionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/SubversionStepTest.java api/src/main/java/org/jenkinsci/plugins/workflow/flow/FlowDefinition.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/PushdStep.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/ReadFileStep.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/RelativePathValidator.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/WriteFileStep.java basic-steps/src/test/java/org/jenkinsci/plugins/workflow/steps/RelativePathValidatorTest.java cps/pom.xml cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowExecution.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowFactoryAction.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsFlowFactoryAction2.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/FlowHead.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/Snippetizer.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/config.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/help-snippetizer.html cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/help-scm.html cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/help-scriptPath.html cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/block.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/Snippetizer/help.html cps/src/test/groovy/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinitionTest.groovy cps/src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java demo/Dockerfile demo/JENKINS_HOME/jobs/cd/config.xml demo/JENKINS_HOME/scriptApproval.xml demo/README.md job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java scm-step/src/main/java/org/jenkinsci/plugins/workflow/steps/scm/GenericSCMStep.java scm-step/src/main/java/org/jenkinsci/plugins/workflow/steps/scm/GitStep.java scm-step/src/main/java/org/jenkinsci/plugins/workflow/steps/scm/SCMStep.java http://jenkins-ci.org/commit/workflow-plugin/f1e8e16057819582ba376226a1af47e45b34798d Log: Merge pull request #40 from jenkinsci/script-from-scm-JENKINS-26101 [FIXED JENKINS-26101] Load script from SCM Compare: https://github.com/jenkinsci/workflow-plugin/compare/e2947e92a2d0...f1e8e1605781 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-26581) CLI: update-job does not update the config.xml with current plugins versions
Damien Nozay created JENKINS-26581 CLI: update-job does not update the config.xml with current plugins versions Issue Type: Bug Assignee: Unassigned Components: cli Created: 24/Jan/15 12:32 AM Description: Hi. I am using the ssh api to update jobs with the 'update-job' command. I have not investigated if this is equivalent 100% to a POST with the config.xml. There is a difference between the behavior I see and changing the job through the UI. The "update-job" command does not update the config.xml with current plugins versions, whereas saving the job in the UI changes the current plugins versions in the config.xml file. Scenario #1 create a job that uses some plugins get the config.xml (config 1) update jenkins with newer plugins restart post the config.xml with update-job command get the config.xml (config 2) compare config 1 and 2 observe that currently config 1 and 2 are the same observe that currently config 2 does not have the new plugins version Scenario #2 create a job that uses some plugins get the config.xml (config 1) update jenkins with newer plugins restart open the job with the "configure" menu perform no changes but hit "save" get the config.xml (config 2) compare config 1 and 2 observe that currently config 1 and 2 are different (expected behavior) observe that currently config 2 DOES have actual plugins version (expected behavior) Action items: either make "update-job" behave the same as UI "save" button, or provide an option to the "update-job" command (e.g. "--update-plugins") that will persist the job and update the relevant plugins version. Environment: 1.580.1 Project: Jenkins Priority: Minor Reporter: Damien Nozay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26575) NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir
Jesse Glick commented on JENKINS-26575 NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir Well this is the critical and identifying aspect of the error. There could be all sorts of unrelated problems running the reverse migrator. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26575) NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir
David Light commented on JENKINS-26575 NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir Easy tracking if you happen to search for that specific portion of the error. That error is still searchable in the description and you've made it unreadable as a title This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-26508) Upgrade to 1.597 breaks Job page
apgray edited a comment on JENKINS-26508 Upgrade to 1.597 breaks Job page Downgrading is NOT where we want to be going forward. So are we waiting for another Disk Usage plugin release or another core release? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-5413) SCM polling getting hung
Nathaniel Irons commented on JENKINS-5413 SCM polling getting hung The script provided on Jan 13 seems to be solving a different problem. On our instance, we see stuck SCM polling threads even when the CPU load is zero. With three SCM polling processes stuck as of this moment, the thread names reported by Thread.getAllStackTraces() are main, Finalizer, Signal Dispatcher, and Reference Handler. I'm pig-ignorant of groovy, and have yet to figure out where its access to Jenkins thread innards are documented, but previous iterations of scripts that did identify a stuck thread to interrupt were ineffective for us — we've yet to find an effective workaround that doesn't rely on restarting the jenkins daemon. We're using 1.590, and looking to switch to LTS releases as soon as they pass us by. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Arpit Gupta commented on JENKINS-26576 old builds not getting cleaned up Not cached. I clicked the builds that the feed was showing and they were present. Further more the log for log rotator showed no info on cleaning up of old jobs when the job finished running. The only entry that was there was that its running log rotation for that job. Right after that i ran the job with post build action for clean up and it cleaned up various old builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Daniel Beck commented on JENKINS-26576 old builds not getting cleaned up Just to be sure, you viewed the raw RSS XML? Or could your web browser or RSS feed reader have cached older entries that are no longer part of the output by 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/d/optout.
[JIRA] [core] (JENKINS-26575) NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir
Jesse Glick updated JENKINS-26575 NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir Intentionally set summary to excerpt of error for easy tracking. Change By: Jesse Glick (23/Jan/15 10:54 PM) Summary: Unmigrate script fails after upgrading to 1 NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator . 597 unmigrateBuildsDir This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Patrik Boström edited a comment on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Jenkins 1.554.2 and Build Pipeline Plugin: 1.4.5 Steps to reproduce: 1. Create project C with a build step that will fail 2. Create project A with post build action “Build other projects” triggering project C 3. Create project B with post build action “Build other projects” triggering project C 4. Trigger build on B 5. Create a Build Pipeline View with Initial Job B 6. Go to view and retry project C The problem is that the wrong upstream project (A) is picked when triggering so no upstream build is found. It will add null as the UpstreamCause which core can't handle. Exactly as Daniel Beck mention in a previous comment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Patrik Boström edited a comment on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Jenkins 1.554.2 and Build Pipeline Plugin: 1.4.5 Steps to reproduce: 1. Create project C with a build step that will fail 2. Create project A with post build action “Build other projects” triggering project C 3. Create project B with post build action “Build other projects” triggering project C 4. Trigger build on B 5. Create a Build Pipeline View with Initial Job B 6. Go to view and retry project C The problem is that the wrong upstream project (A) is picked when triggering so no upstream build is found. It will add null as the UpstreamCause which core can't handle. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26575) Unmigrate script fails after upgrading to 1 .597
David Light updated JENKINS-26575 Unmigrate script fails after upgrading to 1 .597 Change By: David Light (23/Jan/15 10:48 PM) Summary: NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator Unmigrate script fails after upgrading to 1 . unmigrateBuildsDir 597 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Arpit Gupta edited a comment on JENKINS-26576 old builds not getting cleaned up I used the rss show all builds link. It showed builds as far as 2+ days old. Then i ran a build with discard old builds plugin with the setting of keep builds for 1 day (same setting as the in built option) as part of post build action and it printed logs for clean up of various builds I will try to run the above code and provide the data of what it shows. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Arpit Gupta commented on JENKINS-26576 old builds not getting cleaned up I used the rss show all builds link. It showed builds as far as 2+ days old. Then i ran a build with discard old builds plugin as part of post build action and it printed logs for clean up of various builds. I will try to run the above code and provide the data of what it shows. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
Patrik Boström commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Jenkins 1.554.2 and Build Pipeline Plugin: 1.4.5 Steps to reproduce: 1. Create project C with a build step that will fail 2. Create project A with post build action “Build other projects” triggering project C 3. Create project B with post build action “Build other projects” triggering project C 4. Trigger build on B 5. Create a Build Pipeline View with Initial Job B 6. Go to view and retry project C This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Daniel Beck
edited a comment on JENKINS-26576
old builds not getting cleaned up
How do you determine that builds exist but don't get deleted? Are they on the file system? In Jenkins?
There are no other log messages in that logger related to builds of this project?
What is the output when you run the following in Manage Jenkins » Script Console?
def j = Jenkins.instance.getItemByFullName("Job Name") // replace with actual job name
def b = j.firstBuild
while (b != null) {
println b
b = b.nextBuild
}
return
Does it match the builds you see listed in 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/d/optout.
[JIRA] [core] (JENKINS-26578) Adjuncts do not include CSS correctly for removable dom fragments
Daniel Beck commented on JENKINS-26578 Adjuncts do not include CSS correctly for removable dom fragments Is this related to JENKINS-14632? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26575) NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir
Jesse Glick updated JENKINS-26575 NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator.unmigrateBuildsDir Change By: Jesse Glick (23/Jan/15 10:23 PM) Summary: Unmigrate script fails after upgrading to 1 NoClassDefFoundError: javax/servlet/http/HttpServletRequest from RunIdMigrator . 597 unmigrateBuildsDir This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Daniel Beck commented on JENKINS-26576 old builds not getting cleaned up Is this job a Maven Project (instead of e.g. Freestyle)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Daniel Beck edited a comment on JENKINS-26576 old builds not getting cleaned up (please ignore) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Jesse Glick commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value BUILD_ID is defined to be the ID of the build, and the ID is now a number rather than a timestamp, so the current behavior is correct. (There are some things in Jenkins which expect a build ID.) Adding a new BUILD_TIMESTAMP variable for the dedicated purpose of representing time is the only option. I would actually suggest two such variables: BUILD_TIMESTAMP_LEGACY, with the format of the old IDs and in the server’s local timezone. BUILD_TIMESTAMP, in ISO 8601 format (how-to). Note that since builds may now come in at a rate of more than one per second, BUILD_TIMESTAMP_LEGACY could easily be nonunique. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26575) Unmigrate script fails after upgrading to 1.597
Jesse Glick updated JENKINS-26575 Unmigrate script fails after upgrading to 1.597 A code path only run when you encounter a real error. Try locating the JAR containing the Servlet API (possibly %JENKINS_HOME%\war\winstone.jar, depending on how you start Jenkins), and adding that (after ;) to the -classpath used to run the unmigrator. If that fixes this problem, I will add this to the suggested command line. Change By: Jesse Glick (23/Jan/15 10:09 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26579) j:getStatic/invokeStatic does not work on plugin classes
Kohsuke Kawaguchi
commented on JENKINS-26579
j:getStatic/invokeStatic does not work on plugin classes
In the version of commons-jelly that we use in the core (org.jenkins-ci:commons-jelly:jar:1.1-jenkins-20120928), the loadClass method looks like this:
/**
* Loads the given class using the current Thread's context class loader first
* otherwise use the class loader which loaded this class.
*/
public static Class loadClass(String className, Class callingClass) throws ClassNotFoundException {
ClassLoader loader = Thread.currentThread().getContextClassLoader();
if (loader == null) {
return getClassLoader(callingClass).loadClass(className);
} else {
return loader.loadClass(className);
}
}
... so while I haven't verified whether we set context classloader, it seems like we've made an attempt to get this done correctly.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-25435) Embedded Sauce Report does not show up when session ID present in xunit file
Ross Rowe commented on JENKINS-25435 Embedded Sauce Report does not show up when session ID present in xunit file Hi again, if you're using nosetest, would you be able to try add the -s argument to the command line? This should cause the output to be printed to Jenkins console log. If you're not using nosetest or you're still having issues, would you be able to attach your xunit xml file to this ticket so that I can run it through my environment (or you could raise a ticket via support.saucelabs.com, and attach the file to the ticket) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Alex Earl commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module I'm getting this as well, but the sleep doesn't seem to be helping at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26579) j:getStatic/invokeStatic does not work on plugin classes
Jesse Glick commented on JENKINS-26579 j:getStatic/invokeStatic does not work on plugin classes Other workarounds: Use a Groovy view. Avoid static calls by arranging to pass in an instance of this or a related class (for example as it) so you can make instance calls. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Dominic Bishop commented on JENKINS-25203 support embedded content in json Is this issue still being actively progressed? This feature would be extremely useful to me. If this has stalled I'll try and start looking in to it myself but as I have no experience of Jenkins development yet I'd rather not invest that amount of effort if this is still on-going. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26580) For JNLP slaves the master-slave communication should be encrypted
akshay_abd created JENKINS-26580 For JNLP slaves the master-slave communication should be encrypted Issue Type: Improvement Assignee: akshay_abd Components: core Created: 23/Jan/15 7:45 PM Description: For more details about the requirements and possible implementation refer to: https://groups.google.com/forum/#!topic/jenkinsci-dev/Q1KMOSE1IEc Project: Jenkins Priority: Minor Reporter: akshay_abd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26579) j:getStatic/invokeStatic does not work on plugin classes
Jesse Glick
created JENKINS-26579
j:getStatic/invokeStatic does not work on plugin classes
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
23/Jan/15 7:38 PM
Description:
If in j:getStatic or j:invokeStatic you specify a className which is in a plugin, then try to render the resulting Jelly view, you get
java.lang.ClassNotFoundException: some.Class
at org.jenkinsci.maven.plugins.hpi.ServletApiOnlyClassLoader.findClass(ServletApiOnlyClassLoader.java:25)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363)
at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:325)
at org.apache.commons.jelly.tags.core.GetStaticTag.doTag(GetStaticTag.java:106)
Indeed GetStaticTag does
Class type = ClassLoaderUtils.getClassLoader(getClass()).loadClass(className);
which calls
public static ClassLoader getClassLoader(Class clazz) {
ClassLoader callersLoader = clazz.getClassLoader();
if (callersLoader == null) {
callersLoader = ClassLoader.getSystemClassLoader();
}
return callersLoader;
}
so there is no way this could work.
Workaround:
${app.pluginManager.uberClassLoader.loadClass('some.Class').getField('field').get(null)}
${app.pluginManager.uberClassLoader.loadClass('pkg.SomeExtension').getMethod('all', null).invoke(null, null)}
Project:
Jenkins
Labels:
jelly
classloader
Priority:
Minor
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Richard Mortimer commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value I think BUILD_ID should keep the timestamp format. That is the documented behaviour at https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project The BUILD_NUMBER variable gives the build number still. The change of format has broken a couple of my deployment scripts that were expecting the date format. I did a quick fix to use the old formatting code and that seems to have made things work for me. I have not submitted a pull request because I have not had chance to fully test things. For those who are interested the code is at https://github.com/oldelvet/jenkins/tree/jenkins-26520 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26578) Adjuncts do not include CSS correctly for removable dom fragments
Kohsuke Kawaguchi created JENKINS-26578 Adjuncts do not include CSS correctly for removable dom fragments Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Jan/15 7:04 PM Description: Details described in here. CSS needs to be moved into the head tag to avoid the problem. 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/d/optout.
[JIRA] [core] (JENKINS-26577) OutOfMemory errors
Ted Cihak created JENKINS-26577 OutOfMemory errors Issue Type: Bug Assignee: Unassigned Attachments: HeapDumpSummary.txt, PlugIns.PNG Components: core Created: 23/Jan/15 6:56 PM Description: I get OutOfMemory exceptions every so often. I noticed that I can get these to occur if I do a lot of job configuration followed by running them. The jobs themselves are pretty simple. I have heap dumps but don't have a way to share them. I've included the Summary page as an attachment. The JVM parameters are: -Xmx3G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/Users/mobiledevbuilduser/JenkinsCrashes Environment: Jenkins 1.5.92 (Running in Jenkins App) Java HotSpot(TM) 64-Bit Server VM MacOSX 10.10.1 IE 11 PlugIns provided in attached screenshot. Project: Jenkins Labels: outofmemoryerror Priority: Major Reporter: Ted Cihak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sonar] (JENKINS-21413) configuration page exposes sonar password
Oliver Gondža commented on JENKINS-21413 configuration page exposes sonar password Fixed proposed for quite some time: https://github.com/SonarSource/jenkins-sonar-plugin/pull/9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Arpit Gupta commented on JENKINS-26576 old builds not getting cleaned up Also if any one has a suggestion to make the post build action for clean up run faster in case use concurrent builds i am willing to switch to that 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/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Arpit Gupta created JENKINS-26576 old builds not getting cleaned up Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Jan/15 6:51 PM Description: I am running into an issue where old builds are not getting cleaned up. I added a log for hudson.tasks.LogRotator at level FINER and when i look at the log I see stuff like Jan 23, 2015 10:23:33 AM FINE hudson.tasks.LogRotator Running the log rotation for hudson.model.FreeStyleProject@c59337d[JOB_NAME] with numToKeep=-1 daysToKeep=1 artifactNumToKeep=-1 artifactDaysToKeep=1 However builds that are older than 1 day are not getting cleaned up. There is no other log that might say stuff like build is a keeper do not delete etc. When i enable discard old build plugin as a post build action it ends up cleaning a bunch of builds. But the in built feature does not seem to be working. Also it seems specific to just one job as other jobs are being cleaned up. Project: Jenkins Priority: Critical Reporter: Arpit Gupta This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Arpit Gupta updated JENKINS-26576 old builds not getting cleaned up Change By: Arpit Gupta (23/Jan/15 6:52 PM) Environment: CentOS 6, Jenkins v1.595 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26575) Unmigrate script fails after upgrading to 1.597
David Light created JENKINS-26575 Unmigrate script fails after upgrading to 1.597 Issue Type: Bug Assignee: Jesse Glick Components: core Created: 23/Jan/15 6:05 PM Description: After upgrading to 1.597 from 1.588 on Windows I cannot downgrade because trying to run the unmigrate script fails with: Exception in thread "main" java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest at hudson.Util.createSymlinkJava7(Util.java:1224) at hudson.Util.createSymlink(Util.java:1118) at jenkins.model.RunIdMigrator.unmigrateBuildsDir(RunIdMigrator.java:371 ) at jenkins.model.RunIdMigrator.unmigrateJobsDir(RunIdMigrator.java:320) at jenkins.model.RunIdMigrator.main(RunIdMigrator.java:307) Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest at java.net.URLClassLoader$1.run(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) ... 5 more Project: Jenkins Priority: Minor Reporter: David Light This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26564) Update to 1.597 shows 500 error on jobs
David Light closed JENKINS-26564 as Duplicate Update to 1.597 shows 500 error on jobs Updating the disk usage plugin fixed this for me Change By: David Light (23/Jan/15 6:03 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26519) Build records not migrated due to “failed to rename"
Jesse Glick commented on JENKINS-26519 Build records not migrated due to “failed to rename" If you are willing to try up-to-the-minute dev builds, there are a few places where I think I could add better diagnostics. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26174) jenkins slave breaks connection after build steps finishing
Nick Hansen commented on JENKINS-26174 jenkins slave breaks connection after build steps finishing Also experiencing this issue when running multiple, short-running jobs on agents. Same stack trace as copied by OP. Master and agents running on Win2K8R2 VMs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-24673) SimpleBuildWrapper
SCM/JIRA link daemon commented on JENKINS-24673 SimpleBuildWrapper Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/jenkins/tasks/SimpleBuildWrapper.java test/src/test/java/jenkins/tasks/SimpleBuildWrapperTest.java http://jenkins-ci.org/commit/jenkins/416bdef94db123ed8d051d095007491c9184b6ce Log: JENKINS-24673 Noting merge of #1530. Compare: https://github.com/jenkinsci/jenkins/compare/1dd60ec77808...416bdef94db1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-24673) SimpleBuildWrapper
Jesse Glick updated JENKINS-24673 SimpleBuildWrapper Core change merged towards 1.599. Change By: Jesse Glick (23/Jan/15 5:41 PM) Labels: api workflow Component/s: workflow-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-23401) docker plugin requires ssh key pair credentials
Kanstantsin Shautsou commented on JENKINS-23401 docker plugin requires ssh key pair credentials Help files in this PR https://github.com/jenkinsci/docker-plugin/pull/142 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26104) Custom Workflow step for sending mail
Tom FENNELLY commented on JENKINS-26104 Custom Workflow step for sending mail Short blog about this new feature: http://developer-blog.cloudbees.com/2015/01/mail-step-for-jenkins-workflow.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/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-24887) Workflow support of Copyartifact
Tom FENNELLY commented on JENKINS-24887 Workflow support of Copyartifact Here's a short blog about this feature: http://developer-blog.cloudbees.com/2015/01/copying-artifacts-between-builds-in.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/d/optout.
[JIRA] [core] (JENKINS-26406) Build history text field wrap fails when containing markup
Tom FENNELLY edited a comment on JENKINS-26406 Build history text field wrap fails when containing markup Guys, can someone please give this a sanity check please and let me know. There's a link to the jenkins.war in the PR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26406) Build history text field wrap fails when containing markup
Tom FENNELLY edited a comment on JENKINS-26406 Build history text field wrap fails when containing markup Guys, can someone give this a sanity check please and let me know. There's a link to the jenkins.war in the PR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26406) Build history text field wrap fails when containing markup
Tom FENNELLY commented on JENKINS-26406 Build history text field wrap fails when containing markup Guys, can someone give this a sanity check please and let me know. There's a link to the jenkins.war in the PR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26365) Animated ball in job's build history widget won't open Console Output
dogfood commented on JENKINS-26365 Animated ball in job's build history widget won't open Console Output Integrated in jenkins_main_trunk #3944 [FIXED JENKINS-26365] Animated ball in job's build history widget won't open Console Output (Revision 1dd60ec7780870f9c11686659178e52d251c15fc) Result = SUCCESS tom.fennelly : 1dd60ec7780870f9c11686659178e52d251c15fc Files : changelog.html war/src/main/webapp/css/style.css This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20606) Wrong spelling in Russian localization
dogfood commented on JENKINS-20606 Wrong spelling in Russian localization Integrated in jenkins_main_trunk #3944 [FIXED JENKINS-20606] Wrong spelling in Russian localization (Revision 6e6e2d7ec93f99ef178f87ef20fa4bb09d0073ae) Result = SUCCESS pmarcoen : 6e6e2d7ec93f99ef178f87ef20fa4bb09d0073ae Files : core/src/main/resources/hudson/model/Messages_ru.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-26574) Allow distinct template for matrix head build
Nicolas De Loof
created JENKINS-26574
Allow distinct template for matrix head build
Issue Type:
Improvement
Assignee:
Kohsuke Kawaguchi
Components:
build-name-setter-plugin
Created:
23/Jan/15 4:10 PM
Description:
matrix head build can't access file generated during the build, as they only exist on axes-workspaces. For sample, using `${PROPFILE,file="foo.txt",property=bar}` will result into `foo.txt not found`.
Project:
Jenkins
Priority:
Minor
Reporter:
Nicolas De Loof
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26571) Job page becomes un responsive when there are a lot of builds in the queue
Arpit Gupta updated JENKINS-26571 Job page becomes un responsive when there are a lot of builds in the queue Actually this is on the job page itself. Does not have to be in build now state. Change By: Arpit Gupta (23/Jan/15 4:05 PM) Summary: Build now Job page becomes un responsive when there are a lot of builds in the queue Description: After upgrading to 1.595 we have noticed that if a job has a lot of builds in the queue (waiting for executors) and the user clicks the build now button we see 2 issues.1. The scroll bar keeps getting reset to to the top2. The page becomes slow/unresponsive making it difficult to use.This might be related to JENKINS-26445 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-26573) REQ: EC2 IAM role support to inherit credentials
edovale commented on JENKINS-26573 REQ: EC2 IAM role support to inherit credentials Gavin, Your request makes a lot of sense. I currently have very little time available for this though. I would however, make a release if you or somebody else sends me a pull request for this feature. Cheers. Erick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY assigned JENKINS-26445 to Tom FENNELLY Browser freezes when clicking more link on a job to see other builds Change By: Tom FENNELLY (23/Jan/15 3:57 PM) Assignee: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Posted a request for opinions to the dev list: https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/NK_1ALzC6bg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY stopped work on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Change By: Tom FENNELLY (23/Jan/15 3:56 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-26573) REQ: EC2 IAM role support to inherit credentials
Gavin Hamill updated JENKINS-26573 REQ: EC2 IAM role support to inherit credentials Change By: Gavin Hamill (23/Jan/15 3:52 PM) Description: AWS allows EC2 instances to 'inherit' an IAM policy, so that any application on that instance can have account access at the level specified in that policy. This For people like me who run Jenkins on an EC2 instance, this means that instead of having to manually specify a pair of Access + Secret keys, any app using the AWS SDK can automatically Jenkins could magically get account access . http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/java-dg-roles.htmli.e. if there is no access / secret key provided, then try falling back to the InstanceProfileCredentialsProvider()Cheers,Gavin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26571) Build now page becomes un responsive when there are a lot of builds in the queue
Arpit Gupta updated JENKINS-26571 Build now page becomes un responsive when there are a lot of builds in the queue Attaching a screenshot. Will try to create a video next time we have a lot of jobs in the queue. Change By: Arpit Gupta (23/Jan/15 3:50 PM) Attachment: returnedScrollBAr.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudformation-plugin] (JENKINS-26573) REQ: EC2 IAM role support to inherit credentials
Gavin Hamill created JENKINS-26573 REQ: EC2 IAM role support to inherit credentials Issue Type: New Feature Assignee: edovale Components: cloudformation-plugin Created: 23/Jan/15 3:51 PM Description: AWS allows EC2 instances to 'inherit' an IAM policy, so that any application on that instance can have account access at the level specified in that policy. This means that instead of having to manually specify a pair of Access + Secret keys, any app using the AWS SDK can automatically get access http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/java-dg-roles.html i.e. if there is no access / secret key provided, then try falling back to the InstanceProfileCredentialsProvider() Cheers, Gavin. Project: Jenkins Priority: Minor Reporter: Gavin Hamill This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [log-parser-plugin] (JENKINS-26572) Log Parser incompatible with Jenkins 1.597 (build record change)
Mark Sinclair created JENKINS-26572 Log Parser incompatible with Jenkins 1.597 (build record change) Issue Type: Bug Assignee: rgoren Components: log-parser-plugin Created: 23/Jan/15 3:45 PM Description: After upgrade to Jenkins 1.597 the logparser plugin is no longer working. 1.597 includes the major enhancement to how build records are stored, which is possibly a problem for log parser. The following errors appear in the jenkins output log: Jan 23, 2015 9:18:21 AM hudson.plugins.logparser.LogParserParser parseLogBody INFO: LogParserParser: Start parsing : ZZ java.lang.NullPointerException at hudson.plugins.logparser.LogParserParser.parseLogBody(LogParserParser.java:284) at hudson.plugins.logparser.LogParserParser.parseLog(LogParserParser.java:114) at hudson.plugins.logparser.LogParserPublisher.perform(LogParserPublisher.java:54) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1743) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Jan 23, 2015 9:18:21 AM hudson.plugins.logparser.LogParserPublisher perform SEVERE: null Environment: Jenkins 1.597 Project: Jenkins Priority: Major Reporter: Mark Sinclair This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26571) Build now page becomes un responsive when there are a lot of builds in the queue
Tom FENNELLY commented on JENKINS-26571 Build now page becomes un responsive when there are a lot of builds in the queue Arpit, can you add some screen shots for this please. Better again, if you can create a short screen recording and post a link. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
pascal_martin edited a comment on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page I'm have the same issue. with nUnit test loadded with Xunit I temporary fix with downdrade to Junit version 1.0 and no more duplicate chart Jenkins ver. 1.580.2 JUnit Plugin 1.3 NUnit plugin 0.16 xUnit plugin 1.93 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-25527) xUnit reports yield duplicated "Test Result Trend" charts
pascal_martin commented on JENKINS-25527 xUnit reports yield duplicated "Test Result Trend" charts I think is related to this issue https://issues.jenkins-ci.org/browse/JENKINS-26077?focusedCommentId=220058&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-220058 I downgrade junit plugin to 1.0 and no more duplicate for me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
pascal_martin commented on JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page I'm have the same issue. with nUnit test loadded with Xunit I temporary fix with downdrade to Junit version 1.0 and no more duplicate chart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26365) Animated ball in job's build history widget won't open Console Output
SCM/JIRA link daemon commented on JENKINS-26365 Animated ball in job's build history widget won't open Console Output Code changed in jenkins User: tfennelly Path: changelog.html war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/1dd60ec7780870f9c11686659178e52d251c15fc Log: [FIXED JENKINS-26365] Animated ball in job's build history widget won't open Console Output This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26365) Animated ball in job's build history widget won't open Console Output
SCM/JIRA link daemon resolved JENKINS-26365 as Fixed Animated ball in job's build history widget won't open Console Output Change By: SCM/JIRA link daemon (23/Jan/15 3:27 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26571) Build now page becomes un responsive when there are a lot of builds in the queue
Arpit Gupta created JENKINS-26571 Build now page becomes un responsive when there are a lot of builds in the queue Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Jan/15 3:24 PM Description: After upgrading to 1.595 we have noticed that if a job has a lot of builds in the queue (waiting for executors) and the user clicks the build now button we 2 issues. 1. The scroll bar keeps getting reset to to the top 2. The page becomes slow/unresponsive making it difficult to use. This might be related to JENKINS-26445 Environment: CentOS6, Jenkins v1.595 Project: Jenkins Labels: _javascript_ user-experience Priority: Critical Reporter: Arpit Gupta This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds @Tom and @Daniel logged JENKINS-26571 for the build now page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY edited a comment on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Daniel: that would seem right to me tbh. Would be the reverse analogy of tailing a log i.e. once you move away from the tail you stop tailing it. Once you move away from the top of the build history you stop checking for updates until you go back to the top. Bottom line... you can't have your cake and eat it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Daniel: that would not seem right to me tbh. Would be the reverse analogy of tailing a log i.e. once you move away from the tail you stop tailing it. Bottom line... you can't have your cake and eat it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY edited a comment on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Daniel: that would seem right to me tbh. Would be the reverse analogy of tailing a log i.e. once you move away from the tail you stop tailing it. Bottom line... you can't have your cake and eat it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-23074) Add convenience function for creating a standard MimeMessage
Tom FENNELLY resolved JENKINS-23074 as Fixed Add convenience function for creating a standard MimeMessage merged upstream Change By: Tom FENNELLY (23/Jan/15 2:52 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26104) Custom Workflow step for sending mail
Tom FENNELLY resolved JENKINS-26104 as Fixed Custom Workflow step for sending mail merged upstream Change By: Tom FENNELLY (23/Jan/15 2:53 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Daniel Beck commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Pagination has the problem that it's not just historical info but also queued and currently running build. So you could completely miss builds by being on page 2, despite AJAX. Plus, build to page mappings will change (shift) rapidly if builds are quick and frequent. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20606) Wrong spelling in Russian localization
SCM/JIRA link daemon commented on JENKINS-20606 Wrong spelling in Russian localization Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/hudson/model/Messages_ru.properties http://jenkins-ci.org/commit/jenkins/7b03baab95778665cc8546f1a422132b24cef868 Log: Merge pull request #1541 from petermarcoen/JENKINS-20606 [FIXED JENKINS-20606] Wrong spelling in Russian localization Compare: https://github.com/jenkinsci/jenkins/compare/7d652648b207...7b03baab9577 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20606) Wrong spelling in Russian localization
SCM/JIRA link daemon resolved JENKINS-20606 as Fixed Wrong spelling in Russian localization Change By: SCM/JIRA link daemon (23/Jan/15 2:41 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20606) Wrong spelling in Russian localization
SCM/JIRA link daemon commented on JENKINS-20606 Wrong spelling in Russian localization Code changed in jenkins User: Peter Marcoen Path: core/src/main/resources/hudson/model/Messages_ru.properties http://jenkins-ci.org/commit/jenkins/6e6e2d7ec93f99ef178f87ef20fa4bb09d0073ae Log: [FIXED JENKINS-20606] Wrong spelling in Russian localization This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Arpit, I think any other issues should be tracked in a separate JIRA. You can always reference this one suggesting the issues might be related. Don't forget to mention the Jenkins version number etc in case the issue has already been fixed (maybe try latest release if you can) etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Thanks for looking into this @Tom Pagination makes sense to me but i agree there will be some one who does not like it . Also do you think the issues on the build page are related to this? What we see is if you have a lot of builds in queue and i select build now with parameters 2 things happen 1. The scroll bar keeps getting reset to the top 2. Scrolling in general becomes really slow. Let me know if that should be tracked in a separate bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
Jesse Glick resolved JENKINS-26541 as Fixed Rejected sandbox methods inside parallel not being recorded for approval Change By: Jesse Glick (23/Jan/15 2:28 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26541) Rejected sandbox methods inside parallel not being recorded for approval
SCM/JIRA link daemon commented on JENKINS-26541 Rejected sandbox methods inside parallel not being recorded for approval Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowJobNonRestartingTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/SandboxContinuable.java http://jenkins-ci.org/commit/workflow-plugin/b83b89dc448e402d34a7741537f7de675293c5f9 Log: Merge pull request #43 from jenkinsci/RejectedAccessException-parallel-JENKINS-26541 JENKINS-26541 Handle wrapped RejectedAccessException Compare: https://github.com/jenkinsci/workflow-plugin/compare/8f9dc9acc102...b83b89dc448e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Wilfred Hughes edited a comment on JENKINS-23232 SEVERE: I/O error in channel Chunked connection I've seen the same exception with a different header: Caused by: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31352D30 It turned out the cause was my Jenkins slave writing to the channel. My slave configuration was 'Launch slave via execution of the command on the master`, and my script set some JVM flags. The offending flags were: -XX:+PrintGCDetails -Xloggc:/foo/bar/jenkins_gc.log However, since the /foo/bar directory didn't exist, the JVM wrote GC logs to stdout. This resulted in the Stream seeing garbage. If you decode 31352D30 you get '15-0'. This is the start of a log line of the form: 2015-01-23T14:01:04.789+: 26.069: [CMS-concurrent-sweep-start] My workaround was to change my slave to launch via SSH, but I fixed it by ensuring that my GC log directory exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Wilfred Hughes commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection I've seen the same exception with a different header: Caused by: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 31352D30 It turned out the cause was my Jenkins slave writing to the channel. My slave configuration was 'Launch slave via execution of the command on the master`, and my script set some JVM flags. The offending flags were: -XX:+PrintGCDetails -Xloggc:/foo/bar/jenkins_gc.log However, since the /foo/bar directory didn't exist, the JVM wrote GC logs to stdout. This resulted in the Stream seeing garbage. If you decode 31352D30 you get '15-01'. This is the start of a log line of the form: 2015-01-23T14:01:04.789+: 26.069: [CMS-concurrent-sweep-start] My workaround was to change my slave to launch via SSH, but I fixed it by ensuring that my GC log directory exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8927) Create a view from the XML API
Lukasz Tasz commented on JENKINS-8927 Create a view from the XML API this solution works pretty well with few limitation: nestedView plugin does not register it's own class and curl end with exception that NestedView is not resolved. in case of subviews, xml needs to be extended with node, unfortunately in case of coping view a to b, parent node is not visible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-26570) turn on "Mask passwords" to all jobs
Maris Zulis created JENKINS-26570 turn on "Mask passwords" to all jobs Issue Type: Improvement Assignee: Daniel Petisme Components: mask-passwords-plugin Created: 23/Jan/15 2:10 PM Description: Now it's possible to turn on "mask passwords" in each job separately. It could be good to turn it on globally so it wouldn't be possible to turn it of if you don't have administrator privileges. e.g. I have properties file which contains password. It's possible to create job which do cat on this file. For now only solution is to fully remove others to configure and create new jobs. Project: Jenkins Priority: Minor Reporter: Maris Zulis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sonargraph-plugin] (JENKINS-26566) Sonargraph: No graphs displayed due to wrong default setting after updating
SCM/JIRA link daemon commented on JENKINS-26566 Sonargraph: No graphs displayed due to wrong default setting after updating Code changed in jenkins User: Ingmar Kellner Path: pom.xml http://jenkins-ci.org/commit/sonargraph-plugin/21d8424de5fab9b772b514a24207db41a6a230c0 Log: JENKINS-26566: Sonargraph: Show default metrics, if plugin has been updated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-17939) Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist.
Piotr Dytkowski commented on JENKINS-17939 Failed Loading plugin build-pipeline-plugin java.io.IOException: Dependency jquery (1.7.2-1) doesn't exist. I have same problem with build-pipeline-plugin 1.554.2 and Jenkins ver. 1.597 Stacktrace: java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1317) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1116) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Failed to install build-pipeline-plugin plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:470) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1313) ... 5 more Caused by: java.io.IOException: Dependency jquery (1.7.2-1), parameterized-trigger (2.17) doesn't exist at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:480) at hudson.PluginManager.dynamicLoad(PluginManager.java:460) ... 6 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26559) EC2 slaves not connecting
Daniel Beck resolved JENKINS-26559 as Duplicate EC2 slaves not connecting Change By: Daniel Beck (23/Jan/15 1:42 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/d/optout.
[JIRA] [envinject-plugin] (JENKINS-26569) EnvInjectJobProperty inappropriately offered on WorkflowJob
Jesse Glick created JENKINS-26569 EnvInjectJobProperty inappropriately offered on WorkflowJob Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin Created: 23/Jan/15 1:30 PM Description: If you install both EnvInject and the Workflow plugins, then create a workflow job, EnvInjectJobProperty is offered as an option in the configuration screen. It adds nothing of use for workflows, which can already read and write environment variables at arbitrary points, run Groovy logic, and so on, so it is just a source of confusion. EnvInjectJobProperty.DescriptorImpl.isApplicable returns true unconditionally. It does not in fact make any reference to AbstractProject/AbstractBuild. Yet so far as I can tell, all of the other classes which check for the existence of a configured EnvInjectJobProperty are in fact assuming AbstractProject/AbstractBuild and probably could not work otherwise. If I am right, then isApplicable should return AbstractProject.class.isAssignableFrom(jobType), and the class declaration should be public class EnvInjectJobProperty extends JobProperty. (It is unclear to me why you are currently making this class generic, since it concrete and has no subclasses, meaning it is just an ill-typed synonym of public class EnvInjectJobProperty extends JobProperty.) Probably hudson.model.ExternalJob shows the same issue. Project: Jenkins Labels: workflow user-experience Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Hi Arpit. Sorry about this. I am looking into it now. I actually did test this back when I was rejigging things with the build history widget to make it layout a bit better, in that, I created a test job that had a few hundred builds and, to be honest, I could not notice a difference between performance of the new and old layout code. It was dog slow in either case ! How that history widget works is a bit insane anyway. Rendering anything more than 50 or so jobs seems bad UX to me from may perspectives (performance, navigation etc). I think what Daniel says re the more button only showing a few more builds makes sense. In fact, I would go a step further and implement a paging mechanism whereby you have your standard "Prev" and "Next" buttons in the history widget and you never display more than 50 or so builds. I'm sure someone will have an issue with that though This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY started work on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Change By: Tom FENNELLY (23/Jan/15 1:03 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26365) Animated ball in job's build history widget won't open Console Output
Tom FENNELLY commented on JENKINS-26365 Animated ball in job's build history widget won't open Console Output PR: https://github.com/jenkinsci/jenkins/pull/1543 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26365) Animated ball in job's build history widget won't open Console Output
Tom FENNELLY started work on JENKINS-26365 Animated ball in job's build history widget won't open Console Output Change By: Tom FENNELLY (23/Jan/15 12:41 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
