On Sat, Feb 1, 2020 at 1:34 AM gary oblock <[email protected]> wrote:
> Any pointers on how to do these??? Note, URLs of pages with generic help > on these topics might suffice.... > I'm a newbie to both Jenkins and GIT (though user howto documentation on > the later seems more accessible.) > > Thanks, > > Gary > > On Friday, January 31, 2020 at 2:36:03 PM UTC-8, Mark Waite wrote: >> >> Jenkins uses credentials to access private repositories. You'll need to >> provide the credentials for that repository as a Jenkins credential. >> >> Using credentials <https://jenkins.io/doc/book/using/using-credentials/> describes how to create credentials, including both username / password credentials and private key credentials. Jenkins Minute - Creating your first pipeline <https://jenkins.io/doc/book/using/using-credentials/> describes how to create a Jenkins Pipeline job. The Jenkins tutorials <https://jenkins.io/doc/tutorials/> describe how to create jobs to support: - Java application using Maven <https://jenkins.io/doc/tutorials/build-a-java-app-with-maven> - Node.js and React application using npm <https://jenkins.io/doc/tutorials/build-a-node-js-and-react-app-with-npm> - A Python application <https://jenkins.io/doc/tutorials/build-a-python-app-with-pyinstaller> In addition, there is the Blue Ocean tutorial <https://jenkins.io/doc/tutorials/create-a-pipeline-in-blue-ocean> and the Multibranch Pipeline tutorial <https://jenkins.io/doc/tutorials/build-a-multibranch-pipeline-project/>. CloudBees provides a free self-paced training course, Pipeline Fundamentals <https://standard.cbu.cloudbees.com/cloudbees-university-jenkins-pipeline-fundamentals>, which includes a lab that uses ssh to create a Pipeline job with ssh in a Gitea repository using Blue Ocean. Mark Waite > The Jenkins git plugin supports username / password credentials for https >> repositories. >> >> The Jenkins git plugin supports private key credentials for ssh >> repositories. >> >> The sample repository syntax you provided is an https repository. You'll >> need to provide a username / password credential, not a private key >> credential. >> >> Mark Waite >> >> On Friday, January 31, 2020 at 11:30:49 PM UTC+1, gary oblock wrote: >>> >>> Please bear with me. I'd do a search for this information but frankly I >>> don't know enough about Jenkins & GIT to come up with a meaningful >>> query. >>> >>> I'm trying to create a set of scripts shared between myself and a >>> Government customer. >>> They'll be invoking them on a super computer and I'll be invoking them >>> on Thunder2X >>> server via Jenkins. >>> >>> So I've managed to create a private repository which I'll call for the >>> sake of this >>> posting. >>> >>> https://github.com/usergary/scripts.git >>> >>> I've managed to but a test script on it and hand it public ssh key. It >>> all >>> works fine and dandy from my desktop Linux box but here's the >>> grief I run into on Jenkins: >>> >>> I cloned an existing build then started modifying the *Source Code >>> Management* >>> stuff (under the advice of somebody else that doesn't really know this >>> part of >>> Jenkins.) When I clicked the *GIT *button and entered >>> >>> https://github.com/usergary/scripts.git >>> >>> in the *Repository URL* field I got this: >>> >>> Failed to connect to repository : Command "/usr/bin/git ls-remote -h >>> https://github.com/usergary/scripts.git HEAD" returned status code 128: >>> stdout: >>> stderr: remote: Invalid username or password. >>> fatal: Authentication failed for ' >>> https://github.com/usergary/scripts.git/' >>> >>> All I want to do is associated the private ssh key with my invocation of >>> this Jenkins build >>> so I can run the following in the execute shell: >>> >>> >>> git clone https://github.com/usergary/scripts.git >>> >>> What stupid things have I done wrong in my ignorance and what should I >>> be doing instead? >>> >>> Many thanks, >>> >>> Gary Oblock >>> >>> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/47d3e0f5-7909-44d5-abc5-9e68ddbbb9a3%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/47d3e0f5-7909-44d5-abc5-9e68ddbbb9a3%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGOZp19RPjXwKx-Ah%3DpYJv5ZVhjbAOrLgEn9%2BmhiaH1iA%40mail.gmail.com.
