[JIRA] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX When the user requests the Installer to install something for all users, it prompts the user for admin password and elevates permissions to root, making it possible to install Jenkins as a launch daemon. But this is only relevant if we want to keep the possibility of installing as launch daemon. But like I said, I do not look forward to tweaking PackageMaker to achieve many different ways of installing Jenkins to suite everyone's needs. IMHO the PackageMaker based installer is only suitable for one kind of installation with no options at all. (The current Installer has a few options but I'm sure no-one has found them or uses those.) If a more customizable installer is required, it must be based on something else. My favorite is a simple AppleScript application. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX We might want to gather some requirements or user stories for the Jenkins Mac installer. My humble opinion is the only people who want to run Jenkins on Mac are iOS developers. (And Mac developers but there are few of those and their needs might be very similar to iOS developers.) People who do cross-platform development and need to build their software for multiple platforms need to set up Windows, Mac and Linux build servers. They will probably run Jenkins master either on Windows or Linux and run a slave on Mac. Thus we do not need to worry about these people. The iOS developers have some special needs (which I do not know exactly because I haven't done any real development for iOS so feel free to add to the list or set me straight.) Builds must be codesigned. The developer certificate resides in the developer's keychain. The keychain is only accessible within the developer's GUI login session. Automated tests need to execute iOS simulator which is a GUI app. GUI apps can only run in GUI login session. It seems to me the most common use cases for Jenkins master on Mac require that Jenkins has access to GUI login session. This means Jenkins master must be executed either as a launch agent (which are meant for background processes) or within a context of a GUI app wrapper (if we want something visible in Dock or menu bar.) The security aspect of having a Jenkins master with a logged-in user with a GUI session must be addressed separately. I do not believe we can provide a solution that fits everyone's needs. Maybe we can just give hints on how to solve it: put the Mac in a locked room, set up screensaver with short timeout or the trick mentioned above in the ticket description or maybe something else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @Randall: OK, so it can be done, but is it well documented and supported by Xcode? If it's not, lots of programmers are going to try building their iOS projects on Jenkins and will be unhappy. If it just works, then we should be good with the existing installer that sets up a launch daemon. Apparently there are complications because there used to be lots of people asking how to get signing to work when building under Jenkins. (There might still be but I have been away from Jenkins community for a while.) Well, there's the iOS simulator... What do we do about 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] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX It has been years since I last played with PackageMaker but I believe it was possible to build a package that will query if you want to install for all users or for current user only. If all users is chosen, the installer will prompt for admin password. It might be possible to determine which kind of installation happened in a post install script and place the launchd plist file in a location that either makes Jenkins be a launch daemon or launch agent. However, I think it would be rude to unconditionally configure the current user's account such that after login he is immediately presented with the login screen again. It should at least be configurable (= ask the user) but how to do that with PackageMaker... I have no idea. Actually I am really tired with PackageMaker. I believe a better user experience is achieved by creating an application, a single icon the user drags where he wants and runs by double-clicking. The application can then have a conversation with the user or present a rich UI to configure and run Jenkins. If a launch agent or daemon is needed, the application can set those up. So, personally, rather than fight with the limitations of PackageMaker, I would rather improve Jenkins.app. I'm happy to collaborate on it (pull requests are welcome.) Jenkins.app is my own project but if people feel it should be in the official Jenkins git repository, I can renew my request to accept it there. I have kept it outside of the official Jenkins tree because I assumed most people were happy with the PackageMaker based installer which runs Jenkins as a launch daemon. It has it's problems but there are workarounds and plugins like the Xcode plugin which should provide some relief. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-16225) Add note to env-vars.html so user knows that Environment variables configuration is requried to export JENKINS_URL, JOB_URL, BUILD_URL
Sami Tikka commented on JENKINS-16225 Add note to env-vars.html so user knows that Environment variables configuration is requried to export JENKINS_URL, JOB_URL, BUILD_URL Sorry for being so thick-headed.. I only now understood what the problem is and verified it myself. Set up a new Jenkins (1.502), set up a job that runs "env" and build it. Then go to the global configuration, click Save. Then build the job again. Compare the output from env command: The environment variables BUILD_URL, JOB_URL, JENKINS_URL and HUDSON_URL are missing from the first run and only appear after you have visited global configuration AND clicked the Save button. It is not enough to visit the global configuration. You have to click the Save button. This really is a bug. Not a huge bug and there is a good workaround. I'm not sure if anyone would set up a real Jenkins instance without even once visiting the global configuration... but it is a bug 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] (JENKINS-13407) Jenkins does not run sbt builds when the process is in the background
Sami Tikka commented on JENKINS-13407 Jenkins does not run sbt builds when the process is in the background I could not reproduce the problem. Could you tell me the exact command line you use to run Jenkins and the exact command line you use to build in Jenkins 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] (JENKINS-14112) The execution (build) of Project will fail on mkdir on remote disk.
Sami Tikka commented on JENKINS-14112 The execution (build) of Project will fail on mkdir on remote disk. Have you read https://wiki.jenkins-ci.org/display/JENKINS/My+software+builds+on+my+computer+but+not+on+Jenkins ? My understanding is that drive mappings done by the logged-in user are not necessarily available for the Jenkins user. I think you have two possibilities: Run Jenkins in CMD window in your logged-in user session or Use something like https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep to set up network drives so they exist before checkout happens. Still, I fail to see why this is a Jenkins bug. Maybe a Jenkins feature request but also I haven't yet seen what the feature would be. Maybe more clarification is needed? (By the way, personally I would always try to check out and build code on local disk. Network disk can rarely offer comparable performance to local disk and build speed is essential for continuous integration.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-16225) Add note to env-vars.html so user knows that Environment variables configuration is requried to export JENKINS_URL, JOB_URL, BUILD_URL
Sami Tikka commented on JENKINS-16225 Add note to env-vars.html so user knows that Environment variables configuration is requried to export JENKINS_URL, JOB_URL, BUILD_URL The JENKINS_URL and BUILD_URL and other *_URL environment variables should be there in the build step environment. To compute those URLs Jenkins needs to know its own address. Jenkins makes a couple of bad guesses to what its own address should be and I think it has failed for some reason. Is there anything in the Jenkins log file that would give a hint to what went wrong during startup? If you are running Jenkins on a Mac installed from the Jenkins Mac installer, the Jenkins output goes to system log, so you can use Console.app to view and search it. You could also go to the Jenkins global configuration and explicitly set the Jenkins address. That would remove the need for Jenkins to guess. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-14880) BUILD_ID doesn't contain hostname if config hasn't been saved after initial startup
Sami Tikka commented on JENKINS-14880 BUILD_ID doesnt contain hostname if config hasnt been saved after initial startup What should Jenkins use as its own address if an address has not been provided? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-14375) Xcode plugin: Can't use environment variable in Custom xcodebuild arguments field
Sami Tikka assigned JENKINS-14375 to Francis Labrie Xcode plugin: Cant use environment variable in Custom xcodebuild arguments field Please check if this bug has been fixed and then close it. Thanks. Change By: Sami Tikka (03/Feb/13 12:55 AM) Assignee: FrancisLabrie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-14375) Xcode plugin: Can't use environment variable in Custom xcodebuild arguments field
Sami Tikka commented on JENKINS-14375 Xcode plugin: Cant use environment variable in Custom xcodebuild arguments field The PR was merged 2 months ago. Maybe the bug reporter could test it and close if it has been 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] (JENKINS-13407) Jenkins does not run sbt builds when the process is in the background
Sami Tikka commented on JENKINS-13407 Jenkins does not run sbt builds when the process is in the background My guess is Jenkins is passing and inherited stdin to the build script, which then attempts to read it. Hmm... I might be tempted to take a look at this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15178) MacOS X package version does not output to logfile
Sami Tikka commented on JENKINS-15178 MacOS X package version does not output to logfile Jenkins logs to stdout/stderr, and for launch daemons the default destination for those is the system log. You can access the system log either by using the Console.app or reading the file /var/log/system.log This is the standard behavior on the Mac OS platform. If the goal is to make Jenkins on Mac OS behave exactly like Jenkins on Linux, you must also include provide your own logrotate system. Unlike most Linux distress, Mac OS does not provide logrotate for log files other than /var/log/system.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
[JIRA] (JENKINS-16289) Please bundle uninstaller with Jenkins Mac install
Sami Tikka resolved JENKINS-16289 as Fixed Please bundle uninstaller with Jenkins Mac install The Mac version of Jenkins comes with an uninstaller. You can find it in folder /Library/Application Support/Jenkins. I admit it is a fairly new addition and was added only 6 months ago. Maybe the location of the uninstaller could be improved? I did consider placing it under /Applications/Jenkins but that isn't very usual for Mac software. Additionally, I used to make Mac software for a living and I had placed the uninstaller in the same directory with the application. Still, a frequently asked question in customer support was: "How do I uninstall this?" Change By: Sami Tikka (24/Jan/13 10:43 PM) Status: Open Resolved Fix Version/s: current 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
[JIRA] (JENKINS-15256) Unable to launch slave agent via SSH due to OutOfMemoryError
Sami Tikka commented on JENKINS-15256 Unable to launch slave agent via SSH due to OutOfMemoryError "java.lang.OutOfMemoryError: PermGen space" suggests the memory pool where classes are loaded in jvm has run out of memory. I do not think there is anything Jenkins can do about it. This can happen if you install a lot of plugins, for example. You can increase the size of that pool by adding this to the java command line: -XX:MaxPermSize=512m Of course, 512 megabytes might not be enough. Keep incrementing it until it works or use fewer plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15256) Unable to launch slave agent via SSH due to OutOfMemoryError
Sami Tikka commented on JENKINS-15256 Unable to launch slave agent via SSH due to OutOfMemoryError I would close this ticket but as it is owned by Kohsuke, maybe the decision should be his. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14112) The execution (build) of Project will fail on mkdir on remote disk.
Sami Tikka commented on JENKINS-14112 The execution (build) of Project will fail on mkdir on remote disk. I would close this ticket as invalid. This is not a bug in Jenkins but a feature of Windows remote disks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15906) Jenkins Xcode Plugin Packing .ipa file Fail
Sami Tikka commented on JENKINS-15906 Jenkins Xcode Plugin Packing .ipa file Fail A guess: Check what is the value of LANG environment variable in your shell where the build works. Set LANG to the same value in your build script. If Jenkins is started as a launch daemon, the environment not set up similarly to the environment of a full user login environment. I do not consider this a bug in Jenkins. I'm closing this ticket now. If you did in fact run Jenkins inside a logged-in user session, please re-open this ticket and provide more information on how Jenkins is installed and run. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14421) Cannot run Xcode instruments command with jenkins mac installer.
Sami Tikka commented on JENKINS-14421 Cannot run Xcode instruments command with jenkins mac installer. I just remembered I had written a related blog post some time ago: http://thingsyoudidntknowaboutjenkins.tumblr.com/post/23721538439/different-ways-to-run-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
[JIRA] (JENKINS-14016) Xcode codesign fails in Jenkins but works as user running Jenkins
Sami Tikka resolved JENKINS-14016 as Duplicate Xcode codesign fails in Jenkins but works as user running Jenkins Not a bug in Jenkins, more like a feature request. See the comments in the linked duplicate case. Change By: Sami Tikka (18/Jul/12 11:41 PM) Status: Open Resolved Fix Version/s: current Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13407) Jenkins does not run sbt builds when the process is in the background
[
https://issues.jenkins-ci.org/browse/JENKINS-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162979#comment-162979
]
Sami Tikka commented on JENKINS-13407:
--
The next time Jenkins hangs like that, could you run {{sample}} on it? It would
tell us what Jenkins was trying to do when it hanged.
Jenkins does not run sbt builds when the process is in the background
-
Key: JENKINS-13407
URL: https://issues.jenkins-ci.org/browse/JENKINS-13407
Project: Jenkins
Issue Type: Bug
Components: sbt
Affects Versions: current
Environment: awt.nativeDoubleBufferingtrue
awt.toolkit apple.awt.CToolkit
executable-war/Users/dwalend/bin/jenkins.war
file.encoding MacRoman
file.encoding.pkg sun.io
file.separator/
ftp.nonProxyHosts local|*.local|169.254/16|*.169.254/16
gopherProxySetfalse
http.nonProxyHostslocal|*.local|169.254/16|*.169.254/16
hudson.diyChunkingtrue
java.awt.graphicsenv apple.awt.CGraphicsEnvironment
java.awt.headless true
java.awt.printerjob apple.awt.CPrinterJob
java.class.path /Users/dwalend/bin/jenkins.war
java.class.version50.0
java.endorsed.dirs
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/endorsed
java.ext.dirs
/Library/Java/Extensions:/System/Library/Java/Extensions:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/ext
java.home /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
java.io.tmpdir/var/folders/bd/935mn63j479fnh3c7yv0v_9cgn/T/
java.library.path
.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
java.runtime.name Java(TM) SE Runtime Environment
java.runtime.version 1.6.0_29-b11-402-11D50d
java.specification.name Java Platform API Specification
java.specification.vendor Sun Microsystems Inc.
java.specification.version1.6
java.vendor Apple Inc.
java.vendor.url http://www.apple.com/
java.vendor.url.bug http://bugreport.apple.com/
java.version 1.6.0_29
java.vm.info mixed mode
java.vm.name Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.nameJava Virtual Machine Specification
java.vm.specification.vendor Sun Microsystems Inc.
java.vm.specification.version 1.0
java.vm.vendorApple Inc.
java.vm.version 20.4-b02-402
jna.platform.library.path /usr/lib:/usr/lib
line.separator
mail.smtp.sendpartial true
mail.smtps.sendpartialtrue
mrj.build 11D50d
mrj.version 1070.1.6.0_29-402
os.arch x86_64
os.name Mac OS X
os.version10.7.3
path.separator:
socksNonProxyHostslocal|*.local|169.254/16|*.169.254/16
sun.arch.data.model 64
sun.boot.class.path
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jsfd.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/classes.jar:/System/Library/Frameworks/JavaVM.framework/Frameworks/JavaRuntimeSupport.framework/Resources/Java/JavaRuntimeSupport.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/ui.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/laf.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/sunrsasign.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jsse.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/jce.jar:/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Classes/charsets.jar
sun.boot.library.path
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries
sun.cpu.endianlittle
sun.cpu.isalist
sun.io.unicode.encoding UnicodeLittle
sun.java.command /Users/dwalend/bin/jenkins.war
sun.java.launcher SUN_STANDARD
sun.jnu.encoding MacRoman
sun.management.compiler HotSpot 64-Bit Tiered Compilers
sun.os.patch.levelunknown
svnkit.http.methods Digest,Basic,NTLM,Negotiate
svnkit.ssh2.persistentfalse
user.country US
user.dir /Users/dwalend/projects/ogregev
user.home /Users/dwalend
user.language en
user.name dwalend
user.timezone America/New_York
Reporter: David Walend
Assignee: uzilan
Priority: Minor
I'm running jenkins via java -jar jenkins.war in bash on a Mac.
My project is really just doing sbt compile.
If I have jenkins running in the foreground, everything works fine. But if I
run it in the background (to do other things in the same shell), jenkins
becomes unresponsive as soon as I ask it to build something. If I move the
process to the foreground again, suddenly it builds everything I asked it to.
It's pretty minor as bugs go, but it is odd enough I felt I should report it.
--
This
[JIRA] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast
[ https://issues.jenkins-ci.org/browse/JENKINS-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161751#comment-161751 ] Sami Tikka commented on JENKINS-13467: -- OK, I have now had a chance to look into this. I'm pretty sure this is not a Jenkins bug, but a misconfiguration. The Jenkins URL in global configuration is supposed to be a URL and if it is set to debian-amd64-chef or 0.0.0.0, they are not valid URLs and thus it is only appropriate that Jenkins should log a warning. As far as I can see from this bug report, the only problem it causes is the warning and a stack trace, which can be easily corrected by entering a valid URL into Jenkins global configuration. If I have misinterpreted the situation, please correct me. Otherwise I will close this bug in a few days. Thank you. WARNING: Failed to advertise the service to DNS multi-cast --- Key: JENKINS-13467 URL: https://issues.jenkins-ci.org/browse/JENKINS-13467 Project: Jenkins Issue Type: Bug Components: jenkins-plugin-runtime Affects Versions: current Environment: Jenkins ver. 1.459 on Linux CentOS 6 Reporter: Samuel Lopez Assignee: Sami Tikka Priority: Minor WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:617) at java.net.URL.init(URL.java:480) at java.net.URL.init(URL.java:429) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.init(URL.java:522) ... 7 more Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13467) WARNING: Failed to advertise the service to DNS multi-cast
[ https://issues.jenkins-ci.org/browse/JENKINS-13467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sami Tikka reassigned JENKINS-13467: Assignee: Samuel Lopez (was: Sami Tikka) WARNING: Failed to advertise the service to DNS multi-cast --- Key: JENKINS-13467 URL: https://issues.jenkins-ci.org/browse/JENKINS-13467 Project: Jenkins Issue Type: Bug Components: jenkins-plugin-runtime Affects Versions: current Environment: Jenkins ver. 1.459 on Linux CentOS 6 Reporter: Samuel Lopez Assignee: Samuel Lopez Priority: Minor WARNING: Failed to advertise the service to DNS multi-cast java.net.MalformedURLException at java.net.URL.init(URL.java:617) at java.net.URL.init(URL.java:480) at java.net.URL.init(URL.java:429) at hudson.DNSMultiCast.init(DNSMultiCast.java:45) at jenkins.model.Jenkins.init(Jenkins.java:787) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:217) Caused by: java.lang.NullPointerException at java.net.URL.init(URL.java:522) ... 7 more Apr 13, 2012 12:25:26 AM hudson.WebAppMain$2 run INFO: Jenkins is fully up and running -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12798) Plugin does not generate test-reports
[ https://issues.jenkins-ci.org/browse/JENKINS-12798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159818#comment-159818 ] Sami Tikka commented on JENKINS-12798: -- Please provide more details. E.g. a sample build output which fails to produce test-reports file is needed. Also, please report which OS X version you are using and which Xcode. What version of Jenkins and what version of the Xcode plugin? Plugin does not generate test-reports - Key: JENKINS-12798 URL: https://issues.jenkins-ci.org/browse/JENKINS-12798 Project: Jenkins Issue Type: Bug Components: xcode Affects Versions: current Environment: Mac OSX Reporter: Robert Labus Fix For: current A plugin should parse a build output and produce test-reports file, but it's simply not doing it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
