Am Dienstag, den 30.03.2021, 05:59 + schrieb 'Dirk Heinrichs' via
Jenkins Users:
> Am Montag, den 29.03.2021, 11:07 -0700 schrieb eric@gmail.com:
>
> > Please make sure you have the correct access rights
> > and the repository exists.
>
> Oh, yes, forgot that: On the host(s) that does/do
Am Montag, den 29.03.2021, 11:07 -0700 schrieb eric@gmail.com:
> Please make sure you have the correct access rights
> and the repository exists.
Oh, yes, forgot that: On the host(s) that does/do the cloning, you need
to either
* connect to g...@github.com once per SSH on the console and as
I do add the domain and hsot to my known host file before to avoid that nasty
confirm:
sh("ssh -R ${domain} -f \".ssh/known_hosts\"")
sh("ssh -t rsa ${domain} >> \".ssh/known_hosts\"")
that should do the trick and avoid that prompt when later used. Use the domain
of the repos url domain.
Jérôm
The only thing I can guess is that ssh is getting a question when he
attempts to connect wanting to be added to the known_hosts file. Wondering
if maybe there's a way to establish this if this is indeed the issue?
On Monday, March 29, 2021 at 12:07:01 PM UTC-6 eric@gmail.com wrote:
> Thank
Thanks Mark! I believe I'm one step closer but it's still not working.
I'm now getting:
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags
--progress git@myURLRepo:myUser/myProject.git
+refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout:
stderr: ssh: conn
You can't use ssh authentication with an https repository URL. When using
ssh authentication, you need to use an ssh repository URL. When using
username / password or username / token, you must use an HTTPS (or HTTP)
URL.
Mark Waite
On Mon, Mar 29, 2021 at 10:38 AM Eric Fetzer wrote:
> Hmmm,
Hmmm, thought that was going to work but it didn't. I followed
everything to a T at:
https://mohitgoyal.co/2017/02/27/configuring-ssh-authentication-between-github-and-jenkins/
The output shows:
Building on master in workspace /var/lib/jenkins/workspace/Git-Checkout
using credential JenkinsSSHKey
Hi everyone,
I intend to use Version Number Plugin to implement following functionality:
version number from 1.0.1 > 1.0.100 > 1.1.1>.
I already know how to increase the version number from 1.0.1 to 1.0.100.
But I couldn't figure out how to reset number from 100 to 1, I googled
O, duh, I get it now. I create the key with the jenkins user and add
id_rsa.pub to the GitHub account for access. I was somehow thinking I
would need a key on the GitHub side. Feeling kind of foolish now, lol.
Thanks Dirk!
On Mon, Mar 29, 2021 at 7:52 AM 'Dirk Heinrichs' via Jenkins Users <
Am Montag, den 29.03.2021, 07:44 -0600 schrieb Eric Fetzer:
> Thanks for your reply Dirk! I'm a unix guy and that would have been
> my first choice, however I don't have access to the GitHub OS, only
> my particular repositories.
I don't understand. Nobody has this kind of access. But everybody
Thanks for your reply Dirk! I'm a unix guy and that would have been my
first choice, however I don't have access to the GitHub OS, only my
particular repositories.
On Mon, Mar 29, 2021 at 7:40 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
> Am Montag, den 29.03
Am Montag, den 29.03.2021, 07:22 -0600 schrieb Eric Fetzer:
> It was a bit painful, but at least it gets it done. What I've
> implemented is passing the workspace to the checkout, checking out as
> my user to my user workspace (home directory), moving the files
> checked out to the jenkins worksp
Where I got the info to make this work, Bjorn, is from the thread that your
thread referenced:
https://stackoverflow.com/questions/56809684/git-clone-in-jenkins-with-personal-access-token-idles-forever/61104603#61104603
It was a bit painful, but at least it gets it done. What I've implemented
is
Yes Bjorn, that's the thread I used to figure out how to use the access
token. Unfortunately, the jenkins plugin isn't smart enough to pass a
username, it uses the username it runs as. So my master node is running as
the user "jenkins" so it tries to authenticate to GitHub Enterprise as
jenki
Hi all,
Linker publisher from plugin from subject generates broken links to
artifacts (e.g. to nexus) using maven-deploy-plugin version 3.0.
For maven-deploy-plugin version 2.8.2 all looks good.
The problem is in timestamps - looks like 3.0 generates output with version
only (without timestamps)
Did you try to use credentials in jenkins to store the token instead of
fiddling with token on the machine?
See
e.g.
https://stackoverflow.com/questions/61105368/how-to-use-github-personal-access-token-in-jenkins
Then you could do everything in one job instead of doing some copy-magic
(wh
16 matches
Mail list logo
