Skip to content
[Jenkins]Jenkins
log insign up
Success

Console Output

Download View as plain text
Started by upstream project "osmo-st-logging" build number 163
originally caused by:
 Started by an SCM change
Building remotely on OsmocomBuild1 (linux_amd64_debian8) in workspace /home/osmocom-build/jenkins/workspace/osmo-st-core
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url git://git.osmocom.org/smalltalk/osmo-st-core # timeout=10
Fetching upstream changes from git://git.osmocom.org/smalltalk/osmo-st-core
 > git --version # timeout=10
 > git fetch --tags --progress git://git.osmocom.org/smalltalk/osmo-st-core +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 4ff8679b49d2ca4672788c94db658ced32ab3da4 (refs/remotes/origin/master)
Commit message: "dispatcher: Really merge it, verify that install is called"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 4ff8679b49d2ca4672788c94db658ced32ab3da4
 > git rev-list 4ff8679b49d2ca4672788c94db658ced32ab3da4 # timeout=10
Triggering osmo-st-core » FreeBSD_amd64
osmo-st-core » FreeBSD_amd64 completed with result SUCCESS
Triggering a new build of osmo-st-mgcp
Triggering a new build of osmo-st-asn1
Triggering a new build of osmo-st-network
Triggering a new build of osmo-st-sip
Finished: SUCCESS