You are right, Mark. Upon further investigation, we run this script to push
tags to git repo:
#!/usr/bin/env bash
> set -e
> #set -x
> git reset --hard $GIT_COMMIT
> git tag $1
> git config remote.origin.url g...@github.com:$2
> git config credential.username ${GIT_USERNAME}
> git config credentia
Are your agents 100% ephemeral? If not, then a preceding job could have
inadvertently activated a git credential manager.
I believe that git credential managers operate at the account level rather
than at the workspace level. If a prior job installed a credential manager
or misconfigured git to
Thanks, are these setting to be applied on master side or slave or both?
On Wednesday, September 30, 2020 at 12:15:23 AM UTC+8 kuisat...@gmail.com
wrote:
>
>- Why does agent tries to connect to master when its already connected?
>
> That suggests half-closed connections, it means that the ag
Hi Mark,
This error happens randomly. So probably not a configuration issue, but
rather some kind of conflict. Is there a way to narrow this down further
when this issue occurs to get to the root cause?
Today when this happened, I did "yum remove git" then "yum install git"
then the issue went
Usually the message "invalid credentials line" indicates that a git
credentials manager has been configured on that agent or in that
workspace. https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage
describes credential storage in general.
http://microsoft.github.io/Git-Credential-Manager-for
Hi,
At random times, I am getting Authentication error with git checkout. This
issue would persist through rebuilding, until the job is reassigned to a
new slave. The slaves also have git installed via yum:
Installed Packages
git.x86_64
- Why does agent tries to connect to master when its already connected?
That suggests half-closed connections, it means that the agent loses the
connection with the Jenkins instance but the FIN notification never arrived
to the Jenkins instance so the connection is open in the Jenkins in
We have a similar issue that only seems to occur during long running jobs
(over 5 hours). The traceback is different but we also see the EOF
exception. My client is Ubuntu linux
I tried to trace the issue by running tcpdumps at both ends on the ssh
session from the master to the slave but I sa
I have my Azure AD connected to Jenkins. post this step, I am manually
adding users and configuring their roles.
is there any automation possibility that I can take a user from Azure AD
and add as a user in Jenkins and assign an initial or basic rule (like
read-only).
--
You received this m
Hi Team, We are using JNLP to connect Mac agent to Linux master node.
Jenkins agent keeps disconnecting frequently, and we are getting below logs
in master.
Can you please suggest how to resolve this? What are the steps to further
triage the same.
Some of the questions we are trying to answe
10 matches
Mail list logo