Currently a lot of builds have in the build report log a test of appstreamercli failing, with the summary:
"Unable to reach remote location 'https://homepage.x.y.z' - does it"
Looking at the details of that test though, one can see that actually some file copy operation fails, so the report summary is completely misguiding. E.g. "01 Copying the source file 'org.kde.okteta.appdata.xml:org.kde.okteta.desktop:474' from the workspace to the build folder 'e5e5a8f9.tmp' on the Jenkins master failed."
or
" 01 Copying the source file 'org.kde.kdeconnect.kcm.appdata.xml:org.kde.kdeconnect.kcm.desktop:112' from the workspace to the build folder '70cedf1a.tmp' on the Jenkins master failed."
Which hints that there is some filename generation broken. The same strange filename with appdata file and desktop file names being concatenated is also shown in the Appstreamercli result overview page, cmp. e.g. "org.kde.okteta.appdata.xml:org.kde.okteta.desktop" in https://build.kde.org/view/Applications/job/Applications%20okteta%20stable-kf5-qt5%20SUSEQt5.9/17/warnings3Result/ & "org.kde.kdeconnect.kcm.appdata.xml:org.kde.kdeconnect.kcm.desktop" in https://build.kde.org/view/Extragear/job/Extragear%20kdeconnect-kde%20kf5-qt5%20SUSEQt5.9/68/warnings3Result/
Cannot remember to have seen that before, so possibly some recent regression in the CI scripts?