[JIRA] [core] (JENKINS-24550) When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Daniel Beck updated JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut Document Mode Change By: Daniel Beck (03/Sep/14 8:05 AM) Assignee: rshelley Component/s: core Component/s: reviewboard 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] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph
Liviu Jianu edited a comment on JENKINS-23708 Unable to view JaCoCo report and history graph JaCoCo plugin with temporary fix from Tobias for NullPointerException when trying to view the CoverageReport 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] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph
Liviu Jianu updated JENKINS-23708 Unable to view JaCoCo report and history graph JaCoCo plugin with temporary fix for NullPointerException when trying to view the CoverageReport Change By: Liviu Jianu (03/Sep/14 6:21 AM) Attachment: jacoco.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-24551) Docker URL contains invalid version information
Christian Bauer created JENKINS-24551 Docker URL contains invalid version information Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: docker-build-step Created: 03/Sep/14 7:00 AM Description: The remote requests made by the docker-build-step plugin to the docker host have an invalid path, you get 404 response only. The plugin produces: http://my.docker.host:4243/v/xyz Valid request URIs would be: http://my.docker.host:4243/v1.14/xyz http://my.docker.host:4243/xyz Obviously the workaround is to specify a version number in the plugin configuration in the Advances settings. Project: Jenkins Priority: Critical Reporter: Christian Bauer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24520) Recent changes is always empty
Björn Kraus commented on JENKINS-24520 Recent changes is always empty I can confirm this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis updated JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Change By: Alex Ouzounis (03/Sep/14 9:28 AM) Description: Theissueathandisthefollowing:Projectcontainsandsvnurloftheform:$SVN_ROOT_PATH/trunkEachnodesets$SVN_ROOT_PATHtotheSVNmirrorclosertothenodelocation.Thisallowsustohavefastcheckoutsetc.ProblemnowisthatJenkinsseems tothink thatthemasterevaluatedSVNURLisdifferentthantheworkspacecheckoutpathofaslaveandtriggersanewbuild.Thishappensuntilithappensthattheslavethatpicksthebuildisusingthesamemirrorasthemaster.Settingpollingtomasteronly(viathemagicproperty)doesnotfixtheissuesincetheproblemisnotpollingbutJenkinstryingtobesmartanddetectingthattheworkspacehasadifferentSVNURLthantheconfiguration.NotsurehowtotacklethisbutIamhavingalook. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi Richard, tcpdump option It worked with a full pathname. I have added a "bad" (adb server port 5615, emulator port 5613) and a "good" log (adb server port 5613, emulator port 5611) https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/EmulatorTcpdump. Wireshark I recorded some communication and uploaded a "good" (adb server port 5751, emulator port 5749) and "bad" (adb server port 5753, emulator port 5751) log too https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/Wireshark. I tried to look into it but it's hard to comprehend these files. I hope the logs will help. Edit: I forgot to say that there are two adb processes at the beginning and after 1 or 2 seconds only 1 left. So there aren't any other adb servers running. 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] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph
Liviu Jianu updated JENKINS-23708 Unable to view JaCoCo report and history graph JaCoCo.hpi with temporary fix attached Change By: Liviu Jianu (03/Sep/14 6:22 AM) Attachment: jacoco.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24121) Manual trigger in aggregated view
Patrik Boström assigned JENKINS-24121 to Unassigned Manual trigger in aggregated view Change By: Patrik Boström (03/Sep/14 10:55 AM) Assignee: PatrikBoström 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-24560) Customize time fromat for columns in task lists
Daniel Beck updated JENKINS-24560 Customize time fromat for columns in task lists Change By: Daniel Beck (03/Sep/14 11:37 AM) Issue Type: Bug NewFeature Affects Version/s: current Component/s: core Component/s: viewVC 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] [delivery-pipeline] (JENKINS-24556) Ability to show changes in aggregated view
Tommy Tynjä created JENKINS-24556 Ability to show changes in aggregated view Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline Created: 03/Sep/14 10:44 AM Description: It should be possible to display changes in the aggregated view to see what changes are currently flowing through the pipeline. This feature would be a configurable option on the aggregated view. Project: Jenkins Priority: Major Reporter: Tommy Tynjä This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-12316) git plugin should NOT tag every build by default
Mark Waite commented on JENKINS-12316 git plugin should NOT tag every build by default Patrick Hemmer I don't see this result on any of my 100+ jobs, on multiple machines. I use many combinations of authentication (read only, read/write, ssh keys, username/password, etc.), transport (git, ssh, https) and servers (bitbucket, github, assembla, local git server). I'm not seeing a tag per build on any of my jobs, unless the "Additional Behaviours" has been enabled to "Create a tag for every build". Is this happening on every job, including newly created jobs, or only on jobs which were defined prior to your upgrade to git plugin version 2 ? Is "Create a tag for every build" enabled in the job configuration? Is there anything else which might be unique or different about your configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node It seems to me that this "feature" of detecting a configuration change or mismatch between config and last build during polling is not ideal. Maybe trying to resolve the master "raw" svn url using the environment of the last build is better than just looking for "$" and skipping the check altogether ? Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Daniel Beck commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node I am looking if we can detect such a condition (by the presence of a variable in the project configuration svn url) and skip this check if that is true. Are you absolutely sure that the only reason to use variables in the URL is this? Because I've often seen variables used, and never for this. Wouldn't routing (i.e. a network-based approach) be a better idea? 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] [installshield] (JENKINS-24555) centos 6.x jenkins update not working anymore
Martin K. created JENKINS-24555 centos 6.x jenkins update not working anymore Issue Type: Bug Assignee: Tomáš Bambas Components: installshield Created: 03/Sep/14 10:03 AM Description: Hi guys! I'm on centos 6.x and inlcuded the jenkins yum sources like this: sudo wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat/jenkins.repo sudo rpm --import http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key for a while I got updates with this repo, but since a few weeks it doesn't work aynmore it seems with yum update. I'm stuck with version 1.571 even after a yum update Any ideas what might be wrong? Project: Jenkins Priority: Major Reporter: Martin K. 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] [jobconfighistory] (JENKINS-24412) Do not save config for matrix configurations
SCM/JIRA link daemon commented on JENKINS-24412 Do not save config for matrix configurations Code changed in jenkins User: Stefan Brausch Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction.java src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistory/config.jelly src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectActionTest.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/6810fe53983881e743bc6f6f41ec70c6cf47d214 Log: Merge pull request #38 from olivergondza/revisit-saveables FIXED JENKINS-24412FIXED JENKINS-24410 Save only TopLevelItems Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/259de16d36a8...6810fe539838 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis edited a comment on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node I am looking if we can detect such a condition (by the presence of a variable in the project configuration svn url) and skip this check if that is true. Bug exists in subversionSCM: compareRemoteRevisionWith() lines 1360 - 1375 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] [delivery-pipeline] (JENKINS-24556) Ability to show changes in aggregated view
Patrik Boström assigned JENKINS-24556 to Unassigned Ability to show changes in aggregated view Change By: Patrik Boström (03/Sep/14 10:55 AM) Assignee: PatrikBoström 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] [delivery-pipeline] (JENKINS-24559) Ability to use an avatar/image instead of a component name in the pipeline view
Tommy Tynjä created JENKINS-24559 Ability to use an avatar/image instead of a component name in the pipeline view Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline Created: 03/Sep/14 10:55 AM Description: In some cases it would be convenient to use an avatar or image instead of a component name in the pipeline view. Too much text in a pipeline view can be bothersome, so having the ability to use images instead might reduce blur and improve readability and pipeline overlook. Project: Jenkins Priority: Major Reporter: Tommy Tynjä This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis edited a comment on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Created pull request where if property hudson.scm.SubversionSCM.disableTriggerOnScmConfigMismatch is set to true, the comparison is skipped. Default is true to maintain existing behaviour. https://github.com/jenkinsci/subversion-plugin/pull/95 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] (JENKINS-19870) Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds
Chris van Breeden commented on JENKINS-19870 Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds Same issue on Jenkins 1.554.1 Pipeline 1.4.2 is there a workaround available?? 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] [jobconfighistory] (JENKINS-24410) Job config change not saved for maven and matrix projects
SCM/JIRA link daemon commented on JENKINS-24410 Job config change not saved for maven and matrix projects Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectActionTest.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/0cb1752ab5d6a0fa7636e6a7a2456508d1013b22 Log: FIXED JENKINS-24412FIXED JENKINS-24410 Save only ItemGroups 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] [delivery-pipeline] (JENKINS-24557) Ability to display user avatars throughout the pipeline
Tommy Tynjä created JENKINS-24557 Ability to display user avatars throughout the pipeline Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline Created: 03/Sep/14 10:51 AM Description: It would be convenient to be able to display the user avatar(s) associated with a particular change set(s) e.g. alongside the progress bar in the pipeline tasks. This would be practical in e.g. fullscreen mode on information radiators to get an overlook of who's change is currently working its way through the pipeline. Project: Jenkins Priority: Major Reporter: Tommy Tynjä 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-23921) new divs layout doesn't work with IE8
Stephan Herter updated JENKINS-23921 new divs layout doesnt work with IE8 Change By: Stephan Herter (03/Sep/14 8:08 AM) Attachment: warning_document_mode.jpg 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] [rqm] (JENKINS-24553) Missing summary section in plugin (our case 11935)
Mads Nielsen created JENKINS-24553 Missing summary section in plugin (our case 11935) Issue Type: Bug Assignee: Praqma Support Components: rqm Created: 03/Sep/14 8:55 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen 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-24550) When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Daniel Beck commented on JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut Document Mode Have you tried fixing your IE document mode? 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] [jobconfighistory] (JENKINS-24412) Do not save config for matrix configurations
SCM/JIRA link daemon commented on JENKINS-24412 Do not save config for matrix configurations Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectActionTest.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/0cb1752ab5d6a0fa7636e6a7a2456508d1013b22 Log: FIXED JENKINS-24412FIXED JENKINS-24410 Save only ItemGroups 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-23921) new divs layout doesn't work with IE8
Stephan Herter commented on JENKINS-23921 new divs layout doesnt work with IE8 I have attached a screen shot from IE8 with "IE8Standard" document mode. If the document mode is set to "IE7Standard", the warning message disappears. Contrary to my previous statement, the page is displayed correctly in this case. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi Richard, tcpdump option It worked with a full pathname. I have added a "bad" (adb server port 5615, emulator port 5613) and a "good" log (adb server port 5613, emulator port 5611) https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/EmulatorTcpdump. Wireshark I recorded some communication and uploaded a "good" (adb server port 5751, emulator port 5749) and "bad" (adb server port 5753, emulator port 5751) log too https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/Wireshark. I tried to look into it but it's hard to comprehend these files. I hope the logs will help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24552) Exception when use git plugin with ssh public key
sharon xia updated JENKINS-24552 Exception when use git plugin with ssh public key Change By: sharon xia (03/Sep/14 7:25 AM) Environment: Jenkins1.565.1;Gitplugin2. 2. 1 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Justinas Urbanavicius commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException yes, by saying, that it took down jenkins, i mean, i got a page, that looked mutilated, with stack trace, and i couldn't navigate from that page, except for forward back buttons on the browser, that didn't really help, until the connection got restored after a few refreshes. an error message with explanation and server's name would be really appreciated and more informative to me as the end user and anyone that does not know java. 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] [delivery-pipeline] (JENKINS-24559) Ability to use an avatar/image instead of a component name in the pipeline view
Patrik Boström assigned JENKINS-24559 to Unassigned Ability to use an avatar/image instead of a component name in the pipeline view Change By: Patrik Boström (03/Sep/14 10:57 AM) Assignee: PatrikBoström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24529) Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes
Kirill Peskov commented on JENKINS-24529 Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes Yeah, should be. But somehow in this configuration, Jenkins simply ignores master node availability. 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-23333) Label display wrong when using operators in expression
Daniel Beck commented on JENKINS-2 Label display wrong when using operators in _expression_ Daniel, all points taken into account, see new screenshots. I still need to test on a multi-nodes environment. You will see my attempt to build a condensed view. I'm not a UI expert so I'm planning on releasing the plugin like that. I count on other contributors' talent to make it look better if need be! Looks great. I'm not familiar enough yet with jenkins versioning but I suppose it means the plugin will work on subsequent jenkins version That's the idea, yes. There are very few exceptions to this rule. do not work in the test environment of my plugin... Daniel, do you think I should change the dependency Generally, if the plugin can do everything you want with somewhat older core dependency, that's the way to go. Obviously, if you want to use newer APIs or need behavior fixes (e.g. there were several versions where automated tests were broken on Windows), those are reasons to go with newer core versions. The downside of an older core dependency is that this is used for automated tests and hpi:run, so while testing the plugin, you're using an older version. (You could always switch to a newer core during development to see how the plugin looks and works then, but do testing and releases with the older dependency so it's available to more users.) There's a report on stats.jenkins-ci.org that shows how many installations have version X or higher (i.e. if something was added in X, how many installations have it). It may help you decide which version to depend on. With 1.532.1, released 9 months ago, currently ~75% of installations could use your plugin, which seems reasonable. http://stats.jenkins-ci.org/plugin-installation-trend/capabilities.json 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] [naginator] (JENKINS-19071) Naginator plugin causes archiving to hang if the build failed
mwebber commented on JENKINS-19071 Naginator plugin causes archiving to hang if the build failed I'm not currently using Naginator, so I can't report check whether the problem is stil there. Sorry. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Indeed another way forward would be to use the same path on all nodes and setup a proxy or something on the physical machine the slave runs. The issue here is that setting up network routing for all nodes does not really scale so ideally the variables should work, and it does up to a point ;p since I do not care Jenkins detecting that the svn config url has changed and trigger a build I might just fork and delete those lines although I would prefer a solution in the original plugin Alex 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] [checkstyle] (JENKINS-19932) Publish FindBugs/Checkstyle from slave failed
Ulli Hafner commented on JENKINS-19932 Publish FindBugs/Checkstyle from slave failed Ok, I understand. Maybe I should remove the SAX parser setting. This have been added due to some classloading problems on older Java versions. Since we are now depending on Java 6 this might not be necessary anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24552) Exception when use git plugin with ssh public key
sharon xia created JENKINS-24552 Exception when use git plugin with ssh public key Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 03/Sep/14 7:17 AM Description: We are using Git SCM; The git remote repository is managed by stash; We specify urL: ssh://g...@hardware.corp.emc.com:7999/bf/test.git If we don't set Credentials(although I can clone the code from both master and slave node), the job can pull code to slave. However the SCM pooling will report below error: Failed to connect to repository : Command "git ls-remote -h ssh://g...@hardware.corp.emc.com:7999/bf/test.git HEAD" returned status code 128: stdout: stderr: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. This polling issue is only seen in repositories managed in stash. In stash repositories, it cannot work if we remove .git from the clone url. However, the git pollign in jenkins have to work without .git suffix. For repository managed by gerrit, clone either with or without .git suffix will work. So if we do not .git in jenkins scm git config, polling will work without credentials specified. If we specify the repo url ending with .git, and at the same time if we set the credential(master's ssh id_rsa.pub), then the pooling will work, but the build will fail with below exception: Started by user sharon xia EnvInject - Loading node environment variables. Building remotely on GPS-NODE (x86-windows-6.1 6.1 x86-windows windows-6.1 windows x86) in workspace d:\hudson-slave\workspace\test-check FATAL: argument type mismatch java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Environment: Jenkins 1.565.1; Git plugin 2.1 Project: Jenkins Priority: Blocker Reporter: sharon xia 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] [jobconfighistory] (JENKINS-24410) Job config change not saved for maven and matrix projects
SCM/JIRA link daemon commented on JENKINS-24410 Job config change not saved for maven and matrix projects Code changed in jenkins User: Stefan Brausch Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistory.java src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction.java src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistory/config.jelly src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectActionTest.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistoryTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/6810fe53983881e743bc6f6f41ec70c6cf47d214 Log: Merge pull request #38 from olivergondza/revisit-saveables FIXED JENKINS-24412FIXED JENKINS-24410 Save only TopLevelItems Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/259de16d36a8...6810fe539838 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24529) Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes
Kirill Peskov commented on JENKINS-24529 Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes BTW, could it be somehow related to the Git Repo Browser installed? I have gitlist installed, can replace it with Stash if needed. 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] [viewVC] (JENKINS-24560) Customize time fromat for columns in task lists
Maciej Jaros created JENKINS-24560 Customize time fromat for columns in task lists Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: viewVC Created: 03/Sep/14 11:00 AM Description: All of the columns in views are formatted in exactly the same way (as `time since`). I would like to have different formats for "Last Success/Error" and different for "Last duration". Typically "Last duration" is short so I would like it to be more compact (i.e. "01:22,31" instead of "1 min 22 sec"). "Last Success" (and especially Error) column can be in a quite distant past and I would like to simply have it in ISO format "2014-07-03" (or if it was today display an hour or simply the word "today"). So either a list of formats or format string for columns would be nice. Project: Jenkins Priority: Minor Reporter: Maciej Jaros This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23
Vadym Vikulin reopened JENKINS-22125 FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 Still reproduces on 2.25: FATAL: Illegal choice: release_2.8 java.lang.IllegalArgumentException: Illegal choice: release_2.8 at hudson.model.ChoiceParameterDefinition.checkValue(ChoiceParameterDefinition.java:75) at hudson.model.ChoiceParameterDefinition.createValue(ChoiceParameterDefinition.java:87) at hudson.model.ChoiceParameterDefinition.createValue(ChoiceParameterDefinition.java:19) at hudson.plugins.parameterizedtrigger.ProjectSpecificParameterValuesActionTransform.convertToDefinedType(ProjectSpecificParameterValuesActionTransform.java:83) at hudson.plugins.parameterizedtrigger.ProjectSpecificParameterValuesActionTransform.transformParametersAction(ProjectSpecificParameterValuesActionTransform.java:34) at hudson.plugins.parameterizedtrigger.ProjectSpecificParametersActionFactory.getProjectSpecificBuildActions(ProjectSpecificParametersActionFactory.java:32) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getBuildActions(BuildTriggerConfig.java:290) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2(BuildTriggerConfig.java:336) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2(BlockableBuildTriggerConfig.java:57) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:85) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Change By: Vadym Vikulin (03/Sep/14 8:12 AM) Resolution: Fixed Status: Resolved Reopened Assignee: DarrellHamilton huybrechts 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-24560) Customize time fromat for columns in task lists
Daniel Beck resolved JENKINS-24560 as Wont Fix Customize time fromat for columns in task lists Compact Column Plugin may work for you, it's fairly configurable. Besides that, default included columns all have no options (ease of use). Since this can be solved in a simple plugin, it probably should be. Change By: Daniel Beck (03/Sep/14 11:38 AM) Status: Open Resolved Resolution: WontFix 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Tobias Schumacher edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Hi Richard, tcpdump option It worked with a full pathname. I have added a "bad" (adb server port 5615, emulator port 5613) and a "good" log (adb server port 5613, emulator port 5611) https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/EmulatorTcpdump. Wireshark I recorded some communication and uploaded a "good" (adb server port 5751, emulator port 5749) and "bad" (adb server port 5753, emulator port 5751) log too https://github.com/ITobiI/Android-Problem-Jenkins/tree/master/Wireshark. I tried to look into it but it's hard to compare these files. I hope the logs will help. Edit: I forgot to say that there are two adb processes at the beginning and after 1 or 2 seconds only 1 left. So there aren't any other adb servers running. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24463) PyLint parse missing errors
Ulli Hafner commented on JENKINS-24463 PyLint parse missing errors I see. One problem with the new format: the path is missing in the parsed line. If the section header should be scanned (e.g., * Module tests.api.utils.client) then the single line parser cannot be used anymore I think there are two options: Create a new parser for the new file format (interested in providing a pull request?) Don't change the parser and add a note so that users will pick the correct command line option. And ask the maintainer of pylint why this option has been deprecated. What do you think? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node I am looking if we can detect such a condition (by the presence of a variable in the project configuration svn url) and skip this check if that is true. 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-24550) When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Daniel Beck updated JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut Document Mode Change By: Daniel Beck (03/Sep/14 8:06 AM) Priority: Major Minor 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-24550) When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Daniel Beck updated JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut Document Mode Change By: Daniel Beck (03/Sep/14 8:06 AM) Labels: jenkins ieuser-experience This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis created JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Issue Type: Bug Assignee: Unassigned Components: subversion Created: 03/Sep/14 9:25 AM Description: The issue at hand is the following: Project contains and svn url of the form: $SVN_ROOT_PATH/trunk Each node sets $SVN_ROOT_PATH to the SVN mirror closer to the node location. This allows us to have fast checkouts etc. Problem now is that Jenkins seems that the master evaluated SVN URL is different than the workspace checkout path of a slave and triggers a new build. This happens until it happens that the slave that picks the build is using the same mirror as the master. Setting polling to master only (via the magic property) does not fix the issue since the problem is not polling but Jenkins trying to be smart and detecting that the workspace has a different SVN URL than the configuration. Not sure how to tackle this but I am having a look. Project: Jenkins Priority: Major Reporter: Alex Ouzounis 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] [tfs] (JENKINS-24558) Net connect exception when downloading files from TFS
Teja Wuppumandla created JENKINS-24558 Net connect exception when downloading files from TFS Issue Type: Bug Affects Versions: current Assignee: redsolo Attachments: jenkins-tfs-plugin-error.txt Components: tfs Created: 03/Sep/14 10:55 AM Description: When trying to connect to TFS and download contents from a folder, all the files are getting downloaded but the process is throwing a connection timed out exception Environment: Jenkins master (which is also the slave) is running on windows 7 64 bit machine. Jenkins version is 1.578 and tfs plugin version is 3.1.1. Java version is 1.7.0_67. Version of visual studio is VS Ultimate 2010. TFS version is 2012 Fix Versions: current Project: Jenkins Labels: plugin tfs Priority: Blocker Reporter: Teja Wuppumandla This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24554) Builds get triggered multiple times when the SCM URL contains variables that change on each node
Alex Ouzounis commented on JENKINS-24554 Builds get triggered multiple times when the SCM URL contains variables that change on each node Created pull request where is property hudson.scm.SubversionSCM.disableTriggerOnScmConfigMismatch is set to true, the comparison is skipped. Default is true to maintain existing behaviour. https://github.com/jenkinsci/subversion-plugin/pull/95 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-10442) RestartNotSupportedException when trying to do safeRestart
Shannon Kerr commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart I can probably do this next week. This week is bad for me to test that. 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] [naginator] (JENKINS-20864) Unknown Naginator Icon next to Failed Build
SCM/JIRA link daemon commented on JENKINS-20864 Unknown Naginator Icon next to Failed Build Code changed in jenkins User: Tomer Path: src/main/resources/com/chikli/hudson/plugin/naginator/NaginatorAction/badge.jelly http://jenkins-ci.org/commit/naginator-plugin/6ae2bfca65e8ee03395f148448bfbf45f66a20f4 Log: JENKINS-20864 Fix rebuild badge URL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph
Liviu Jianu commented on JENKINS-23708 Unable to view JaCoCo report and history graph sorry for the double post. 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] [delivery-pipeline] (JENKINS-24557) Ability to display user avatars throughout the pipeline
Patrik Boström assigned JENKINS-24557 to Unassigned Ability to display user avatars throughout the pipeline Change By: Patrik Boström (03/Sep/14 10:54 AM) Assignee: PatrikBoström 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] [nodejs] (JENKINS-24425) Using both NodeJS and Rbenv build environment plugins, rbenv is unable to create .rbenv.lock directory
Jonathan Langevin commented on JENKINS-24425 Using both NodeJS and Rbenv build environment plugins, rbenv is unable to create .rbenv.lock directory I'm seeing issues that are possibly similarly related, wherein the NodeJS paths aren't getting set when the rbenv plugin is installed. Also seemingly related to issues found in JENKINS-20636 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings] (JENKINS-24463) PyLint parse missing errors
Ulli Hafner edited a comment on JENKINS-24463 PyLint parse missing errors I see. One problem with the new format: the path is missing in the parsed line. If the section header should be scanned (e.g., * Module tests.api.utils.client) then the single line parser cannot be used anymore I think there are two options: Create a new parser for the new file format (interested in providing a pull request?) Don't change the parser and add a note so that users will pick the correct command line option. And ask the maintainer of pylint why this option has been deprecated. What do you think? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [etc] (JENKINS-24555) centos 6.x jenkins yum update not working anymore
Martin K. updated JENKINS-24555 centos 6.x jenkins yum update not working anymore Change By: Martin K. (03/Sep/14 10:04 AM) Summary: centos6.xjenkins yum updatenotworkinganymore 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] [valgrind] (JENKINS-24561) Result files are aggregated in the workspace
Knut Petter S created JENKINS-24561 Result files are aggregated in the workspace Issue Type: Bug Affects Versions: current Assignee: Johannes Ohlemacher Components: valgrind Created: 03/Sep/14 12:27 PM Description: Results from previous builds/valgrind runs are stored in the workspace. After fixing memory leaks the count will not go down since the old runs are imported as new. The can be seen in the log by something like: Valgrind Files to copy: x.12345.result x.23456.result x.34567.result and so on All these previous builds will be copied into the current build's results. This cannot be correct behaviour? My workaround is to remove all (old) .result files in the workspace before i do the analysis. Environment: Linux rhel 6.3 Project: Jenkins Priority: Minor Reporter: Knut Petter S 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] [delivery-pipeline] (JENKINS-24557) Ability to display user avatars throughout the pipeline
Marcus Philip commented on JENKINS-24557 Ability to display user avatars throughout the pipeline The avatar could spin. Would be fun This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23985) Handle commits that are out of scope for sparse checkout
Mark Waite resolved JENKINS-23985 as Cannot Reproduce Handle commits that are out of scope for sparse checkout After a little less than a month of waiting without a response for more details to duplicate the problem, I'm closing this bug report. If someone finds the steps which can duplicate the problem, it can be reopened. Change By: Mark Waite (03/Sep/14 1:40 PM) Status: Open Resolved Resolution: CannotReproduce 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] [read-only-configurations] (JENKINS-24458) JobConfiguration doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Mark Towfiq commented on JENKINS-24458 JobConfiguration doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions To be clear, this appears to be happening with many, many plugins, and the error message does not suggest a remediation: root@jenkins:/var/lib/jenkins# grep ExportedBean /var/log/jenkins/jenkins.log | sort| uniq org.kohsuke.stapler.export.NotExportableException: class com.castlemon.jenkins.performance.CucumberProjectAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class com.cloudbees.jenkins.GitHubPushTrigger$GitHubWebHookPollingAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class com.coravy.hudson.plugins.github.GithubLinkAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class htmlpublisher.HtmlPublisherTarget$HTMLAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.rubyMetrics.flog.FlogBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.rubyMetrics.rcov.RcovBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.warnings.AggregatedWarningsProjectAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.warnings.AggregatedWarningsResultAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.warnings.WarningsProjectAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.plugins.warnings.WarningsResultAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.scm.SCMRevisionState$None doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.tasks.MailMessageIdAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.tasks.test.TestResultProjectAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.triggers.SCMTrigger$BuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class hudson.triggers.SCMTrigger$SCMAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class net.masterthought.jenkins.CucumberReportBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class net.masterthought.jenkins.CucumberReportProjectAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions org.kohsuke.stapler.export.NotExportableException: class org.jvnet.jenkins.plugins.nodelabelparameter.LabelBadgeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions 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] [valgrind] (JENKINS-24562) Publish Valgrind results and ClearCase
Knut Petter S created JENKINS-24562 Publish Valgrind results and ClearCase Issue Type: Improvement Affects Versions: current Assignee: Johannes Ohlemacher Components: valgrind Created: 03/Sep/14 12:49 PM Description: The ClearCase version control system works by spawning a subshell in "view context". (This is something like chroot). The correct version of files are not available until a view is set. I.e., the file /path/to/source/main.cpp is different depending on which view i set. The "Publish Valgrind results" post-build action does not handle this. Wrong version of the source file seems to be copied as seen by the "Valgrind copying source file...] log statements. So when clicking on a memory issue in the results wrong version of the file is presented. However, files can also be accessed by their abosolute path in /view/myviewname/path/to/source/main.cpp. So, if the plugin could offer an optional "prefix path" which if set was prepended to the from file in the abovementioned copy i think this would help. Environment: rhel 6.3 and ClearCase Project: Jenkins Priority: Major Reporter: Knut Petter S 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-23263) Move hudson.tasks.junit to a bundled plugin
Daniel Beck commented on JENKINS-23263 Move hudson.tasks.junit to a bundled plugin Reinhard Karbas: Please ask for assistance in #jenkins on Freenode or on the jenkinsci-users mailing list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23985) Handle commits that are out of scope for sparse checkout
Mark Waite closed JENKINS-23985 as Cannot Reproduce Handle commits that are out of scope for sparse checkout Change By: Mark Waite (03/Sep/14 1:40 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] [integrity-plugin] (JENKINS-24532) Integrity Checkin Task takes optional changePackageID
Cletus DSouza commented on JENKINS-24532 Integrity Checkin Task takes optional changePackageID This is already supported today. Simply pass in the IssueID as a parameter to the build (see Jenkins parametrized build) and the plugin will create a Change Package against that ID. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-jenkins] (JENKINS-24564) The 'Allow Sudo' option overwrites the existing sudoers file.
Dave Johnston created JENKINS-24564 The Allow Sudo option overwrites the existing sudoers file. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jclouds-jenkins Created: 03/Sep/14 1:25 PM Description: The 'Allow Sudo' option overwrites the existing sudoers file. This may cause problems for some users, who have setup other settings in a sudoers file. A better alternative would be to use the sudoers.d folder, and drop in a 'jenkins' specific file. Environment: Jenkins with jclouds configured to launch an openstack-nova slave. Project: Jenkins Labels: jclouds openstack Priority: Minor Reporter: Dave Johnston This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24546) Git plugin doesn't use environment variables when running git for polling
Mark Waite commented on JENKINS-24546 Git plugin doesnt use environment variables when running git for polling If you're not adding the "Additional Behaviours" to "Force polling using workspace", then the polling is performed from the master node and may be using the environment of the master node. Since you indicated that the master node also sets LD_LIBRARY_PATH, can you confirm that a job which executes a git command as one of its build steps runs as expected on your master node? Can you provide more detailed instructions so that others can duplicate your case? I don't modify LD_LIBRARY_PATH in my Red Hat, SuSE, Debian, or Ubuntu environments and I use git on all those machines. 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-23263) Move hudson.tasks.junit to a bundled plugin
Reinhard Karbas commented on JENKINS-23263 Move hudson.tasks.junit to a bundled plugin After going from version 1.575 to 1.578 now it seems the values for TEST_COUNTS is not set properly in Jenkins anymore and my email does not get generated properly Based on the description of this fix I assume this is the issue as the functionality was moved out to a new plugin However the name of the plugin is not shown anywhere What do I need to install to get this to work again? 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] [p4] (JENKINS-24565) P4 Plugin doesn't support perforce edge server
Punith C created JENKINS-24565 P4 Plugin doesnt support perforce edge server Issue Type: Bug Assignee: Unassigned Components: p4 Created: 03/Sep/14 3:04 PM Description: It is giving below error when used against edge server 07:53:42 P4: Unable to use Workspace: com.perforce.p4java.exception.RequestException: Client 'noclient' is restricted to use on server '', not 'svl_edge'. 07:53:42 07:53:42 ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Client 'noclient' is restricted to use on server '', not 'svl_edge'. 07:53:42 07:53:42 ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Client 'noclient' is restricted to use on server '', not 'svl_edge'. 07:53:42 Project: Jenkins Priority: Major Reporter: Punith 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] [naginator] (JENKINS-20864) Unknown Naginator Icon next to Failed Build
Tomer Galun resolved JENKINS-20864 as Fixed Unknown Naginator Icon next to Failed Build Fixed in 1.13 Change By: Tomer Galun (03/Sep/14 1:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24563) attempting to rename a project name with a trailing space ends up with an Oops
Guillaume BELLETESTE created JENKINS-24563 attempting to rename a project name with a trailing space ends up with an Oops Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Sep/14 1:10 PM Description: I accidentally renamed a project to a name ending with a space. When I tried to delete this trailing space, I was welcomed with the following message: Oops! A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.io.IOException: Failed to create a temporary file in C:\Program Files\Jenkins\jobs\Generate - Vxworks - Build-and-promote at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:67) at hudson.util.AtomicFileWriter.init(AtomicFileWriter.java:54) at hudson.XmlFile.write(XmlFile.java:175) at hudson.model.AbstractItem.save(AbstractItem.java:458) at hudson.model.Job.save(Job.java:163) at hudson.model.AbstractProject.save(AbstractProject.java:287) at hudson.model.AbstractItem.setDisplayName(AbstractItem.java:157) at hudson.model.Job.doConfigSubmit(Job.java:1121) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:786) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.collabnet.auth.CNFilter.doFilter(CNFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
[JIRA] [join] (JENKINS-24566) Join job should be run even if some or all downstream jobs fail
Paulo Matos created JENKINS-24566 Join job should be run even if some or all downstream jobs fail Issue Type: New Feature Assignee: mdonohue Components: join Created: 03/Sep/14 3:23 PM Description: In Join Plugin 1.15 it doesn't run a simple diamond: A-B A-C B-D C-D Even though A is marked to build D even if some of the downstream jobs are unstable, the last job B or C to complete complain: "Notifying upstream build rall #407 of job completion All downstream projects complete! Minimum result threshold not met for join project " I think the threshold was not met because B fails and C succeeds. It would be great to have an option to force D to run no matter the status of B or C. Project: Jenkins Priority: Major Reporter: Paulo Matos 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Tommi Kiviniemi commented on JENKINS-23958 Pipe Broken I am sorry that I haven't gotten back to you regarding the sample project yet, but we are just about to release our game and have been too swamped to find time for it. Just wanted to let you know that I will do it as soon as time permits. PS. We are using Unity Cache server, running on the same machine as everything else. If you have it could you try enabling it to see if you get the sample project build to fail? 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] [delivery-pipeline] (JENKINS-23485) TokenMacro for getting a version value stored in environment variable
Patrik Boström assigned JENKINS-23485 to Unassigned TokenMacro for getting a version value stored in environment variable Change By: Patrik Boström (03/Sep/14 10:56 AM) Assignee: PatrikBoström 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] [naginator] (JENKINS-22524) a failed multi-configuration child job causes overall job to fail, even if naginator makes it pass.
Tomer Galun resolved JENKINS-22524 as Fixed a failed multi-configuration child job causes overall job to fail, even if naginator makes it pass. Should be fixed in 1.12 (for multi-configuration jobs you can choose to rerun only failed parts, or else the whole combinations will rerun) Change By: Tomer Galun (03/Sep/14 1:44 PM) Status: Open Resolved Assignee: NicolasDeLoof TomerGalun 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-23921) new divs layout doesn't work with IE8
Tom FENNELLY commented on JENKINS-23921 new divs layout doesnt work with IE8 @Stephen - so that sounds like there's no issue, right? 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] [active-directory] (JENKINS-20816) BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException
Daniel Beck commented on JENKINS-20816 BadCredentialsException: Failed to retrieve user information for jusurb; nested exception is javax.naming.PartialResultException Was it a page with "angry Jenkins" (https://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/images/rage.png), or one completely "without design"? 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
Steve Jansen commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Not sure if this helps or not, but I faced a similar issue with this network topology: LAN A (OpenStack cluster with a 192.168.2.0/24 internal network, NAT'd to the rest of the LAN via the 10.166.140.0/24 "floating" IPs) Jenkins master @ 192.168.2.10 or 10.166.140.10 Jenkins slave 1 @ 192.168.2.11 Jenkins slave 2 @ 192.168.2.12 LAN B (3rd party data center, connected to LAN A via site-to-site VPN) Jenkins slave 3 @ 10.21.26.50 Jenkins slave 4 @ 10.21.26.51 The CLI worked fine over the master node's private ip address, e.g. `java -jar jenkins-cli.jar -s http://192.168.2.10:8080/ help` The CLI failed on any slave in either LAN when using the master node's public ip address, e.g., `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` raised the error "SEVERE: I/O error in channel Chunked connection" The problem was ultimately the software firewall in the OpenStack cluster that only applied to the floating IPs (e.g., 10.166.140.0/24). The resolution was to allowing UDP ingress on ports 1024-65535 and TCP ingress on ports 1024-65535 for my slaves public IPs (10.21.26.0/24 and 10.166.140.0/24). Executing `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` then worked as expected on all slaves in both data centers. My $0.02 - there is some complex networking for CLI connections: there seems to be ICMP, UDP, and TCP in use at the same time, along with random (JNLP?) ports on the server. The CLI client could use connectivity checks and/or clearcut error messages to better explain when connectivity fails for a specific protocol/address/port. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Do you have the console and logcat output logs for each of the good and bad examples? That would help to match things up with events in the packet capture. 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-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Jesse Glick resolved JENKINS-24458 as Fixed SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions https://github.com/stapler/stapler/commit/143049bdbb6683d33d70b84ec7339a47ab4ac2a0 should be in Stapler 1.229, which core will pick up at some point (up to @kohsuke when). Change By: Jesse Glick (03/Sep/14 5:19 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24458) SomeAction doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions
Jesse Glick updated JENKINS-24458 SomeAction doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions Change By: Jesse Glick (03/Sep/14 5:17 PM) Summary: JobConfiguration SomeAction doesnthave@ExportedBeansocannotwritehudson.model.Actionable.actions Assignee: JesseGlick Component/s: core Component/s: read-only-configurations 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-24550) When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut 'Document Mode'
Andrei Ababei commented on JENKINS-24550 When I update my Jenkins from 1.563 to 1.566 or lator，my Internet Explorer gets waring：Your Internet Explorer appears to be set to a non-defalut Document Mode Seems to be a duplicate of JENKINS-23921. 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] [selenium] (JENKINS-23348) changes to selenium configuration under jenkins 'manager jenkins' is not saved
Matt Bailey commented on JENKINS-23348 changes to selenium configuration under jenkins manager jenkins is not saved I'm also having this same issue (Jenkins ver. 1.577, Selenium Plugin 2.4.1) 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
Steve Jansen edited a comment on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Not sure if this helps or not, but I faced a similar issue with this network topology: LAN A (OpenStack cluster with a 192.168.2.0/24 internal network, NAT'd to the rest of the LAN via "floating" public IPs on 10.166.140.0/24) Jenkins master @ 192.168.2.10 or 10.166.140.10 Jenkins slave 1 @ 192.168.2.11 Jenkins slave 2 @ 192.168.2.12 LAN B (3rd party data center, connected to LAN A via site-to-site VPN which NAT to 10.21.26.0/24 on LAN A) Jenkins slave 3 @ 10.21.26.50 Jenkins slave 4 @ 10.21.26.51 The CLI worked as expected when using the master node's private ip address but not the master node's public ip address. For example `java -jar jenkins-cli.jar -s http://192.168.2.10:8080/ help` worked, but `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` raised the error "SEVERE: I/O error in channel Chunked connection" on any slave. The problem was ultimately the software firewall in the OpenStack cluster that only applied to the floating IPs (e.g., 10.166.140.0/24). The resolution was to allowing UDP ingress on ports 1024-65535 and TCP ingress on ports 1024-65535 where the destination was the Jenkins master node and the source was my slaves public IPs (10.21.26.0/24 and 10.166.140.0/24). After the firewall change, executing `java -jar jenkins-cli.jar -s http://10.166.140.10:8080/ help` worked as expected on all slaves in both data centers. My $0.02 - there is some complex networking for CLI connections: there seems to be ICMP, UDP, and TCP in use at the same time, along with random (JNLP?) ports on the server. The CLI client could use connectivity checks and/or clearcut error messages to better explain when connectivity fails for a specific protocol/address/port. 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken No cache server here Settings up the test project should take 5 min if you have the envinject plugin already installed. Good luck with your launch. Feel free to mail me to announce it (or if you need test users, I have testflight/hockeyapp accounts if needed) 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-23263) Move hudson.tasks.junit to a bundled plugin
Jesse Glick commented on JENKINS-23263 Move hudson.tasks.junit to a bundled plugin @rkarbas if using Email Ext plugin, upgrade 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] [git] (JENKINS-12316) git plugin should NOT tag every build by default
Patrick Hemmer
commented on JENKINS-12316
git plugin should NOT tag every build by default
I noticed after I submitted that comment that it doesn't happen unless the git-publisher is enabled (post-build action). As soon as it's enabled, it starts generating tags of the form "jenkins-${project}-${build_number}-SUCCESS"
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-23921) new divs layout doesn't work with IE8
Tom FENNELLY edited a comment on JENKINS-23921 new divs layout doesnt work with IE8 @Stephen - so that sounds like there's no issue, right? EDIT - Correction having read it again that does sound like it's not right Sorry. 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] [openid] (JENKINS-23009) [openid-plugin] Support 3 different email attributes for AX Extension
SCM/JIRA link daemon commented on JENKINS-23009 [openid-plugin] Support 3 different email attributes for AX Extension Code changed in jenkins User: Nirmal Jonnalagedda Path: src/main/java/hudson/plugins/openid/impl/UserInfoExtension.java src/test/java/hudson/plugins/openid/OpenIdAXEmailAttributesTest.java src/test/java/hudson/plugins/openid/OpenIdTestCase.java src/test/java/hudson/plugins/openid/OpenIdTestService.java http://jenkins-ci.org/commit/openid-plugin/d5eeed596d5791017bca422286f9de944cdcd8e6 Log: FIXED JENKINS-23009 Try 3 different email AX attributes 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] [support-core] (JENKINS-24567) java.lang.IllegalArgumentException: Invalid thread ID parameter: -1
Walter Kacynski created JENKINS-24567 java.lang.IllegalArgumentException: Invalid thread ID parameter: -1 Issue Type: Bug Assignee: Unassigned Components: support-core Created: 03/Sep/14 5:37 PM Description: I just updated to the latest support-core 2.13 and my master is throwing out these messages now. Sep 3, 2014 1:29:18 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@68ef7262 failed java.lang.IllegalArgumentException: Invalid thread ID parameter: -1 at sun.management.ThreadImpl.verifyThreadIds(ThreadImpl.java:136) at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:143) at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:114) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:103) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Project: Jenkins Priority: Major Reporter: Walter Kacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23
mwebber commented on JENKINS-22125 FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 @vikulin: Are you running with -Dhudson.plugins.parameterizedtrigger.ProjectSpecificParametersActionFactory.compatibility_mode=true as described above? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Chris Tobey commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @stephenconnolly Is the option of adding a checkbox to "Use these credentials for all externals" out of the question? 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] [active-directory] (JENKINS-8151) Authentication against active-directory doesn't work from IE8 browser.
Daniel Beck resolved JENKINS-8151 as Wont Fix Authentication against active-directory doesnt work from IE8 browser. Internet Explorer 8 is not supported by Jenkins, so resolving as Won't Fix. If this issue occurs on more recent versions of Internet Explorer, please file a new issue. https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix Change By: Daniel Beck (03/Sep/14 7:21 PM) Status: Open Resolved Resolution: WontFix 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-13540) Redirects do not work properly on IE
Daniel Beck resolved JENKINS-13540 as Wont Fix Redirects do not work properly on IE Internet Explorer 8 is no longer supported by Jenkins, so resolving as Won't Fix. If this issue occurs on more recent versions of Internet Explorer, please file a new issue. https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix Change By: Daniel Beck (03/Sep/14 7:24 PM) Status: Open Resolved Resolution: WontFix 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] [openid] (JENKINS-23009) [openid-plugin] Support 3 different email attributes for AX Extension
SCM/JIRA link daemon resolved JENKINS-23009 as Fixed [openid-plugin] Support 3 different email attributes for AX Extension Change By: SCM/JIRA link daemon (03/Sep/14 7:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24353) UI Themes plugin
Chris Tobey commented on JENKINS-24353 UI Themes plugin Hey guys, Is there a way to somehow manually change the behavior to nowrap now via some configuration file or css somewhere, or is this not possible until this feature is implemented? 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-24353) UI Themes plugin
Chris Tobey updated JENKINS-24353 UI Themes plugin Not very pretty. Change By: Chris Tobey (03/Sep/14 6:52 PM) Attachment: BuildExecutors.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] [git] (JENKINS-12316) git plugin should NOT tag every build by default
owenmehegan commented on JENKINS-12316 git plugin should NOT tag every build by default 1. I think if you previously used a version of the git plugin which DID enable tags on builds by default, then simply upgrading to the version where tags are disabled by default would not change that setting in your existing builds. You would need to manually do that. 2. In either case, I think the tags are only created in your local checkout of the repo. They would not be pushed to the remote repo unless you happened to do a 'git push' or 'git push --tags' as part of your build job, or used the git-publisher action as Patrick points out. In my case we create our own tags for builds, in certain cases, and push those. Each time we did that we would also end up with the superfluous Jenkins tags crapping up the remote repo. I think this is why not everyone saw this auto-tag behavior as such a big deal. 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I've had a quick look over the Wireshark captures. In the "bad" capture the emulator never responds to the connection (CNXN) request from ADB and at first glance that seems to jam the whole adb-emulator connection up. I haven't worked out whether ADB or the emulator is a fault because ADB only gives the emulator about 0.5 second to respond before it forcefully closes the connection. The emulator doesn't release (TCP FIN) its end of the connection for about another 17 seconds. For reference this all occurs in the TCP connection from port 62625 to port 5752 that starts at packet 371 in the bad pcap file. Good connection looks like 43 4e 58 4e 00 00 00 01 00 10 00 00 07 00 00 00 CNXN 0010 32 02 00 00 bc b1 a7 b1 68 6f 73 74 3a 3a 002... host::. 43 4e 58 4e 00 00 00 01 00 10 00 00 5a 00 00 00 CNXN Z... 0010 41 22 00 00 bc b1 a7 b1 64 65 76 69 63 65 3a 3a A".. device:: 0020 72 6f 2e 70 72 6f 64 75 63 74 2e 6e 61 6d 65 3d ro.produ ct.name= 0030 67 6f 6f 67 6c 65 5f 73 64 6b 3b 72 6f 2e 70 72 google_s dk;ro.pr 0040 6f 64 75 63 74 2e 6d 6f 64 65 6c 3d 67 6f 6f 67 oduct.mo del=goog 0050 6c 65 5f 73 64 6b 3b 72 6f 2e 70 72 6f 64 75 63 le_sdk;r o.produc 0060 74 2e 64 65 76 69 63 65 3d 67 65 6e 65 72 69 63 t.device =generic 0070 3b 00;. 001F 4f 50 45 4e 17 00 00 00 00 00 00 00 1f 00 00 00 OPEN 002F ed 0b 00 00 b0 af ba b1 73 68 65 6c 6c 3a 67 65 shell:ge 003F 74 70 72 6f 70 20 64 65 76 2e 62 6f 6f 74 63 6f tprop de v.bootco 004F 6d 70 6c 65 74 65 00 mplete. 0072 4f 4b 41 59 01 00 00 00 17 00 00 00 00 00 00 00 OKAY 0082 00 00 00 00 b0 b4 be a6 008A 57 52 54 45 01 00 00 00 17 00 00 00 02 00 00 00 WRTE 009A 17 00 00 00 a8 ad ab ba 0d 0a .. 0056 4f 4b 41 59 17 00 00 00 01 00 00 00 00 00 00 00 OKAY 0066 00 00 00 00 b0 b4 be a6 00A4 43 4c 53 45 00 00 00 00 17 00 00 00 00 00 00 00 CLSE 00B4 00 00 00 00 bc b3 ac ba 006E 43 4c 53 45 17 00 00 00 01 00 00 00 00 00 00 00 CLSE 007E 00 00 00 00 bc b3 ac ba ... truncated here because it is uninteresting for our purposes... Bad connection stream contains 43 4e 58 4e 00 00 00 01 00 10 00 00 07 00 00 00 CNXN 0010 32 02 00 00 bc b1 a7 b1 68 6f 73 74 3a 3a 002... host::. I likely will not get to look at this further for at least the next 36 hours. I will do a bit of digging in the emulator/ADB code to see if my analysis matches what the code does once I get some spare time. 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.
