Started by an SCM change00113323321.00977197714501a47384d81869ab1b82b34f7d1cca90d83e0e1c91a47384d81869ab1b82b34f7d1cca90d83e0e1c9refs/remotes/origin/master1a47384d81869ab1b82b34f7d1cca90d83e0e1c91a47384d81869ab1b82b34f7d1cca90d83e0e1c9refs/remotes/origin/master1a47384d81869ab1b82b34f7d1cca90d83e0e1c91a47384d81869ab1b82b34f7d1cca90d83e0e1c9refs/remotes/origin/masterhttps://gerrit.osmocom.org/docker-playgroundfalse#450332255update-osmo-ci-on-slaves-dp #450450falsefalse4501195215SUCCESS1688556670297https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/450/build2-deb11build-ansibleredmine/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.shgithttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smith