Started by an SCM change
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/master-osmo-pcap/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXSOwHre/agent.1939788
SSH_AGENT_PID=1939791
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-osmo-pcap/workspace@tmp/private_key_10770426219748988363.key (osmocom-jenkins)
[ssh-agent] Using credentials docs (OS#5798)
The recommended git tool is: NONE
No credentials specified
> git rev-parse --resolve-git-dir /var/jenkins_home/jobs/master-osmo-pcap/workspace/.git # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://gerrit.osmocom.org/osmo-pcap # timeout=10
Fetching upstream changes from https://gerrit.osmocom.org/osmo-pcap
> git --version # timeout=10
> git --version # 'git version 2.39.5'
> git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-pcap +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision eeb3d67adda27231f964c5404918db9b572e1d8c (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f eeb3d67adda27231f964c5404918db9b572e1d8c # timeout=10
Commit message: "pcap-server: Fix [no] max-file-size regression"
> git rev-list --no-walk d32320167a9f303593fd8a46411a38652607c9b2 # timeout=10
Triggering master-osmo-pcap » a1=default,a2=default,a3=default,a4=default,osmocom-master
master-osmo-pcap » a1=default,a2=default,a3=default,a4=default,osmocom-master completed with result SUCCESS
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 1939791 killed;
[ssh-agent] Stopped.
Triggering a new build of Osmocom_OBS_master
Finished: SUCCESS