[JIRA] [cloudbees-plugin-gateway] (JENKINS-17627) NPE while loading Cloudbees folders at Jenkins startup
Christian Apel commented on JENKINS-17627 NPE while loading Cloudbees folders at Jenkins startup I have downloaded the plugin manually to update Jenkins last Thursday, but after your change there were a few more plugin updates listed (free plugins license, license manager and registration plugin). Thank you for the update and the link to the release notes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-plugin-gateway] (JENKINS-17627) NPE while loading Cloudbees folders at Jenkins startup
Christian Apel closed JENKINS-17627 as Fixed NPE while loading Cloudbees folders at Jenkins startup Change By: Christian Apel (29/Apr/13 6:37 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/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Christian Apel closed JENKINS-16426 as Fixed Backup fails while copying a file from the jobs folder Change By: Christian Apel (29/Apr/13 6:38 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16749) Exception in EmailTrigger
Christian Apel closed JENKINS-16749 as Fixed Exception in EmailTrigger Change By: Christian Apel (29/Apr/13 6:39 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/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi commented on JENKINS-17566 Severe polling error when using script trigger The plugin was updates to 0.24 and Jenkins to 1.513. The message changed a little bit, but no additional information: Polling started on Apr 29, 2013 7:12:13 AM Polling for the job Lucene-Solr-trunk-Windows Looking nodes where the poll can be run. Looking for a node to the restricted label master. Can't find any eligible nodes. Trying to poll on master node. Polling on master. The expected script execution code is 1 [ERROR] - Polling error... In the general Jenkins main log file is no message at all about an error, just in the "Script Trigger Log" of the job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi edited a comment on JENKINS-17566 Severe polling error when using script trigger The plugin was updates to 0.24 and Jenkins to 1.513. The message changed a little bit, but no additional information: [ScriptTrigger] - Poll with a shell or batch script Polling started on Apr 29, 2013 7:12:13 AM Polling for the job Lucene-Solr-trunk-Windows Looking nodes where the poll can be run. Looking for a node to the restricted label master. Can't find any eligible nodes. Trying to poll on master node. Polling on master. The expected script execution code is 1 [ERROR] - Polling error... In the general Jenkins main log file is no message at all about an error, just in the "Script Trigger Log" of the job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
Henrik Skupin commented on JENKINS-6890 clone-workspace-scm doesnt work when source job is a matrix job. I have asked on the pull request. Lets see if we can get some progress. It would be great to see this issue fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi
commented on JENKINS-17566
Severe polling error when using script trigger
One detail about this configuration:
At the time of the polling, the slave node is not yet running (it is a VirtualBox VM started only when jobs are running), so when scripttrigger triggers the build, the job should be queued and the slave node starts up because of this triggering. Maybe this is the reason for the "Can't find eligible nodes" error. But scripttrigger is configured to run on node with label "master", so the child should not be involved.
The shell script behind script trigger is just a check ("pgrep ..."), if other VirtualBox VMs are running at the same time, so scripttrigger will not trigger the job, if another VM is running concurrently (because too many VMs cannot be handled by the server it is running on).
The whole setup works sometimes, but in most cases you have to trigger the job manually.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-15703) Cobertura ClassCastException
Ignas Mikalajunas commented on JENKINS-15703 Cobertura ClassCastException Yeah, I though it was not working for a couple of days, but after Jenkins restart it started to. So I think the fix is OK This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-15703) Cobertura ClassCastException
Ignas Mikalajunas edited a comment on JENKINS-15703 Cobertura ClassCastException Yeah, I though it was not working for a couple of days, but after Jenkins restart it started to. So I think the fix is OK 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/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi commented on JENKINS-17566 Severe polling error when using script trigger FYI: I changed the polling to use a groovy "system script", its seems to work better. By checking "system script" it always runs on master. My checks can also be done with Grovvy (it just needs to look if other virtual machine slaves are running). I will report back if this works. Otherwise: There should be somehow a setting for shell scripts to be run always on master (like system script). I think the NULL pointer exception may be caused by the fact that the node is not running when script trigger wants to run the shell script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Peter Lamberg commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. java version "1.7.0_05" Java(TM) SE Runtime Environment (build 1.7.0_05-b06) Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) Linux jenkins 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Jenkins ver. 1.512 Publish Over SSH 1.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Peter Lamberg edited a comment on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. java version "1.7.0_05" Java(TM) SE Runtime Environment (build 1.7.0_05-b06) Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) Ubuntu 11.10 Linux jenkins 3.0.0-12-server #20-Ubuntu SMP Fri Oct 7 16:36:30 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Jenkins ver. 1.512 Publish Over SSH 1.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-15199) Slaves turns to Dead state after connecting to remote machine
David Gang commented on JENKINS-15199 Slaves turns to Dead state after connecting to remote machine I have the same problem with jenkins 1.513 and slave plugin 2.17 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-12001) Print console output for slave builds in matrix build
Barthélémy von Haller commented on JENKINS-12001 Print console output for slave builds in matrix build You have to navigate to the node where the test was run. There you can select the output to see. I agree with you it is misleading and impractical. A simple change would be to add the links to the "sub-jobs" output from the matrix job output. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17680) Upgrade to new Copy Artifacts version erases all job names to copy from
Max Wahler commented on JENKINS-17680 Upgrade to new Copy Artifacts version erases all job names to copy from I've also seen this issue. In 1.26, the tag name changed from projectName to project. I edited all our config.xml files manually and it does the trick. Bad news is, that saving the configuration in Jenkins throws an exception. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17692) Active Directory Plugin - Fails to retreive users with swedish characters in full name
SCM/JIRA link daemon commented on JENKINS-17692 Active Directory Plugin - Fails to retreive users with swedish characters in full name Code changed in jenkins User: Marc Schoechlin Path: src/main/java/hudson/plugins/active_directory/ActiveDirectoryUnixAuthenticationProvider.java http://jenkins-ci.org/commit/active-directory-plugin/77ab72e11eac474f09a8f484f2ebc7589a6350b3 Log: Reverted 45987d2e/tbarbieri Login in with german umlauts in the distinguished name ist not possible anyore. We tested sucessfully the revert with our setup. See also: JENKINS-17692 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17692) Active Directory Plugin - Fails to retreive users with swedish characters in full name
Marc Schoechlin commented on JENKINS-17692 Active Directory Plugin - Fails to retreive users with swedish characters in full name It seems that commit 45987d2e/tbarbieri breaks handling with german umlauts in the destinguished name(dn). I reverted the the change by 77ab72e11eac474f09a8f484f2ebc7589a6350b3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-15983) Possibility to define a custom SCM tag in project config
Lucien Weller commented on JENKINS-15983 Possibility to define a custom SCM tag in project config Rebased to 0.11.0-SNAPSHOT. WOuld be nice if it can be pulled before release of 0.11.00. Actually Bild Hive marks the build as failing, but in my opinion it is more a Build Hive configuration problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-17767) Unable to get warnings from all parsers via API
Ulli Hafner updated JENKINS-17767 Unable to get warnings from all parsers via API Change By: Ulli Hafner (29/Apr/13 10:22 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/groups/opt_out.
[JIRA] [cobertura] (JENKINS-15703) Cobertura ClassCastException
sogabe resolved JENKINS-15703 as Fixed Cobertura ClassCastException fixed in 1.9. Change By: sogabe (29/Apr/13 10:51 AM) Status: Open Resolved Assignee: stephenconnolly sogabe Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17715) Display Name is not shown
Vincent Latombe commented on JENKINS-17715 Display Name is not shown Fix submitted in https://github.com/jenkinsci/jenkins/pull/764 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17771) Allow replacement of username with build params
Johannes Haseitl created JENKINS-17771 Allow replacement of username with build params Issue Type: Bug Affects Versions: current Assignee: bap Components: publish-over-ssh Created: 29/Apr/13 11:29 AM Description: In the current version only transfer parameters seem to be able to replaced by build parameters. But in some cases it would be really usefuly to let credentials be replaced as well, especially the username. Project: Jenkins Priority: Major Reporter: Johannes Haseitl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17771) Allow replacement of username with build params
Johannes Haseitl updated JENKINS-17771 Allow replacement of username with build params Change By: Johannes Haseitl (29/Apr/13 11:29 AM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17772) Sort by columns broken in IE8 : Jenkins core = 1.513
Ben Golding created JENKINS-17772 Sort by columns broken in IE8 : Jenkins core = 1.513 Issue Type: Bug Assignee: Unassigned Attachments: js_error.txt Components: core Created: 29/Apr/13 11:40 AM Description: Sort by clicking on the column name feature: Broken in Internet Explorer 8.0.7601.17514 Works in Google Chrome 26.0.1410.64 m Error log from IE8 attached Environment: Jenkins core 1.513 All plugins DISABLED except Cloudbees Build Flow Master: Windows 7 x64 / Java 1.7.0-b147 Project: Jenkins Priority: Major Reporter: Ben Golding This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urltrigger] (JENKINS-17468) NullPointerException in URLTrigger.getFTPResponse during startup
Artur Szostak closed JENKINS-17468 as Fixed NullPointerException in URLTrigger.getFTPResponse during startup Now works with fix applied and explicit setting of user to anonymous. Change By: Artur Szostak (29/Apr/13 1:14 PM) Status: Reopened Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scripttrigger] (JENKINS-17566) Severe polling error when using script trigger
thetaphi commented on JENKINS-17566 Severe polling error when using script trigger The problem also occurs with Groovy triggers: [ScriptTrigger] - Poll with a Groovy script Polling started on Apr 29, 2013 1:08:13 PM Polling for the job Lucene-Solr-trunk-Windows Looking nodes where the poll can be run. Looking for a candidate node to run the poll. Trying to find an eligible node with the assigned project label windows. Can't find any eligible nodes. Trying to poll on master node. Polling on master. [ERROR] - Polling error... So it does not matter if its a shell script or a groovy script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jacoco] (JENKINS-17773) Slow rendering of the main view when many jobs
Patrick Roth created JENKINS-17773 Slow rendering of the main view when many jobs Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 29/Apr/13 1:41 PM Description: When many jobs are managed in Jenkins (we have typically about 150 jobs), then rendering the main view takes a lot of time (usually 20-40 sec.) when the jacoco plugin is activated. Deactivating the plugin leads to a rendering time of 3-4 sec. Removing the coverage column from the main view does not change much, 20-30 sec are still required to render the view. Environment: Linux, Jenkins 1.505, Jacoco plugin 1.0.11 and 1.0.12 Project: Jenkins Priority: Major Reporter: Patrick Roth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-6188) When a build is aborted, Hudson does not kill all the descendant processes recursively to avoid run-away processes on the Slave Build machines.
peter_schuetze commented on JENKINS-6188 When a build is aborted, Hudson does not kill all the descendant processes recursively to avoid run-away processes on the Slave Build machines. I have the same issue with following configuration Jenkins 1.461 on Windows Server 2008 Enterprise Edition using build in winstone SSH slave plugin 0.21 Slave running on AIX IBM Java 1.6 Process started wsadmin.sh (scripting environment from Websphere Application Server 8.0) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-3002) TFS Support to get labels
sheryl pinto commented on JENKINS-3002 TFS Support to get labels Is it possible to get the code for this update? We would like to use the 'get label' feature in TFS. You will find my email id in my user profile. 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/groups/opt_out.
[JIRA] [core] (JENKINS-17774) Testing plugin in Windows fails with requested operation can't be performed on file with user-mapped section open
ikedam created JENKINS-17774 Testing plugin in Windows fails with requested operation cant be performed on file with user-mapped section open Issue Type: Bug Assignee: Unassigned Attachments: TEST-jp.ikedam.jenkins.plugins.extensible_choice_parameter.TextareaChoiceListProviderJenkinsTest.xml Components: core Created: 29/Apr/13 2:32 PM Description: Running tests of extensible-choice-parameter plugin in Windows often fails. This failure is caused by 500 error in Jenkins (or Jetty). 500 error is caused by java.io.FileNotFoundException with an error message "requested operation can't be performed on file with user-mapped section open". (I attached a sunfire-report file generated when this problem happened, but the error message is output in Japanese.) This probably happens only in Windows (maybe Windows Vista or later) FileNotFoundException happens when copying(overwriting) jenkins-for-test to jetty's webapps directory. This seems happen only after running hpi:run. It probably depends on Jetty's working directory. Before running hpi:run, Jetty's working directory is %TEMP%\Jetty_0_0_0_0_0_jenkins.for.test__.bj8wp3. After running hpi:run, Jetty seems run in (project directory)\work\Jetty_0_0_0_0_0_jenkins.for.test__.bj8wp3 . I have no idea why it affects. I can reproduce this in https://github.com/ikedam/extensible-choice-parameter, tag reproduce_23_user-mapped_section. And I have fixed it in branch feature/23_JettyOnWindows, by setting useFileMappedBuffer to false in Jetty webapp context (SEE http://docs.codehaus.org/display/JETTY/Files+locked+on+Windows). I think this is related to JENKINS-12647 (I have not succeeded reproducing problems reported in this issue). As long as I tested, the problem in extensible-choice-parameter is fixed in a way of followings: setting useFileMappedBuffer to false, setting setCopyWebDir to true setting useFileMappedBuffer to false, setting setCopyWebDir to false setting setCopyWebDir to false (disabling JENKINS-12647) Environment: Windows8 (64bit), JDK 1.7.0_17, Jenkins 1.466 Project: Jenkins Priority: Minor Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents
Jesse Glick commented on JENKINS-17775 IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents The full exception, in case that build log becomes inaccessible: org.apache.maven.InternalErrorException: Internal error: java.lang.IllegalStateException: Failed to build parent project for org.jenkins-ci.plugins:ant:hpi:1.3-SNAPSHOT at org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:104) at hudson.maven.Maven3Builder.call(Maven3Builder.java:70) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.IllegalStateException: Failed to build parent project for org.jenkins-ci.plugins:ant:hpi:1.3-SNAPSHOT at org.apache.maven.project.MavenProject.getParent(MavenProject.java:378) at hudson.maven.reporters.MavenFingerprinter.recordParents(MavenFingerprinter.java:141) at hudson.maven.reporters.MavenFingerprinter.postBuild(MavenFingerprinter.java:110) at hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectSucceeded(Maven3Builder.java:349) at hudson.maven.Maven3Builder$MavenExecutionListener.projectSucceeded(Maven3Builder.java:323) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:74) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:91) ... 24 more Caused by: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [ERROR] Unresolveable build extension: Plugin org.jenkins-ci.tools:maven-hpi-plugin:1.74 or one of its dependencies could not be resolved: Could not find artifact org.jenkins-ci.tools:maven-hpi-plugin:jar:1.74 in central (http://repo.cloudbees.com/content/repositories/central) @ at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:176) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:309) at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:267) at org.apache.maven.project.MavenProject.getParent(MavenProject.java:374) ... 31 more Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.jenkins-ci.plugins:plugin:1.456 [ERROR] Unresolveable build extension: Plugin org.jenkins-ci.tools:maven-hpi-plugin:1.74 or one of its dependencies could not be resolved: Could not find artifact org.jenkins-ci.tools:maven-hpi-plugin:jar:1.74 in central (http://repo.cloudbees.com/content/repositories/central) @ at
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-17776) Add option to save entire results folder, not just report
Jonathan Price created JENKINS-17776 Add option to save entire results folder, not just report Issue Type: Improvement Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 29/Apr/13 2:59 PM Description: In the current version of the plugin (1.0.2), there doesn't appear to be a way to archive the entire results folder for a test. We write some logging, screenshots and other files to the results folder that we perform some post processing on, in order to get the results in the form required by our releasing process. It would be really useful if the entire results folder for each test could be saved in the build artefacts. Project: Jenkins Priority: Major Reporter: Jonathan Price This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents
stephenconnolly commented on JENKINS-17775 IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents Actually there are no custom settings.xml required at all to trigger this issue. For example if you build the Jenkins ant-plugin using a Maven Project type on a clean system with no settings.xml defined at all, this issue can occur as the repositories defined within the project are not consulted. Most people have probably been avoiding this error by defining a settings.xml that adds the repositories to the effective list up front This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-17777) Build Failure on Maven Clean
Jeff Humphry created JENKINS-1 Build Failure on Maven Clean Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: AdminPriv.jpg, ConsoleText.txt, ConsoleText_M2.txt Components: maven2 Created: 29/Apr/13 3:04 PM Description: Running Maven build project pulled from GitHub. It's failing on the third project trying to clean. Can't delete some files. Attached is the console output log ConsoleText.txt When I build using Maven at the command line, I get the same result, with some additional information; some of the folders seem to be created by Jenkins with higher security: Usingmvn clean install -e [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on project com.sap. core: Failed to clean project: Failed to delete D:\Jenkins\jobs\CQ_Development_Branch_jtest\workspace\bundles\com.sap.co re\target\generated-sources\annotations - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-clean-plug in:2.5:clean (default-clean) on project com.sap.core: Failed to clean project: Failed to delete D:\Jenkins\jobs\CQ_Devel opment_Branch_jtest\workspace\bundles\com.sap.core\target\generated-sources\annotations at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) ... Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to clean project: Failed to delete D:\Jenkins\jobs\CQ_ Development_Branch_jtest\workspace\bundles\com.sap.core\target\generated-sources\annotations at org.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:215) ... Caused by: java.io.IOException: Failed to delete D:\Jenkins\jobs\CQ_Development_Branch_jtest\workspace\bundles\com.sap.c ore\target\generated-sources\annotations at org.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:249) ... I attached the full console output ConsoleText_M2.txt If I try to go and manually delete the files, I get a prompt that I need administrator privileges to delete: AdminPriv.jpg Tried the following: Run the service under account that is administrator on the machine Set compatibility mode on jenkins.exe to run with administrative privileges Set the "Wipe out workspace before build" option Add mvn clean as a pre-step Disable all virus-scanning on the server All give same result. A couple other oddities: Adding the -e switch to the goals in the Jenkins configuration doesn't seem to work. The Jenkins output doesn't have any information about the file delete IO error. Environment: Windows 2008 R2 Service Pack 1 64-bit Processor: Intel Xeon CPU E5405 @ 2.00GHz Installed memory (RAM): 1.33 GB Jenkins 1.512 running as widows service. Running as domain account which is administrator on PC Java SE JDK 6 Update 43 64-bit Java JRE 6 Update 43 64-bit Git version 1.8.1.2 Jenkins GIT client plugin 1.0.5 Jenkins GIT plugin 1.3.0 Project: Jenkins Labels: jenkins maven error build clean Priority: Major Reporter: Jeff Humphry This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA,
[JIRA] [maven2] (JENKINS-17777) Build Failure on Maven Clean
Jeff Humphry
updated JENKINS-1
Build Failure on Maven Clean
Change By:
Jeff Humphry
(29/Apr/13 3:07 PM)
Description:
RunningMavenbuildprojectpulledfromGitHub.Itsfailingonthethirdprojecttryingtoclean.Cantdeletesomefiles.Attachedistheconsoleoutputlog[^ConsoleText.txt]WhenIbuildusingMavenatthecommandline,Igetthesameresult,withsomeadditionalinformation;someofthefoldersseemtobecreatedbyJenkinswithhighersecurity:Usingnbsp;nbsp;nbsp;{{mvncleaninstall-e}}
{noformat}[ERROR]Failedtoexecutegoalorg.apache.maven.plugins:maven-clean-plugin:2.5:clean(default-clean)onprojectcom.sap.core:Failedtocleanproject:FailedtodeleteD:\Jenkins\jobs\CQ_Development_Branch_jtest\workspace\bundles\com.sap.core\target\generated-sources\annotations-[Help1]org.apache.maven.lifecycle.LifecycleExecutionException:Failedtoexecutegoalorg.apache.maven.plugins:maven-clean-plugin:2.5:clean(default-clean)onprojectcom.sap.core:Failedtocleanproject:FailedtodeleteD:\Jenkins\jobs\CQ_Development_Branch_jtest\workspace\bundles\com.sap.core\target\generated-sources\annotationsatorg.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)...Causedby:org.apache.maven.plugin.MojoExecutionException:Failedtocleanproject:FailedtodeleteD:\Jenkins\jobs\CQ_Development_Branch_jtest\workspace\bundles\com.sap.core\target\generated-sources\annotationsatorg.apache.maven.plugin.clean.CleanMojo.execute(CleanMojo.java:215)...Causedby:java.io.IOException:FailedtodeleteD:\Jenkins\jobs\CQ_Development_Branch_jtest\workspace\bundles\com.sap.core\target\generated-sources\annotationsatorg.apache.maven.plugin.clean.Cleaner.delete(Cleaner.java:249)...{noformat}Iattachedthefullconsoleoutput[^ConsoleText_M2.txt]IfItrytogoandmanuallydeletethefiles,IgetapromptthatIneedadministratorprivilegestodelete:
[^
!
AdminPriv.jpg
]
|width=500!
Triedthefollowing:*Runtheserviceunderaccountthatisadministratoronthemachine*Setcompatibilitymodeonjenkins.exetorunwithadministrativeprivileges*SettheWipeoutworkspacebeforebuildoption*Addmvncleanasapre-step*Disableallvirus-scanningontheserverAllgivesameresult.Acoupleotheroddities:*Addingthe-eswitchtothegoalsintheJenkinsconfigurationdoesntseemtowork.*TheJenkinsoutputdoesnthaveanyinformationaboutthefiledeleteIOerror.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-17762) Renaming the Clang parsers silently breaks Jenkins configs
Ulli Hafner commented on JENKINS-17762 Renaming the Clang parsers silently breaks Jenkins configs Actually the old name still is used as ID. The next time I should insist on tests for all pull requests I need to verify why the ID is not used in your case. Can you please attach your config.xml of your job? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents
Jesse Glick updated JENKINS-17775 IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents Change By: Jesse Glick (29/Apr/13 3:24 PM) Labels: exception 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/groups/opt_out.
[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents
SCM/JIRA link daemon commented on JENKINS-17775 IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents Code changed in jenkins User: Jesse Glick Path: changelog.html maven-plugin/src/main/java/hudson/maven/reporters/MavenFingerprinter.java http://jenkins-ci.org/commit/jenkins/d477296ffd3114f9f8416981f82e49cace605600 Log: JENKINS-17775 If MavenProject.getParent throws ISE during fingerprinting, report it but at least proceed. Proper fix is to ensure that the model resolution uses the same environment as the actual build, or is otherwise more lenient about finding the parent (e.g. enables plugin resolution). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17657) HealthAwareRecorder.logExceptionToFile() isn't handle a null getDefaultEncoding()
Ulli Hafner commented on JENKINS-17657 HealthAwareRecorder.logExceptionToFile() isnt handle a null getDefaultEncoding() Thanks for adding the patch! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17657) HealthAwareRecorder.logExceptionToFile() isn't handle a null getDefaultEncoding()
SCM/JIRA link daemon commented on JENKINS-17657 HealthAwareRecorder.logExceptionToFile() isnt handle a null getDefaultEncoding() Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/HealthAwareRecorder.java http://jenkins-ci.org/commit/analysis-core-plugin/70a24268cdca3ba50fe47d0c760c199cd38790e1 Log: FIXED JENKINS-17657 Get valid encoding from EncodingValidator. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17657) HealthAwareRecorder.logExceptionToFile() isn't handle a null getDefaultEncoding()
SCM/JIRA link daemon resolved JENKINS-17657 as Fixed HealthAwareRecorder.logExceptionToFile() isnt handle a null getDefaultEncoding() Change By: SCM/JIRA link daemon (29/Apr/13 3:36 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Matt Riedemann commented on JENKINS-17475 Backup stops when processing some file like latestfailedbuild Hi, is there any progress on this issue? I think I've determined that this is actually corrupting/wiping out the history of our jobs when it encounters failed builds for jobs, so essentially our backup is wiping out our history - which is what we are trying to backup. This is really nasty and I've had to disable the thinBackup plugin from our Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-16929) GNU make + GCC parser can't handle UTF-8
Ulli Hafner resolved JENKINS-16929 as Fixed GNU make + GCC parser cant handle UTF-8 Change By: Ulli Hafner (29/Apr/13 3:53 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Ulli Hafner resolved JENKINS-16298 as Cannot Reproduce DRY FATAL: null java.lang.StackOverflowError Change By: Ulli Hafner (29/Apr/13 3:54 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-collector] (JENKINS-15989) Inconsistent display, some warnings are assigned to Default Module
Ulli Hafner resolved JENKINS-15989 as Cannot Reproduce Inconsistent display, some warnings are assigned to Default Module Change By: Ulli Hafner (29/Apr/13 3:54 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-17408) Monitoring error 500 with Mac OS X master
evernat commented on JENKINS-17408 Monitoring error 500 with Mac OS X master Any news on this issue after my previous comment? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-15966) Build flow breaks when triggering next job
Mattias Persson commented on JENKINS-15966 Build flow breaks when triggering next job Could this be related to the facts that Jenkins won't allow you to start jobs with same parameters? For me it seems like the case anyway. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17775) IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents
dogfood commented on JENKINS-17775 IllegalStateException from MavenProject.getParent can break MavenFingerprinter.recordParents Integrated in jenkins_main_trunk #2497 JENKINS-17775 If MavenProject.getParent throws ISE during fingerprinting, report it but at least proceed. (Revision d477296ffd3114f9f8416981f82e49cace605600) Result = SUCCESS Jesse Glick : d477296ffd3114f9f8416981f82e49cace605600 Files : changelog.html maven-plugin/src/main/java/hudson/maven/reporters/MavenFingerprinter.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-7285) Allow the combination filter to accept parameter values
Oliver Gondža edited a comment on JENKINS-7285 Allow the combination filter to accept parameter values Pull request: https://github.com/jenkinsci/jenkins/pull/584 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-4995) Support windows AMI's in EC2 plugin
Francis Upton commented on JENKINS-4995 Support windows AMIs in EC2 plugin As a temporary measure, you can make a script in your Windows instance to connect with JNLP, the spot folks have used that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-16680) Downstream project being triggered twice since installing v0.11 version of plugin
Thomas Fields commented on JENKINS-16680 Downstream project being triggered twice since installing v0.11 version of plugin Hi vjuranek, Sorry to bother you but did you manage to repro and/or fix this issue? Cheers, Tom This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-17778) Allow to specify module versions when releasing multi module projects
Massimiliano Turri updated JENKINS-17778 Allow to specify module versions when releasing multi module projects Change By: Massimiliano Turri (29/Apr/13 6:28 PM) Summary: Allowtospecifymoduleversionswhen deploying releasing multimoduleprojects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-11564) Line number anchors for jobName/number/consoleFull
Eric Smalling commented on JENKINS-11564 Line number anchors for jobName/number/consoleFull Sorry I dropped the ball on this - will try to pick it back up later this week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17410) Unable to delete ec2 slave
jake bishop commented on JENKINS-17410 Unable to delete ec2 slave I also have this problem. The instance no longer exists on ecs2 so jenkins cannot delete 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/groups/opt_out.
[JIRA] [core] (JENKINS-6400) schedule triggering not working sometimes
evernat resolved JENKINS-6400 as Incomplete schedule triggering not working sometimes No response from the initial reporter, so resolving as incomplete. The probable cause seems to be an undersized heap memory for critical tasks. Change By: evernat (29/Apr/13 6:50 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/groups/opt_out.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Corey OConnor commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException We are using jenkins 1.484 and are experiencing the same issue. The "-Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true" option did result in the threads no longer taking 100% CPU. However, this broke loading the CSS. Perhaps due to what Walter Kacynski noticed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17581) Using the API Token beyond 496 causes intermittent 500 errors
herque updated JENKINS-17581 Using the API Token beyond 496 causes intermittent 500 errors Stack trace of bind failure. This happens when using api-token which should bypass other authentication mechanisms. Change By: herque (29/Apr/13 6:59 PM) Attachment: jenkins-17581-stacktrace.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ansicolor] (JENKINS-11752) ANSI color plugin adds garbage to log
Anze Zagar
commented on JENKINS-11752
ANSI color plugin adds garbage to log
Suggested temporary fix (until JENKINS-13816 allows better way of doing this):
src/main/java/hudson/plugins/ansicolor/AnsiColorNote.java (revision 36259)
+++ src/main/java/hudson/plugins/ansicolor/AnsiColorNote.java (working copy)
@@ -65,6 +65,7 @@
*/
@Override
public ConsoleAnnotator annotate(Object context, MarkupText text, int charPos) {
+ if (this.data.contains(ConsoleNote.PREAMBLE_STR)) return null;
try {
String colorizedData = colorize(StringEscapeUtils.escapeHtml(this.data), this.getColorMap());
if (! colorizedData.contentEquals(this.data)) {
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [timestamper] (JENKINS-17779) Timestamps incorrect in .../console when truncated
Jesse Glick created JENKINS-17779 Timestamps incorrect in .../console when truncated Issue Type: Bug Assignee: stevengbrown Components: timestamper Created: 29/Apr/13 7:09 PM Description: Created a test job ?xml version='1.0' encoding='UTF-8'? project actions/ description/description keepDependenciesfalse/keepDependencies properties/ scm class="hudson.scm.NullSCM"/ canRoamtrue/canRoam disabledfalse/disabled blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding triggers class="vector"/ concurrentBuildfalse/concurrentBuild builders hudson.tasks.Shell commandfor x in 0 1 2 3 4; do for y in 0 1 2 3 4; do for z in 0 1 2 3 4; do echo $x$y$z; cat /etc/pnm2ppa.conf; sleep 1; done; done; done/command /hudson.tasks.Shell /builders publishers/ buildWrappers hudson.plugins.timestamper.TimestamperBuildWrapper plugin="timestamper@1.5.3"/ /buildWrappers /project and ran it for a while, until there was enough output to truncate, then stopped it and compared .../console with .../consoleFull. The timestamps between the two are off by 1-2 seconds. For example, in console I see 14:51:31 + echo 021 14:51:31 021 whereas in consoleFull I see 14:51:33 + echo 021 14:51:33 021 and so on until the end of the file. TimestampAnnotatorFactory.getOffset looked suspicious, though its default of 150Kb does still match the current value in Run/console.jelly. Environment: 1.480.3 (reported), 1.515-SNAPSHOT on Linux (reproduced) Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-16347) No images served to Anonymous users
Kevin Garlow commented on JENKINS-16347 No images served to Anonymous users This is a significant annoyance for me as well. Even the "log in" button does not appear to an anonymous user. Perhaps we can better refine when this bug appeared. It was not present in version 1.456, but IS present in 1.510. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17759) Email notification source tries to indent HTML from console output
Georgi Todorov commented on JENKINS-17759 Email notification source tries to indent HTML from console output 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17780) Expose plug-in results in build and project action
Ulli Hafner created JENKINS-17780 Expose plug-in results in build and project action Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core Created: 29/Apr/13 7:23 PM Description: Currently the build results of the analysis plug-ins are only exposed on the results object. All these information should be visible in the corresponding actions, too. Project: Jenkins Priority: Minor Reporter: Ulli Hafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-17767) Unable to get warnings from all parsers via API
Ulli Hafner commented on JENKINS-17767 Unable to get warnings from all parsers via API Currently there is no "aggregated" result created. It makes sense to expose this information on such a aggregated action. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17581) Using the API Token beyond 496 causes intermittent 500 errors
herque commented on JENKINS-17581 Using the API Token beyond 496 causes intermittent 500 errors Some more history. environment that didn't work RHEL 5.5 Tomcat 7.0.26 jenkins version 509/510 with latest AD plugin I first noticed the issue because or post commit hook stopped working and while debugging that realized that the call was sometimes getting a 500 error. It was pretty random, would work 3-4 times then would not work 3-4 times. I put a loop in the hook to try ten times checking to make sure wget has a 0 exit. Although not ideal, it got my working. However this wasn't a good solution (obviously) so I thought to try out straight ldap and it worked as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17780) Expose plug-in results in build and project action
Ulli Hafner updated JENKINS-17780 Expose plug-in results in build and project action Change By: Ulli Hafner (29/Apr/13 7:31 PM) Description: Currentlythebuildresultsoftheanalysisplug-insareonlyexposedontheresultsobject.Alltheseinformationshouldbevisibleinthecorrespondingactions,too. Thefollowinginformationshouldbevisible:*numberofwarnings(new,fixed,all,high,normal,low)*referencebuild*pluginresult This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-16680) Downstream project being triggered twice since installing v0.11 version of plugin
vjuranek commented on JENKINS-16680 Downstream project being triggered twice since installing v0.11 version of plugin I;m sorry, not yet (able to reproduce, but not so trivial to fix, so not fixed yet), hopefully by end of this week will do another attempt (after next LTS release). Thanks for understanding. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17781) TAP Plugin: fails to report errors for
Steve Purkis
created JENKINS-17781
TAP Plugin: fails to report errors for
Issue Type:
Bug
Affects Versions:
current
Assignee:
Bruno P. Kinoshita
Attachments:
Jenkins-TAP-no-parse-errors-bug.jpg
Components:
tap
Created:
29/Apr/13 7:44 PM
Description:
Thanks for your work on the Jenkins TAP Plugin!
In our tests, we've found it ignores this parse error. Given this perl test:
$ cat fail.t
use Test::More tests = 2;
ok('before die');
die "eek!";
ok('after die');
And a Jenkins Job with this shell build step:
cd $JENKINS_HOME
mkdir -p $WORKSPACE/tap-output
set +e
prove -m --archive $WORKSPACE/tap-output/ fail.t
echo "prove exited with: $?"
Plus a Publish TAP step...
Running the job you get this TAP output:
$ cat ~/jobs/TAP-Plugin-Bug/workspace/tap-output/fail.t
1..2
ok 1
eek! at fail.t line 4.
Looks like you planned 2 tests but ran 1.
Looks like your test exited with 255 just after 1.
This should result in a Parse Error (because we planned 2 tests, but ran only 1). TAP::Harness confirms:
$ cp ~/jobs/TAP-Plugin-Bug/workspace/tap-output/fail.t ~/fail.tap
$ prove -v ~/fail.tap
... snip - TAP ...
Failed 1/2 subtests
Test Summary Report
---
fail.tap (Wstat: 0 Tests: 1 Failed: 0)
Parse errors: Bad plan. You planned 2 tests but ran 1.
Files=1, Tests=1, 0 wallclock secs ( 0.02 usr + 0.03 sys = 0.05 CPU)
Result: FAIL
But the Jenkins TAP plugin reports a successful build:
1 tests, 1 ok, 0 not ok, 0 skipped, 0 Bail Out!.
...
No parse errors found.
See screenshot for more details.
I've marked this as critical: as it stands Jenkins TAP will report false positives in these cases. As a worst-case scenario this may result in some users deploying bugs to production.
Environment:
Jenkins: 1.500
TAP Plugin: 1.10
Optional: perl: 5.8.9, TAP::Harness: 3.26, TAP::Harness::Archive: 0.14
Project:
Jenkins
Labels:
tap
parse-error
Priority:
Critical
Reporter:
Steve Purkis
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-8889) LOC / CC static analysis
Ulli Hafner assigned JENKINS-8889 to Unassigned LOC / CC static analysis Change By: Ulli Hafner (29/Apr/13 7:48 PM) Assignee: UlliHafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17781) TAP Plugin: fails to report errors for
Bruno P. Kinoshita commented on JENKINS-17781 TAP Plugin: fails to report errors for Hi Steve! Thanks for reporting the issue, and for including details. At moment I'm working on other open source projects and private projects. But I'll have a new cycle to work on Jenkins plug-ins within the next days. I'll take a look on this issue and will try to cut a release as soon as I've found a fix for it. In the meantime, feel free to comment on this issue and/or, in case you have time, submit a pull request via GitHub All the best, Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17781) TAP Plugin: fails to report errors for TAP streams where # tests run doesn't match plan
Steve Purkis updated JENKINS-17781 TAP Plugin: fails to report errors for TAP streams where # tests run doesnt match plan Change By: Steve Purkis (29/Apr/13 7:52 PM) Summary: TAPPlugin:failstoreporterrorsfor TAPstreamswhere#testsrundoesntmatchplan Description: ThanksforyourworkontheJenkinsTAPPlugin!Inourtests,wevefounditignores this parse error errorswhere#testsrundoesnotmatchtheplan .Giventhisperltest:$catfail.tuseTest::Moretests=2;ok(beforedie);dieeek!;ok(afterdie);AndaJenkinsJobwiththisshellbuildstep:cd$JENKINS_HOMEmkdir-p$WORKSPACE/tap-outputset+eprove-m--archive$WORKSPACE/tap-output/fail.techoproveexitedwith:$?PlusaPublishTAPstep...RunningthejobyougetthisTAPoutput:$cat~/jobs/TAP-Plugin-Bug/workspace/tap-output/fail.t1..2ok1eek!atfail.tline4.#Lookslikeyouplanned2testsbutran1.#Lookslikeyourtestexitedwith255justafter1.ThisshouldresultinaParseError(becauseweplanned2tests,butranonly1).TAP::Harnessconfirms:$cp~/jobs/TAP-Plugin-Bug/workspace/tap-output/fail.t~/fail.tap$prove-v~/fail.tap...snip-TAP...Failed1/2subtestsTestSummaryReport---fail.tap(Wstat:0Tests:1Failed:0)Parseerrors:Badplan.Youplanned2testsbutran1.Files=1,Tests=1,0wallclocksecs(0.02usr+0.03sys=0.05CPU)Result:FAILButtheJenkinsTAPpluginreportsasuccessfulbuild:1tests,1ok,0notok,0skipped,0BailOut!Noparseerrorsfound.Seescreenshotformoredetails.Ivemarkedthisascritical:asitstandsJenkinsTAPwillreportfalsepositivesinthesecases.Asaworst-casescenariothismayresultinsomeusersdeployingbugstoproduction. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-13350) Static Code Analysis Plug-ins: Failed to install
Ulli Hafner resolved JENKINS-13350 as Cannot Reproduce Static Code Analysis Plug-ins: Failed to install Change By: Ulli Hafner (29/Apr/13 7:52 PM) Status: Open Resolved Assignee: TácioDiogo UlliHafner Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [virtualbox] (JENKINS-15260) Can't release VirtualBox Plugin
SCM/JIRA link daemon commented on JENKINS-15260 Cant release VirtualBox Plugin Code changed in jenkins User: mirumpf Path: pom.xml http://jenkins-ci.org/commit/viewVC-plugin/bfbe4ec2456757b49ec2385564f31862a7c26408 Log: Use fix from JENKINS-15260 for the org.jenkins-ci.tools:maven-hpi-plugin:1.64 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17663) Fail by publishing report will fail whole build
Ulli Hafner updated JENKINS-17663 Fail by publishing report will fail whole build Change By: Ulli Hafner (29/Apr/13 8:06 PM) Component/s: analysis-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/groups/opt_out.
[JIRA] [dry] (JENKINS-3129) Show duplicate as a diff view
Ulli Hafner updated JENKINS-3129 Show duplicate as a diff view Change By: Ulli Hafner (29/Apr/13 8:16 PM) Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17047) Make dependency to bundled ant plugin optional
Ulli Hafner updated JENKINS-17047 Make dependency to bundled ant plugin optional Change By: Ulli Hafner (29/Apr/13 8:18 PM) Issue Type: Improvement 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-15246) Analysis plugins should have quiet mode
Ulli Hafner updated JENKINS-15246 Analysis plugins should have quiet mode Change By: Ulli Hafner (29/Apr/13 8:20 PM) Summary: Warningplugin Analysisplugins shouldhavequietmode Component/s: analysis-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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-15246) Analysis plugins should have quiet mode
Ulli Hafner updated JENKINS-15246 Analysis plugins should have quiet mode Change By: Ulli Hafner (29/Apr/13 8:21 PM) Description: Bydefaultwarningplugincontainsverbosityandinformwhichfilesareprocessed-incaseofprocessingfiles.Incaseofbigprojectwhichcontainslotoflogsconsoleoutputcontainsunnecessaryprintslike:[WARNINGS]Successfullyparsedfile:pathtofile Thereshouldbeaglobaloptiontochangetheverbosityoftheanalysisplug-ins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-collector] (JENKINS-17187) Add columns to the main view that show the number of warnings
Ulli Hafner updated JENKINS-17187 Add columns to the main view that show the number of warnings Change By: Ulli Hafner (29/Apr/13 8:24 PM) Issue Type: NewFeature Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17196) Add an action that allows to reset the reference build
Ulli Hafner updated JENKINS-17196 Add an action that allows to reset the reference build Change By: Ulli Hafner (29/Apr/13 8:25 PM) Issue Type: NewFeature Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dry] (JENKINS-3129) Show duplicate as a diff view
Ulli Hafner updated JENKINS-3129 Show duplicate as a diff view Change By: Ulli Hafner (29/Apr/13 8:26 PM) Issue Type: NewFeature Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-17780) Expose plug-in results in build and project action
Ulli Hafner updated JENKINS-17780 Expose plug-in results in build and project action Change By: Ulli Hafner (29/Apr/13 8:30 PM) Issue Type: Improvement 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/groups/opt_out.
[JIRA] [core] (JENKINS-17782) Internal stack traces exposed to users
Jesse Glick created JENKINS-17782 Internal stack traces exposed to users Issue Type: Bug Assignee: Jesse Glick Components: core Created: 29/Apr/13 8:56 PM Description: If you trigger an uncaught error in Stapler, such as browsing /static/ prior to stapler 552aaab, the stack trace is displayed in the web browser. This is usually harmless but there could in principle be stack traces which expose internal details of value to an attacker. These should be suppressed. Project: Jenkins Labels: security Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [hockeyapp] (JENKINS-17783) Uploading app doesn't respect App ID
Sveinung Kval Bakken created JENKINS-17783 Uploading app doesnt respect App ID Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: hockeyapp Created: 29/Apr/13 9:41 PM Description: When the user has multiple applications with the same package name (for different release types) the plugin doesn't respect the App ID when uploading a new version. Steps to reproduce: 1. Create App 1 with package name a.b.c 2. Create App 2 with package name a.b.c 3. Use App 2's ID when uploading 4. App 1 gets the new version. Project: Jenkins Priority: Major Reporter: Sveinung Kval Bakken This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17782) Internal stack traces exposed to users
SCM/JIRA link daemon commented on JENKINS-17782 Internal stack traces exposed to users Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/security/csrf/CrumbFilter.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/jenkins/model/Jenkins/error.jelly core/src/main/resources/jenkins/model/Jenkins/error.properties war/src/main/webapp/WEB-INF/web.xml http://jenkins-ci.org/commit/jenkins/121c1312d5bd9c69f5d9a859926659217c69e61d Log: JENKINS-17782 Set a custom error page for the web app and suppress stack traces for non-administrators. Needs a matching change in Stapler. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17782) Internal stack traces exposed to users
Jesse Glick commented on JENKINS-17782 Internal stack traces exposed to users https://github.com/stapler/stapler/pull/15 and https://github.com/jenkinsci/jenkins/pull/765 have an impl. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17782) Internal stack traces exposed to users
Jesse Glick started work on JENKINS-17782 Internal stack traces exposed to users Change By: Jesse Glick (29/Apr/13 9:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17782) Internal stack traces exposed to users
Kohsuke Kawaguchi commented on JENKINS-17782 Internal stack traces exposed to users I'm worried about the drop in the quality of reported bug due to this change. It seems to me that the number of cases where the stack trace is security sensitive is very small, whereas the stack trace is often very useful in identifying where the problem is and how to work around. Could this functionality be moved to another plugin that can be installed by security conscious deployments? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17782) Internal stack traces exposed to users
Jesse Glick commented on JENKINS-17782 Internal stack traces exposed to users There is no way the functionality could be moved. Perhaps rather than checking ADMINISTER some new permission could be introduced, but then you have the usual problem of defaulting it to on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-15504) NPE on running a job
aaron neerenberg commented on JENKINS-15504 NPE on running a job I've seen this as well. Some digging around in the console log suggests that the following sequence occurs. Please note, my snapshots are taken in powered-off state, using jnlp connection, set to revert after 1 build, slave to remain online as much as possible. 1. Slave comes online normally 2. Build assigned to slave, build runs to completion normally. 3. vsphere plugin starts to shutdown and revert the node 4. while the shutdown/disconnect is running, another build dequeues into the slave node and starts running. 5. While the second build is running, the vm finally shuts down and reverts, resulting in either a socket exception, the null pointer exception shown above, or a channelclosed exception. Log from catalina follows one of my build nodes through a couple of sequences. I've put in markers to indicate when various builds started and stopped. Apr 28, 2013 10:13:05 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Finished wait for VMTools http://hbo-jenkins/jenkins/job/Build-Common_Types_1.x/20/ BUILD RAN AT THIS POINT Apr 28, 2013 10:41:33 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Running disconnect procedure... Apr 28, 2013 10:41:33 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Shutting down Virtual Machine... Apr 28, 2013 10:41:33 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel HIORTCBLD1 Apr 28, 2013 10:41:33 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: Disconnecting the slave agent on HIORTCBLD1 due to limited build threshold Apr 28, 2013 10:41:34 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Attempting a graceful shutdown Apr 28, 2013 10:41:54 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Guest shutdown succeeded Apr 28, 2013 10:41:54 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Reverting to snapshot:build 11 Apr 28, 2013 10:41:58 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Running disconnect procedure... Apr 28, 2013 10:41:58 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Shutting down Virtual Machine... Apr 28, 2013 10:41:58 PM jenkins.slaves.JnlpSlaveAgentProtocol$Handler$1 onClosed WARNING: Channel reader thread: HIORTCBLD1 for + HIORTCBLD1 terminated Apr 28, 2013 10:43:20 PM hudson.slaves.SlaveComputer tryReconnect INFO: Attempting to reconnect HIORTCBLD1 Apr 28, 2013 10:43:20 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Starting Virtual Machine... Apr 28, 2013 10:43:20 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Reverting to snapshot:build 11 Apr 28, 2013 10:43:26 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Powering on VM Apr 28, 2013 10:43:29 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Waiting for VMTools http://hbo-jenkins/jenkins/job/Build-PTO_Custom_Components/36/ BUILD RAN AT THIS POINT Apr 28, 2013 10:44:14 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 VM Tools are running Apr 28, 2013 10:44:14 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Finished wait for VMTools Apr 28, 2013 11:14:01 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: Disconnecting the slave agent on HIORTCBLD1 due to limited build threshold http://hbo-jenkins/jenkins/job/Build-iFast-rtc/138/ BUILD RAN AT THIS POINT Apr 28, 2013 11:14:01 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Running disconnect procedure... Apr 28, 2013 11:14:01 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Shutting down Virtual Machine... Apr 28, 2013 11:14:01 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel HIORTCBLD1 Apr 28, 2013 11:14:02 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Attempting a graceful shutdown Apr 28, 2013 11:14:02 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: Disconnecting the slave agent on HIORTCBLD1 due to limited build threshold Apr 28, 2013 11:14:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Guest shutdown succeeded Apr 28, 2013 11:14:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog INFO: HIORTCBLD1 Reverting to snapshot:build 11 Apr 28, 2013 11:14:32 PM
[JIRA] [xunit] (JENKINS-17784) Not all unit test failures reported; looks like not all xml files being read
Joe Spr created JENKINS-17784 Not all unit test failures reported; looks like not all xml files being read Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: junitResult.xml, TEST--1205405971.xml, TEST--424792108.xml, TEST--459194063.xml, TEST-1166885271.xml, TEST-1168216595.xml, TEST-1237775542.xml, TEST-1909086772.xml, TEST-238631542.xml, TEST-240831352.xml, TEST-571237265.xml Components: xunit Created: 29/Apr/13 10:37 PM Description: Using xUnit. Not all unit test failures reported; looks like not all xml files being read. The TEST-*.xml files in generatedJUnitFiles/ directory contains all results, but it looks like not all of them getting into the junitResult.xml file. Therefore Jenkin's displayed result of job run does not show all failures. Attached are all 8 of the TEST-.xml files and the junitResult.xml file. As you see, the junitResult.xml does not contain all of the TEST-.xml files. Note sure if this is the same issue as JENKINS-11217 (This is my first Jenkins Jira, so let me know if this report needs improvement.) Environment: Jenkins 1.512 xUnit 1.54 Project: Jenkins Labels: plugin Priority: Major Reporter: Joe Spr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15309) NPE (isEmpty) from main.groovy
Jesse Glick commented on JENKINS-15309 NPE (isEmpty) from main.groovy Observed with a ListView in $JENKINS_HOME/config.xml that is missing a required field: jobNames class="tree-set" comparator class="hudson.util.CaseInsensitiveComparator"/ /jobNames This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15309) NPE (isEmpty) from main.groovy
Jesse Glick assigned JENKINS-15309 to Jesse Glick NPE (isEmpty) from main.groovy Change By: Jesse Glick (29/Apr/13 11:04 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17782) Internal stack traces exposed to users
Kohsuke Kawaguchi resolved JENKINS-17782 as Fixed Internal stack traces exposed to users Implemented as a plugin: https://wiki.jenkins-ci.org/display/JENKINS/Suppress+Stack+Trace+Plugin Change By: Kohsuke Kawaguchi (30/Apr/13 12:15 AM) Status: InProgress Resolved Assignee: JesseGlick KohsukeKawaguchi Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17785) Slave description does not get loaded in slave configure page
Eric Caron created JENKINS-17785 Slave description does not get loaded in slave configure page Issue Type: Bug Affects Versions: current Assignee: Eric Caron Components: ec2 Created: 30/Apr/13 12:54 AM Description: This prevents you from saving a new description for the slave. It also causes the description to resolve to "null" if a new configuration is saved for the slave. Project: Jenkins Priority: Minor Reporter: Eric Caron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17785) EC2 Slave description does not get loaded in slave configure page
Eric Caron updated JENKINS-17785 EC2 Slave description does not get loaded in slave configure page Change By: Eric Caron (30/Apr/13 1:03 AM) Summary: EC2 Slavedescriptiondoesnotgetloadedinslaveconfigurepage This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
Tony Le commented on JENKINS-12800 Cant add xcodebuild parameters including whitespace I'm experiencing the same issue. I've also tried escaping in a variety of ways and all of them seem to fail. CODE_SIGN_IDENTITY=iPhone\ Distribution:\ MangoDango,\ Inc CODE_SIGN_IDENTITY="iPhone Distribution: MangoDango, Inc" CODE_SIGN_IDENTITY="iPhone\ Distribution:\ MangoDango,\ Inc" CODE_SIGN_IDENTITY='iPhone Distribution: MangoDango, Inc' CODE_SIGN_IDENTITY=\"iPhone Distribution: MangoDango, Inc\" CODE_SIGN_IDENTITY=iPhone\ Distribution\:\ MangoDango\,\ Inc There doesn't seem to be any other way in the xcode plugin to specify code signing identities. It allows you to specify a provisioning profile, but not the code sign identity for the underlying xcrun command. Furthermore, there is a bug with that area as well. See JENKINS-14028. Any other suggestions than the ones mentioned above? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15081) Errors with multiple EC2 Clouds
Ray Sennewald commented on JENKINS-15081 Errors with multiple EC2 Clouds Francis got to it and asked me to pull in his recent updates for spot instances. So I've closed my original PR, merged in his code, revised my modifications and issued a new PR: https://github.com/jenkinsci/ec2-plugin/pull/48 . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-755) Default JDK meaning in project options is confusing.
Go Tanaka commented on JENKINS-755 Default JDK meaning in project options is confusing. I met the same issue when added a second JDK on Windows Server. In my case, I renamed the files, java.exe, javaw.exe, javaws.exe in Windows\System32, into java_.exe, javaw_.exe, javaws_.exe and finally Jenkins runs using JAVA_HOME's java with "Default". I guess installing a second JDK will update java.exe in Windows\System32 and "Default" setting won't use JAVA_HOME. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [hockeyapp] (JENKINS-17783) Uploading app doesn't respect App ID
Sveinung Kval Bakken resolved JENKINS-17783 as Not A Defect Uploading app doesnt respect App ID Found out how I enabled this by checking the source code. Maybe consider using "Use new API URL" by default if App ID is set? Change By: Sveinung Kval Bakken (30/Apr/13 2:34 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
