[JIRA] [core] (JENKINS-25704) Scheduled triggering stops working until restart
David Resnick updated JENKINS-25704 Scheduled triggering stops working until restart Change By: David Resnick (14/Dec/14 8:35 AM) Attachment: hudson.triggers-ALL.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25704) Scheduled triggering stops working until restart
David Resnick commented on JENKINS-25704 Scheduled triggering stops working until restart I've attached log hudson.triggers-ALL.log. It seems to show that again, for no apparent reason, cron triggers stop at a certain point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25704) Scheduled triggering stops working until restart
David Resnick updated JENKINS-25704 Scheduled triggering stops working until restart Change By: David Resnick (14/Dec/14 8:36 AM) Attachment: hudson.triggers-ALL.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim-plugin] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
David Resnick commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Thanks, I've updated the wiki about this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-26061) Incompatible argument to function
Sakthivel C created JENKINS-26061 Incompatible argument to function Issue Type: Bug Assignee: Unassigned Attachments: jenkins.err.log Components: other Created: 14/Dec/14 10:29 AM Description: Team, My jenkins setup was running succesfully for the last few months and all of a sudden all the jobs started failing when i click "Build Now". Even then, the scheduled jobs were running successfully. But since today they also started failing and I am getting the following error in the console output, FATAL: (class: org/apache/commons/codec/binary/Base64OutputStream, method: signature: (Ljava/io/OutputStream;ZI[B)V) Incompatible argument to function FATAL: (class: org/apache/commons/codec/binary/Base64OutputStream, method: signature: (Ljava/io/OutputStream;ZI[B)V) Incompatible argument to function Finished: null I am unable to proceed with any build now. Can you please help me? P:S I tried adding -Xverify:none option as well.I tried removing the fingerprints directory also. Attaching the error log. The time since it started failing is 10/Dec/14-12:00 noon. (if in case you need to know the exact time of failure) Environment: Windows 7 Enterprise Jenkins 1.580 Plugins : Greenballs,deploy. deploy-websphere,mapdb-api, multiple-scms,ws-cleanup Project: Jenkins Labels: jenkins exception windows maven Priority: Blocker Reporter: Sakthivel 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] [xcode-plugin] (JENKINS-24897) Build fails with jenkins XCode Integration Plugin with XCode 6.0.1
lacostej commented on JENKINS-24897 Build fails with jenkins XCode Integration Plugin with XCode 6.0.1 By config, I meant config of the xcode-plugin within your job. Which fields are set and how to reproduce the issue. The best would be to have a test project and the associated part of the config.xml that is relevant to the xcode plugin configuration and environement. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-24897) Build fails with jenkins XCode Integration Plugin with XCode 6.0.1
lacostej commented on JENKINS-24897 Build fails with jenkins XCode Integration Plugin with XCode 6.0.1 I've created a test project with one test target with a scheme with space and I was able to build and run the tests by appending commands so that jenkins runs: /usr/bin/xcodebuild -scheme CocoaPodsExample -workspace CocoaPodsExample.xcworkspace build "CODE_SIGN_IDENTITY=." test -destination "platform=iOS Simulator,name=iPhone 6" /Users/lacostej/.jenkins/jobs/xcode_JENKINS-24897_spaces/workspace/CocoaPodsExampleTests/CocoaPodsExampleTests.m:35: Test Case '-[CocoaPodsExampleTests testPerformanceExample]' measured [Time, seconds] average: 0.000, relative standard deviation: 71.133%, values: [0.04, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01, 0.01], performanceMetricID:com.apple.XCTPerformanceMetric_WallClockTime, baselineName: "", baselineAverage: , maxPercentRegression: 10.000%, maxPercentRelativeStandardDeviation: 10.000%, maxRegression: 0.100, maxStandardDeviation: 0.100 Test Case '-[CocoaPodsExampleTests testPerformanceExample]' passed (0.297 seconds). Test Suite 'CocoaPodsExampleTests' passed at 2014-12-14 11:38:27 +. Executed 2 tests, with 0 failures (0 unexpected) in 0.297 (0.298) seconds Test Suite 'CocoaPodsExample Tests.xctest' passed at 2014-12-14 11:38:27 +. Executed 2 tests, with 0 failures (0 unexpected) in 0.297 (0.300) seconds Test Suite 'All tests' passed at 2014-12-14 11:38:27 +. Executed 2 tests, with 0 failures (0 unexpected) in 0.297 (0.301) seconds Finished: SUCCESS So I will close this issue until I get something that I can reproduce. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-24897) Build fails with jenkins XCode Integration Plugin with XCode 6.0.1
lacostej resolved JENKINS-24897 as Cannot Reproduce Build fails with jenkins XCode Integration Plugin with XCode 6.0.1 Change By: lacostej (14/Dec/14 11:41 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-24897) Build fails with jenkins XCode Integration Plugin with XCode 6.0.1
lacostej closed JENKINS-24897 as Cannot Reproduce Build fails with jenkins XCode Integration Plugin with XCode 6.0.1 Change By: lacostej (14/Dec/14 11:41 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Daniel Beck commented on JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Is this specific to the Maven project type? Or to freestyle? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clone-workspace-plugin] (JENKINS-26058) Implement a tarball-only option for cloning the workspace
Daniel Beck commented on JENKINS-26058 Implement a tarball-only option for cloning the workspace Did you compare the numbers in a realistic scenario to make sure this would actually help? In my experience, gzip adds very little (time) overhead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25948) Restrict where this project can be run does not get saved in 1.592
Daniel Beck resolved JENKINS-25948 as Duplicate Restrict where this project can be run does not get saved in 1.592 Duplicates JENKINS-23966. Change By: Daniel Beck (14/Dec/14 11:49 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-plugin] (JENKINS-25948) Restrict where this project can be run does not get saved in 1.592
Daniel Beck edited a comment on JENKINS-25948 Restrict where this project can be run does not get saved in 1.592 Duplicates JENKINS-25533. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25947) Jenkins server accessed but tested item get lost, get a empty dashboard
Daniel Beck resolved JENKINS-25947 as Incomplete Jenkins server accessed but tested item get lost, get a empty dashboard Report does not contain nearly enough information to act on it. https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue It looks like something's wrong with Robot Plugin, probably just disabled. Change By: Daniel Beck (14/Dec/14 11:51 AM) Status: Open Resolved Assignee: R. Tyler Croy Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25936) Maven environment variables are not expanded when triggering another project.
Daniel Beck commented on JENKINS-25936 Maven environment variables are not expanded when triggering another project. ikedam: core's CommandInterpreter.perform(...) iterates over build.getEnvironment(...) to build the process's environment variables. Maven plugin contributes the POM_ variables to that map. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25962) Using Jenkins Job Builder to create triggers based on comment regex fails to trigger
Daniel Beck resolved JENKINS-25962 as Duplicate Using Jenkins Job Builder to create triggers based on comment regex fails to trigger IMO for issues with JJB to be relevant here they need to be reproducible with Jenkins itself. In this case, probably through the REST API by POSTing config.xml. Resolving as duplicate of the linked issue. Change By: Daniel Beck (14/Dec/14 12:14 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25962) Using Jenkins Job Builder to create triggers based on comment regex fails to trigger
Daniel Beck reopened JENKINS-25962 Using Jenkins Job Builder to create triggers based on comment regex fails to trigger Reopening as the other seems limited to build loss rather than the overall "Trigger not updated" issue. Change By: Daniel Beck (14/Dec/14 12:15 PM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25912) Workspace remains on disk after job has been ( deleted, moved, renamed )
Daniel Beck commented on JENKINS-25912 Workspace remains on disk after job has been ( deleted, moved, renamed ) The problem of course is offline nodes while performing the action. Those simply cannot be updated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25967) Job rename does not update reference to new workspace
Daniel Beck resolved JENKINS-25967 as Duplicate Job rename does not update reference to new workspace Change By: Daniel Beck (14/Dec/14 12:19 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-19528) Mask Password Plugin should support Maven Style Projects
Daniel Beck updated JENKINS-19528 Mask Password Plugin should support Maven Style Projects You wanting something does not make it a blocker. It looks like the plugin is currently without an active maintainer, so it should be possible for you to apply for commit access to fix this. Change By: Daniel Beck (14/Dec/14 12:23 PM) Priority: Blocker Major Labels: mask-passwords plugins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25972) Add disable/enable project to drop down menu
Daniel Beck commented on JENKINS-25972 Add disable/enable project to drop down menu Enable/disable are currently not actions that appear in the sidepanel, and only those are provided in the menu. Similar issue with 'Mark slave offline'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25973) Provide an option to exclude disabled projects from a view
Daniel Beck resolved JENKINS-25973 as Won't Fix Provide an option to exclude disabled projects from a view View Job Filters Plugin does a great job providing additional filters. Change By: Daniel Beck (14/Dec/14 12:26 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25984) Jenkins subversion plugin does not handle git-flow style branch names
Daniel Beck commented on JENKINS-25984 Jenkins subversion plugin does not handle git-flow style branch names What exactly is the bug here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-23573) Set an umask
Daniel Beck updated JENKINS-23573 Set an umask Not a bug. Workarounds: Set an umask for Jenkins. Tons of side effects. Chmod the files during the build. Hence reducing priority. Change By: Daniel Beck (14/Dec/14 12:31 PM) Issue Type: Bug New Feature 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-25986) Cannot save jenkins job after updating it
Daniel Beck resolved JENKINS-25986 as Cannot Reproduce Cannot save jenkins job after updating it Tried scenario 2 and was unable to reproduce this. In general, unless Jenkins crashes (and I don't mean the "Oops" error page), it will respond to requests, or take forever to time out. If Jenkins runs behind a reverse proxy, make sure its configuration is correct. Check the (access and error) logs of every server software involved (possibly reverse proxy, webapp container if applicable, Jenkins itself). Change By: Daniel Beck (14/Dec/14 12:36 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25988) Major performance issues on pages with large build queues (100+ items)
Daniel Beck updated JENKINS-25988 Major performance issues on pages with large build queues (100+ items) Change By: Daniel Beck (14/Dec/14 12:37 PM) Labels: performance user-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] [core] (JENKINS-25988) Major performance issues on pages with large build queues (100+ items)
Daniel Beck commented on JENKINS-25988 Major performance issues on pages with large build queues (100+ items) Workaround is of course to collapse the build queue by clicking the '-'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25993) Java 9 completely changes JDK directory layout and drops tools.jar
Daniel Beck resolved JENKINS-25993 as Duplicate Java 9 completely changes JDK directory layout and drops tools.jar The form validation for valid JDK dir is tracked as JENKINS-25601. Any other specific issues in core or plugins need to be filed independently against the affect component. If you just want to raise awareness of these changes, Jira is the wrong way. Maybe email the dev list. Change By: Daniel Beck (14/Dec/14 12:43 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25980) How to checkin report summary file on post build using Integrity plugin
Daniel Beck resolved JENKINS-25980 as Not A Defect How to checkin report summary file on post build using Integrity plugin JIRA is an issue tracker, not a support site. Change By: Daniel Beck (14/Dec/14 12:48 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26013) In build history, again make visible if a link was visited
Daniel Beck updated JENKINS-26013 In build history, again make visible if a link was visited Change By: Daniel Beck (14/Dec/14 1:00 PM) Issue Type: Bug Improvement Labels: user-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] [core] (JENKINS-25971) Job list and console output are not properly aligned in the new UI
Daniel Beck updated JENKINS-25971 Job list and console output are not properly aligned in the new UI Change By: Daniel Beck (14/Dec/14 1:03 PM) Labels: gui user-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] [core] (JENKINS-26015) Layout broken since 1.593
Daniel Beck resolved JENKINS-26015 as Duplicate Layout broken since 1.593 Duplicates JENKINS-25971. Change By: Daniel Beck (14/Dec/14 1:03 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-10864) Matrix project page does not show test result information, though aggregate test result information does exist.
Daniel Beck updated JENKINS-10864 Matrix project page does not show test result information, though aggregate test result information does exist. I don't think Andrew cares at the moment, so unassigning. Change By: Daniel Beck (14/Dec/14 1:02 PM) Assignee: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
Daniel Beck resolved JENKINS-26019 as Not A Defect build with form submission does not return queue location You're POSTing to the wrong URL. Change By: Daniel Beck (14/Dec/14 1:06 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25869) Jenkins is getting crashed and shutting down once in a while
Daniel Beck commented on JENKINS-25869 Jenkins is getting crashed and shutting down once in a while That looks like a completely different issue. What is the relation of that to the earlier reported JRE crashes? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25742) Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state
Daniel Beck updated JENKINS-25742 Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state Change By: Daniel Beck (14/Dec/14 1:17 PM) Labels: jenkins deadlock This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25742) Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state
Daniel Beck updated JENKINS-25742 Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state Change By: Daniel Beck (14/Dec/14 1:18 PM) Labels: deadlock lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25989) No wrap up(not in multiple lines) of too long list of slaves at label page
Daniel Beck commented on JENKINS-25989 No wrap up(not in multiple lines) of too long list of slaves at label page Could you upload a PNG, JPG or GIF file with a screenshot of the different behavior? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25986) Cannot save jenkins job after updating it
Daniel Beck edited a comment on JENKINS-25986 Cannot save jenkins job after updating it Tried scenario 2 and was unable to reproduce this. In general, unless Jenkins crashes (and I don't mean the "Oops" error page), it will respond to requests, or take forever to time out. If Jenkins runs behind a reverse proxy, make sure its configuration is correct. Check the (access and error) logs of every server software involved (possibly reverse proxy, webapp container if applicable, Jenkins itself). If it takes a while for the error to appear, also check the /threadDump URL to see what Jenkins does (look for "Handling 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Daniel Beck commented on JENKINS-18567 Add Watch button to Job summary screen Alex: Is this in Git for review? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Daniel Beck edited a comment on JENKINS-18567 Add Watch button to Job summary screen (Obsolete: Found 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] [clone-workspace-plugin] (JENKINS-26058) Implement a tarball-only option for cloning the workspace
Daniel Beck commented on JENKINS-26058 Implement a tarball-only option for cloning the workspace JENKINS-26008 indicates a significant speedup when archiving artifacts and not using gzip. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25876) Log files retained in memory until process is killed
Daniel Beck commented on JENKINS-25876 Log files retained in memory until process is killed "produces about 200KB of logging" in what time frame? 200KB*37 is still basically nothing if that's the total. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clone-workspace-plugin] (JENKINS-26058) Implement a tarball-only option for cloning the workspace
Luke Petre commented on JENKINS-26058 Implement a tarball-only option for cloning the workspace I've already implemented the feature here: https://github.com/jenkinsci/jenkins-clone-workspace-scm-plugin/pull/8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clone-workspace-plugin] (JENKINS-26058) Implement a tarball-only option for cloning the workspace
Luke Petre commented on JENKINS-26058 Implement a tarball-only option for cloning the workspace Yes, I'm running this change locally and it is a significant improvement. Our workspace is 1.6GB as an uncompressed tarball and 1.1GB compressed. This change saves 90 seconds for each job in our build pipeline, which is about a 20% speedup overall. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-9693) maven.build.timestamp.format is not obeyed in maven builds
Daniel Beck resolved JENKINS-9693 as Fixed maven.build.timestamp.format is not obeyed in maven builds Comment indicates this has been resolved. Change By: Daniel Beck (14/Dec/14 2:02 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
René Scheibe commented on JENKINS-26019 build with form submission does not return queue location There is buildWithParameters (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build) too but the API documentation states to use build (https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API) with JSON. So I thought buildWithParameters is only to be used when the parameters are specified as query parameters in the URL. Could you please provide the correct URL to use? At least the documentation needs to be 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] [perforce-plugin] (JENKINS-25830) Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work
Daniel Beck updated JENKINS-25830 Since upgrading to 1.590 the "Max # of builds to keep with artifacts" option does not seem to work Change By: Daniel Beck (14/Dec/14 2:06 PM) Component/s: perforce-plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
René Scheibe reopened JENKINS-26019 build with form submission does not return queue location Change By: René Scheibe (14/Dec/14 2:08 PM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Susanne Lindgren commented on JENKINS-16345 CLI does not work through reverse proxy How is hudson.TcpSlaveAgentListener.hostName used? I tried adding -Dhudson.TcpSlaveAgentListener.hostName=$HOSTNAME to the parameters when starting my jenkins, but cli access failed in the same way as before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
René Scheibe assigned JENKINS-26019 to Daniel Beck build with form submission does not return queue location Change By: René Scheibe (14/Dec/14 2:10 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25737) 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started on remote-node.
Daniel Beck commented on JENKINS-25737 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started on remote-node. Oleg: Could you elaborate on that please? What system Groovy script demonstrated this issue without Perforce? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25670) SecretRewriterTest (in Jenkins.core) fails when doing Maven build of Jenkins source
Daniel Beck commented on JENKINS-25670 SecretRewriterTest (in Jenkins.core) fails when doing Maven build of Jenkins source No, the build was successful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
René Scheibe edited a comment on JENKINS-26019 build with form submission does not return queue location Sure there is buildWithParameters (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build) too. BUT: The API documentation states to use build (https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API) with JSON. Running a parameterized build manually from the Jenkins UI via "Build with Parameters" the build URL is used. So I thought buildWithParameters is only to be used when the parameters are specified as query parameters in the URL. Could you please provide the correct URL to use? At least the documentation needs to be 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-25670) SecretRewriterTest (in Jenkins.core) fails when doing Maven build of Jenkins source
Daniel Beck commented on JENKINS-25670 SecretRewriterTest (in Jenkins.core) fails when doing Maven build of Jenkins source Comment to JENKINS-25937 may be relevant here, and this can probably be considered a duplicate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Daniel Beck commented on JENKINS-16345 CLI does not work through reverse proxy Is the host name from the environment variable known to the CLI client (including how it's (not) fully qualified)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
Daniel Beck updated JENKINS-26019 build with form submission does not return queue location Change By: Daniel Beck (14/Dec/14 2:28 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
Daniel Beck commented on JENKINS-26019 build with form submission does not return queue location You left out both build and buildWithParameters in your "command line excerpt", hence my confusion. IMO the wiki is wrong about how to do this. AFAICT it's not meant for programmatic use (it's basically the "browser way"). Use the method described on the /job/foo/api page, section "Perform a build". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication
Daniel Beck commented on JENKINS-24958 UsernameNotFoundException when ActiveDirectory used for API and token authentication Felix: You're just doing it wrong. Leave out token=ASDF, that's only needed if read access to the job is available and you want to build without being allowed by your authentication. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication
Daniel Beck edited a comment on JENKINS-24958 UsernameNotFoundException when ActiveDirectory used for API and token authentication Felix: You're just doing it wrong. Leave out token=ASDF, that's only needed if read access to the job is available and you want to build without being allowed by your authentication. Basically, (I also have a build trigger token, but I don't know if that matters) that is the reason Expected and Actual are different. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication
Daniel Beck resolved JENKINS-24958 as Incomplete UsernameNotFoundException when ActiveDirectory used for API and token authentication Resolving as incomplete as requested additional information has not been provided in months. Change By: Daniel Beck (14/Dec/14 2:33 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
René Scheibe edited a comment on JENKINS-26019 build with form submission does not return queue location Sure there is buildWithParameters (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build) too. BUT: The API documentation states to use build (https://wiki.jenkins-ci.org/display/JENKINS/Remote+access+API) with JSON. Running a parameterized build manually from the Jenkins UI via "Build with Parameters" the build URL is used. Using POST on buildWithParameters and JSON the parameters are not assigned any values. So I thought buildWithParameters is only to be used when the parameters are specified as query parameters in the URL. Could you please provide the correct URL to use? At least the documentation needs to be 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] [_test] (JENKINS-25881) The Jenkins homepage crashes
Daniel Beck commented on JENKINS-25881 The Jenkins homepage crashes Pipeline Plugin is known to handle incomplete configuration badly. Several issues have been filed against it already. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26019) build with form submission does not return queue location
René Scheibe
updated JENKINS-26019
build with form submission does not return queue location
Change By:
René Scheibe
(14/Dec/14 2:41 PM)
Description:
related to JENKINS-23235 and JENKINS-13546.When creating builds using /build, the result is a 201 response where the Location header points to the queue item that represents the new build. Example:
$
curl -X POST "https://myjenkins/job/plainJob/build" --insecure --include
{code}
HTTP/1.1
100 ContinueHTTP/1.1
201 CreatedDate: Thu, 11 Dec 2014 15:23:38 GMT Server: Jetty(winstone-2.8)Location: https://myjenkins/queue/item/39/Content-Length: 0Content-Type: text/plain
{code}
I would expect that parametrized builds with form submission would point to the queue item as well.However location header only contains the job link itself:
$
curl -X POST "https://myjenkins/job/formJob
/build
" --insecure -
-include -
F json='{"parameter": [{"name":"ID", "value":"260"}]}'
--include
{code}
HTTP/1.1 100 ContinueHTTP/1.1 201 CreatedDate: Thu, 11 Dec 2014 15:24:20 GMT Server: Jetty(winstone-2.8)Location: https://myjenkins/job/formJob/Content-Length: 0Content-Type: text/plain
{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
René Scheibe commented on JENKINS-26019 build with form submission does not return queue location Yes, I just saw it right now. BIG sorry. I fixed the description now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
René Scheibe commented on JENKINS-26019 build with form submission does not return queue location Following the documentation under /job/foo/api it states: If the build has parameters, post to this URL and provide the parameters as form data. The "this URL" link resolves to /job/job1/buildWithParameters. BUT: Performing a POST and sending the parameters as form data (not as URL query parameters), they are not assigned any value in Jenkins. So is this another bug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-25433) Xcodebuild sigining fails
lacostej commented on JENKINS-25433 Xcodebuild sigining fails Hello everyone. As explained by Matan, jenkins kust calls the xcrun command and never invokes the xcodesign command directly. If the xcrun command is obsolete or needs adjustement for Yosemite, I would love to get some insight into what is required to run the command properly. I don't have a Yosemite running server with xcode 6.1 yet in place. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-19528) Mask Password Plugin should support Maven Style Projects
Matteo Castellarin commented on JENKINS-19528 Mask Password Plugin should support Maven Style Projects A security plugin unmaintained for already 3 years and having a security issue is actually blocking. Moving beyond the controversy: it is not clear whether the problem is with the plugin itself or with Jenkins, who erroneously propagates the properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-24789) Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter
Raphael CHAUMIER commented on JENKINS-24789 Possibility to skip a deployment task during a build by specifying what task to disable with a build parameter We can imagine that if an env/parametrized variable naming DEPLOY__SKIP is found the following deployment task won't be triggered . corresponding to the value of the task Name field This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-19862) NPE when copying job with deployer plugin
Raphael CHAUMIER commented on JENKINS-19862 NPE when copying job with deployer plugin Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:285) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:628) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475) Caused by: java.lang.NullPointerException at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1021) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:448) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:688) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:444) at hudson.model.AbstractProject.save(AbstractProject.java:266) at hudson.model.Job.onLoad(Job.java:192) at hudson.model.AbstractProject.onLoad(AbstractProject.java:278) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:746) at hudson.model.Items.load(Items.java:221) at hudson.model.ItemGroupMixIn.copy(ItemGroupMixIn.java:208) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:164) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:2857) at jenkins.model.Jenkins.doCreateItem(Jenkins.java:308) at hudson.model.AllView.doCreateItem(AllView.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
[JIRA] [mask-passwords-plugin] (JENKINS-19528) Mask Password Plugin should support Maven Style Projects
Daniel Beck commented on JENKINS-19528 Mask Password Plugin should support Maven Style Projects A security plugin unmaintained for already 3 years and having a security issue is actually blocking. FWIW security issues should be filed in the SECURITY project. But AFAIU this is just the case that the plugin does not support the Maven job type, i.e. it does not work, rather than e.g. make the passwords public? Please clarify if I'm wrong about this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22865) buildWithParameters doesn't redirect to the build page
Daniel Beck resolved JENKINS-22865 as Incomplete buildWithParameters doesn't redirect to the build page No response to comment asking for clarification in half a year, so resolving as Incomplete. Change By: Daniel Beck (14/Dec/14 4:52 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
Daniel Beck resolved JENKINS-26019 as Cannot Reproduce build with form submission does not return queue location Works for me with both form values and URL parameters. Form values example: curl -X POST --netrc --data 'foo=qux' http://jenkins/job/buildWithParametersTest/buildWithParameters Jenkins 1.593. Resolving this issue for now. My test instance works like a charm, so either there's something wrong with your instance, or you're doing it wrong. Change By: Daniel Beck (14/Dec/14 5:03 PM) Status: Reopened Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25984) Jenkins subversion plugin does not handle git-flow style branch names
Justin Gordon commented on JENKINS-25984 Jenkins subversion plugin does not handle git-flow style branch names feature/some-feature shows up as feature There's some escaping issue, or problem with a regex. git branch names have slashes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25984) Jenkins subversion plugin does not handle git-flow style branch names
Justin Gordon edited a comment on JENKINS-25984 Jenkins subversion plugin does not handle git-flow style branch names A branch named "feature/some-feature" shows up as "feature" There's some escaping issue, or problem with a regex. git branch names have slashes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25984) Jenkins subversion plugin does not handle git-flow style branch names
Daniel Beck commented on JENKINS-25984 Jenkins subversion plugin does not handle git-flow style branch names From http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html, emphasis mine: The Key Concepts Behind Branching You should remember two important lessons from this section. First, Subversion has no internal concept of a branch—it knows only how to make copies. When you copy a directory, the resultant directory is only a “branch” because you attach that meaning to it. You may think of the directory differently, or treat it differently, but to Subversion it's just an ordinary directory that happens to carry some extra historical information. Second, because of this copy mechanism, Subversion's branches exist as normal filesystem directories in the repository. This is different from other version control systems, where branches are typically defined by adding extra-dimensional “labels” to collections of files. The location of your branch directory doesn't matter to Subversion. Most teams follow a convention of putting all branches into a /branches directory, but you're free to invent any policy you wish. Since branches are just directories, just like anything else in a repo, it makes sense from a tools perspective to assume one level of directories are branches, and not recurse. Aside from the performance issue, you'd need to offer every possible directory in the repository as a possible branch root directory. I think you'll also have a difficult time creating those Git-style branches in the first place except by manually creating the feature parent folder separately (which should give you a hint as to how well-supported this is in the first place). Different tools work differently, so arguing that it works in Git leads you nowhere. Not a bug IMO, and not something that needs support in the first place. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25991) Tree-like build log
Daniel Beck commented on JENKINS-25991 Tree-like build log What about plugins like https://wiki.jenkins-ci.org/display/JENKINS/Collapsing+Console+Sections+Plugin ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-26061) Incompatible argument to function
Daniel Beck commented on JENKINS-26061 Incompatible argument to function It started happening after a restart. Why did you restart, what was changed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26020) Will not start builds even though there are available slots on executor
Daniel Beck commented on JENKINS-26020 Will not start builds even though there are available slots on executor Any interesting errors getting logged? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25224) Use VirtualFile for workspace browser
Daniel Beck commented on JENKINS-25224 Use VirtualFile for workspace browser Would be good if this were designed with extensibility of the file browser in mind. There are several issues around that are about adding features to the workspace browser (e.g. file permissions on Unix nodes, file modification times, and/or allowing to edit or delete files specific). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25870) Jenkins is not validating the proxy settings from "manage plugins" even though they are correct
Daniel Beck commented on JENKINS-25870 Jenkins is not validating the proxy settings from "manage plugins" even though they are correct It appears as Jenkins does not support NTLM authentication at all. Maybe your proxy can be configured to support other authentication methods as a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-plugin] (JENKINS-25984) Jenkins subversion plugin does not handle git-flow style branch names
Justin Gordon commented on JENKINS-25984 Jenkins subversion plugin does not handle git-flow style branch names This is not about subversion... The git-flow model is very popular for production projects, and it uses a slash in branch names. https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow http://nvie.com/posts/a-successful-git-branching-model/ There's no git plugin that supports picking branches. The SVN one seems to work with git, except it strips out the branch name after the slash. It's definitely a bug if git branch names will be supported, as there should not be any truncation of a branch name. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25499) Warning on console about toNormalizedIconNameClass
Tom FENNELLY resolved JENKINS-25499 as Fixed Warning on console about toNormalizedIconNameClass Fixed this issue (and JENKINS-25498) in the icon-shim plugin. Updated dependency to new version of same. Change By: Tom FENNELLY (14/Dec/14 8:12 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] [icon-shim-plugin] (JENKINS-25498) Inappropriate use of GString
Tom FENNELLY resolved JENKINS-25498 as Fixed Inappropriate use of GString Fixed this issue (and JENKINS-25499) in the icon-shim plugin. Updated dependency to new version of same. Change By: Tom FENNELLY (14/Dec/14 8:12 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-22865) buildWithParameters doesn't redirect to the build page
Orgad Shaneh reopened JENKINS-22865 buildWithParameters doesn't redirect to the build page Sorry for the late response. I didn't notice the previous comment. In my use-case, I have a web form with action="" target=_blank and method=post. I expect that when the form is submitted and the new tab is opened, that it won't be blank, but will be redirected to either the newly created job or if that's not possible (because the job hasn't started yet) to the project page. Change By: Orgad Shaneh (14/Dec/14 8:40 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25499) Warning on console about toNormalizedIconNameClass
dogfood commented on JENKINS-25499 Warning on console about toNormalizedIconNameClass Integrated in jenkins_main_trunk #3870 [FIXED JENKINS-25499] Updated icon-set dependency to version 1.0.5 (Revision f87c72f15858edf5dd499349569497c3c2bf4449) Result = SUCCESS tom.fennelly : f87c72f15858edf5dd499349569497c3c2bf4449 Files : changelog.html core/pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22865) buildWithParameters doesn't redirect to the build page
Daniel Beck resolved JENKINS-22865 as Won't Fix buildWithParameters doesn't redirect to the build page /buildWithParameters is the programmatic API endpoint. It sends a Location header value specifying the location of the queue item with information about the queued job. So the behavior you're seeing is intentional. You may be able to make /build work. Change By: Daniel Beck (14/Dec/14 9:10 PM) Status: Reopened Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jdk_parameter_plugin] (JENKINS-26062) Jenkins Config won't save
Rob Park created JENKINS-26062 Jenkins Config won't save Issue Type: Bug Assignee: Unassigned Components: jdk_parameter_plugin Created: 14/Dec/14 10:47 PM Description: Several paths in the Jenkins System Config won't save. I don't see any errors in the log either. Sometimes when I change fields, but always after save and go back to config my jdk home will be set to 'git' not the correct path. JDK is just an example. Many others are not saving properly: android home, gradle home, jenkins home URL, etc... Environment: v1.593, amazon linux Project: Jenkins Labels: configuration Priority: Major Reporter: Rob Park This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
René Scheibe commented on JENKINS-26019 build with form submission does not return queue location But how to send a file? If I perform the below request, the file parameter is received correctly but the string parameter has no value in Jenkins. curl -X POST JENKINS_URL/job/JOB_NAME/buildWithParameters --form string_parameter=foo --form file_parameter=@test.bin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
Daniel Beck commented on JENKINS-26019 build with form submission does not return queue location Let me guess, curl -X POST JENKINS_URL/job/JOB_NAME/buildWithParameters?string_parameter=foo --form file_parameter=@test.bin would be too straightforward? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jdk_parameter_plugin] (JENKINS-26062) Jenkins Config won't save
Daniel Beck commented on JENKINS-26062 Jenkins Config won't save Are you sure they're not saved to disk? Check the respective XML config files to make sure. Important: Don't go back to a form using the 'Back' feature (e.g. button, or pressing backspace) of your web browser, there's some known brokenness involved in that, so don't trust the values that are shown in that case (and never submit that either). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26062) Jenkins Config won't save
Daniel Beck updated JENKINS-26062 Jenkins Config won't save Clearly not about the JDK parameter plugin… Change By: Daniel Beck (15/Dec/14 12:34 AM) Component/s: core Component/s: jdk_parameter_plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25556) Deploy p4jenkins test artifact
dan tran commented on JENKINS-25556 Deploy p4jenkins test artifact I would like to reuse your test infrastructure to manage test instances of p4d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26062) Jenkins Config won't save
Rob Park commented on JENKINS-26062 Jenkins Config won't save Agreed not about the JDK plugin... sorry, it was a required field and I didn't realize "core" was the right choice. Also, yeah, definitely not using the back button or any kind of resubmit. If I only change the JDK path, yes it will save to the jenkins config.xml, but if I change anything about the android plugin it will be wiped out. But I don't believe it's specific to the android plugin either. The gradle plugin has the same problem as does Jenkins location, and hipchat build server url. I haven't been able to establish a true pattern though. It's challenging where the UI always sets the name back to 'default' and the directory to 'git'. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event
rin_ne commented on JENKINS-26010 Workflow plugin not working with with Gerrit event ParameterizedJobMixIn.ParameterizedJob cannot be built since it is not BuildableItem. GT has trigger feature in order to schedule build for its job. So I think it is no reason why GT treats non-buildable job. Should we fix isApplicable() only? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25989) No wrap up(not in multiple lines) of too long list of slaves at label page
hiteswar kumar updated JENKINS-25989 No wrap up(not in multiple lines) of too long list of slaves at label page Hi Daniel, please find attatched print screen of issue on LTS_1.554.2 and LTS 1.580.1 Change By: hiteswar kumar (15/Dec/14 5:12 AM) Attachment: Issue-on-LTS_1.554.2.jpg Attachment: Issue-on-LTS_1.580.1.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] [cli] (JENKINS-16345) CLI does not work through reverse proxy
Susanne Lindgren commented on JENKINS-16345 CLI does not work through reverse proxy Yes, both the short hostname and the fully qualified hostname are found with nslookup on the host that I execute the CLI client from. I tested with both, with the same result as when I don't use the hudson.TcpSlaveAgentListener.hostName parameter at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor We get ~5000 JnlpSlaveHandshake errors per hour: Dec 15, 2014 8:40:10 AM jenkins.slaves.JnlpSlaveHandshake error WARNING: TCP slave agent connection handler #150398 with /10.33.21.14:62740 is aborted: generic_AESL-JENKINS07 is already connected to this master. Rejecting this connection. We get these errors at all times, also when we can schedule on all slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26019) build with form submission does not return queue location
René Scheibe commented on JENKINS-26019 build with form submission does not return queue location But that's an inconsistent usage and the not according to the documentation at JENKINS_URL/job/JOB_NAME/api which states to "provide the parameters as form data". It's really cumbersome to have to try all possible forms and combinations of form parameter submission out there. I was hoping to get the API fixed in way that its working consistently and easy to discover for everybody. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26020) Will not start builds even though there are available slots on executor
Christian Bremer commented on JENKINS-26020 Will not start builds even though there are available slots on executor Other than that I see no errors in the log that occurs when it fails to schedule on a node although I might have missed it since our logs are flooded. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
