Started by upstream project "registry-rebuild-upload-titan" build number 1,4511451registry-rebuild-upload-titanjob/registry-rebuild-upload-titan/00667847841.08782878209566877587759012eb695bc4491f640a6a47411666986709fbc6abf2eb695bc4491f640a6a47411666986709fbc6abfrefs/remotes/origin/master2eb695bc4491f640a6a47411666986709fbc6abf2eb695bc4491f640a6a47411666986709fbc6abfrefs/remotes/origin/master2eb695bc4491f640a6a47411666986709fbc6abf2eb695bc4491f640a6a47411666986709fbc6abfrefs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundhttps://jenkins.osmocom.org/jenkins/view/all/job/registry-rebuild-upload-ttcn3-bts-tests/901/artifacthttps://jenkins.osmocom.org/jenkins/view/all/job/registry-rebuild-upload-ttcn3-bts-tests/changeshttps://jenkins.osmocom.org/jenkins/view/all/job/registry-rebuild-upload-ttcn3-bts-tests/901/https://jenkins.osmocom.org/jenkins/view/all/job/registry-rebuild-upload-ttcn3-bts-tests/901/testReportfalse#90178420543registry-rebuild-upload-ttcn3-bts-tests #901901falsefalse9011196044SUCCESS1688604200203https://jenkins.osmocom.org/jenkins/view/all/job/registry-rebuild-upload-ttcn3-bts-tests/901/build3-deb11build-ansible- redmine/docker-entrypoint-osmo.sh1a47384d81869ab1b82b34f7d1cca90d83e0e1c91688551862000https://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmith@sysmocom.deredmine: fix auto-scan of repositories
While inspecting the running docker container I found that the script
already runs as redmine user. I had assumed that it runs as root
earlier. Running 'su' as redmine user fails, therefore it currently does
not run the fetch_changesets command.
Related: OS#6083
Change-Id: I195311b93868eb5fd73ad6e3c165d48f3b7b53ce
2023-07-05 12:11:02 +02001a47384d81869ab1b82b34f7d1cca90d83e0e1c9redmine: fix auto-scan of repositorieseditredmine/docker-entrypoint-osmo.sh
- ttcn3-stp-test/osmo-stp.cfgttcn3-smlc-test/osmo-stp.cfgttcn3-hnbgw-test/osmo-stp.cfgttcn3-bsc-test-vamos/osmo-stp.cfgosmo-stp-master/osmo-stp.cfgnplab-sua-test/osmo-stp.cfgnplab-m3ua-test/osmo-stp.cfgttcn3-sgsn-test/osmo-stp.cfgttcn3-bsc-test/osmo-stp.cfgttcn3-msc-test/osmo-stp.cfgosmo-stp-latest/osmo-stp.cfg2eb695bc4491f640a6a47411666986709fbc6abf1688564935000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.de*/osmo-stp.cfg: Explicitly define role & sctp-role
It was recently decided it's a good practice to always specify the role
and sctp-role for all ASPs configured in the VTY, since it's an
important configuration providing feedback on the network setup
expectancies.
Change-Id: Ia495bc3c5dd4421e5730c74b2f5dc4e4cdc1a673
2023-07-05 13:48:55 +00002eb695bc4491f640a6a47411666986709fbc6abf*/osmo-stp.cfg: Explicitly define role & sctp-roleeditttcn3-bsc-test-vamos/osmo-stp.cfgeditttcn3-hnbgw-test/osmo-stp.cfgeditttcn3-stp-test/osmo-stp.cfgeditosmo-stp-master/osmo-stp.cfgeditttcn3-sgsn-test/osmo-stp.cfgeditttcn3-smlc-test/osmo-stp.cfgeditnplab-sua-test/osmo-stp.cfgeditttcn3-bsc-test/osmo-stp.cfgeditttcn3-msc-test/osmo-stp.cfgeditnplab-m3ua-test/osmo-stp.cfgeditosmo-stp-latest/osmo-stp.cfg
githttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smithosmithhttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin