[JIRA] (JENKINS-40468) Ability to force clone
Title: Message Title cowwoc commented on JENKINS-40468 Re: Ability to force clone No need. Users can simply invoke "deleteDir()" before "checkout()" and this will have the desired effect. Also, this design scales better than stuffing this functionality in the SCM plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40468) Ability to force clone
Title: Message Title cowwoc closed an issue as Not A Defect Jenkins / JENKINS-40468 Ability to force clone Change By: cowwoc Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40468) Ability to force clone
Title: Message Title cowwoc created an issue Jenkins / JENKINS-40468 Ability to force clone Issue Type: Bug Assignee: Unassigned Components: mercurial-plugin Created: 2016/Dec/15 6:16 AM Priority: Minor Reporter: cowwoc Unlike git, the Mercurial "checkout" command only offers a "Clean Build" option which is used to purge the working directory. We need an equivalent of the "Wipe workspace and force clone" functionality available to the git plugin. Specifically, I am running into problems where the local repository contains more commits than the remote which is causing problems. I need to force a re-clone; otherwise, the script will need to be able to recover from a partially-updated repository after a failed build. Add Comment
[JIRA] (JENKINS-16151) Maven "release:perform" cannot find hg
Title: Message Title cowwoc commented on JENKINS-16151 Re: Maven "release:perform" cannot find hg I believe we can close this issue because in the new Pipeline design users will need to add HG to the PATH anyway (to interact with it from a shell, etc). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40423) pipeline-stage-tags-metadata v0.7 is missing
Title: Message Title cowwoc commented on JENKINS-40423 Re: pipeline-stage-tags-metadata v0.7 is missing Something was screwed up with Jenkins. I had Pipeline: Model Definition v0.7.1 in both the Installed and Available tabs. Installing it a second time seems to have fixed the problem. Did you deploy the same plugin version twice? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40423) pipeline-stage-tags-metadata v0.7 is missing
Title: Message Title cowwoc commented on JENKINS-40423 Re: pipeline-stage-tags-metadata v0.7 is missing Andrew, Ah, looks like the error message has changed. I have "Pipeline: Stage Tags Metadata v0.7.1" installed, but now Jenkins still complains: Pipeline: Model Definition v0.7.1 pipeline-model-api v0.7.1 is missing. To fix, install v0.7.1 or later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40423) pipeline-stage-tags-metadata v0.7 is missing
Title: Message Title cowwoc commented on JENKINS-40423 Re: pipeline-stage-tags-metadata v0.7 is missing Same here. Please reopen this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40423) pipeline-stage-tags-metadata v0.7 is missing
Title: Message Title cowwoc created an issue Jenkins / JENKINS-40423 pipeline-stage-tags-metadata v0.7 is missing Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Dec/13 9:44 PM Priority: Minor Reporter: cowwoc Upon upgrading to Model Definition v0.7 I get the following error message in the "Manage Jenkins" screen: Pipeline: Model Definition v0.7 pipeline-stage-tags-metadata v0.7 is missing. To fix, install v0.7 or later. It's not clear what, if anything, I need to install to fix this. I couldn't find a plugin corresponding to pipeline-stage-tags-metadata v0.7 Add Comment
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Joe George For sure, share it. Ideally the author of this plugin will pull in your changes so we will get it out of the box standard. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. As far as I can tell, the only way to authenticate properly under Windows is to pass the username/password to an HTTPS url. See http://stackoverflow.com/a/33630506/14731 and JENKINS-28335 for more details. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
cowwoc commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Beware: ssh-agent will not currently work under windows: JENKINS-28279 ("git plugin", such as the "checkout" task will fail to authenticate) As far as I can tell, the only option under Windows is to pass the username/password to an HTTPS url: http://stackoverflow.com/a/33630506/14731
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
I could swear I had this working recently (as mentioned above) but now I am getting a slightly different problem from you guys. I had this working in the past, but it now looks like I am getting a different problem from you.1. ssh-agent seems to launch successfully:{code}[ssh-agent] Using credentials cowwoc[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/tomcat-native ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Started.{code}2. But git.exe is not using it:{code}debug1: Authentications that can continue: publickeydebug1: Next authentication method: publickeydebug1: Offering RSA public key: /c/Users/builds/.ssh/id_rsadebug1: Server accepts key: pkalg ssh-rsa blen 535debug1: read_passphrase: can't open /dev/tty: No such device or address{code}(I got the above debugging output by setting system property GIT_SSH_COMMAND="ssh -v" as mentioned at http://stackoverflow.com/a/36038548/14731)*UPDATE*: I think I get it now. "git in a shell" works fine, but "git plugin" is not. This seems to be a known problem . See https : JENKINS-20356 //groups . google.com/forum/#!topic/jenkinsci-users/4yXiBwwthMg At first glance, it seems you can workaround this problem by using an HTTPS URL for "git checkout" (as opposed to ssh). This gets around the "git plugin" bug (it uses the credentials from Jenkins instead of from ssh-agent).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
I could swear I had this working recently (as mentioned above) but now I am getting a slightly different problem from you guys. I had this working in the past, but it now looks like I am getting a different problem from you.1. ssh-agent seems to launch successfully:{code}[ssh-agent] Using credentials cowwoc[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/tomcat-native ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Started.{code}2. But git.exe is not using it:{code}debug1: Authentications that can continue: publickeydebug1: Next authentication method: publickeydebug1: Offering RSA public key: /c/Users/builds/.ssh/id_rsadebug1: Server accepts key: pkalg ssh-rsa blen 535debug1: read_passphrase: can't open /dev/tty: No such device or address{code}(I got the above debugging output by setting system property GIT_SSH_COMMAND="ssh -v" as mentioned at http://stackoverflow.com/a/36038548/14731) *UPDATE*: I think I get it now. "git in a shell" works fine, but "git plugin" is not. This seems to be a known problem: JENKINS-20356.At first glance, it seems you can workaround this problem by using an HTTPS URL for "git checkout" (as opposed to ssh). This gets around the "git plugin" bug (it uses the credentials from Jenkins instead of from ssh-agent).
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
I am could swear I had this working recently (as mentioned above) but now having I am getting a similar slightly different problem as Will and Joe reported from you guys. I had this working in the past , which is to say that "git checkout" is ignoring but it now looks like I am getting a different problem from you.1. ssh-agent and failing with seems to launch successfully : {code} [ssh-agent] Using credentials cowwoc[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/tomcat-native ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Started. {code} ERROR 2. But git.exe is not using it : Error cloning remote repo 'origin' stderr {code}debug1 : Permission denied ( Authentications that can continue: publickey ) debug1: Next authentication method: publickeydebug1: Offering RSA public key: /c/Users/builds/ . ssh/id_rsadebug1: Server accepts key: pkalg ssh-rsa blen 535debug1: read_passphrase: can't open /dev/tty: No such device or address {code} How did you guys enable debug output from git? ( I want to figure out whether it's failing due to got the same error you pasted above debugging output by setting system property GIT_SSH_COMMAND="ssh -v" as mentioned at http://stackoverflow . com/a/36038548/14731)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
cowwoc edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
[~wsaxon] I am now having a similar problem as Will and Joe reported, which is to say that "git checkout" is ignoring ssh-agent and failing with:{code}ERROR: Error cloning remote repo 'origin'stderr: Permission denied (publickey).{code}How did you guys enable debug output from git? I want to figure out whether it's failing due to the same error you pasted.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Will Saxon I am now having a similar problem as Will and Joe reported, which is to say that "git checkout" is ignoring ssh-agent and failing with: ERROR: Error cloning remote repo 'origin' stderr: Permission denied (publickey). How did you guys enable debug output from git? I want to figure out whether it's failing due to the same error you pasted. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40050) JGit fails to find translation bundles
Title: Message Title cowwoc commented on JENKINS-40050 Re: JGit fails to find translation bundles All agents are running the same JDK version. The problem seems to be specific the environment though because if I blow away the slave VM and restart from a snapshot then I no longer see the error. I ran across this error a few times and every time the machine goes into this "bad state" it will keep on getting the error forever, but I'm not sure how to get it into the bad state in the first place. One idea that comes to mind is that maybe the Jenkins master is in the middle of running something on the slaves when I forcibly restart the instance (Windows restart service). Maybe the git plugin thinks the JGit files are fully installed but in fact the package is only partially extracted. Just a thought... I'll let you know if I find a way to reproduce this on demand. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title cowwoc commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Will's installation instructions for Windows worked perfectly (hint: Jenkins expects a 32-bit DLL, even on a 64-bit OS). To the author of this plugin, please update the official documentation with these steps! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40050) JGit fails to find translation bundles
Title: Message Title cowwoc commented on JENKINS-40050 Re: JGit fails to find translation bundles Mark Waite I appreciate the detailed response. I have a Jenkins pipeline project that reproduces this error 100% of the time. Unfortunately, I don't have a minimal testcase for you. Is it possible for me to grant you access to my Jenkins instance, in order for you to debug this further? It might help you figure out what sequence of steps are necessary to reproduce this on your end. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40050) JGit fails to find translation bundles
Title: Message Title cowwoc updated an issue Jenkins / JENKINS-40050 JGit fails to find translation bundles Change By: cowwoc Environment: Jenkins 2.33 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40050) JGit fails to find translation bundles
Title: Message Title cowwoc created an issue Jenkins / JENKINS-40050 JGit fails to find translation bundles Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Nov/26 3:12 AM Priority: Minor Reporter: cowwoc I have been using JGit without a problem for a while but all of a sudden my build is failing with the following exception: org.eclipse.jgit.errors.TranslationBundleLoadingException: Loading of translation bundle failed for [org.eclipse.jgit.internal.JGitText, en_US] at org.eclipse.jgit.nls.TranslationBundle.load(TranslationBundle.java:168) at org.eclipse.jgit.nls.GlobalBundleCache.lookupBundle(GlobalBundleCache.java:96) at org.eclipse.jgit.nls.NLS.get(NLS.java:132) at org.eclipse.jgit.nls.NLS.getBundleFor(NLS.java:118) at org.eclipse.jgit.internal.JGitText.get(JGitText.java:59) at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:859) at org.eclipse.jgit.transport.FetchProcess.askForIsComplete(FetchProcess.java:340) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:160) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1201) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:128) at org.jenkinsci.plugins.gitclient.JGitAPIImpl$2.execute(JGitAPIImpl.java:606) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50)
[JIRA] (JENKINS-39706) JNLP missing "permissions" manifest entry
Title: Message Title cowwoc updated an issue Jenkins / JENKINS-39706 JNLP missing "permissions" manifest entry Change By: cowwoc Environment: Windows 10, 64-bit Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-39706) JNLP missing "permissions" manifest entry
Title: Message Title cowwoc created an issue Jenkins / JENKINS-39706 JNLP missing "permissions" manifest entry Issue Type: Bug Assignee: Unassigned Components: core, remoting Created: 2016/Nov/14 2:40 AM Priority: Minor Reporter: cowwoc Repro steps: 1. Launch https://jenkins-ci.org/jenkins.jnlp from a Windows machine running JDK 1.8.0_112. 2. Error dialog will pop up: Your security settings have blocked an application from running due to missing a "Permissions" manifest attribute in the main jar. Reproducible 100% of the time. See http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/security/manifest.html and http://stackoverflow.com/a/21427782/14731 for an explanation of the Permissions attribute. Add Comment
[JIRA] (JENKINS-39605) Documentation for "parallel" step is broken
Title: Message Title cowwoc updated an issue Jenkins / JENKINS-39605 Documentation for "parallel" step is broken Change By: cowwoc Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-39605) Documentation for "parallel" step is broken
Title: Message Title cowwoc created an issue Jenkins / JENKINS-39605 Documentation for "parallel" step is broken Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Nov/08 11:32 PM Priority: Critical Reporter: cowwoc Looking at https://jenkins.io/doc/pipeline/steps/workflow-cps/#parallel-execute-in-parallel I see: parallel: Execute in parallel org.kohsuke.stapler.NoStaplerConstructorException: There’s no @DataBoundConstructor on any constructor of class org.jenkinsci.plugins.workflow.cps.steps.ParallelStep Notice that the description is missing. Add Comment
[JIRA] (JENKINS-39597) Plugin produces broken links
Title: Message Title cowwoc created an issue Jenkins / JENKINS-39597 Plugin produces broken links Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage-plugin Created: 2016/Nov/08 8:25 PM Priority: Minor Reporter: cowwoc 1. Run Jenkins with a non-standard context path (e.g. --prefix=/builds) 2. Install Disk Usage plugin 3. Open project page 4. Notice that images associated with the Disk Usage plugin are pointing to "/plugin/disk-usage/icons/directory16.png" ignoring the context-path Expected behavior: links should be relative to "/builds/plugin/disk-usage/etc" Add Comment
[JIRA] [core] (JENKINS-15252) Why is Prevent Cross Site Request Forgery exploits disabled by default?
cowwoc commented on JENKINS-15252 Why is Prevent Cross Site Request Forgery exploits disabled by default? That sounds okay to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
cowwoc commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel I suggest doing the opposite. Set the value to a small number, like 10 seconds, to make the issue easier to reproduce and investigate a fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19465) OSX Slave hangs while being launched
cowwoc commented on JENKINS-19465 OSX Slave hangs while being launched I can no longer reproduce this issue in version 1.570. How about the other reporters? Does this issue still happen for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-19396) Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
cowwoc commented on JENKINS-19396 Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger @Daniel Beck, Sorry, the last comment was directed at you. I am getting a very verbose syntax: [pool-3-thread-1] INFO org.apache.maven.cli.transfer.Slf4jMavenTransferListener - Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.4/maven-install-plugin-2.4.pom It looks like the logging pattern is at fault. I am expecting the line to begin with "Downloading". Is there any way to make it less verbose? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux 1.0.11-beta3 works for me. Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux Is this a bug in Jenkins or in the xvfb 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux Both exceptions occur under Jenkins 1.564. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux I get the following exception in 1.0.11-beta: javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.model.AbstractProject$AbstractProjectDescriptor.doCheckAssignedLabelString(Ljava/lang/String;)Lhudson/util/FormValidation; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc edited a comment on JENKINS-23155 Only run plugin under Linux I get the following exception in version 1.0.11-beta with Jenkins 1.564: javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.model.AbstractProject$AbstractProjectDescriptor.doCheckAssignedLabelString(Ljava/lang/String;)Lhudson/util/FormValidation; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux I just got a second exception but, unlike the previous one, this one actually causes the build to fail: FATAL: hudson.model.labels.LabelExpression$Not cannot be cast to hudson.model.labels.LabelAtom java.lang.ClassCastException: hudson.model.labels.LabelExpression$Not cannot be cast to hudson.model.labels.LabelAtom at jenkins.model.Jenkins.getLabelAtom(Jenkins.java:1600) at hudson.model.Label.parse(Label.java:556) at org.jenkinsci.plugins.xvfb.XvfbBuildWrapper.setUp(XvfbBuildWrapper.java:537) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:653) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) I got this exception when trying to run the job under OSX. Other platforms (Windows and Linux) did not get this exception. The plugin is configured to only run under Linux so I don't understand why it's triggering this failure under OSX. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux (This issue should be a feature request, not a bug report) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc created JENKINS-23155 Only run plugin under Linux Issue Type: Bug Assignee: zregvart Components: xvfb Created: 22/May/14 3:24 PM Description: I'd like to enable the xvfb plugin for a job that may run on multiple platforms. Because the job isn't node-linked, I need a mechanism to ensure that xvfb is only launched for certain nodes but not others. Can you provide such a mechanism? Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvfb] (JENKINS-23155) Only run plugin under Linux
cowwoc commented on JENKINS-23155 Only run plugin under Linux I prefer adding a label mechanism to the job configuration. Meaning "Start Xvfb before the build, and shut it down after ... but only for these labels". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23163) xserver 1.13 does not support -displayfd
cowwoc created JENKINS-23163 xserver 1.13 does not support -displayfd Issue Type: Bug Assignee: zregvart Components: xvfb Created: 22/May/14 10:50 PM Description: According to https://wiki.jenkins-ci.org/display/JENKINS/Xvfb+Plugin the "Let Xvfb choose display name" requires "xserver 1.13 or newer". On my machine, "Xorg -version" returns: X.Org X Server 1.13.3 Release Date: 2013-03-07 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.42-37-generic x86_64 Ubuntu Current Operating System: Linux ubuntu 3.8.0-39-generic #58~precise1-Ubuntu SMP Fri May 2 21:33:40 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-39-generic root=UUID=6ba2eac6-1c3f-4c59-afe7-641ae6dcad14 ro quiet splash Build Date: 16 October 2013 04:46:41PM xorg-server 2:1.13.3-0ubuntu6~precise3 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.30.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. but Xvfb fails to start with: /usr/bin/Xvfb -displayfd 2 -screen 0 1024x768x24 -fbdir /home/builds/.jenkins/2014-05-22_18-38-033155263806738782739xvfb Unrecognized option: -displayfd use: X [:display] [option] -a # default pointer acceleration (factor) -acdisable access control restrictions -audit int set audit trail level -auth file select authorization file -brcreate root window with black background +bsenable any backing store support -bsdisable any backing store support -c turns off key-click c #key-click volume (0-100) -cc intdefault color visual class -nocursor disable the cursor -core generate core dump on fatal error -dpi int screen resolution in dots per inch -dpms disables VESA DPMS monitor control -deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs -f # bell base (0-100) -fc string cursor font -fn string default font name -fp string default font path -help prints message with these options -I ignore all remaining arguments -ld intlimit data space to N Kb -lf intlimit number of open files to N -ls intlimit stack space to N Kb -nolockdisable the locking mechanism -nolisten string don't listen on protocol -noreset don't reset after last client exists -background [none] create root window with no background -nr(Ubuntu-specific) Synonym for -background none -reset reset after last client exists -p # screen-saver pattern duration (minutes) -pnaccept failure to listen on all ports -nopn reject failure to listen on all ports -r turns off auto-repeat r turns on auto-repeat -render [default|mono|gray|color] set render color alloc policy -retro start with classic stipple and cursor -s # screen-saver timeout (minutes) -t # default pointer threshold (pixels/t) -terminate terminate at server reset -to # connection time out -tst disable testing extensions ttyxx server started from init on /dev/ttyxx v video blanking for screen-saver -v screen-saver without video blanking -wmWhenMapped default backing-store -wrcreate root window with white background -maxbigreqsize set maximal bigrequest size +xinerama Enable XINERAMA extension -xinerama Disable XINERAMA extension -dumbSched Disable smart scheduling, enable old behavior -schedInterval int Set scheduler interval in msec -sigstop Enable SIGSTOP based
[JIRA] [maven2] (JENKINS-19396) Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger
cowwoc commented on JENKINS-19396 Extra logging added to Maven builds makes the build log hard to read - org.apache.maven.cli.event.ExecutionEventLogger @Christian, I have the Maven Integration plugin 2.2 installed, and I'm still seeing org.apache.maven.cli.event.ExecutionEventLogger everywhere. Shouldn't this issue be 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] [www] (JENKINS-22735) Upgrade JIRA
cowwoc created JENKINS-22735 Upgrade JIRA Issue Type: Bug Assignee: Unassigned Components: www Created: 23/Apr/14 4:10 PM Description: Please update the JIRA instance hosted on jenkins-ci.org. It is severely out of date, which means you're missing critical security fixes and more importantly a lot of new social features like being able to refer to @users in comments. I think performance is improved too. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [pollscm] (JENKINS-22678) Ability to restrict Poll SCM to a specific path
cowwoc created JENKINS-22678 Ability to restrict Poll SCM to a specific path Issue Type: Improvement Assignee: Vincent Latombe Components: pollscm Created: 18/Apr/14 8:13 PM Description: Use-case: We have one repository for multiple operating systems, but different Jenkins jobs per operating system. Each job wants to get triggered if it's platform-specific files got modified, but not when the other platforms got modified. We should be able to specify multiple filespec entries, where a filespec entry could be a fully-specified path, or a path containing a wildcard. http://stackoverflow.com/q/5243593/14731 shows there is demand for this, but I'm using Mercurial instead of git. This feature should really apply across all SCMs. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22680) Ability to restrict Poll SCM to a specific path
cowwoc created JENKINS-22680 Ability to restrict Poll SCM to a specific path Issue Type: Improvement Assignee: Unassigned Components: core Created: 18/Apr/14 9:48 PM Description: Use-case: We have one repository for multiple operating systems, but different Jenkins jobs per operating system. Each job wants to get triggered if it's platform-specific files got modified, but not when the other platforms got modified. We should be able to specify multiple filespec entries, where a filespec entry could be a fully-specified path, or a path containing a wildcard. http://stackoverflow.com/q/5243593/14731 shows there is demand for this, but I'm using Mercurial instead of git. This feature should really apply across all SCMs. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [pollscm] (JENKINS-22678) Ability to restrict Poll SCM to a specific path
cowwoc commented on JENKINS-22678 Ability to restrict Poll SCM to a specific path Moved to JENKINS-22680. 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] [mercurial] (JENKINS-5396) Support tags instead of branches
cowwoc commented on JENKINS-5396 Support tags instead of branches (Confused) Is this fix part of the public plugin? Or is it not released to the public yet? Last time I checked I didn't see a separate "tag" UI field. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21944) Documentation contains broken link
cowwoc commented on JENKINS-21944 Documentation contains broken link Sorry. I remember looking for an Edit button, but at the time I did not see it. I see it now, though. Thanks for the head's up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, Will this fix jobs where malformed culprits were being copied from earlier builds, or do we need to manually "flush" the job history somehow? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I see. So just to make sure I understand correctly: Until a user makes a new commit, any existing jobs will keep on using the incorrect email address. Once a user makes a new commit, his email address will get corrected system-wide across all jobs. Alternatively, deleting the contents of the "builds" directory will remove all changelogs and force re-evaluation of the email address. Is that correct? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git] (JENKINS-21944) Documentation contains broken link
cowwoc created JENKINS-21944 Documentation contains broken link Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 25/Feb/14 5:13 AM Description: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin# contains a broken link to http://computercamp.cdwilson.us/jenkins-git-clone-via-ssh-on-windows-7-x64 I believe this link can be replaced by http://computercamp-cdwilson-us.tumblr.com/post/48589650930/jenkins-git-clone-via-ssh-on-windows-7-x64 Project: Jenkins Priority: Minor Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc
updated JENKINS-16332
Leading and trailing underscores are added to commiters email address, unable to send build notification
Guys,
I've managed to produce a minimal testcase for this bug.
Extract testcase.zip into $JENKINS_HOME/jobs
Run the job
You should get this output:
Started by user Gili Tzabari
[EnvInject] - Loading node environment variables.
Building remotely on MacOS X 10.8 in workspace /Users/builds/.jenkins/workspace/Test
[Test] $ /usr/local/bin/hg showconfig paths.default
ERROR: Workspace reports paths.default as https://bbs.darktech.org/code/test/
which looks different than https://cow...@bitbucket.org/cowwoc/test
so falling back to fresh clone rather than incremental update
$ /usr/local/bin/hg clone --rev default --noupdate https://cow...@bitbucket.org/cowwoc/test /Users/builds/.jenkins/workspace/Test
adding changesets
adding manifests
adding file changes
added 19 changesets with 19 changes to 2 files
[Test] $ /usr/local/bin/hg update --rev default
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
[Test] $ /usr/local/bin/hg log --rev . --template {node}
[Test] $ /usr/local/bin/hg log --rev . --template {rev}
[Test] $ /usr/local/bin/hg log --rev 6ddb7626f1d05f3e67a4c92fa255ba32a5406020
changeset: 18:6ddb7626f1d0
tag: tip
user:Getcho Getchev getcho.getc...@gmail.com
date:Fri Feb 21 23:40:41 2014 +0200
summary: added line 10
[Test] $ /usr/local/bin/hg log --template "changeset node='{node}' author='{author|xmlescape}' rev='{rev}' date='{date}'msg{desc|xmlescape}/msgadded{file_adds|stringify|xmlescape}/addeddeleted{file_dels|stringify|xmlescape}/deletedfiles{files|stringify|xmlescape}/filesparents{parents}/parents/changeset\n" --rev default:0 --follow --prune 6ddb7626f1d05f3e67a4c92fa255ba32a5406020 --encoding UTF-8 --encodingmode replace
[Test] $ /bin/sh -xe /var/folders/ht/zq3sdm6s55j4cv6gvjtkc8vmgp/T/hudson4438504154854395225.sh
+ ./test.sh
/var/folders/ht/zq3sdm6s55j4cv6gvjtkc8vmgp/T/hudson4438504154854395225.sh: line 2: ./test.sh: No such file or directory
Build step 'Execute shell' marked build as failure
Invalid address: Getcho Getchev _getcho.getchev@gmail.com_
Invalid address: Gili Tzabari _gili.tzabari@gmail.com_
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE
Change By:
cowwoc
(23/Feb/14 6:05 AM)
Attachment:
testcase.zip
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, I am now 100% I am seeing: Jan 08, 2014 6:36:06 PM FINE hudson.model.User hudson.model.User$FullNameIdResolver@934e9b mapped First Last _first.last@gmail.com_ to First Last _first.last@gmail.com_ without: [JENKINS-16332] Suspicious fullName being stored: First Last _first.last@gmail.com_ ever being logged. It looks like you'll need to add more aggressive logging for us to track this down. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20204) Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file
cowwoc commented on JENKINS-20204 Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file Mark, This is not an option on OSX, where scripts must run as a normal user (not over SSH) otherwise you lose the ability to run the iOS simulator. JNLP support is a must. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20204) Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file
cowwoc commented on JENKINS-20204 Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file No pull request will do fix this. Jenkins needs a SSL certificate. Then you simply sign the JAR file with it and (I think) you're done. I believe that the only person who can do this is Kohsuke, since he owns the 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/groups/opt_out.
[JIRA] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
cowwoc commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @Randall First rule of security: anyone with physical access to a computer can subvert any protection you put in (they can remove the HD and probe it using an external Linux/OSX installation). I don't think it makes sense to protect against such a case. I can't believe you'd want to give Jenkins more permissions than it need (root privileges) because when it inevitably gets exploited (Jenkins is not the most secure software in the world) your entire OS just got exploited as well. I'd much rather run Jenkins under a normal (non-admin) user account. @Sami Tikka: I'm trying to run the iOS simulator under a Jenkins slave under OSX. As far as I know, this requires us to install Jenkins under ~/LaunchAgents. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I didn't see such a log entry but I will keep my eye open if this happens again. Mail-Ext just committed an interesting bugfix: https://issues.jenkins-ci.org/browse/JENKINS-20215 Do you think this could have been at fault? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I didn't see such a log entry but I will keep my eye open if this happens again. The EMail-ext plugin just fixed an interesting bug: https://issues.jenkins-ci.org/browse/JENKINS-20215 Do you think this could have been at fault? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Okay, so to reiterate, I did not see [JENKINS-16332] Suspicious fullName being stored: First Last _first.last@gmail.com_ in the log file even though the problem occurred. Doesn't that imply that we need to add more logs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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
cowwoc commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @randall I don't buy the security argument for two reasons: There will always be security exploits. Security is a bottomless pit. As such, you are chasing more of a theoretical problem than a concrete one. We know for a fact that using ~/LaunchAgents fixes a much-needed use-case that cannot be run with LaunchDaemons. I would be more than happy to use a more secure solution if it was possible; but (as far as I can tell) it is not. Now, more concretely... The login plist/hook approaches force control back to the login screen immediately after logging in. How would you exploit that? I agree that we should get user consent for installing Jenkins. If anyone chooses to install it on their machine, we can (and should) explain what username will get used and that autologin will take place. Installing for "All Users": I still don't understand how this is more secure, but even if it is ... we'd still need to find a way to ensure that Jenkins doesn't run multiple times per computer. If my wife and I share the same computer, and each has their own profile, we don't want Jenkins to launch dialogs every time we log in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification @Jesse, I enabled this log a few weeks ago, so that's unlikely. That being said, the log did seem pretty short (2 pages long). Does Jenkins truncate the log on startup? Does it begin logging automatically or do I need to intervene manually every startup? Does it log to disk or just to memory? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
cowwoc commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @Sami Tikka, I don't see the point of ever installing Jenkins for all users. You always want to install it for one user, be that the current user or some other user. What I'd really like to see Jenkins' official installer install into the current user, and a unification of #jenkinsapp and https://github.com/rhwood/jenkins-slave-osx for installing Jenkins outside the current user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, I triggered a build that failed, and tried emailing the author: Invalid address: First Last _first.last@gmail.com_ I opened the logger and saw these two lines: Jan 08, 2014 6:36:06 PM FINE hudson.model.User hudson.model.User$FullNameIdResolver@934e9b mapped First Last _first.last@gmail.com_ to First Last _first.last@gmail.com_ Jan 08, 2014 6:36:06 PM FINE hudson.model.User hudson.model.User$FullNameIdResolver@934e9b mapped First Last _first.last@gmail.com_ to First Last _first.last@gmail.com_ (I've replaced the person's actual name with "First Last" but the rest of the log is identical) Does this help? Where do we go from 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/groups/opt_out.
[JIRA] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
cowwoc created JENKINS-21237 Jenkins should use LaunchAgents under OSX Issue Type: Improvement Assignee: Unassigned Components: core, xcode Created: 06/Jan/14 5:20 PM Description: JENKINS-9399 changed the Jenkins from using LaunchAgents to LaunchDaemons because, at the time, there were problems with running as an agent and using LaunchDaemons seems like the right approach. Two years later, it's pretty clear that using LaunchDaemons creates a whole host of problems which (I argue) are worse than using LaunchAgents in the first place. LaunchDaemons cannot launch GUI applications which means you cannot unit test iOS applications or launch with XCode "instructions"... both of which are in high demand. Anyway, I believe I discovered a way for us to have the best of both worlds: using LaunchAgents, having it auto-launch on boot, and preventing it from running under other users. I believe this will solve all outstanding problems. Configure Jenkins to use LaunchAgents (reverse JENKINS-9399). Install the plist into ~/Library/LaunchAgents instead of /Library/LaunchAgents to prevent it from getting triggered by other users logging in. Configure the Jenkins user to auto-login on startup, but return to the login menu immediately: http://www.tuaw.com/2011/03/07/terminally-geeky-use-automatic-login-more-securely/ Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, I just reproduced the problem. Unfortunately I didn't have the logger enabled so we missed an opportunity. I did notice something very interesting though: 1. A build failed and tried to send an email to an auto-generated user with underscores 2. I went into Jenkins - People and sure enough the user's email address had underscores 3. I rebooted Jenkins and went into Manage Jenkins - Manage Users and all of a sudden that same user no longer had underscores in the email address. It's not clear whether the reboot or Manage Users fixed the email address, but that's another clue of what's going on. I've enabled the logger, so the next time this happens I will catch 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-20779) Jenkins 1.541 crashes JVM on startup
cowwoc commented on JENKINS-20779 Jenkins 1.541 crashes JVM on startup Gentlemen, please avoid posting "me too!" comments. That's what the "Vote" button for (in the top-right corner). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20779) Jenkins 1.541 crashes JVM on startup
cowwoc created JENKINS-20779 Jenkins 1.541 crashes JVM on startup Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Nov/13 4:31 AM Description: Every time I upgrade from Jenkins 1.537 to 1.541 I get the following JVM crash on startup: # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x77d5df85, pid=1332, tid=9312 # # JRE version: 7.0_25-b17 # Java VM: Java HotSpot(TM) Client VM (23.25-b01 mixed mode windows-x86 ) # Problematic frame: # C [ntdll.dll+0x2df85] memset+0x45 # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # --- T H R E A D --- Current thread (0x24cc5800): JavaThread "Loading job WebRTC for iOS (SNAPSHOT)" daemon [_thread_in_native, id=9312, stack(0x2563,0x2568)] siginfo: ExceptionCode=0xc005, writing address 0x23fe9000 Registers: EAX=0x, EBX=0x2567e538, ECX=0x00f6, EDX=0x ESP=0x2567e460, EBP=0x2567e50c, ESI=0x, EDI=0x23fe9000 EIP=0x77d5df85, EFLAGS=0x00010206 Top of Stack: (sp=0x2567e460) 0x2567e460: 2567e530 77d6a531 23fe8bd8 0x2567e470: 0800 5230e66c 23fe8bd8 2567e570 0x2567e480: 0800 0080 0x2567e490: 41000445 000f 0020001e 00835818 0x2567e4a0: 0002 0050 23fe8bd8 001e 0x2567e4b0: 00835813 77e30440 00835818 0x2567e4c0: 0103 0800 23fe8bd8 2567e4ec 0x2567e4d0: 77d70fc4 00835818 007b17f0 001e Instructions: (pc=0x77d5df85) 0x77d5df65: 83 c7 01 83 e9 01 75 f6 8b c8 c1 e0 08 03 c1 8b 0x77d5df75: c8 c1 e0 10 03 c1 8b ca 83 e2 03 c1 e9 02 74 06 0x77d5df85: f3 ab 85 d2 74 0a 88 07 83 c7 01 83 ea 01 75 f6 0x77d5df95: 8b 44 24 08 5f c3 8b 44 24 04 c3 90 90 90 90 90 Register to memory mapping: EAX=0x is an unknown value EBX=0x2567e538 is pointing into the stack for thread: 0x24cc5800 ECX=0x00f6 is an unknown value EDX=0x is an unknown value ESP=0x2567e460 is pointing into the stack for thread: 0x24cc5800 EBP=0x2567e50c is pointing into the stack for thread: 0x24cc5800 ESI=0x is an unknown value EDI=0x23fe9000 is an unknown value Stack: [0x2563,0x2568], sp=0x2567e460, free space=313k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C [ntdll.dll+0x2df85] memset+0x45 C [ntdll.dll+0x3adf4] RtlGetFullPathName_UEx+0x3b C [ntdll.dll+0x4fb23] RtlGetFullPathName_U+0x1a C [kernel32.dll+0x2cb00] GetModuleHandleExA+0xb8 C [kernel32.dll+0x2d486] GetTempPathW+0x12 C [jna7474229582147247668.dll+0xcb67] Java_com_sun_jna_Native_initialize_1ffi_1type+0x3807 C [jna7474229582147247668.dll+0xc782] Java_com_sun_jna_Native_initialize_1ffi_1type+0x3422 C [jna7474229582147247668.dll+0x44ae] Java_com_sun_jna_Native_getString+0x9de C [jna7474229582147247668.dll+0x4d0e] Java_com_sun_jna_Native_invokeInt+0x2e j com.sun.jna.Native.invokeInt(JI[Ljava/lang/Object;)I+0 j com.sun.jna.Function.invoke([Ljava/lang/Object;Ljava/lang/Class;Z)Ljava/lang/Object;+333 j com.sun.jna.Function.invoke(Ljava/lang/Class;[Ljava/lang/Object;Ljava/util/Map;)Ljava/lang/Object;+214 j com.sun.jna.Library$Handler.invoke(Ljava/lang/Object;Ljava/lang/reflect/Method;[Ljava/lang/Object;)Ljava/lang/Object;+341 j com.sun.proxy.$Proxy30.GetTempPathW(ILcom/sun/jna/Pointer;)I+23 j hudson.util.jna.Kernel32Utils.getTempDir()Ljava/io/File;+18 j jenkins.diagnosis.HsErrPidList.init()V+55 v ~StubRoutines::call_stub V [jvm.dll+0x124afa] V [jvm.dll+0x1d224e] V [jvm.dll+0x124b7d] V [jvm.dll+0x12f95f] V [jvm.dll+0x12fceb] V [jvm.dll+0xd1108] C [java.dll+0x7d91] Java_sun_reflect_NativeConstructorAccessorImpl_newInstance0+0x11 j sun.reflect.NativeConstructorAccessorImpl.newInstance([Ljava/lang/Object;)Ljava/lang/Object;+72 J
[JIRA] [core] (JENKINS-20779) Jenkins 1.541 crashes JVM on startup
cowwoc commented on JENKINS-20779 Jenkins 1.541 crashes JVM on startup It's not clear whether this is the same issue as JENKINS-20630. The stack-trace looks 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/groups/opt_out.
[JIRA] [core] (JENKINS-18956) Cache location should be configurable through the GUI
cowwoc created JENKINS-18956 Cache location should be configurable through the GUI Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 26/Jul/13 6:50 PM Description: This is a follow-up to JENKINS-18578. The cache location should be configurable through the GUI. "Launch slave agents on Unix machines via SSH" does not allow specifying -jar-cache so we are expected to manually edit the machine configuration by hand, making it a maintenance nightmare. If this configuration were configurable by GUI, we could create a Slave "template" and copy it when creating new nodes. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
cowwoc commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable I disagree with the way this was resolved, so I filed JENKINS-18956. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18781) Configurable channel timeout for slaves
cowwoc created JENKINS-18781 Configurable channel timeout for slaves Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 16/Jul/13 9:30 PM Description: This issue is related to JENKINS-6817. I am running Jenkins slaves inside virtual machines. Sometimes these machines are overloaded and I get the following exception: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:713) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at $Proxy38.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.Maven.perform(Maven.java:327) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:773) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Is it possible to make the channel timeout configurable? I'd like to increase the value from, say 5 seconds, to 30 seconds or a minute. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15306) Ability to rebuild non-parameterized projects
cowwoc commented on JENKINS-15306 Ability to rebuild non-parameterized projects You're right except for one problem: there is no "build now" button in the build details view. You have to navigate up one level in order to "build now". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16331) Invoke top-level Maven targets ignores JVM Options
cowwoc created JENKINS-16331 Invoke top-level Maven targets ignores JVM Options Issue Type: Bug Assignee: Unassigned Components: maven Created: 13/Jan/13 6:03 PM Description: 1. Create a new Freestyle project. 2. Add two "Invoke top-level Maven targets" build steps 3. Click "advanced" on each build specify and specify "-Dhttps.protocols=SSLv3 -Dforce.http.jre.executor=true" for JVM Options 4. Run the project. Notice that the JVM options are never used. Instead, I get this output: [boost_snapshot] $ /home/builds/.jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_auto-install_/bin/mvn -Dsonatype_password= -Dsonatype_username= -Plinux-i386-gcc-debug deploy This is reproducible always. The reason I consider this critical is there is a critical Maven bug that we cannot work around without the ability to specify MAVEN_OPTS. See http://jira.codehaus.org/browse/MNG-5363 for more information. Project: Jenkins Priority: Critical Reporter: cowwoc This message is automatically generated by JIRA. 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-16331) Invoke top-level Maven targets ignores JVM Options
cowwoc commented on JENKINS-16331 Invoke top-level Maven targets ignores JVM Options Instead of specifying these values as "JVM Options", I specified them as "Properties" and it worked: https.protocols=SSLv3 force.http.jre.executor=true You can downgrade the priority of this bug but the issue remains: it's not clear why JVM Options are not passed on to "mvn". If you cannot pass on the options, they shouldn't be configurable in the first place. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15945) Auto-install of JDK fails on Windows Slave
cowwoc commented on JENKINS-15945 Auto-install of JDK fails on Windows Slave I believe this is a duplicate of JENKINS-15945 This message is automatically generated by JIRA. 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-5408) Quoting Issue with JDK Installer with Windows Slave
cowwoc commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave This issue also occurs on a Windows master. This bug report is almost 3 years old. Please fix 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
[JIRA] (JENKINS-16151) Maven release:perform cannot find hg
cowwoc commented on JENKINS-16151 Maven release:perform cannot find hg I posted this question to the Maven mailing list and it doesn't look like this is supported at this time: http://maven.40175.n5.nabble.com/How-to-specify-full-path-of-a-executable-for-a-scm-vendor-tp5463712p5739204.html Currently I am using the EnvInject plugin to add hg to the PATH but obviously this sort of thing should be handled automatically by Jenkins. Let me know what you think. This message is automatically generated by JIRA. 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-16151) Maven release:perform cannot find hg
cowwoc created JENKINS-16151 Maven release:perform cannot find hg Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: maven, mercurial Created: 17/Dec/12 5:18 PM Description: When I execute a build using a Maven 3 project, the initial checkout/out works fine (referencing "hg" using its full path) but subsequently the build fails as follows: [INFO] --- maven-release-plugin:2.1:perform (default-cli) @ cmake --- [INFO] Checking out the project to perform the release ... [INFO] Removing /Users/builds/.jenkins/workspace/cmake/target/checkout [INFO] EXECUTING: /bin/sh -c cd /Users/builds/.jenkins/workspace/cmake/target hg clone -r release-2.8.10-b1 https://cmake-maven-project.googlecode.com/hg/ /Users/builds/.jenkins/workspace/cmake/target/checkout [ERROR] EXECUTION FAILED Execution of cmd : clone failed with exit code: 127. Working directory was: /Users/builds/.jenkins/workspace/cmake/target Your Hg installation seems to be valid and complete. Hg version: NA (OK) In other words, it looks like Jenkins is smart enough to reference hg using its full path, but the hg scm vendor (used by "release:perform" goal) assumes "hg" is on the PATH. I couldn't find a workaround. I found one other discussion thread but no solution: http://maven.40175.n5.nabble.com/How-to-specify-full-path-of-a-executable-for-a-scm-vendor-td5463712.html To reproduce the problem, create a Maven3 project with the following build task: "clean:clean release:clean release:perform -Pmac -Dtag=release-2.8.10-b1 -DconnectionUrl=scm:hg:https://cmake-maven-project.googlecode.com/hg/" Environment: OSX 10.8.2 Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. 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-16151) Maven release:perform cannot find hg
cowwoc commented on JENKINS-16151 Maven release:perform cannot find hg Also, you should be able to reproduce this problem under Linux. I don't think it's OSX specific. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16005) CommandInstaller assumes write access to installation directory
cowwoc commented on JENKINS-16005 CommandInstaller assumes write access to installation directory If you click Install automatically then Installation directory disappears so I am not sure why you have it set I am using Hudson 1.492 and this isn't the case. Selecting "install automatically" does not cause the "installation directory" field to become hidden. Should I file an additional bug report for 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
[JIRA] (JENKINS-16022) Install Automatically does not hide Installation Directory field
cowwoc created JENKINS-16022 Install Automatically does not hide Installation Directory field Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 03/Dec/12 7:37 PM Description: When "Install automatically" is selected for the Mercurial tool, the field "Installation directory" is supposed to disappear, but in Jenkins 1.492 it does not. According to Jesse Glick this used to work under version 1.424 so this is a possible regression. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. 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-16005) CommandInstaller assumes write access to installation directory
cowwoc commented on JENKINS-16005 CommandInstaller assumes write access to installation directory Filed JENKINS-16022. This message is automatically generated by JIRA. 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-16005) Mercurial plugin assumes write access to installation directory
cowwoc commented on JENKINS-16005 Mercurial plugin assumes write access to installation directory I forgot to mention, my environment is Ubuntu 12.04, 64-bit edition. This message is automatically generated by JIRA. 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-16005) Mercurial plugin assumes write access to installation directory
cowwoc created JENKINS-16005 Mercurial plugin assumes write access to installation directory Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: mercurial Created: 03/Dec/12 2:08 AM Description: The Mercurial incorrectly assumes write-access to the Mercurial installation directory, triggering the following exception: hudson.util.IOException2: Failed to create a temp file on /usr at hudson.FilePath.createTextTempFile(FilePath.java:1163) at hudson.FilePath.createTextTempFile(FilePath.java:1114) at hudson.tools.CommandInstaller.performInstallation(CommandInstaller.java:82) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:203) at hudson.plugins.mercurial.MercurialInstallation.forNode(MercurialInstallation.java:103) at hudson.plugins.mercurial.MercurialSCM.findHgExe(MercurialSCM.java:201) at hudson.plugins.mercurial.HgExe.init(HgExe.java:80) at hudson.plugins.mercurial.MercurialSCM.clone(MercurialSCM.java:554) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:389) at hudson.model.AbstractProject.checkout(AbstractProject.java:1324) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at hudson.model.Run.execute(Run.java:1518) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.util.IOException2: remote file operation failed: /usr at hudson.remoting.Channel@26528fa4:Ubuntu 12.04 at hudson.FilePath.act(FilePath.java:848) at hudson.FilePath.act(FilePath.java:825) at hudson.FilePath.createTextTempFile(FilePath.java:1141) ... 18 more My configuration is as follows: Installation directory = /usr Executable = INSTALLATION/bin/hg Installation Automatically using command: "sudo apt-get install mercurial" Jenkin's user does not have general access to /usr, nor to "sudo". It only has executable permissions in /usr/bin and "sudoers" permission to "apt-get". Expected behavior: write temporary files into the path specified by the "java.io.tmpdir" system property. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. 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-16005) Mercurial plugin assumes write access to installation directory
cowwoc commented on JENKINS-16005 Mercurial plugin assumes write access to installation directory Workaround: Set "Installation directory" to Jenkins' home directory (which we have write access to) and "Tool Home" remains pointed to /usr. PS: What's the difference between "Installation directory" and "Tool Home"? There is no help tooltip for "Installation directory". This message is automatically generated by JIRA. 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-15514) Backup 'userContents' folder is missing help
cowwoc created JENKINS-15514 Backup userContents folder is missing help Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 13/Oct/12 5:02 AM Description: If you click the question-mark for option "Backup 'userContents' folder" you will get: "ERROR: Failed to load help file: Not Found" Fix Versions: current Project: Jenkins Priority: Trivial Reporter: cowwoc This message is automatically generated by JIRA. 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-3070) Uninstaller for plugins
cowwoc commented on JENKINS-3070 Uninstaller for plugins Kohsuke, I believe this is a bug at https://github.com/jenkinsci/jenkins/commit/29f6a5dd010d490569014bd0d045daea777521b3#L4R1 "This will remove the plugin binary from your $JENKINS_HOME": I suggest removing the word "your" "but it'll the configuration files of the plugin": you seem to be missing a word. What are you trying to say about the configuration files? This message is automatically generated by JIRA. 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-15385) Mercurial auto-installer does not work
cowwoc commented on JENKINS-15385 Mercurial auto-installer does not work Jesse, Good answer but shouldn't this be documented on the plugin page? Is it possible to convert this issue into a RFE for a documentation 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
[JIRA] (JENKINS-15385) Mercurial auto-installer does not work
cowwoc commented on JENKINS-15385 Mercurial auto-installer does not work Good news. I did just discover such a source. If you go to http://mercurial.selenic.com/wiki/Download#Linux_.28others.29 then click on Arch Linux you will notice they provide binary packages for both 32-bit and 64-bit linux. I just tried them and I can confirm they work great. A standalone version of Python is bundled. This message is automatically generated by JIRA. 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-15385) Mercurial auto-installer does not work
cowwoc commented on JENKINS-15385 Mercurial auto-installer does not work I would recommend adding xz support, assuming it's not too difficult to do. This message is automatically generated by JIRA. 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-9598) Include the Git plugin as part of the standard distribution
cowwoc commented on JENKINS-9598 Include the Git plugin as part of the standard distribution I agree with David. Improve the UI, as opposed to bundling unnecessary functionality into 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
[JIRA] (JENKINS-14993) JDK auto-installer for OSX
cowwoc commented on JENKINS-14993 JDK auto-installer for OSX Please increase the priority of this issue. Java is no longer bundled with OSX 10.8, which means that we can't even launch a slave node without manual intervention! Here is the output I get: BASH=/bin/bash BASH_ARGC=() BASH_ARGV=() BASH_EXECUTION_STRING=set BASH_LINENO=() BASH_SOURCE=() BASH_VERSINFO=([0]="3" [1]="2" [2]="48" [3]="1" [4]="release" [5]="x86_64-apple-darwin12") BASH_VERSION='3.2.48(1)-release' DIRSTACK=() EUID=502 GROUPS=() HOME=/Users/builds HOSTNAME=gili-mac HOSTTYPE=x86_64 IFS=$' \t\n' LOGNAME=builds MACHTYPE=x86_64-apple-darwin12 MAIL=/var/mail/builds OPTERR=1 OPTIND=1 OSTYPE=darwin12 PATH=/usr/bin:/bin:/usr/sbin:/sbin PPID=382 PS4='+ ' PWD=/Users/builds SHELL=/bin/bash SHELLOPTS=braceexpand:hashall:interactive-comments SHLVL=1 SSH_CLIENT='192.168.1.100 28990 22' SSH_CONNECTION='192.168.1.100 28990 192.168.1.101 22' TERM=dumb TMPDIR=/var/folders/88/8l3vck9x15zfc4y7f7w1lx_cgp/T/ UID=502 USER=builds _=bash [10/03/12 10:07:49] [SSH] Checking java version of java Couldn't figure out the Java version of java No Java runtime present, requesting install. 2012-10-03 10:08:08.032 java[385:100b] JLRequestRuntimeInstall: Error calling: CFMessagePortCreateRemote [10/03/12 10:07:49] [SSH] Checking java version of /usr/bin/java Couldn't figure out the Java version of /usr/bin/java No Java runtime present, requesting install. 2012-10-03 10:08:08.061 java[386:100b] JLRequestRuntimeInstall: Error calling: CFMessagePortCreateRemote [10/03/12 10:07:49] [SSH] Checking java version of /usr/java/default/bin/java Couldn't figure out the Java version of /usr/java/default/bin/java bash: /usr/java/default/bin/java: No such file or directory [10/03/12 10:07:49] [SSH] Checking java version of /usr/java/latest/bin/java Couldn't figure out the Java version of /usr/java/latest/bin/java bash: /usr/java/latest/bin/java: No such file or directory [10/03/12 10:07:49] [SSH] Checking java version of /usr/local/bin/java Couldn't figure out the Java version of /usr/local/bin/java bash: /usr/local/bin/java: No such file or directory [10/03/12 10:07:49] [SSH] Checking java version of /usr/local/java/bin/java Couldn't figure out the Java version of /usr/local/java/bin/java bash: /usr/local/java/bin/java: No such file or directory [10/03/12 10:07:49] [SSH] Checking java version of /Users/builds/.jenkins/jdk/bin/java Couldn't figure out the Java version of /Users/builds/.jenkins/jdk/bin/java bash: /Users/builds/.jenkins/jdk/bin/java: No such file or directory Darwin gili-mac 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64 hudson.util.IOException2: Could not find any known supported java version in [java, /usr/bin/java, /usr/java/default/bin/java, /usr/java/latest/bin/java, /usr/local/bin/java, /usr/local/java/bin/java, /Users/builds/.jenkins/jdk/bin/java], and we also failed to install JDK as a fallback at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:350) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:288) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Failed to detect the environment for automatic JDK installation. Please report this to jenkinsci-us...@googlegroups.com: Darwin gili-mac 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64 at hudson.plugins.sshslaves.SSHLauncher.attemptToInstallJDK(SSHLauncher.java:405) at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:348) ... 7 more [10/03/12 10:07:49] [SSH] Connection 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
[JIRA] (JENKINS-8848) custom workspace not available for maven or ivy projects
cowwoc reopened JENKINS-8848 custom workspace not available for maven or ivy projects Change By: cowwoc (03/Oct/12 4:43 PM) Resolution: Fixed Status: Closed 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
[JIRA] (JENKINS-8848) custom workspace not available for maven or ivy projects
cowwoc resolved JENKINS-8848 as Fixed custom workspace not available for maven or ivy projects Change By: cowwoc (03/Oct/12 4:44 PM) Status: Reopened 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-8848) custom workspace not available for maven or ivy projects
cowwoc commented on JENKINS-8848 custom workspace not available for maven or ivy projects I found this under Build - Use Custom Workspace. This differs from freestyle projects that list it under Advanced Project Options. This message is automatically generated by JIRA. 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-15394) Custom workspace should be configurable from the same location regardless of the project type
cowwoc created JENKINS-15394 Custom workspace should be configurable from the same location regardless of the project type Issue Type: Improvement Assignee: Unassigned Components: core Created: 03/Oct/12 4:47 PM Description: JENKINS-8848 adds custom workspaces for Maven projects, but the user interface should be improved in that freestyle projects list the options under one section (Advanced Project Options) whereas Maven lists it under another (Build). This makes Jenkins hard to use. Please ensure this option is available under the same location regardless of the project type. Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. 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-15385) Mercurial auto-installer does not work
cowwoc created JENKINS-15385 Mercurial auto-installer does not work Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: mercurial Created: 03/Oct/12 2:30 AM Description: I created a Mercurial instance under the global configuration. I then enabled "install automatically". I then configured a job to use this Mercurial instance on an Ubuntu slave node. When I run the job, it fails with: $ /usr/bin/hg clone --rev default --noupdate https://host.com/hg/gstreamer-android/ /home/builds/.jenkins/workspace/GStreamer_Android_snapshot ERROR: Failed to clone https://host.com/hg/gstreamer-android/ because hg could not be found; check that you've properly configured your Mercurial installation ERROR: Failed to clone https://host.com/hg/gstreamer-android/ Sure enough, /usr/bin/hg does not exist yet the tool auto-installer is not kicking in. The Mercurial auto-installer has two sub-options: Extract .zip/.tar.gz Run command I don't know how where to get the Mercurial binaries for Ubuntu in *.zip or *.tar.gz form (the sources are posted online, but not the binaries). As for "run command" I know "sudo apt-get install mercurial" will work but this requires root access and I cannot grant Jenkins root access, for security reasons. Please explain how this is supposed to work. Is this a bug or am I misunderstanding how to configure this? Project: Jenkins Priority: Major Reporter: cowwoc This message is automatically generated by JIRA. 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-15293) Can't configure Maven Installations on Jenkins ver. 1.483, 1.484
cowwoc commented on JENKINS-15293 Cant configure Maven Installations on Jenkins ver. 1.483, 1.484 Olivier, Maybe I misunderstood, but shouldn't the OR in the condition be an AND? That is, we only want to remove installations if they have an empty name and an empty home directory. Right? This message is automatically generated by JIRA. 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-15305) Job-level configuration is missing
cowwoc commented on JENKINS-15305 Job-level configuration is missing Confirmed. Is there a way to fix this (convert it to a top-level configuration option)? There is a similar plugin by the name "buildcoin" and it provides top-level configuration. Alternatively (less desirable), please document where to find the configuration option in the Wiki page. This message is automatically generated by JIRA. 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-15305) Job-level configuration is missing
cowwoc commented on JENKINS-15305 Job-level configuration is missing No. I mean it should show up in a job's configuration at the same level as "Source Code Management" (meaning, one level higher than it is currently). That being said, I am beginning to see the logic of listing it as a post-build step. I think it's going to be hard for users to find it unless you document it in a prominent location. Also, take a look at the way Buildcoin works. They're doing a lot of things right, from a usability point of view (they do a lot more to entice users to fix builds and earn points/money, such as sending out emails). This message is automatically generated by JIRA. 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-15305) Job-level configuration is missing
cowwoc created JENKINS-15305 Job-level configuration is missing Issue Type: Bug Affects Versions: current Assignee: redsolo Components: ci-game Created: 25/Sep/12 5:10 PM Description: I enabled ci-game in Jenkins' global configuration but, contrary to what the Wiki says, there is no ci-game configuration in the job configuration. Any ideas? Environment: Jenkins 1.482 ci-game 1.1.9 Project: Jenkins Priority: Blocker Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
