| @newbie23:matrix.org | > <@fungicide:matrix.org> newbie23: have you checked the task details in the console view? do they have any additional detail that's not getting echoed into the flat log? | 15:42 |
|---|---|---|
| I checked but unfortunately this was not the case. | ||
| The failing task output has been registered to an Ansible variable (not printed/displayed anywhere), but it is part of a role inside a config project. I was hoping I could see the errors in an easy way (e.g equivalent of ansible-playbook -vvv, just for a job) without having to merge changes to the config project protected branch. | ||
| @fungicide:matrix.org | > <@newbie23:matrix.org> I checked but unfortunately this was not the case. | 15:58 |
| > The failing task output has been registered to an Ansible variable (not printed/displayed anywhere), but it is part of a role inside a config project. I was hoping I could see the errors in an easy way (e.g equivalent of ansible-playbook -vvv, just for a job) without having to merge changes to the config project protected branch. | ||
| probably no easy solution in that case. since config projects are intended to house sensitive job configuration, things like secrets and playbooks that handle credentials, being able to dump variables from there without that first being approved by the maintainers of the config repo could be very unsafe | ||
| @fungicide:matrix.org | implementing extra *safe* debugging features in the job, or moving the job out of the config repo if it's not sensitive (so that speculative changes will be allowed by zuul) are your best bets | 15:59 |
| @fungicide:matrix.org | it's generally recommended to limit config repos to things you don't want projects to be able to change without permission of the zuul admins, even speculatively (either for reasons of central control or risk of disclosing sensitive data). in many of our tenants we have job repos which are not config repos, where non-sensitive job configuration can be more easily shared between projects, and changes to those can be tested/troubleshot speculatively | 16:03 |
| @fungicide:matrix.org | as described in https://zuul-ci.org/docs/zuul/latest/howtos/pti.html | 16:05 |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 903911: Produce consistent merge commit shas https://review.opendev.org/c/zuul/zuul/+/903911 | 20:13 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!