[JIRA] [testng] (JENKINS-19217) Change class names to not contain package names on result pages (increases readability)
Nalin Makar resolved JENKINS-19217 as Fixed Change class names to not contain package names on result pages (increases readability) Fixed in v1.7 Change By: Nalin Makar (29/Jun/14 7:00 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23611) Role strategy: no way to provide users with the ability to add nodes without being an admin
Oleg Nenashev commented on JENKINS-23611 Role strategy: no way to provide users with the ability to add nodes without being an admin This case works correctly on 1.509.4 and 1.532.2 You just need to add Slave.Create permission to a global non-admin role. If it does not work, please provide more info This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-23612) Failed to run AVD creation command
Di Chen created JENKINS-23612 Failed to run AVD creation command Issue Type: Bug Affects Versions: current Assignee: Di Chen Components: android-emulator Created: 29/Jun/14 8:09 AM Description: Jenkins builded my Android_Test project and alert me following sentences: $ D:\software\adt-bundle-windows-x86_64\sdk\tools\android.bat list target [android] Using Android SDK: D:\software\adt-bundle-windows-x86_64\sdk [android] Creating Android AVD: C:\Windows\system32\config\systemprofile\.android\avd\hudson_zh-CN_240_WVGA_android-19_armeabi-v7a.avd [android] D:\software\adt-bundle-windows-x86_64\sdk\tools\android.bat create avd -f -a -c 100M -s WVGA800 -n hudson_zh-CN_240_WVGA_android-19_armeabi-v7a -t android-19 --abi armeabi-v7a [android] Could not create Android emulator: Failed to run AVD creation command But I input above command line at the Server of Jenkins. It's successful. Due Date: 29/Jun/14 12:00 AM Environment: Windows 2008 R2 x64 Jenkins 1.568 Project: Jenkins Priority: Major Reporter: Di Chen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23611) Role strategy: no way to provide users with the ability to add nodes without being an admin
Yaniv Kaul commented on JENKINS-23611 Role strategy: no way to provide users with the ability to add nodes without being an admin Please let me know what more information I can provide. All roles I have (but Anon) do have Slave.Create checked. I don't think they see the menu item of Manage Jenkins, so they can't get to the nodes sub-menu. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23611) Role strategy: no way to provide users with the ability to add nodes without being an admin
Oleg Nenashev
commented on JENKINS-23611
Role strategy: no way to provide users with the ability to add nodes without being an admin
Do they have access to ${JENKINS_URL}/computer ?
This link should be available on Jenkins page ("Build Executors" in the Queue side panel)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23611) Role strategy: no way to provide users with the ability to add nodes without being an admin
Oleg Nenashev
edited a comment on JENKINS-23611
Role strategy: no way to provide users with the ability to add nodes without being an admin
Do they have access to ${JENKINS_URL}/computer ?
This link should be available on Jenkins page ("Build Executors" in the Queue side panel)
P.S: ${JENKINS_URL}/manage is available for administrators 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-10887) Windows Installer should ask which port to use
Daniel Beck updated JENKINS-10887 Windows Installer should ask which port to use Not a bug. Change By: Daniel Beck (29/Jun/14 2:01 PM) Summary: during windows installer setup, no asking Windows Installer should ask which port to use Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5699) Terminate when HTTP port bind fails
Daniel Beck resolved JENKINS-5699 as Cannot Reproduce Terminate when HTTP port bind fails Cannot reproduce on recent Jenkins versions: They abort when the port is taken. Change By: Daniel Beck (29/Jun/14 2:00 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] [other] (JENKINS-23613) Builds (web driver jobs) hang on Jenkins in random time on random place
Oleg Nenashev moved JENKINS-23613 Builds (web driver jobs) hang on Jenkins in random time on random place Change By: Oleg Nenashev (29/Jun/14 2:08 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 98 23613 Workflow: jira JNJira Component/s: other Component/s: etc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11128) Free space on nodes should be validated against the custom workspace's disk, if defined in job
Daniel Beck resolved JENKINS-11128 as Not A Defect Free space on nodes should be validated against the custom workspace's disk, if defined in job Not a bug: Jenkins checks the Jenkins install directory's available disk space, as that's where Jenkins will write all data by default. This includes tool auto-installations and all job workspaces that don't have custom workspaces defined. So Jenkins absolutely wants to make sure enough free space is available for this. Custom workspaces are your responsibility, so they're ignored in that context. Solutions: Install Jenkins slave home to the disk with more free space so all data actually gets stored there Disable disk space monitoring, or reduce the threshold Change By: Daniel Beck (29/Jun/14 2:08 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] [other] (JENKINS-23613) Builds (web driver jobs) hang on Jenkins in random time on random place
Oleg Nenashev commented on JENKINS-23613 Builds (web driver jobs) hang on Jenkins in random time on random place The request has been submitted to the improper project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-11265) rssFailed feed should not report "not built" modules in a Maven 3 multi-module project with incremental build enabled.
Daniel Beck commented on JENKINS-11265 rssFailed feed should not report "not built" modules in a Maven 3 multi-module project with incremental build enabled. Is this still an issue on current versions of Jenkins? Could you provide the steps to reproduce the issue from scratch, e.g. with building an open-source project, so this can be investigated further? First idea: RunList.failureOnly() needs to also exclude NOT_BUILT if that's the build result used for these modules. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14073) Installing Jenkins as a windows service on Windows Server 2007 x64
Daniel Beck resolved JENKINS-14073 as Incomplete Installing Jenkins as a windows service on Windows Server 2007 x64 No response to question asking for updated information posted a year ago, so resolving as Incomplete. Change By: Daniel Beck (29/Jun/14 2:16 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-17948) Downstream projects section is not visibile and downstream projects are not triggered
Daniel Beck commented on JENKINS-17948 Downstream projects section is not visibile and downstream projects are not triggered Is this still an issue? Would you be willing to run a few diagnostic scripts to help investigate this issue? Please also provide updated information on Jenkins version and plugin versions. Note that to prevent unnecessary work on issues that have been fixed since, we generally only care about issues in current Jenkins versions, which is 1.554.x and 1.56x at the moment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17948) Downstream projects section is not visibile and downstream projects are not triggered
Daniel Beck updated JENKINS-17948 Downstream projects section is not visibile and downstream projects are not triggered Change By: Daniel Beck (29/Jun/14 2:20 PM) Component/s: maven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23357) Role-Based Strategy plugin cannot add project or node roles
Oleg Nenashev commented on JENKINS-23357 Role-Based Strategy plugin cannot add project or node roles Please provide the IE version and a modes you use (document and compatibility modes). The issue is confirmed for the IE10 Compatibility View This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-4390) Hudson hangs on archiving
Daniel Beck commented on JENKINS-4390 Hudson hangs on archiving Does this issue still occur on recent Jenkins versions (say, 1.554.x or 1.56x)? If so, please provide information about your setup, like Java + OS vendor, Java + OS version, Jenkins version, how you're launching your slaves, etc. Does the workaround mentioned by Cristina Aiftimiei (updating the Java used to run Jenkins) also work for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-21653) Gradle build command not working as Gradle version is unavailable for selection in Configure
Navin I commented on JENKINS-21653 Gradle build command not working as Gradle version is unavailable for selection in Configure @John: Couldn't find any "Gradle" option under "Manage Jenkins". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-4179) PDF report of test results
Oleg Nenashev updated JENKINS-4179 PDF report of test results Change By: Oleg Nenashev (29/Jun/14 3:52 PM) Issue Type: Improvement New Feature Component/s: plugin Component/s: junit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-2427) JavaTest component should allow multiple test suites
Oleg Nenashev resolved JENKINS-2427 as Fixed JavaTest component should allow multiple test suites XUnit Plugin provides the requested feature Change By: Oleg Nenashev (29/Jun/14 3:55 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-11696) jenkins commandline version list-changes command PLAIN CSV format doesnot produce desired result
Daniel Beck resolved JENKINS-11696 as Incomplete jenkins commandline version list-changes command PLAIN CSV format doesnot produce desired result User did not respond to a comment asking for clarification, so resolving as incomplete. Note that all output formats contain different information, depending on the flexibility of the format. For example, CSV isn't suitable for including a list of files for every change. Change By: Daniel Beck (29/Jun/14 3:56 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] [redmine] (JENKINS-23483) java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport()
Łukasz Jąder assigned JENKINS-23483 to Łukasz Jąder java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport() Change By: Łukasz Jąder (29/Jun/14 4:02 PM) Assignee: gaooh Łukasz Jąder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-6741) DirectoryScanner shouldn't die when it sees unreadable directory
Daniel Beck resolved JENKINS-6741 as Not A Defect DirectoryScanner shouldn't die when it sees unreadable directory It seems to be a reasonable assumption that Jenkins has complete read+write access to a job's workspace. In most configurations, this should be a fatal error, as warnings would easily be missed unless reading the log, leading to difficult to investigate issues, incomplete artifacts, reports, etc. Due to features like Wipe Out Workspace, the Workspace Cleanup Thread, and plugins such as SCM easily able to request a clean workspace, linking the entire file system from that appears to be a dangerous approach in general that maybe needs to be reconsidered. Change By: Daniel Beck (29/Jun/14 4:02 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] [redmine] (JENKINS-18110) even the redmine project exists the pluging marks all builds as failure
Łukasz Jąder assigned JENKINS-18110 to Łukasz Jąder even the redmine project exists the pluging marks all builds as failure Change By: Łukasz Jąder (29/Jun/14 4:02 PM) Assignee: gaooh Łukasz Jąder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20086) Allow disabling use of default exclude patterns (.git, .svn, etc.) for archiving
Daniel Beck updated JENKINS-20086 Allow disabling use of default exclude patterns (.git, .svn, etc.) for archiving Change By: Daniel Beck (29/Jun/14 4:06 PM) Summary: Allow disabling use of default exclude patterns (.git, .svn, etc.) for archiving This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14355) Allow disabling use of default exclude patterns (.git, .svn, etc.) for fingerprinting
Daniel Beck updated JENKINS-14355 Allow disabling use of default exclude patterns (.git, .svn, etc.) for fingerprinting Change By: Daniel Beck (29/Jun/14 4:06 PM) Summary: create-fingerprint-plugin cant find .dotfiles Allow disabling use of default exclude patterns ( e . g git, . : svn, etc . git/FETCH_HEAD ) for fingerprinting Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16338) Jenkins fails to keep connection alive on Windows 8
Daniel Beck updated JENKINS-16338 Jenkins fails to keep connection alive on Windows 8 Is this still an issue in recent Jenkins versions (say, 1.554.x or 1.56x)? If so, please provide updated thread dumps, and, if possible, provide a support bundle (from the Support Core plugin). What are the circumstances of this issue occurring? Please check on the slave computer whether the java process requires a lot of memory, increasing the limit (e.g. -Xmx1g argument to java) might help to have this issue occur less. Change By: Daniel Beck (29/Jun/14 4:10 PM) Labels: remoting Assignee: Kohsuke Kawaguchi Component/s: slave-setup Component/s: slave-status This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14586) JellyTagException : No page found 'config.jelly' for class hudson.scm.SubversionSCM$DescriptorImpl
Daniel Beck resolved JENKINS-14586 as Cannot Reproduce JellyTagException : No page found 'config.jelly' for class hudson.scm.SubversionSCM$DescriptorImpl Looks like a transient error after a plugin update or change. Should easily be resolvable by ensuring the .hpi/.jpi of the plugin isn't broken and deleting the extracted files cache to force a new extraction when restarting Jenkins. Resolving as Cannot Reproduce due to age and nature of the issue. Change By: Daniel Beck (29/Jun/14 4:13 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-9410) Remote API for creating a new Job is not working - using createItem
Daniel Beck resolved JENKINS-9410 as Not A Defect Remote API for creating a new Job is not working - using createItem User error, and the docs have been extended to mention the Content-Type requirement a while ago. Create Job To create a new job, post config.xml to this URL with query parameter name=JOBNAME. You need to send a Content-Type: application/xml header. You'll get 200 status code if the creation is successful, or 4xx/5xx code if it fails. Change By: Daniel Beck (29/Jun/14 4:14 PM) Status: Open Resolved Assignee: kohsuke_agent 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-7488) CLONE -java.io.IOException: Unable to delete - files in dir: []
Daniel Beck resolved JENKINS-7488 as Duplicate CLONE -java.io.IOException: Unable to delete - files in dir: [] Too little information in the original report and some of the comments to investigate further. One of the comments seems to essentially duplicate JENKINS-12610. Due to the age and nature of this issue, I'm resolving this as duplicate. If this is still an issue for you on current Jenkins versions (1.554.x or 1.56x), please file a new issue and provide as much information as you can. If you're on Windows or otherwise locking file systems, disable search indexer, antivirus, and similar processes. Change By: Daniel Beck (29/Jun/14 4:21 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-14808) IOException: Unable to delete on Windows Slaves
Daniel Beck resolved JENKINS-14808 as Duplicate IOException: Unable to delete on Windows Slaves Seems to duplicate JENKINS-15331. Change By: Daniel Beck (29/Jun/14 4:23 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-17587) Slave label expressions with multiple quoted slave names joined by logical operators are no longer recognised
Daniel Beck commented on JENKINS-17587 Slave label expressions with multiple quoted slave names joined by logical operators are no longer recognised Reproduced on Jenkins 1.567: Label: "s1(b1)" || "s2(b2)" Message: There’s no slave/cloud that matches this assignment. Did you mean ‘s1(b1)’ instead of ‘s1(b1)" || "s2(b2)’? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14275) Wrong folder permissions when downloading artifacts
Daniel Beck resolved JENKINS-14275 as Cannot Reproduce Wrong folder permissions when downloading artifacts Cannot reproduce on 1.567. When running unzip from the command line, the folders are executable afterwards. Change By: Daniel Beck (29/Jun/14 4:34 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-18497) zipped files generated from userContent have their permissions removed/flattened
Daniel Beck commented on JENKINS-18497 zipped files generated from userContent have their permissions removed/flattened Is this still an issue on recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10061) http:///pluginManager/checkUpdates does not work without GUI / javascript
Daniel Beck resolved JENKINS-10061 as Duplicate http:///pluginManager/checkUpdates does not work without GUI / _javascript_ Change By: Daniel Beck (29/Jun/14 4:41 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-10012) Normal user shoulod not be able to wipe out the workspace
Daniel Beck resolved JENKINS-10012 as Not A Defect Normal user shoulod not be able to wipe out the workspace This report only makes sense if you're not using workspaces as storage for temporary build data (e.g. store important data there, or set the custom workspace location to a critical location such as a file system root directory), in which case it's a problem with your setup. Change By: Daniel Beck (29/Jun/14 4:50 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-9863) Add Upgrade to Release Candidate on Manage Jenkins Page
Daniel Beck resolved JENKINS-9863 as Won't Fix Add Upgrade to Release Candidate on Manage Jenkins Page This issue gained no support despite it's age, so it's safe to assume it's dead. Bring it up on the mailing lists if this is still something you're interested in. Also, requires extension to update center metadata (i.e. INFRA project) to include current RC. Change By: Daniel Beck (29/Jun/14 4:53 PM) Status: Open Resolved Fix Version/s: current 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] [core] (JENKINS-16962) Linux slave on different timezone - immediate ping timeout exception
Daniel Beck commented on JENKINS-16962 Linux slave on different timezone - immediate ping timeout exception I don't think this can be resolved by disabling the node monitor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18925) broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() javascript function instead of numbers
Daniel Beck commented on JENKINS-18925 broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() _javascript_ function instead of numbers Is this issue still unresolved in recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19023) help attribute for jelly tag appears unproperly documented
Daniel Beck resolved JENKINS-19023 as Not A Defect help attribute for jelly tag appears unproperly documented It appears you did not follow the instructions in step 7 and placed the file with the related resources, rather than in webapp. (Custom icons in plugins work similarly.) Change By: Daniel Beck (29/Jun/14 5:02 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] [testlink] (JENKINS-22220) TestLink Plugin is not executing testng method and showing Not Run in jenkins excution report
Nalin Makar updated JENKINS-0 TestLink Plugin is not executing testng method and showing Not Run in jenkins excution report Change By: Nalin Makar (29/Jun/14 5:02 PM) Description: TestLink Plugin is not executing testng method and showing Not Run in jenkins execution reportFollowing are testlink, jenkins and testlink plug in versions that used for configuration.TestLink 1.9.9Jenkins ver. 1.523Jenkins TestLink Plugin - 3.10Created testlink project,testplan and custom fields, refer attachments for details.In test suite, 2 test cases are presentLogin test which uses following java class to executecom.mycompany.myproject.testscripts.ConceptTestand for this used custom field is - TestMethodjava class com.mycompany.myproject.testscripts.ConceptTest contains several testng methods refer attached source fileeg login, registration etcRegistration test used following value for custom fieldTestMethod: com.mycompany.myproject.testscripts.ConceptTest#TestLinkTest11Actual registration test script present in testng method - TestLinkTest11After executing above configuration jenkins and testlink test execution result says - Not run in result screen. refer screenshots for reference Component/s: testng This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testng] (JENKINS-23539) Initialize TestNgResult from testng result xml tag
Nalin Makar commented on JENKINS-23539 Initialize TestNgResult from testng result xml tag Peter, we don't save any data for testng plugin other than the testng-results.xml files generated in the builds. To be able to display testng results in Jenkins, we need to parse the complete 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-23302) Header background not showing up
Daniel Beck resolved JENKINS-23302 as Incomplete Header background not showing up No response to question asking for more information in two weeks, so resolving as Incomplete. As background is just a meta-property combining all background-* attributes, this seems weird. background-image and background-repeat should work without setting background-color. Change By: Daniel Beck (29/Jun/14 5:25 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-14190) Wrong autocompletion of node names with spaces
Daniel Beck updated JENKINS-14190 Wrong autocompletion of node names with spaces Change By: Daniel Beck (29/Jun/14 5:26 PM) Labels: labels This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Daniel Beck updated JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ Change By: Daniel Beck (29/Jun/14 5:29 PM) Labels: labels This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17587) Slave label expressions with multiple quoted slave names joined by logical operators are no longer recognised
Daniel Beck updated JENKINS-17587 Slave label expressions with multiple quoted slave names joined by logical operators are no longer recognised Change By: Daniel Beck (29/Jun/14 5:29 PM) Labels: labels This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14190) Wrong autocompletion of node names with spaces
Daniel Beck commented on JENKINS-14190 Wrong autocompletion of node names with spaces Reproduced on 1.567: Slave name: a b c Error: Invalid boolean _expression_: unexpected token: b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17134) plugin description source inconsistency
Daniel Beck commented on JENKINS-17134 plugin description source inconsistency As the data source for un-installed plugins is the update center, this seems to be more of an INFRA issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23250) Failed to inspect ... build.xml warnings in jenkins log
Daniel Beck commented on JENKINS-23250 Failed to inspect ... build.xml warnings in jenkins log If you can get by for a bit without fingerprints, rename that directory in JENKINS_HOME and restart Jenkins. If the cleanup thread is actually the cause of this, this should reduce the impact or make the problem disappear. Another alternative would be to get a heap dump and check what consumes all the memory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19134) Disallow Users to set a custom workspace
Daniel Beck commented on JENKINS-19134 Disallow Users to set a custom workspace Tempted to resolve this as Won't Fix given that plugins can override the config screen. Anyone opposed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21716) missing encoding header for /env-vars.html/
SCM/JIRA link daemon commented on JENKINS-21716 missing encoding header for /env-vars.html/ Code changed in jenkins User: Harald Albers Path: core/src/main/resources/hudson/model/EnvironmentContributor/EnvVarsHtml/index.groovy http://jenkins-ci.org/commit/jenkins/013d55518f56accf04f89dfc248189d0f474e6d0 Log: Merge pull request #1302 from daniel-beck/JENKINS-21716 [FIXED JENKINS-21716] Set Content-Type header for env-vars.html Compare: https://github.com/jenkinsci/jenkins/compare/0bfab57ec013...013d55518f56 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21716) missing encoding header for /env-vars.html/
SCM/JIRA link daemon commented on JENKINS-21716 missing encoding header for /env-vars.html/ Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/EnvironmentContributor/EnvVarsHtml/index.groovy http://jenkins-ci.org/commit/jenkins/8e2328df329e4abb1946c61eff240136315613cd Log: [FIXED JENKINS-21716] Set Content-Type header for env-vars.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21716) missing encoding header for /env-vars.html/
SCM/JIRA link daemon resolved JENKINS-21716 as Fixed missing encoding header for /env-vars.html/ Change By: SCM/JIRA link daemon (29/Jun/14 6:10 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21716) missing encoding header for /env-vars.html/
dogfood commented on JENKINS-21716 missing encoding header for /env-vars.html/ Integrated in jenkins_main_trunk #3492 [FIXED JENKINS-21716] Set Content-Type header for env-vars.html (Revision 8e2328df329e4abb1946c61eff240136315613cd) Result = SUCCESS daniel-beck : 8e2328df329e4abb1946c61eff240136315613cd Files : core/src/main/resources/hudson/model/EnvironmentContributor/EnvVarsHtml/index.groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23500) ACL to protect some artifacts
Oleg Nenashev updated JENKINS-23500 ACL to protect some artifacts Currently, Jenkins do not provide permission control hooks on artifact level. BTW, such extension could be useful. Change By: Oleg Nenashev (29/Jun/14 8:09 PM) Summary: acl ACL to protect some artifacts Component/s: core Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23500) ACL to protect some artifacts
Oleg Nenashev updated JENKINS-23500 ACL to protect some artifacts Change By: Oleg Nenashev (29/Jun/14 8:10 PM) Issue Type: Improvement New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22409) API Token no longer working for API calls
Oleg Nenashev updated JENKINS-22409 API Token no longer working for API calls Change By: Oleg Nenashev (29/Jun/14 8:12 PM) Component/s: github Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-3261) Hudson service restart within hudson fails
Oleg Nenashev resolved JENKINS-3261 as Cannot Reproduce Hudson service restart within hudson fails I don't see such behavior on newer versions. The referenced discussion is not available anymore Change By: Oleg Nenashev (29/Jun/14 8:18 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] [other] (JENKINS-3261) Hudson service restart within hudson fails
Oleg Nenashev closed JENKINS-3261 as Cannot Reproduce Hudson service restart within hudson fails Change By: Oleg Nenashev (29/Jun/14 8:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-14084) Throttle per axis
Oleg Nenashev updated JENKINS-14084 Throttle per axis Change By: Oleg Nenashev (29/Jun/14 8:20 PM) Component/s: matrix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21716) missing encoding header for /env-vars.html/
Daniel Beck commented on JENKINS-21716 missing encoding header for /env-vars.html/ Integrated towards 1.571. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-21716) missing encoding header for /env-vars.html/
menra selala commented on JENKINS-21716 missing encoding header for /env-vars.html/ great This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23500) ACL to protect some artifacts
Daniel Beck commented on JENKINS-23500 ACL to protect some artifacts IMO this is a horrible idea. Interaction with downstream jobs (e.g. Copy Artifact) would be quite complex (QueueItemAuthenticator?) and any change could have severe unexpected side effects. Just publish the public artifacts somewhere else and restrict access within Jenkins to trusted users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-5336) Users are automatically created when going thru HUDSON_URL/user/[anything]
Daniel Beck commented on JENKINS-5336 Users are automatically created when going thru HUDSON_URL/user/[anything] It is not an issue for me, but I can go to any publicly known Hudson application, http://deadlock.netbeans.org/hudson/, and create unlimited amount of users, which could exhaust the memory? Only admins can create users this way. It'll be 404 Not Found for everyone else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-14096) XPath is not working with Jaxen provided by Jenkins
Daniel Beck resolved JENKINS-14096 as Not A Defect XPath is not working with Jaxen provided by Jenkins PluginFirstClassloader appears to be the way to go as a comment mentions, so this isn't a bug. Regarding the slf4j issue, please consider asking for help on the jenkinsci-dev mailing list, it has a much larger audience than issue reports. Change By: Daniel Beck (29/Jun/14 8:49 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-19284) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/D:/Jenkins/war/WEB-INF/lib/jenkins-core-1.527.jar!/hudson/model/AbstractProject/main
Daniel Beck resolved JENKINS-19284 as Duplicate javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/D:/Jenkins/war/WEB-INF/lib/jenkins-core-1.527.jar!/hudson/model/AbstractProject/main.jelly:76:66: java.lang.NullPointerException Duplicates JENKINS-20932. Also, .docx? For a dozen lines of text? WTF... Change By: Daniel Beck (29/Jun/14 8:52 PM) Status: Open Resolved Fix Version/s: current 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] (JENKINS-23614) URL isn't escaped properly (leads to an 404 error).
Matteo Kloiber created JENKINS-23614 URL isn't escaped properly (leads to an 404 error). Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2014-06-29 at 10.50.39 PM.png Components: matrix Created: 29/Jun/14 8:52 PM Description: When I use special characters in a multi-configuration build, I always end up getting a 404 error. I use user-defined axis with following values: https://www.djangoproject.com/download/1.7b3/tarball/ Django>=1.5,<1.6 Django>=1.6,<1.7 Django # (This one works!) the name is: django. I can build the project with these configurations but when I go to the Project and select the configuration, I get a 404 error (see attachment, the second axis (Python), doesn't make a different). I think the commas break the URL but I'm not sure. I can't change the name of the axis because the define the exaction version (for instance, `=>1.5,1.6` means that every version that is new that 1.5 but older than 1.6 is allowed (e.g 1.5, 1.5.1, ...)). Environment: Mac OS X Mavericks, Jenkins ver. 1.569 Project: Jenkins Labels: axis Priority: Major Reporter: Matteo Kloiber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-19939) Discard Old Builds I/O Performance Issue
Daniel Beck updated JENKINS-19939 Discard Old Builds I/O Performance Issue Looks more like an improvement. Re 1: Builds are considered finished once their final result has been determined. Build discarding happens afterwards. I don't think this should or will be changed. Change By: Daniel Beck (29/Jun/14 9:00 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5336) Users are automatically created when going thru HUDSON_URL/user/[anything]
Kanstantsin Shautsou commented on JENKINS-5336 Users are automatically created when going thru HUDSON_URL/user/[anything] Well, this is not a good behavior for UI. When i tested it still allowed create users. Maybe something changed. If such action ends to 404 for non admin users now, then bug priority maybe decreased. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-12296) Programs with user prompts fill jenkins log until disk runs out of space
Daniel Beck resolved JENKINS-12296 as Not A Defect Programs with user prompts fill jenkins log until disk runs out of space Not a Jenkins bug, but a bug in the build script or the tools being called that should be able to determine that they're not writing their output to an interactive shell. From Jenkins, what happens should be indistinguishable from a well-behaving build. Aborting running builds before space runs out seems pointless, because on a Jenkins server, builds getting aborting because space has run out appears to be the most severe result. Plugins like Logfilesizechecker and build-timeout plugin do the job wrt automatically determinable misbehaving builds. Change By: Daniel Beck (29/Jun/14 9:04 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-16497) Builds with surefire on Windows OS prevent deletion of files with output from tests.
Daniel Beck resolved JENKINS-16497 as Cannot Reproduce Builds with surefire on Windows OS prevent deletion of files with output from tests. Was fixed in 1.522: https://github.com/jenkinsci/jenkins/commit/047233eb483de1bea5f1aba93156764373dc1cc8 Change By: Daniel Beck (29/Jun/14 9:10 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-23500) ACL to protect some artifacts
Oleg Nenashev commented on JENKINS-23500 ACL to protect some artifacts The case is similar to build-specific permissions... It just proposes an additional security atomization within an item. I don't think the idea is horrible. But it would require a very significant update in the quite legacy Artifacts mechanism. I think it could be done if somebody decouples it to a separate plugin (the mission seems to be impossible) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-16497) Builds with surefire on Windows OS prevent deletion of files with output from tests.
Daniel Beck edited a comment on JENKINS-16497 Builds with surefire on Windows OS prevent deletion of files with output from tests. Was fixed in 1.522: https://github.com/jenkinsci/jenkins/commit/047233eb483de1bea5f1aba93156764373dc1cc8 and https://github.com/jenkinsci/jenkins/commit/14d980c4377dc703df8db76f192de19246a0266e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-5620) Hudson can't detect UTF-16 encoding for HTML files in workspace.
Daniel Beck commented on JENKINS-5620 Hudson can't detect UTF-16 encoding for HTML files in workspace. Is this still an issue on recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-8045) Weird log display behavior for too fast workerThread in TaskAction
Daniel Beck commented on JENKINS-8045 Weird log display behavior for too fast workerThread in TaskAction Does this issue still occur on recent Jenkins versions? If so, could you please provide detailed and complete steps to reproduce the problem on a default Jenkins installation? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-8662) Mac JNLP connection crashes to Windows Master
Daniel Beck commented on JENKINS-8662 Mac JNLP connection crashes to Windows Master Does the issue still occur on recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-21327) Offering access to users with RUN_SCRIPTS is redundant
Daniel Beck commented on JENKINS-21327 Offering access to users with RUN_SCRIPTS is redundant Dominik Bartholdi: If you'r right and RUN_SCRIPTS has more power then ADMINISTRATOR, then I must say that RUN_SCRIPT is not well documented and a very very misleading name. It's as useless on almost all instances as the UploadPlugins and ConfigureUpdateCenter permissions (i.e. 3 out of 5) that only exist to enable somewhat secure Cloudbees-hosted instances. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-20940) Project source of a multi-config project inside a folder not working
SCM/JIRA link daemon commented on JENKINS-20940 Project source of a multi-config project inside a folder not working Code changed in jenkins User: ikedam Path: pom.xml src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/db1e878df26acea9e627716fd538a8fcaea3ecbd Log: JENKINS-20940 Added a test to reproduce JENKINS-20940. Fails to copy from a matrix project in the same folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-20940) Project source of a multi-config project inside a folder not working
SCM/JIRA link daemon commented on JENKINS-20940 Project source of a multi-config project inside a folder not working Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java http://jenkins-ci.org/commit/copyartifact-plugin/06fa45810ca4aaddc93fa0becba0e08160b7a695 Log: [FIXED JENKINS-20940] Use rootProject as copying sources. This allows correct project name resolving from matrix projects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-20940) Project source of a multi-config project inside a folder not working
SCM/JIRA link daemon commented on JENKINS-20940 Project source of a multi-config project inside a folder not working Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/2b0845a38433e36672b6dcee9c7ccad44ba6d2b3 Log: JENKINS-20940 Fix permissionTest not to run the constructor directly, but to use UI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout] (JENKINS-23012) Build-timeout plugin causes builds to slow
ikedam resolved JENKINS-23012 as Fixed Build-timeout plugin causes builds to slow Thanks for the fix report. Please reopen this issue for the case the problem remains. Change By: ikedam (29/Jun/14 11:30 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-20940) Project source of a multi-config project inside a folder not working
SCM/JIRA link daemon resolved JENKINS-20940 as Fixed Project source of a multi-config project inside a folder not working Change By: SCM/JIRA link daemon (29/Jun/14 11:31 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] [copyartifact] (JENKINS-20940) Project source of a multi-config project inside a folder not working
SCM/JIRA link daemon commented on JENKINS-20940 Project source of a multi-config project inside a folder not working Code changed in jenkins User: ikedam Path: pom.xml src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/test/java/hudson/plugins/copyartifact/CopyArtifactTest.java http://jenkins-ci.org/commit/copyartifact-plugin/b33ceb5d1cd5f59ea4e4b7248acdf74aec9be9a2 Log: Merge pull request #40 from ikedam/feature/JENKINS-20940_relativeFromMatrix JENKINS-20940 relative project names from matrix projects. Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/1cc07c249d2b...b33ceb5d1cd5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
adam bishop commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users This is so important in organizations that aren't agile. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-19775) Github plugin - Set build status on github commit - No result
n0mer commented on JENKINS-19775 Github plugin - Set build status on github commit - No result hi folks, just faced the same problem. my advice is to look at https://github.com///branches - this contains green tick if your build is successful for that specific branch. hope this helps This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-23212) Option "Delay between launch and boot complete" doesn't work
Jason Swager commented on JENKINS-23212 Option "Delay between launch and boot complete" doesn't work Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-23212) Option "Delay between launch and boot complete" doesn't work
Jason Swager resolved JENKINS-23212 as Not A Defect Option "Delay between launch and boot complete" doesn't work Expected behavior Change By: Jason Swager (30/Jun/14 3:27 AM) Status: Open Resolved Assignee: Jason Swager 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] [sbt] (JENKINS-23542) Add license info to sbt plugin
uzilan resolved JENKINS-23542 as Fixed Add license info to sbt plugin Change By: uzilan (30/Jun/14 5:35 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23615) Unexpected behaviour when using different capitalization for variable name on windows
Andreas Kleber created JENKINS-23615 Unexpected behaviour when using different capitalization for variable name on windows Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 30/Jun/14 5:57 AM Description: On windows environment variable names an not case sensitive. If you use different capitalization in variable names with the envinject plugin the results are unexpected. To reproduce create a envinject build step or build environment setting with the following content: Foo=test FOO=bar;$FOO If I run the job on a windows slave I would expect the result to be: echo %FOO% bar;test But instead I get: echo %FOO% bar;bar;bar;bar;bar;bar;bar;bar;.bar;bar;bar;$FOO On the "Environment Variables" page on the job result page there are two entries with the different capitalization but also not filled correctly. I would expect only one. I found out about this because on a freshly installed windows machine the Path environment variable is "Path" but I used "PATH" in the envinject plugin which gave me quite some headache. Project: Jenkins Priority: Critical Reporter: Andreas Kleber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-18925) broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() javascript function instead of numbers
Rene Hess commented on JENKINS-18925 broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() _javascript_ function instead of numbers Looks ok in my installation 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-23616) Jenkins RPM should have a dependency with x11-devel (required to properly render workspace)
Yaniv Kaul created JENKINS-23616 Jenkins RPM should have a dependency with x11-devel (required to properly render workspace) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 30/Jun/14 6:33 AM Description: It appears as if without x11-devel libraries installed, a NPE occurs when trying to render the workspace. Therefore, it'll ease people's life if x11-devel will be a dependency of the Jenkins RPM. Environment: Linux, RPM based Project: Jenkins Labels: rpm Priority: Major Reporter: Yaniv Kaul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-23616) Jenkins RPM should have a dependency with x11-devel (required to properly render workspace)
Yaniv Kaul updated JENKINS-23616 Jenkins RPM should have a dependency with x11-devel (required to properly render workspace) Change By: Yaniv Kaul (30/Jun/14 6:34 AM) Issue Type: Bug Improvement 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] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
enterit
created JENKINS-23617
Cannot use spaces in groovy script parameters
Issue Type:
Bug
Affects Versions:
current
Assignee:
vjuranek
Components:
groovy
Created:
30/Jun/14 6:43 AM
Description:
The issue is caused by oversimplified parameters parsing implementation in this class: https://github.com/jenkinsci/groovy-plugin/blob/master/src/main/java/hudson/plugins/groovy/Groovy.java
//Add groovy parameters
if(parameters != null) {
StringTokenizer tokens = new StringTokenizer(parameters);
while(tokens.hasMoreTokens()) {
list.add(Util.replaceMacro(tokens.nextToken(),vr));
}
}
I would suggest to switch to org.apache.commons.exec.CommandLine.parse(..) method from Apache commons-exec.
Not ideal, I know, but probably the best possible option if parsing command-line is inevitable.
Is anyone interested in the patch? It would be very straightforward.
Project:
Jenkins
Priority:
Major
Reporter:
enterit
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-23193) UI blocked frequently
Saulo Alvarado Mateos commented on JENKINS-23193 UI blocked frequently Yes, there are. But not so good news as we will like. After upgrade to the last LTS (1.554.2), problems starts again. With more virulence if it is possible. The same day, our Jenkins stops working suddenly three times. And suddenly works fine for four days long. Then stops again. Currently we are studying to start to work with other application server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
