Differential Revision: https://phabricator.kde.org/D19219

For everyone else, tests will run afterwards.

Ref T3689

Also fix some typos, correct logic and ensure the correct library is selected (taking into account branchGroup and platform)

Differential Revision: https://phabricator.kde.org/D17099

Differential Revision: https://phabricator.kde.org/D16814

Differential Revision: https://phabricator.kde.org/D16705

Ref T3689

Ref T9662

Make sure the file always exists

This slows down all builds, especially those on Windows which unpack everything into the Workspace.
It also costs us quite a bit of bandwidth, for something which isn't used by anyone according to the web server logs

Differential Revision: https://phabricator.kde.org/D9466

Ref T7583

Replace the Frameworks ones with new SUSEQt5.7 builds.
Complete the purge of Fedora and the Qt 4 based CI system

While this is nice in theory, it causes mails to get caught up by Mailman's default limits too often.
We'll disable this for now and see how things go

This is driven by Frameworks. With few exceptions, only Frameworks uses XenialQt5.7 so this shouldn't affect anyone else.
CCMAIL: kde-frameworks-devel@kde.org

Fixes T6247

Provisionally mark builds as successful at the start, to ensure later checks we do to see if the build status has changed work properly

1) Build emails for failing / unstable builds
2) Capturing workspaces for failing or unstable builds

Also remove Appstreamcli from those platforms, as it doesn't make sense.
Migrate to the proper warnings plugin support for Pipeline, from step()

Hopefully this will eliminate the 'changed after creation' warning which Jenkins shows.
Also, setup cron and commit hook polling for Dependency Builds and Normal Builds respectively to reflect how we will be using them

Refactor to include the Product name in job titles, and the packages stored on the master package repositories.
This is being done now to avoid a big rebuild later on and is a requirement to allow for various products to do things in a different manner.
It also ensures products don't interact with each other - a key requirement for the new system's design, to avoid breakages in ECM killing the entire CI