Re: Problem with git ssh access from Unix slave
Before anyone wastes time on this: The explanation was that the embedded ssh server of our git server (Atlassian stash) has its own host key and I had connected with the ssh server of the hosting machine, thus creating the mismatch. Removing the entry from known_hosts and then manually connecting to the git server's ssh port resolved this. On Wed, Sep 17, 2014 at 5:42 PM, Robert Krüger wrote: > Hi, > > I'm trying to install and use my first slave (Unix) and I'm obviously > doing something wrong here. > > I have created a user account jenkins with a home directory on my > slave (Linux) box and have added the public key of my master's user to > its authorized_keys file and verified that I can log in to the slave > using SSH and the jenkins master user. Launch worked. > > Then I copied an existing job, which works fine on the master and > restricted it to the new slave node. > > My job fails when accessing the git repo with this error: > > FATAL: Failed to fetch from ssh://git@ > hudson.plugins.git.GitException: Failed to fetch from > ssh://g...@git.lesspain.de:7999/fnd/de.lesspain.common.git > at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:627) > at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:865) > at hudson.plugins.git.GitSCM.checkout(GitSCM.java:890) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1251) > at > hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) > at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) > at > hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) > at hudson.model.Run.execute(Run.java:1706) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:231) > Caused by: hudson.plugins.git.GitException: Command "git fetch --tags > --progress ssh://git@/fnd/de.lesspain.common.git > +refs/heads/*:refs/remotes/origin/*" returned status code 128: > stdout: > stderr: @@@ > @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > @@@ > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > Someone could be eavesdropping on you right now (man-in-the-middle attack)! > It is also possible that the RSA host key has just been changed. > The fingerprint for the RSA key sent by the remote host is > 31:80:ac:b5:cd:c7:7e:d5:38:d3:ae:1f:7c:44:ca:80. > Please contact your system administrator. > Add correct host key in /home/jenkins/.ssh/known_hosts to get rid of > this message. > Offending key in /home/jenkins/.ssh/known_hosts:1 > RSA host key for git.lesspain.de has changed and you have requested > strict checking. > Host key verification failed. > fatal: Could not read from remote repository. > ... > > I have manually opened an ssh connection to the git server just before > that and accepted the host key, so the server is a known host. I don't > see how its key could have changed inbetween. This is all happening in > a protected environment. > > Any clues where I should look next? > > Thanks, > > Robert -- Robert Krüger Managing Partner Lesspain GmbH & Co. KG www.lesspain-software.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Problem with git ssh access from Unix slave
Hi, I'm trying to install and use my first slave (Unix) and I'm obviously doing something wrong here. I have created a user account jenkins with a home directory on my slave (Linux) box and have added the public key of my master's user to its authorized_keys file and verified that I can log in to the slave using SSH and the jenkins master user. Launch worked. Then I copied an existing job, which works fine on the master and restricted it to the new slave node. My job fails when accessing the git repo with this error: FATAL: Failed to fetch from ssh://git@ hudson.plugins.git.GitException: Failed to fetch from ssh://g...@git.lesspain.de:7999/fnd/de.lesspain.common.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:627) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:865) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:890) at hudson.model.AbstractProject.checkout(AbstractProject.java:1251) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://git@/fnd/de.lesspain.common.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: @@@ @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 31:80:ac:b5:cd:c7:7e:d5:38:d3:ae:1f:7c:44:ca:80. Please contact your system administrator. Add correct host key in /home/jenkins/.ssh/known_hosts to get rid of this message. Offending key in /home/jenkins/.ssh/known_hosts:1 RSA host key for git.lesspain.de has changed and you have requested strict checking. Host key verification failed. fatal: Could not read from remote repository. ... I have manually opened an ssh connection to the git server just before that and accepted the host key, so the server is a known host. I don't see how its key could have changed inbetween. This is all happening in a protected environment. Any clues where I should look next? Thanks, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Web interface images disappear after a while
Hi, I am running a Jenkins instance on OSX and everything works like a charm except that after a while the images of the web interface are no longer there (http not found when looking at the image urls). They reappear after a server restart. I don't know where those images are kept. Could it be the case that the server copies/unpacks them into a temp directory which gets deleted by the OS once in a while or something like that? If so, is there a way to configure that directory and if it's something else, what is it and what can I do about it? Thanks in advance, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Support for JDK 8?
OK, thanks for the clarification! Then I'll stop testing until I read here that it does :-). On Wed, Feb 26, 2014 at 1:52 PM, Mark Waite wrote: > Jenkins does not support JDK 8. > > On Feb 26, 2014 5:47 AM, "Robert Krüger" wrote: >> >> Hi, >> >> I did not find any info in the archive. Every once in a while I try >> starting my Jenkins installation (Mac) using the latest Oracle JDK 8 >> Previews (including the first release candidate) and get errors with >> weird stacktraces in some cases when starting, in others when using >> the web interface. Does it make sense to post this here or is JDK 8 >> not supported as a runtime for Jenkins yet? >> >> Thanks, >> >> Robert >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Support for JDK 8?
Hi, I did not find any info in the archive. Every once in a while I try starting my Jenkins installation (Mac) using the latest Oracle JDK 8 Previews (including the first release candidate) and get errors with weird stacktraces in some cases when starting, in others when using the web interface. Does it make sense to post this here or is JDK 8 not supported as a runtime for Jenkins yet? Thanks, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How to find out why a test was skipped
Thanks! I will try the thing with the listener. That sounds reasonable. On Mon, Feb 10, 2014 at 4:37 PM, Nalin wrote: > TestNG plugin doesn’t capture output like the inbuilt junit plugin. But you > should be able to look at the class level results in TestNG plugin report > where the test failed to see if the failed configuration is mentioned there. > > Also, it’s best to implement a listener which runs on test/config failures > and prints out the exception stack traces. Otherwise, TestNG usually doesn’t > print out stack traces for failed methods. > > -nalin > > On Monday, February 10, 2014 at 7:33, Robert Krüger wrote: > > On Mon, Feb 10, 2014 at 4:28 PM, Nalin wrote: > > Tests skip for two reasons when using TestNG. > > 1. The test explicitly throws SkipException because it isn’t implemented > 2. Another test or configuration method (@BeforeMethod etc) that the test > depends on failed. > > You should look for failures in other tests and configuration methods that > the test depends on to figure out the root cause. > > > I know. In this case it is likely the setup method. My question was > rather "where can I find the respective exception in Jenkins > UI/output". I don't see it anywhere. I can only see exceptions in test > methods but nothing else. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: How to find out why a test was skipped
On Mon, Feb 10, 2014 at 4:28 PM, Nalin wrote: > Tests skip for two reasons when using TestNG. > > 1. The test explicitly throws SkipException because it isn’t implemented > 2. Another test or configuration method (@BeforeMethod etc) that the test > depends on failed. > > You should look for failures in other tests and configuration methods that > the test depends on to figure out the root cause. I know. In this case it is likely the setup method. My question was rather "where can I find the respective exception in Jenkins UI/output". I don't see it anywhere. I can only see exceptions in test methods but nothing else. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
How to find out why a test was skipped
Hi, I managed to get Jenkins to work with Gradle and TestNG and create reports using the testng plugin but now I need to find out why many of my tests are skipped. Usually this is caused by stuff like Exceptions in setup methods or data providers but I cannot see the console output or the stacktrace of the exceptions causing this anywhere, so it is kind of hard to debug. Am I missing anything obvious? Thanks, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Complete confusion regarding testng report parsing
Ah, so my gradle buildfile was incorrect. Thank you!!! For those running into this, I changed the gradle buildfile like described here http://forums.gradle.org/gradle/topics/how_to_generate_testng_xml_report and that did the trick. On Wed, Feb 5, 2014 at 4:21 PM, Nalin wrote: > Robert, > > you need to use the XML files generated by using the > org.testng.reporters.XMLReporter reporter. Usually this is just a single > file named testng-results.xml. The other files like TEST-*.xml files are > generated by Junit Reporter and are used with the inbuilt Junit reporting. > > I am not sure about the XML version issue that you are facing. If you still > run into that issue after fixing your configuration, please file a bug and > I’ll take a look. > > -nalin > > On Wednesday, February 5, 2014 at 6:57, Robert Krüger wrote: > > On Tue, Feb 4, 2014 at 5:17 PM, Robert Krüger wrote: > > > First of all, which of the test result files are the correct ones that > should be parsed? The ones named testng-results* or > TEST-.xml? > > > OK, I found out the testng-results-.xml ones in the build > directory are copies of the TEST-.xml in the workspace. > However, I do not see when those are copied because it is obviously > not happening for every new result file that is generated. Is this > documented somewhere? I read the testng plugin documentation. There it > is not documented AFAICS. > > Are there any other sources of information but the plugin source code? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Complete confusion regarding testng report parsing
On Tue, Feb 4, 2014 at 5:17 PM, Robert Krüger wrote: > > First of all, which of the test result files are the correct ones that > should be parsed? The ones named testng-results* or > TEST-.xml? OK, I found out the testng-results-.xml ones in the build directory are copies of the TEST-.xml in the workspace. However, I do not see when those are copied because it is obviously not happening for every new result file that is generated. Is this documented somewhere? I read the testng plugin documentation. There it is not documented AFAICS. Are there any other sources of information but the plugin source code? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Complete confusion regarding testng report parsing
Hi, I am trying to get a Jenkins job to run that builds using Gradle and runs tests using their Testng integration. I have the latest Jenkins installed. I have set up "Publish TestNG Results" and used the pattern "**/test-results/TEST-*.xml" because I found that after a build I had lots of files with paths like this one in my workspace: workspace/de.lesspain/de.lesspain.scheduling/build/test-results/TEST-de.lesspain.scheduling.CronScheduleTest.xml What my job reports is lots of the following: Processing '/Users/Shared/Jenkins/Home/jobs/Mediatool-SSH/builds/2014-02-04_16-58-47/testng/testng-results-9.xml' Failed to parse XML: only 1.0 is supported as .xml? Then I do not understand, why the pattern above matches in that case and then why do I get this error messages when both types of xml files generated by testng seem to be declared with xml version 1.1? Is there currently a known problem with the combination of jenkins, gradle and testng or am I just doing stuff wrong (probably)? Thanks for any insight, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Jenkins-Job with 2 git repositories
No, I wasn't using the plugin as the default Git plugin lets me add multiple repos to a job (wonder how that's supposed to work with its current behaviour). I installed the Multiple SCMs Plugin and that solved the problem. Thank you. On Tue, Feb 4, 2014 at 2:57 PM, Marc MacIntyre wrote: > Assuming you're using the multi-scm plugin, in each git repository section > of the configuration, there's an "advanced" button below the "branches to > build" section. (Not to be confused with the "advanced" button in the > "repository url" section). In there you'll find a "local subdirectory for > repo" field you can set. > > > On Tue, Feb 4, 2014 at 5:43 AM, Robert Krüger wrote: >> >> Hi, >> >> I have a project that builds using gradle and is organized as a >> multi-project build but is managed in two different git repositories. >> The build works if both are cloned into the same directory like so >> >> - project1 >>- master-module >> - project2 >>- sub-module1 >>- sub-module2 >>- sub-module3 >> ... >> >> Now to build this you execute a gradle build script in >> project1/build.gradle >> >> I have now set up my Jenkins job to check out those two repos and it >> seems the checkouts overwrite each other in workspace. What I want is >> the directory structure specified above underneath "workspace" but >> what I get is that master-module, sub-modulke1 etc. are checked out >> directly under workspace apparently even overwriting/deleting each >> other. >> >> How can I solve this? >> >> I don't see an option where I can specify where it is checked out >> into. I want it to behave like a git clone performed in the workspace >> which would retain the top-level directories project1, project2. >> >> Thanks in advance, >> >> Robert >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > Marc MacIntyre > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Jenkins-Job with 2 git repositories
Hi, I have a project that builds using gradle and is organized as a multi-project build but is managed in two different git repositories. The build works if both are cloned into the same directory like so - project1 - master-module - project2 - sub-module1 - sub-module2 - sub-module3 ... Now to build this you execute a gradle build script in project1/build.gradle I have now set up my Jenkins job to check out those two repos and it seems the checkouts overwrite each other in workspace. What I want is the directory structure specified above underneath "workspace" but what I get is that master-module, sub-modulke1 etc. are checked out directly under workspace apparently even overwriting/deleting each other. How can I solve this? I don't see an option where I can specify where it is checked out into. I want it to behave like a git clone performed in the workspace which would retain the top-level directories project1, project2. Thanks in advance, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Best practices for handling Git credentials securely with Jenkins
OK, thank you. On Fri, Nov 8, 2013 at 5:39 PM, nicolas de loof wrote: > I recommended ssh over self-signed certificate http that require extra > configuration. Not from a security perspective. > > Le 8 nov. 2013 12:50, "Robert Krüger" a écrit : >> >> Hi, >> >> I am setting up a Jenkins Job which accesses a Git (Stash) repo over >> HTTPS using global credentials. Since I was not asked for a password >> for encrypting the credentials database, I guess they are not strongly >> encrypted in the XML file where they are stored. Is there a more >> secure way of setting this up? In another thread Nicolas de Loof >> recommended SSH over HTTPS for such a setup. Is this one of the >> reasons? >> >> Thanks, >> >> Robert >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Best practices for handling Git credentials securely with Jenkins
Thanks. On Fri, Nov 8, 2013 at 1:46 PM, Stephen Connolly wrote: > The credentials database is encrypted using Jenkins' secret key > infrastructure. Obviously Jenkins can decrypt them as Jenkins has the secret > key... and the secret keys are stored on disk in $JENKINS_HOME, but I assure > you the passwords themselves are not stored in plain text or a simple > obfuscated form... they are stored using a reversible encryption technique > > > On 8 November 2013 11:50, Robert Krüger wrote: >> >> Hi, >> >> I am setting up a Jenkins Job which accesses a Git (Stash) repo over >> HTTPS using global credentials. Since I was not asked for a password >> for encrypting the credentials database, I guess they are not strongly >> encrypted in the XML file where they are stored. Is there a more >> secure way of setting this up? In another thread Nicolas de Loof >> recommended SSH over HTTPS for such a setup. Is this one of the >> reasons? >> >> Thanks, >> >> Robert >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't get Git access (stash) with credentials to work
in our case its only an interim solution. we will buy the cert :-). On Fri, Nov 8, 2013 at 4:41 PM, nicolas de loof wrote: > Right. So looks secure but actually unsecured. > > Le 8 nov. 2013 16:39, "Kevin Fleming (BLOOMBERG/ 731 LEXIN)" > a écrit : > >> It does make things secure if you also use client-side certificates and >> check them on the server side (so that a client-side certificate is >> mandatory to establish a connection). It also encrypts the traffic on the >> wire, but of course does not protect against man-in-the-middle attacks. >> >> - Original Message - >> From: jenkinsci-users@googlegroups.com >> To: jenkinsci-users@googlegroups.com >> Cc: Kevin Fleming (BLOOMBERG/ 731 LEXIN) >> At: Nov 8 2013 10:36:47 >> >> I don't understand why people host git over https with self-signed >> certificate. This don't make things secure, so why not just use http ? >> >> I only have used self-signed certificate for development/test of https >> webapps. >> >> Le 8 nov. 2013 16:33, "nicolas de loof" a écrit >> : >>> >>> Add this as a java system property to your java command line. >>> >>> Le 8 nov. 2013 15:49, "Саша Щербаков" a écrit : >>>> >>>> Could anybody explain how to run Jenkins with >>>> org.jenkinsci.plugins.gitclient.GitClient.untrustedSSL=true ? >>>> >>>> Thanks >>>> >>>> Пʼятниця, 8 листопада 2013 р. 16:41:48 UTC+2 користувач Kevin Fleming >>>> написав: >>>>> >>>>> I am starting to think that the new credentials system may be just a >>>>> bit over-engineered :-) >>>>> >>>>> - Original Message - >>>>> From: jenkins...@googlegroups.com >>>>> To: jenkins...@googlegroups.com >>>>> At: Nov 8 2013 07:50:15 >>>>> >>>>> Ahhh did you not add any specifications to the domain? >>>>> >>>>> You need to provide the domain with some specifications to match >>>>> against. The domain's name is only used by humans... the specifications >>>>> are >>>>> used by Jenkins. >>>>> >>>>> If there is at least 1 specification, then the credentials in that >>>>> domain will be available unless there is a specification that is *not* >>>>> matched... >>>>> >>>>> >>>>> On 8 November 2013 11:45, Robert Krüger wrote: >>>>>> >>>>>> On Fri, Nov 8, 2013 at 12:18 PM, Robert Krüger >>>>>> wrote: >>>>>> > Thanks, that works now with credentials in the URL. >>>>>> > >>>>>> > Is there any way I can use the credentials mechanism instead? >>>>>> > Shouldn't I have the credentials for that domain in the list? >>>>>> >>>>>> It does work if I enter global credentials. I guess I misunderstood >>>>>> the domain concept in that context. >>>>>> >>>>>> > >>>>>> > On Fri, Nov 8, 2013 at 11:00 AM, nicolas de loof >>>>>> > wrote: >>>>>> >> run jenkins with >>>>>> >> org.jenkinsci.plugins.gitclient.GitClient.untrustedSSL=true >>>>>> >> >>>>>> >> Anyway I recommend ssh >>>>>> > >>>>>> > Just out of curiosity, why? Is the HTTP(S) support not mature? >>>>>> > >>>>>> >> >>>>>> >> >>>>>> >> 2013/11/8 Robert Krüger >>>>>> >>> >>>>>> >>> On Fri, Nov 8, 2013 at 10:41 AM, nicolas de loof >>>>>> >>> wrote: >>>>>> >>> > does your git repo use sef-signed certificates ? >>>>>> >>> >>>>>> >>> Yes ist does. Is there no way to specify something like >>>>>> >>> GIT_SSL_NO_VERIFY=true or specify/import the CA cert somewhere? >>>>>> >>> >>>>>> >>> > can't you use ssh to access it ? >>>>>> >>> >>>>>> >>> I have to check with our sysad. >>>>>> >>> >>>>>> >>> > >>>>>> >>> > >>>>>> >>> > 2013/11/8 Robert K
Best practices for handling Git credentials securely with Jenkins
Hi, I am setting up a Jenkins Job which accesses a Git (Stash) repo over HTTPS using global credentials. Since I was not asked for a password for encrypting the credentials database, I guess they are not strongly encrypted in the XML file where they are stored. Is there a more secure way of setting this up? In another thread Nicolas de Loof recommended SSH over HTTPS for such a setup. Is this one of the reasons? Thanks, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't get Git access (stash) with credentials to work
On Fri, Nov 8, 2013 at 12:18 PM, Robert Krüger wrote: > Thanks, that works now with credentials in the URL. > > Is there any way I can use the credentials mechanism instead? > Shouldn't I have the credentials for that domain in the list? It does work if I enter global credentials. I guess I misunderstood the domain concept in that context. > > On Fri, Nov 8, 2013 at 11:00 AM, nicolas de loof > wrote: >> run jenkins with org.jenkinsci.plugins.gitclient.GitClient.untrustedSSL=true >> >> Anyway I recommend ssh > > Just out of curiosity, why? Is the HTTP(S) support not mature? > >> >> >> 2013/11/8 Robert Krüger >>> >>> On Fri, Nov 8, 2013 at 10:41 AM, nicolas de loof >>> wrote: >>> > does your git repo use sef-signed certificates ? >>> >>> Yes ist does. Is there no way to specify something like >>> GIT_SSL_NO_VERIFY=true or specify/import the CA cert somewhere? >>> >>> > can't you use ssh to access it ? >>> >>> I have to check with our sysad. >>> >>> > >>> > >>> > 2013/11/8 Robert Krüger >>> >> >>> >> Hi, >>> >> >>> >> I just installed a fresh Jenkins 1.538 on Mac OS 10.8.5 and am trying >>> >> to configure a Job that checks out from a Git repository hosted on a >>> >> Stash server. The git/stash access is via https and protected using >>> >> http credentials. >>> >> >>> >> I Installed the Git plugin but when I enter the repository URL (e.g. >>> >> https://git.mydomain.com/scm/PROJ/myproject.git), I get the red error >>> >> message "Failed to connect to repository : Failed to connect to >>> >> https://git.mydomain.com/scm/PROJ/myproject.git";. >>> >> >>> >> I tried with and without credentials in the URL with the same result. >>> >> >>> >> Then I created a domain (under credentials), named it git.mydomain.com >>> >> and added a set of credentials to that domain for my build user. Then >>> >> I returned to the job configuration page but in the credentials >>> >> section of the Git settings I still only have the "- none -" option in >>> >> the drop-down. >>> >> >>> >> What am I doing wrong? >>> >> >>> >> Is there a log file where I can look for clues? >>> >> >>> >> Thanks in advance, >>> >> >>> >> Robert >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> >> Groups >>> >> "Jenkins Users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send >>> >> an >>> >> email to jenkinsci-users+unsubscr...@googlegroups.com. >>> >> For more options, visit https://groups.google.com/groups/opt_out. >>> > >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups >>> > "Jenkins Users" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> > an >>> > email to jenkinsci-users+unsubscr...@googlegroups.com. >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to jenkinsci-users+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't get Git access (stash) with credentials to work
Thanks, that works now with credentials in the URL. Is there any way I can use the credentials mechanism instead? Shouldn't I have the credentials for that domain in the list? On Fri, Nov 8, 2013 at 11:00 AM, nicolas de loof wrote: > run jenkins with org.jenkinsci.plugins.gitclient.GitClient.untrustedSSL=true > > Anyway I recommend ssh Just out of curiosity, why? Is the HTTP(S) support not mature? > > > 2013/11/8 Robert Krüger >> >> On Fri, Nov 8, 2013 at 10:41 AM, nicolas de loof >> wrote: >> > does your git repo use sef-signed certificates ? >> >> Yes ist does. Is there no way to specify something like >> GIT_SSL_NO_VERIFY=true or specify/import the CA cert somewhere? >> >> > can't you use ssh to access it ? >> >> I have to check with our sysad. >> >> > >> > >> > 2013/11/8 Robert Krüger >> >> >> >> Hi, >> >> >> >> I just installed a fresh Jenkins 1.538 on Mac OS 10.8.5 and am trying >> >> to configure a Job that checks out from a Git repository hosted on a >> >> Stash server. The git/stash access is via https and protected using >> >> http credentials. >> >> >> >> I Installed the Git plugin but when I enter the repository URL (e.g. >> >> https://git.mydomain.com/scm/PROJ/myproject.git), I get the red error >> >> message "Failed to connect to repository : Failed to connect to >> >> https://git.mydomain.com/scm/PROJ/myproject.git";. >> >> >> >> I tried with and without credentials in the URL with the same result. >> >> >> >> Then I created a domain (under credentials), named it git.mydomain.com >> >> and added a set of credentials to that domain for my build user. Then >> >> I returned to the job configuration page but in the credentials >> >> section of the Git settings I still only have the "- none -" option in >> >> the drop-down. >> >> >> >> What am I doing wrong? >> >> >> >> Is there a log file where I can look for clues? >> >> >> >> Thanks in advance, >> >> >> >> Robert >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "Jenkins Users" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> >> an >> >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Jenkins Users" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to jenkinsci-users+unsubscr...@googlegroups.com. >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Can't get Git access (stash) with credentials to work
On Fri, Nov 8, 2013 at 10:41 AM, nicolas de loof wrote: > does your git repo use sef-signed certificates ? Yes ist does. Is there no way to specify something like GIT_SSL_NO_VERIFY=true or specify/import the CA cert somewhere? > can't you use ssh to access it ? I have to check with our sysad. > > > 2013/11/8 Robert Krüger >> >> Hi, >> >> I just installed a fresh Jenkins 1.538 on Mac OS 10.8.5 and am trying >> to configure a Job that checks out from a Git repository hosted on a >> Stash server. The git/stash access is via https and protected using >> http credentials. >> >> I Installed the Git plugin but when I enter the repository URL (e.g. >> https://git.mydomain.com/scm/PROJ/myproject.git), I get the red error >> message "Failed to connect to repository : Failed to connect to >> https://git.mydomain.com/scm/PROJ/myproject.git";. >> >> I tried with and without credentials in the URL with the same result. >> >> Then I created a domain (under credentials), named it git.mydomain.com >> and added a set of credentials to that domain for my build user. Then >> I returned to the job configuration page but in the credentials >> section of the Git settings I still only have the "- none -" option in >> the drop-down. >> >> What am I doing wrong? >> >> Is there a log file where I can look for clues? >> >> Thanks in advance, >> >> Robert >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Can't get Git access (stash) with credentials to work
Hi, I just installed a fresh Jenkins 1.538 on Mac OS 10.8.5 and am trying to configure a Job that checks out from a Git repository hosted on a Stash server. The git/stash access is via https and protected using http credentials. I Installed the Git plugin but when I enter the repository URL (e.g. https://git.mydomain.com/scm/PROJ/myproject.git), I get the red error message "Failed to connect to repository : Failed to connect to https://git.mydomain.com/scm/PROJ/myproject.git";. I tried with and without credentials in the URL with the same result. Then I created a domain (under credentials), named it git.mydomain.com and added a set of credentials to that domain for my build user. Then I returned to the job configuration page but in the credentials section of the Git settings I still only have the "- none -" option in the drop-down. What am I doing wrong? Is there a log file where I can look for clues? Thanks in advance, Robert -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Disable git auto tagging
Hi, I want to keep some of my Jenkins (v. 1.490) builds from tagging my Git repository. I came across this link: https://issues.jenkins-ci.org/browse/JENKINS-12316 and I have the exact same problem as the last poster, i.e. the advanced option does not seem to be there anymore. Is it gone? What else can I do? Thanks in advance, Robert
