| I'm afraid i've not attempted to reproduce this bug, and experimenting with returning our production systems to a potentially broken state isn't really an option. The only thing I could recommend in this case would be using https://invent.kde.org/sysadmin/ci-tooling/blob/master/pipeline-templates/SUSEQt5.12.template as a starting point. The only Stage that matters in that job from the perspective of this bug is the Checkout Sources stage, so you can probably delete the rest without too much impact (although it may be worth forcing the build to always be UNSTABLE) It is worth noting that we were also experiencing issues with job runs not being considered Successful by Jenkins unless they were also Stable, which impacted views as noted above. As only some jobs were experiencing the issue of not having the correct branches polled, it is possible that these two issues are somehow related - especially given they both disappeared when the plugin is installed. Is it possible that the plugin is causing side effects within Jenkins - so it isn't the symlinks themselves that matter - but rather something else that it causes within Jenkins when performing the symlink update - which resolves our problem here? The additional Groovy declarations you'll need to include to use the above template are as follows: ```def repositoryUrl = "git://anongit.kde.org/konsole"
def browserUrl = "https://cgit.kde.org/konsole.git"
def branchToBuild = "master"
def productName = "Applications"
def projectName = "konsole"
def branchGroup = "kf5-qt5"
def currentPlatform = "SUSEQt5.12"
def ciEnvironment = "production"
def buildFailureEmails = "konsol...@kde.org"
def unstableBuildEmails = ""``` |
