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-android-apdu-proxy/workspace
[ssh-agent] Looking for ssh-agent implementation...
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXWxHOY9/agent.1985494
SSH_AGENT_PID=1985497
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /var/jenkins_home/jobs/master-android-apdu-proxy/workspace@tmp/private_key_5668764899270355066.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-android-apdu-proxy/workspace/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gerrit.osmocom.org/android-apdu-proxy # timeout=10
Fetching upstream changes from https://gerrit.osmocom.org/android-apdu-proxy
 > git --version # timeout=10
 > git --version # 'git version 2.39.5'
 > git fetch --tags --force --progress -- https://gerrit.osmocom.org/android-apdu-proxy +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision f0a90b9a267b5d913e277342e8d9bcbfd2ae0d4e (origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f f0a90b9a267b5d913e277342e8d9bcbfd2ae0d4e # timeout=10
Commit message: "MainActivity: use the API level to check the Android release version"
 > git rev-list --no-walk 4894fe0696f204fcb7273d7e6588ef2148c82cd1 # timeout=10
Triggering master-android-apdu-proxy » a1=default,a2=default,a3=default,a4=default,osmocom-master
master-android-apdu-proxy » 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 1985497 killed;
[ssh-agent] Stopped.
Triggering a new build of Osmocom_OBS_master
Finished: SUCCESS