[checkmk-commits] [tribe29/checkmk] 0212b6: Use Branch variable instead of hardcoded value

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 0212b6fdf7b8514981e129b3061f207a05a56449 https://github.com/tribe29/checkmk/commit/0212b6fdf7b8514981e129b3061f207a0… Author: Alex Zurhake &lt;alex.zurhake(a)tribe29.com&gt; Date: 2019-06-05 (Wed, 05 Jun 2019) Changed paths: M buildscripts/scripts/nightly-master.jenkins Log Message: ----------- Use Branch variable instead of hardcoded value Change-Id: Ic857a5c1eb6a11c14f501d20ce19de0ac6b885c7 Commit: 761b8fee0dc153d66b218287b9e6b87ff53c701c https://github.com/tribe29/checkmk/commit/761b8fee0dc153d66b218287b9e6b87ff… Author: Moritz Kiemer &lt;mo(a)mathias-kettner.de&gt; Date: 2019-06-05 (Wed, 05 Jun 2019) Changed paths: A .werks/7482 M agents/plugins/mk_mysql Log Message: ----------- 7482 FIX mk_mysql: More consistent naming of instances The naming of different mysql instances has been simplified. The item names of the monitored instances are now given by the corresponding sockets (e.g. an instance using the socket "/var/run/mysql.sock" will be called "/var/run/mysql.sock"). The sockets are determined by the socket argument in the mysgl.cfg file or by the <tt>--socket=</tt> option found in <tt>ps -fww -C mysqld</tt>. If neiter of those is found, only one instance will be monitored, using the default name "mysql". Previously as a third attempt the <tt>--user=</tt> option of the afore mentioned ps output has been used as instance name. This is not longer considered. Change-Id: Id2698b20c771913276c57f6eb475d88e70c7349e Compare: https://github.com/tribe29/checkmk/compare/4be33878d0be...761b8fee0dc1