Change Details

Whenever clicking {nav RUN PUPPET COMPILER} or commenting `check experimental`, Zuul CI runs two jobs: ``` experimental: - operations-puppet-catalog-compiler-test - operations-puppet-catalog-compiler-puppet7-test ``` The first is hardwired to run Puppet version 5, however some roles and hosts have started breaking back compatibility. The first job thus fail and that is to be expected. When our `wmf-checks-api` Javascript plugin process the result, we get a red chipset indicating the compilation failed: {F56789758 size=full} Which really is just version 5 failing: {F56789791 size=full}

Whenever clicking {nav RUN PUPPET COMPILER} or commenting `check experimental`, Zuul CI runs two jobs: ``` experimental: - operations-puppet-catalog-compiler-test - operations-puppet-catalog-compiler-puppet7-test ``` The first is hardwired to run Puppet version 5, however some roles and hosts have started breaking back compatibility. The first job thus fail and that is to be expected. When our `wmf-checks-api` Javascript plugin process the result, we get a red chipset indicating the compilation failed: {F56789758 size=full} Which really is just version 5 failing: {F56789791 size=full} Demo change: https://gerrit.wikimedia.org/r/c/operations/puppet/+/1057967?tab=checks

Whenever clicking {nav RUN PUPPET COMPILER} or commenting `check experimental`, Zuul CI runs two jobs: ``` experimental: - operations-puppet-catalog-compiler-test - operations-puppet-catalog-compiler-puppet7-test ``` The first is hardwired to run Puppet version 5, however some roles and hosts have started breaking back compatibility. The first job thus fail and that is to be expected. When our `wmf-checks-api` Javascript plugin process the result, we get a red chipset indicating the compilation failed: {F56789758 size=full} Which really is just version 5 failing: {F56789791 size=full} Demo change: https://gerrit.wikimedia.org/r/c/operations/puppet/+/1057967?tab=checks