[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Title: Message Title Thilo Boehm commented on JENKINS-23396 Re: SSH credentials not supported We had the same error with our internal GitLab-Server with SSH and credentials with version 0.4.0. Then I built a version from master (0.4.1-SNAPSHOT) and it works on our enviroment. What is the plan to release this bugfix? Regards Thilo Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Amedee Van Gasse commented on JENKINS-23396 SSH credentials not supported I created a job that runs this shell script: rm -f $HOME/.ssh/id_rsa $HOME/.ssh/id_rsa.pub ssh-keygen -q -t rsa -C lee...@itextpdf.com -P "" -f $HOME/.ssh/id_rsa cat $HOME/.ssh/id_rsa.pub Copied the output of the ssh public key into Gitlab, and Robert is indeed a son of my grandfather. By the way, I don't use GitHub, I use GitLab. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Amedee Van Gasse commented on JENKINS-23396 SSH credentials not supported @Tommy Thanks for the suggestion, that's some creative out of the box thinking! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Tommy McNeely commented on JENKINS-23396 SSH credentials not supported You don't need direct shell access to run commands. If you are in a "simple" environment where there aren't a bunch of jenkins slaves, you can just create a new jenkins job with a "build script" to create the SSH key. http://stackoverflow.com/questions/10767488/automate-ssh-keygen-t-rsa-so-it-does-not-ask-for-a-passphrase ssh-keygen -t rsa -f ~/.ssh/id_rsa -N '' echo "SSH Public Key: cat ~/.ssh/id_rsa.pub Then take the output from the job and put it into a "new account" in github, grant that account read only access to your repo (since it doesn't have a password). Then some guy named Robert will be your parents sibling (Bob's your uncle). It would be nice if it was just fixed tho, of course ~tommy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Amedee Van Gasse commented on JENKINS-23396 SSH credentials not supported The workaround suggested in #1 only works if you have shell access to the server that runs Jenkins, and if you can login with the user that runs Jenkins (either directly or with sudo). In a hosted environment, this will not be possible. As a workaround, I used another plugin: Extensible Choice. In that plugin I have a Groovy script that calls a PHP script on another server that is under my control. That PHP script executes `git ls-remote -t` on the webserver, which gets a list of tags. Some strings parsing is then done and the Extensible Choice plugin is fed with a list of tags that is presented as a dropdown list in Jenkins. More details in this StackOverflow question: http://stackoverflow.com/questions/28543482/jenkins-git-parameter-plugin-cannot-fetch-tags This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Tommy Bø commented on JENKINS-23396 SSH credentials not supported I haven't tested this particular case, but it should fix that as well. -T This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Mustafa Sak commented on JENKINS-23396 SSH credentials not supported Hi, does your commit fix following issue, too: I configured a job with git scm to a repository reachable by https:// + credentials. The checkout works fine but git paramter receives an error, that the authentication failed. Stack trace javax.servlet.ServletException: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress https://XX +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed for 'https://XX/' at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) 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.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) 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:85) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) 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:49) 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:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.Servl
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger commented on JENKINS-23396 SSH credentials not supported I don't agree with your last sentence, because in Version 0.4.0 I already used GitSCM as a client, but it did not work for me. Only after commit https://github.com/jenkinsci/git-parameter-plugin/commit/67d0443473a4f989f3e6da18f362b62c6194f16c I was able to work with my simple project, where I had just one credential. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Tommy Bø commented on JENKINS-23396 SSH credentials not supported If you use GitSCM to create the client, the credentials will already been set. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger commented on JENKINS-23396 SSH credentials not supported Thanks for testing! I will take a closer look at how to get the right credentials. I hope to find a similar use case somewhere. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Tommy Bø commented on JENKINS-23396 SSH credentials not supported Hi @ngiger. I've tested your fix, and it didn't work quite as expected. Our instance has got multiple credentials available, but while you add everyone to the git-client the setCredentials-method clears all credentials before setting default credentials, so you basically set the last credential in the list as default. I think you may have to check which credentials are used by the git-plugin to choose which one to add. (BTW I changed parent-pom to be v 1.580.2 before building the plugin). -T This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
Tommy McNeely commented on JENKINS-23396 SSH credentials not supported Hi @ngiger: If you have any "documentation" on how to test this, we could test. We are currently on LTS Jenkins via RPM on CentOS. If there is an "installable" version of this module somewhere, we could give it a try. If it involves setting up a development environment, I am out, I tried to do some of that to look into the "Folders" bug, and figured out I have no business in there ~tommy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger started work on JENKINS-23396 SSH credentials not supported Change By: ngiger (17/Jan/15 11:02 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger commented on JENKINS-23396 SSH credentials not supported Should be fixed with commit https://github.com/jenkinsci/git-parameter-plugin/commit/67d0443473a4f989f3e6da18f362b62c6194f16c. If you have time and know how to test drive it, I would appreciate a feedback. I will wait about a week till I will publish a new version, in case any problem pops up in the mean time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
SCM/JIRA link daemon commented on JENKINS-23396 SSH credentials not supported Code changed in jenkins User: Niklaus Giger Path: pom.xml src/main/java/net/uaznia/lukanus/hudson/plugins/gitparameter/GitParameterDefinition.java http://jenkins-ci.org/commit/git-parameter-plugin/67d0443473a4f989f3e6da18f362b62c6194f16c Log: JENKINS-23396Get credentials before fetching info This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-23396) SSH credentials not supported
ngiger commented on JENKINS-23396 SSH credentials not supported I finally found some time to dig into some pending issues of the git-parameter plugins. I could reproduce the problem here. Will investigate the cause. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
