[JIRA] [hp-application-automation-tools-plugin] (JENKINS-22702) HP ALM 11.52 Performance Center (Standalone) and Jenkins Integration
Richa Sharma commented on JENKINS-22702 HP ALM 11.52 Performance Center (Standalone) and Jenkins Integration Hi Gautam, Were you able to resolve or workaround with this issue? I am facing the same issue when I try to run tests using the HP-Application-Automation Tools plugin. I am using the "Execute HP tests using the HP Performance Center" option. I am using: HP Performance Center 11 Jenkins 1.558 My questions are: 1. In the configuration for the Build options, for the PC Server input what do we need to put in? If I put in only the machine name (.xx.xx.com) or the IP address, as mentioned in the guide/help text, I get the following error: Started by user anonymous Building in workspace C:\Program Files (x86)\Jenkins\jobs\Perf-Run\workspace Validating parameters before run Trying to login PCServer=.xx.xx.com, User=xxx org.apache.http.conn.HttpHostConnectException: Connection to http://.xx.xx.com refused Login failed Empty Results Result Status: UNSTABLE - - Build step 'Execute HP tests using HP Performance Center' changed build result to UNSTABLE Report not found Build step 'Publish HP tests result' changed build result to FAILURE Finished: FAILURE If I try to change the PC Server input to .xx.xx.com:8080/qcbin, I get the following error: Started by user anonymous Building in workspace C:\Program Files (x86)\Jenkins\jobs\Perf-Run\workspace Validating parameters before run Trying to login PCServer=.xx.xx.com:8080/qcbin, User=xxx HTTP/1.1 404 Not Found Login failed Empty Results Result Status: UNSTABLE - - Build step 'Execute HP tests using HP Performance Center' changed build result to UNSTABLE Report not found Build step 'Publish HP tests result' changed build result to FAILURE Finished: FAILURE Please advise what exactly needs to be put in the input for the connection to be successful. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-22702) HP ALM 11.52 Performance Center (Standalone) and Jenkins Integration
Richa Sharma stopped work on JENKINS-22702 HP ALM 11.52 Performance Center (Standalone) and Jenkins Integration Change By: Richa Sharma (06/Jun/14 6:59 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-22702) HP ALM 11.52 Performance Center (Standalone) and Jenkins Integration
Richa Sharma started work on JENKINS-22702 HP ALM 11.52 Performance Center (Standalone) and Jenkins Integration Change By: Richa Sharma (06/Jun/14 6:58 AM) 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/d/optout.
[JIRA] [android-emulator] (JENKINS-23346) Path to android-sdk subfolders is incorrect
wearbif created JENKINS-23346 Path to android-sdk subfolders is incorrect Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-emulator Created: 06/Jun/14 7:51 AM Description: It seems as though Android Emulator Plugin v2.11.1 is completely broken on remote unix-slaves if server itself running on windows. So a path to sdk subfolders is incorrect concatenate? /home/jenkins/tools/android-sdk\tools\android list target. Plugin v2.10 works well. Started by build flow MyProject_App#1098 EnvInject - Loading node environment variables. Building remotely on buildserver in workspace /home/jenkins/workspace/MyProject Cleaning up /home/jenkins/workspace/MyProject/. Deleting /home/jenkins/workspace/MyProject/bin Deleting /home/jenkins/workspace/MyProject/gen Deleting /home/jenkins/workspace/MyProject/monkey.txt Deleting /home/jenkins/workspace/MyProject/AndroidManifest.xml Deleting /home/jenkins/workspace/MyProject/version.properties Updating https://my.domain.com/svn/MyProject/trunk/MyProjectCont at revision '2014-06-06T09:01:56.448 +0200' At revision 570 no change for https://my.domain.com/svn/MyProject/trunk/MyProjectCont since the previous build No emails were triggered. $ /home/jenkins/tools/android-sdk\tools\android list target FATAL: Cannot run program "/home/jenkins/tools/android-sdk\tools\android": error=2, Datei oder Verzeichnis nicht gefunden java.io.IOException: Cannot run program "/home/jenkins/tools/android-sdk\tools\android": error=2, Datei oder Verzeichnis nicht gefunden at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:998) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:965) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$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.io.IOException: error=2, Datei oder Verzeichnis nicht gefunden at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.init(UNIXProcess.java:135) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021) ... 15 more Due Date: 06/Jun/14 12:00 AM Environment: Master: Windows Server 2008 Slave: Ubuntu 12.04 LTS Jenkins ver. 1.532.1 Project: Jenkins Labels: jenkins plugin android Priority: Critical Reporter: wearbif This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message
[JIRA] [plugin] (JENKINS-17158) Quiet subversion checkout?
Libero Scarcelli commented on JENKINS-17158 Quiet subversion checkout? A few months ago I had a look at the SVNKit API and I had the impression this library does not support quiet check out. Hence Jenkins would have to redirect the output to null while downloading the code from the repository This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring] (JENKINS-20947) Failed to monitor for Free Swap Space
Andreas Kuttruff updated JENKINS-20947 Failed to monitor for Free Swap Space I am running also massively into this issue rearding running VM's on demand which run slaves. More Information see attached PDF file 'MonitorFreeSwapSpace.pdf' Change By: Andreas Kuttruff (06/Jun/14 8:30 AM) Attachment: MonitorFreeSwapSpace.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23347) Several minutes delay at end of job
Baptiste Mathus created JENKINS-23347 Several minutes delay at end of job Issue Type: Bug Assignee: Unassigned Attachments: JIRA.zip Components: core Created: 06/Jun/14 8:48 AM Description: At the end of a build, as this seems to be finished, Jenkins then shows the spinner during many minutes. Note this happens with many (still have to double-check to say all?) our jobs. I'm attaching threadDumps of the whole server: two during the issue one after to be able to analyze the difference if necessary The slave on which the offending job was running is rhel6-5 Thanks for any feedback. Environment: Jenkins 1.559, RHEL on master slaves Project: Jenkins Priority: Minor Reporter: Baptiste Mathus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23347) Several minutes delay at end of job
Baptiste Mathus commented on JENKINS-23347 Several minutes delay at end of job Still to be confirmed, but first analysis led me to JENKINS-21718 (see attached thread dumps, a Disk Usage thread is always present doing a DiskUsageUtil.isSymlink call). We just uninstalled disk usage to see if this makes a difference. Waiting to restart Jenkins asap to check. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-22838) Building a Dockerfile fails when using ADD with a file in a subfolder
Hack Kampbjørn resolved JENKINS-22838 as Fixed Building a Dockerfile fails when using ADD with a file in a subfolder Yes, this works now in version 1.4. Thanks Change By: Hack Kampbjørn (06/Jun/14 9:36 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23347) Several minutes delay at end of job
Baptiste Mathus commented on JENKINS-23347 Several minutes delay at end of job Still to be confirmed, but first analysis led me to JENKINS-21718. In fact, the attached thread dumps always show a stack calling DiskUsageUtil.isSymlink. So we're gonna uninstall the Disk Usage plugin to see how it goes and post the results here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23347) Several minutes delay at end of job
Corneil du Plessis commented on JENKINS-23347 Several minutes delay at end of job Disabling the disk-usage plugin allowed us to get rid of the huge delay at the end of the job. Our workspace has about 80k files. I think the plugin is collecting the info from the slave over the network. Jobs that run on the master or where the workspace has fewer files doesn't suffer the same delay. I don't know enough about the Jenkins Master and Slave interaction to suggest a solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23238) Single and Multi select multi level choice does not work.
Oleg Nenashev commented on JENKINS-23238 Single and Multi select multi level choice does not work. The functionality has been corrupted in 0.31 Commit: https://github.com/jenkinsci/extended-choice-parameter-plugin/commit/96ed8ebfbec7ba49173960bbb4b028f099927167 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23238) Single and Multi select multi level choice does not work.
Oleg Nenashev updated JENKINS-23238 Single and Multi select multi level choice does not work. Change By: Oleg Nenashev (06/Jun/14 11:50 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23238) Single and Multi select multi level choice does not work.
Oleg Nenashev assigned JENKINS-23238 to vimil Single and Multi select multi level choice does not work. Change By: Oleg Nenashev (06/Jun/14 11:55 AM) Assignee: vimil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23112) Already configured Extended Choice Parameter value is not filled in
Oleg Nenashev assigned JENKINS-23112 to vimil Already configured Extended Choice Parameter value is not filled in Change By: Oleg Nenashev (06/Jun/14 11:56 AM) Assignee: vimil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-19867) resolve variables on the config. parameters
Oleg Nenashev assigned JENKINS-19867 to vimil resolve variables on the config. parameters Change By: Oleg Nenashev (06/Jun/14 11:57 AM) Assignee: vimil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extended-choice-parameter] (JENKINS-23092) Config with an Extended Choice Parameter can't be saved
Oleg Nenashev assigned JENKINS-23092 to vimil Config with an Extended Choice Parameter cant be saved Change By: Oleg Nenashev (06/Jun/14 11:56 AM) Assignee: vimil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Ireneusz Makowski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) We still have an issue on latest 2.38 version with huge amount of time to send email This is the output from Debug mode: Checking for post-build Performing post-build step Checking if email needs to be generated Email was triggered for: Failure - Any Email was triggered for: Failure - Still Trigger Failure - Any was overridden by another trigger and will not send an email. Sending email for trigger: Failure - Still Overriding default server settings, creating our own session messageContentType = text/html; charset=UTF-8 It hangs after messageContentType for 20 minutes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
Mark Waite commented on JENKINS-23345 Git Plugin should have an option to use clone instead of init/fetch This is the first I've heard that clone is faster than fetch at retrieving the remote repository. I don't see any mention in my google searches that indicate "git fetch" is slower than "git clone". Can you give some pointers that provide support for the statement that clone is more efficient than fetch? Even if clone is faster, I'm hesitant to support such an addition to the plugin. Git fetch was chosen because there are fewer ways it can hang (prompting for authentication information) in the various authentication scenarios supported by the plugin. It is even more challenging because there are currently no unit tests for the authentication scenarios, so they must be tested interactively (or not tested) at each plugin release. Adding the option to use "clone" instead of "fetch" would effectively double the cases we need to test in an already very complicated portion of the code. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Ireneusz Makowski reopened JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) See my comment below. Sometimes this job hangs over 40 minutes to send email. Change By: Ireneusz Makowski (06/Jun/14 12:11 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Please provide a stack trace of what is happening. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
bbonn commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Hi Heather, Yes we use Oracles JVM on all of our masters and slaves. We have thought about loading the toolkit but it would be a pain to maintain for all of our slaves (approx 100). If we could install it automatically like the jdk and ant that would be great, but I feel like I tried that and it didn't work. Are you saying for a future version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Hi Bernie We (and another user of the plugin) have tried it out and it does work. The auto-install can't be from the jazz.net page, but it can be from your own internal location. The wiki page for the plugin has been recently updated to describe a setup. https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-Master%2FSlaveConfiguration (scenario works for all the versions of the plugin since the auto-install is a Jenkins feature). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9913) Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent
M S commented on JENKINS-9913 Not obvious why some post-build tasks enforce serial behavior even when builds are concurrent To resolve this problem use xplugin as an intermediary to nunit/junit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
SCM/JIRA link daemon commented on JENKINS-23289 ClassCastException in JobDSL whith removed Folder Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/ExecuteDslScripts.java job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ExecuteDslScriptsTest.java http://jenkins-ci.org/commit/job-dsl-plugin/3c6caff7d0b47f56562a45ab86ff41be4feedcec Log: fixed JENKINS-23289 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
Daniel Spilker resolved JENKINS-23289 as Fixed ClassCastException in JobDSL whith removed Folder Will be released in 1.24. Change By: Daniel Spilker (06/Jun/14 3:13 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
SCM/JIRA link daemon commented on JENKINS-23289 ClassCastException in JobDSL whith removed Folder Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/ExecuteDslScripts.java job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ExecuteDslScriptsTest.java http://jenkins-ci.org/commit/job-dsl-plugin/5f029b0bda5a3ca752b285e95b643d0b6bdc9d4d Log: Merge pull request #214 from CoreMedia/JENKINS-23289 JENKINS-23289 Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/714333643a78...5f029b0bda5a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-23289) ClassCastException in JobDSL whith removed Folder
SCM/JIRA link daemon commented on JENKINS-23289 ClassCastException in JobDSL whith removed Folder Code changed in jenkins User: Daniel Spilker Path: docs/Home.md http://jenkins-ci.org/commit/job-dsl-plugin/912e712e56a0ab107ac914f7bdfae7fc00984513 Log: added release notes entry for JENKINS-23289 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-23348) changes to selenium configuration under jenkins 'manager jenkins' is not saved
ragavan Ambighananthan created JENKINS-23348 changes to selenium configuration under jenkins manager jenkins is not saved Issue Type: Bug Affects Versions: current Assignee: Richard Lavoie Attachments: selenium-jenkins.jpg Components: plugin, selenium Created: 06/Jun/14 3:34 PM Description: Problem: Data entered into jenkins admin selenium section is not saved 1. As a jenkins admin, goto 'Manage Jenkins' - Configure Systems - Expand 'Selenium' Advance section 2. Enter Set -newSessionWaitTimeout as 30 (5mins) for new new test to timeout after waiting for a node. 3. Click apply/Save 4. Open Configure Systems - Expand 'Selenium', this entered data will not be available We need to configure this -newSessionWaitTimeout as we are lots of test than the available number of nodes so we need to configure the time for new tests to wait for freed slots. Can we get this fix please ? Due Date: 20/Jun/14 12:00 AM Environment: jenkins selenium plugin version: 2.4.1 Jenkins version: 1.565 OS: Win2k8 R2 Project: Jenkins Labels: plugin Priority: Major Reporter: ragavan Ambighananthan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-23348) changes to selenium configuration under jenkins 'manager jenkins' is not saved
ragavan Ambighananthan updated JENKINS-23348 changes to selenium configuration under jenkins manager jenkins is not saved Change By: ragavan Ambighananthan (06/Jun/14 3:38 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23349) Views who's name start with an emoji are not accessible
R. Tyler Croy commented on JENKINS-23349 Views whos name start with an emoji are not accessible This isn't an infrastructure ticket but rather something that should be triaged as part of the JENKINS JIRA project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23349) Views who's name start with an emoji are not accessible
R. Tyler Croy moved JENKINS-23349 Views whos name start with an emoji are not accessible Change By: R. Tyler Croy (06/Jun/14 3:42 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 86 23349 Workflow: jira JNJira Component/s: jira Component/s: jira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-22777) Pass in Flag to indicate if Jenkins Emergency reroute is non-blank
Frank Merrow commented on JENKINS-22777 Pass in Flag to indicate if Jenkins Emergency reroute is non-blank So I noticed that this CR was not mentioned in the Version History for either 2.38 or 2.38.1 . . . but thought I would test it just in case. Unfortunately, 2.38.1 still does not suppress an Recipients added by my presend script when under Emergency Redirect. When is this change likely to make it into a release? Frank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [secure-requester-whitelist] (JENKINS-23350) Describe where the configuration option for the whitelisting can be found
Dom Fretz created JENKINS-23350 Describe where the configuration option for the whitelisting can be found Issue Type: Improvement Assignee: Jesse Glick Components: secure-requester-whitelist Created: 06/Jun/14 6:14 PM Description: I had a hard time finding where I can configure the secure whitelist plugin. A small hint in the wiki and/or the Readme on Github would help: For anyone looking for a solution: It can be found in 'Manage Jenkins - Global Security' Project: Jenkins Priority: Major Reporter: Dom Fretz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-23347) Several minutes delay at end of job
Daniel Beck updated JENKINS-23347 Several minutes delay at end of job Change By: Daniel Beck (06/Jun/14 6:20 PM) Component/s: disk-usage Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-22777) Pass in Flag to indicate if Jenkins Emergency reroute is non-blank
Alex Earl commented on JENKINS-22777 Pass in Flag to indicate if Jenkins Emergency reroute is non-blank Should be in 2.39 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testflight] (JENKINS-23351) Tesflight Plugin: Add support for Custom URL
Jonathon Lamon created JENKINS-23351 Tesflight Plugin: Add support for Custom URL Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: testflight Created: 06/Jun/14 6:29 PM Description: If you request it, you can receive from Testflight a custom url for uploading depending on your needs and their agreement. My company has requested and received such a url. It would be nice to be able to specify the url for the upload of the .ipa within the Jenkins api, either as an Advanced option in Global Configuration or an Advanced option in project configuration. Fix Versions: current Project: Jenkins Labels: plugin Priority: Minor Reporter: Jonathon Lamon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
Jason Salaz commented on JENKINS-23345 Git Plugin should have an option to use clone instead of init/fetch Hey Mark, I've been working with Dave on this issue so I can expand on some of the details. I'll note that my information is still second hand, as I've received this information from someone else, but that someone works on git, so, I'm satisfied with the answer. Here's hoping I'm repeating the information again correctly . When you use git clone, you receive cryptographic/verifiable assurance that the server has provided you all the objects. When you run 'git clone', the directory is set up, the server collects all the objects, the transfer happens. After it's complete, the receiving end runs a quick verification on the packfile(s), and then puts all the objects in place on the local filesystem, and the process is done. This is as opposed to git fetch, which is meant for incremental updates. After a fetch completes, git walks the object graph; In most cases this is merely from your previous head forward through all of the new objects, verifying that everything is intact. In Dave's case, walking the entire history of the repository accounts for the vast majority of the execution time. Longer than the default fetch timeout of 10 minutes, for the record. Receiving data itself isn't any faster, but the verification that takes place after receiving objects via fetch is dramatically different. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-22459) NullPointerException in NaginatorActionFactory caused by empty Managed windows batch build step
Jonathan Brecher commented on JENKINS-22459 NullPointerException in NaginatorActionFactory caused by empty Managed windows batch build step We just observed this same NPE, in a job that had no "Managed Windows Batch" built step at all. We've downgraded to version 1.9 of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor] (JENKINS-23352) Build monitor plugin slow to open config page with lots of jobs
Jonathan Brecher created JENKINS-23352 Build monitor plugin slow to open config page with lots of jobs Issue Type: Bug Assignee: Unassigned Components: build-monitor Created: 06/Jun/14 9:23 PM Description: We have a Jenkins server with ~1,100 jobs. It takes over 50 seconds just to open the config page for any Build Monitor Plugin view. That's far too slow. Project: Jenkins Priority: Major Reporter: Jonathan Brecher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-23134) Mixed separators fail for Linux paths
Barak Weiss commented on JENKINS-23134 Mixed separators fail for Linux paths I have the same problem. When I run the groovy script "println File.separator" it prints the correct slash. How's that possible? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23353) Using a Delivery Pipeline view as the default view in Jenkins breaks the New Item sidebar link
Steve Jansen created JENKINS-23353 Using a Delivery Pipeline view as the default view in Jenkins breaks the New Item sidebar link Issue Type: Bug Affects Versions: current Assignee: Patrik Boström Components: delivery-pipeline Created: 06/Jun/14 10:18 PM Description: Overview Pull Request #67 added the ability to use a Delivery Pipeline view as the default view in Jenkins (see JENKINS-23282). However, this fix introduced a defect when trying to create a new job from the default view. Steps to Reproduce --- 1. As a Jenkins admin, install version 0.8.0 or later of the Delivery Pipeline plugin in Jenkins 2. Create a new pipeline view by navigating to /newView in Jenkins, selecting "Build Pipeline View", assigning a name, and clicking "Ok" 3. In the newly created view from #2, click the "Edit View" sidebar link to add one or more jobs to the pipeline view. Click Ok to save the changes to the pipeline view. 4. Click the "Manage Jenkins" sidebar link, and click the "Configure System" link. 5. Change the default view to the pipeline view created in step #2. Click Ok to save. 6. Navigate to the Jenkins default view by clicking the Jenkins logo in the upper left hand header region of the screen 7. Click the "New Item" sidebar link to create a new job. 8. Enter a new job name such as "test", select "Build a free-style software project", and click the "OK" button. Expected Result --- Jenkins should create a new job using the name provided in step #8 and render the configure page for the new job. Actual Result - An error page displays with a stack trace of javax.servlet.ServletException: java.lang.StackOverflowError ... Caused by: java.lang.StackOverflowError at hudson.model.ViewGroupMixIn.getPrimaryView(ViewGroupMixIn.java:127) at jenkins.model.Jenkins.getPrimaryView(Jenkins.java:1484) at se.diabol.jenkins.pipeline.DeliveryPipelineView.doCreateItem(DeliveryPipelineView.java:363) at se.diabol.jenkins.pipeline.DeliveryPipelineView.doCreateItem(DeliveryPipelineView.java:363) at se.diabol.jenkins.pipeline.DeliveryPipelineView.doCreateItem(DeliveryPipelineView.java:363) ... Remarks --- The hudson.model.View abstract class declares the doCreateItem method as abstract. The current implementation of doCreateItem in the DeliveryPipelineView class defers implementation of doCreateItem to the default system view. This causes an infinite loop when the DeliveryPipeline view is the default view, as it keeps calling it's own doCreateItem method. Project: Jenkins Labels: plugin Priority: Minor Reporter: Steve Jansen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pam-auth] (JENKINS-21507) libpam4j problem under FreeBSD 10
Anthony Williams commented on JENKINS-21507 libpam4j problem under FreeBSD 10 I have created a Pull Request (https://github.com/jenkinsci/jna/pull/2) against the jenkinsci/jna repository which resolves this problem. The existing libpam4j library works under FreeBSD 10, but the jna library does not as it is expecting the system .so files to be in a different format (I believe this is because the one it is trying to load is now a symlink under FreeBSD 10), throwing an exception. I have tested this change by building the patched version of jna and including it in a local build of Jenkins, and it appears to be functionally sound under FreeBSD 10 - multiple users have been able to log in successfully, and has been seen to work on several recent Jenkins builds. Thanks, Anthony This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pam-auth] (JENKINS-21507) libpam4j problem under FreeBSD 10
Anthony Williams edited a comment on JENKINS-21507 libpam4j problem under FreeBSD 10 I have created a Pull Request (https://github.com/jenkinsci/jna/pull/2) against the jenkinsci/jna repository which resolves this problem. The existing libpam4j library works under FreeBSD 10, but the jna library does not as it is expecting the system .so files to be in a different format (I believe this is because the one it is trying to load is now a symlink under FreeBSD 10), throwing an exception. I have tested this change by building the patched version of jna and including it in a local build of Jenkins, and it appears to be functionally sound under FreeBSD 10 - multiple users have been able to log in successfully, and has been seen to work on several recent Jenkins builds. Note that this is a backported fix from https://github.com/twall/jna/issues/279. Thanks, Anthony This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23354) agentCommand is empty after creating a node with command launcher through rest api
jerry zhao
created JENKINS-23354
agentCommand is empty after creating a node with command launcher through rest api
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Attachments:
agentcommand_empty.JPG
Components:
core
Created:
06/Jun/14 11:07 PM
Description:
create a node with command launcher method by rest api, but launch command is empty.
The decoded json should be:
{"launcher": {"stapler-class": "hudson.slaves.CommandLauncher", "agentCommand": "/home/jenkins/launch_slave.sh root /home/nodepool/.ssh/id_rsa 10.145.81.65 192.168.100.35"}, "numExecutors": 1, "nodeProperties": {"stapler-class-bag": "true"}, "name": "centos-dev-testcloud-dev-118", "retentionStrategy": {"stapler-class": "hudson.slaves.RetentionStrategy$Always"}, "remoteFS": "/home/jenkins", "type": "hudson.slaves.DumbSlave$DescriptorImpl", "nodeDescription": "Dynamic single use centos-dev node", "labelString": "centos-dev", "mode": "EXCLUSIVE"}
The raw http packet capture:
GET /openstackcijenkins/computer/doCreateItem?json=%7B%22launcher%22%3A+%7B%22stapler-class%22%3A+%22hudson.slaves.CommandLauncher%22%2C+%22agentCommand%22%3A+%22%26quot%3B%2Fhome%2Fjenkins%2Flaunch_slave.sh%26quot%3B+%26quot%3Broot%26quot%3B+%26quot%3B%2Fhome%2Fnodepool%2F.ssh%2Fid_rsa%26quot%3B+%26quot%3B10.145.81.65%26quot%3B+%26quot%3B192.168.100.35%26quot%3B%22%7D%2C+%22numExecutors%22%3A+1%2C+%22nodeProperties%22%3A+%7B%22stapler-class-bag%22%3A+%22true%22%7D%2C+%22name%22%3A+%22centos-dev-testcloud-dev-118%22%2C+%22retentionStrategy%22%3A+%7B%22stapler-class%22%3A+%22hudson.slaves.RetentionStrategy%24Always%22%7D%2C+%22remoteFS%22%3A+%22%2Fhome%2Fjenkins%22%2C+%22type%22%3A+%22hudson.slaves.DumbSlave%24DescriptorImpl%22%2C+%22nodeDescription%22%3A+%22Dynamic+single+use+centos-dev+node%22%2C+%22labelString%22%3A+%22centos-dev%22%2C+%22mode%22%3A+%22EXCLUSIVE%22%7Dtype=hudson.slaves.DumbSlave%24DescriptorImplname=centos-dev-testcloud-dev-118 HTTP/1.1
Accept-Encoding: identity
Host: 10.145.81.234
Connection: close
Authorization: Basic YWRtaW46NmIxMTJiZGNlZGIzOTliOTJlMjUxOGRjMDhiOWNlZDc=
User-Agent: Python-urllib/2.7
HTTP/1.1 302 Found
Date: Fri, 06 Jun 2014 22:07:08 GMT
Server: Jetty(8.y.z-SNAPSHOT)
Location: http://10.145.81.234/openstackcijenkins/computer/
Content-Length: 0
Connection: close
Content-Type: text/plain
Environment:
jenkins version: 1.549
Project:
Jenkins
Priority:
Major
Reporter:
jerry zhao
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23355) Protocol-independent contextual ancestors
Kohsuke Kawaguchi created JENKINS-23355 Protocol-independent contextual ancestors Issue Type: Improvement Assignee: Unassigned Components: core Created: 06/Jun/14 11:11 PM Description: Various places in Jenkins we have to look up StaplerRequest.getAncestor to find the parent Project/Build/etc that an object in question is built for. Similar pattern exists during XStream deserialization, as one often wants to know the context in which an object is deserialized. There's a room for generalizing this to create a protocol-agnostic contextual ancestor retrieval mechanism. (Jesse wanted a separate but related ability to register callbacks to XStream that gets fired at the end of the deserialization when all objects in the graph are fully ready, which allows a far more sophisticated readResolve()) to be written. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
trejkaz edited a comment on JENKINS-23305 NPE on running some slaves of a matrix build - failure with no explanation Definitely using 1.566 (assuming the version shown at the bottom of the page is accurate!), but I agree, if that's the code running in 1.566, I don't see where there can be an NPE, unless there is some unboxing going on which is not evident by seeing just that fragment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
trejkaz commented on JENKINS-23305 NPE on running some slaves of a matrix build - failure with no explanation Definitely using 1.566, but I agree, if that's the code running in 1.566, I don't see where there can be an NPE, unless there is some unboxing going on which is not evident by seeing just that fragment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
trejkaz
commented on JENKINS-23305
NPE on running some slaves of a matrix build - failure with no explanation
Well hey, how about that.
/**
* True if this computer is a Unix machine (as opposed to Windows machine).
*
* @return
* null if the computer is disconnected and therefore we don't know whether it is Unix or not.
*/
public Boolean isUnix() {
return isUnix;
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23356) NTLM Proxy issue - authentication fails
Jim Goodspeed created JENKINS-23356 NTLM Proxy issue - authentication fails Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Jun/14 12:59 AM Description: When trying to install new plugins with a Proxy configured I am getting the following error: SEVERE: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials org.apache.commons.httpclient.auth.InvalidCredentialsException: Credentials cannot be used for NTLM authentication: org.apache.commons.httpclient.UsernamePasswordCredentials I have checked my credentials many times and have also tried a co-workers credentials. We started noticing this after installing the Build Failure Analyzer plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer Not sure if it is really related or not, but wanted to mention it in the event there was a conflict (we are using the MongoDB configuration as part of the plugin). Environment: RHEL 6, Oracle JDK 1.7 Project: Jenkins Priority: Major Reporter: Jim Goodspeed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-metrics] (JENKINS-23316) Some projects have builds whose timestamps are inconsistent
Clay Osborn closed JENKINS-23316 as Duplicate Some projects have builds whose timestamps are inconsistent Change By: Clay Osborn (07/Jun/14 4:17 AM) Status: Open Closed Assignee: ClayOsborn Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
