Skip to content
Success

Console Output

Started by an SCM change
Running as SYSTEM
Building on the built-in node in workspace /var/jenkins_home/jobs/master-osmo-iuh/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXj3PMew/agent.1993901
SSH_AGENT_PID=1993904
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-osmo-iuh/workspace@tmp/private_key_4317473000365306922.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-iuh/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gerrit.osmocom.org/osmo-iuh # timeout=10
Fetching upstream changes from https://gerrit.osmocom.org/osmo-iuh
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
 > git fetch --tags --force --progress -- https://gerrit.osmocom.org/osmo-iuh +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision b5f6ad9cca1ae75ab8d6539f3000074be27f30cb (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f b5f6ad9cca1ae75ab8d6539f3000074be27f30cb # timeout=10
Commit message: "jenkins.sh: libosmo-netif no longer depends on libosmo-abis"
 > git rev-list --no-walk 655aa8125553b16adbfb0c8fdf9777f3277bf690 # timeout=10
Triggering master-osmo-iuh » a1=default,a2=default,a3=default,a4=default,osmocom-master
master-osmo-iuh » 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 1993904 killed;
[ssh-agent] Stopped.
Triggering a new build of Osmocom_OBS_master
Triggering a new build of master-osmo-msc
Triggering a new build of master-osmo-hnbgw
Triggering a new build of master-osmo-hnodeb
Triggering a new build of master-osmo-sgsn
Finished: SUCCESS