@adri:avm99963.com | Hi! How do you run Zuul locally while developing it? | 17:34 |
---|---|---|
I'd like to contribute a small improvement for the authorization rule conditions (the ability to check boolean claims, e.g. `email_verified = true`), but I'm new to Python development and can't get to start any of the Zuul components locally (I only managed to build the Docker images, which I'll use now to check whether my change works). Thanks in advance! :)) | ||
@fungicide:matrix.org | adri: use nox to run zuul's unit tests while developing, they're extensive enough already that they should do a good job of making sure you haven't broken anything. if you're wanting to try out your changes in a demo install of zuul, then use the "quick start" setup in the documentation (which, yes, is container-based because zuul itself consists of a fleet of special-purpose services acting in concert, and also needs other services like a database, zookeeper, somewhere to run ansible, somewhere to store build logs, a code review system to communicate with...) | 17:42 |
@fungicide:matrix.org | the quickstart compose file starts up just the most minimal usable set of services to be able to test things out interactively, but can also be extended as desired | 17:44 |
@fungicide:matrix.org | but even the unit tests are pretty resource-heavy compared to a lot of other projects, so there's no shame in making your best guess and pushing that up for review to see what our zuul thinks | 17:45 |
@fungicide:matrix.org | and for a lot of small features, you may find that you can just exercise them by adding a new test rather than needing to try them out manually in a full interactive deployment | 17:48 |
@fungicide:matrix.org | plus, that acts as a safeguard against the feature regressing in the future | 17:49 |
@adri:avm99963.com | Thank you so much fungi! Writing a test seems like a good plan for this! I'll try to find which test suite is more appropriate for it (though I might ask you for help here again! I'm not that much familiarized with the Zuul codebase even if I've glanced it several times when I wanted to troubleshoot issues in my homelab Zuul deployment) | 17:55 |
@fungicide:matrix.org | there are also plenty of others in here with a far better grasp of zuul development than i have, but happy to help sure! | 17:56 |
@jim:acmegating.com | Adrià Vilanova: https://opendev.org/zuul/zuul/src/branch/master/TESTING.rst may be helpful | 17:57 |
@adri:avm99963.com | No problem fungi, thanks! And thank you corvus as well! | 17:59 |
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: | 19:19 | |
- [zuul/zuul] 937947: Add web API image delete endpoints https://review.opendev.org/c/zuul/zuul/+/937947 | ||
- [zuul/zuul] 938022: Allow deleting images through web UI https://review.opendev.org/c/zuul/zuul/+/938022 | ||
- [zuul/zuul] 938023: Add REST API method to trigger image build https://review.opendev.org/c/zuul/zuul/+/938023 | ||
- [zuul/zuul] 938024: Add a web UI button to build an image https://review.opendev.org/c/zuul/zuul/+/938024 | ||
- [zuul/zuul] 938087: Add labels and flavors to web https://review.opendev.org/c/zuul/zuul/+/938087 | ||
- [zuul/zuul] 938088: Add niz nodes to rest api nodes list endpoint https://review.opendev.org/c/zuul/zuul/+/938088 | ||
-@gerrit:opendev.org- Adrià Vilanova Martínez proposed wip: [zuul/zuul] 938986: Allow boolean claim rules https://review.opendev.org/c/zuul/zuul/+/938986 | 23:31 | |
-@gerrit:opendev.org- Adrià Vilanova Martínez proposed wip: [zuul/zuul] 938986: Allow boolean claim rules https://review.opendev.org/c/zuul/zuul/+/938986 | 23:44 | |
-@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: | 23:45 | |
- [zuul/zuul] 938987: Remove root exists check in TreeCache startup https://review.opendev.org/c/zuul/zuul/+/938987 | ||
- [zuul/zuul] 938988: DNM: Reduce parallelization in tests https://review.opendev.org/c/zuul/zuul/+/938988 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!