Note that there are some explanatory texts on larger screens.

plurals
  1. POJenkins access private BitBucket repo over SSH
    primarykey
    data
    text
    <p>I'm having trouble getting Jenkins to clone a git repository on BitBucket via SSH. It's failing with the following message:</p> <pre><code>Building in workspace /var/lib/jenkins/workspace/test [ssh-agent] Using credentials git (git@bitbucket.org:&lt;user&gt;/&lt;repo&gt;.git) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/JNR ssh-agent [ssh-agent] Started. Checkout:test / /var/lib/jenkins/workspace/test - hudson.remoting.LocalChannel@2b619bca Using strategy: Default Fetching changes from 1 remote Git repository Fetching upstream changes from origin ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t origin +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: ssh: connect to host bitbucket.org port 22: Connection refused fatal: The remote end hung up unexpectedly </code></pre> <h3>Steps taken</h3> <ul> <li>Create an SSH keypair</li> <li>Add the public key as a deployment key for the repository on BitBucket</li> <li>Install the SSH key and username (have tried both 'git' and my BB account name) in the Jenkins Credentials manager plugin</li> <li><p>Attempt to clone the repository in the build using a URL in form of </p> <p><code>git@bitbucket.org:&lt;user&gt;/&lt;repo&gt;.git</code></p></li> </ul> <p>I've also tried not using the credentials manager and manually installing the keys in <code>/var/log/jenkins/.ssh/</code>, but to no avail.</p> <p>Any ideas what I'm doing wrong?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload