mkcloud runs from Jenkins should include job details in Jenkins

[aspiers]

We should make mkcloud write a /var/log/mkcloud.txt containing details of the mkcloud run (including Jenkins job number), and make the supportconfig plugin capture this. So then if you have a mystery supportconfig, you can tell where it came from and how mkcloud was configured.

[bmwiedemann]

mkcloud already creates and copies a (bash-readable) mkcloud.config file with all relevant settings to the admin node. I guess we could expand on that one.

[aspiers]

@bmwiedemann Yes:

• capture the Jenkins job
• distribute to all hosts not just admin
• make supportconfig plugin capture it

[aspiers]

SUSE-Cloud/automation#760 (mkcloud, qa_crowbarsetup: show info about jenkins job in /etc/motd) captured the Jenkins job info in /root/mkcloud.config, and SUSE-Cloud/supportutils-plugin-suse-openstack-cloud#55 (collect mkcloud files) ensured that it appears in supportconfigs of the admin node. So it only remains to copy the same file to the other nodes.