We are using Gitlab and we’ve done some pretty interesting things with it.
There isn’t a lot of best-practice, or design ideas out on the web for integrating the two. So I wanted to see what other people have gotten up to with it. I’d like to spark some conversation about successes/failures.
Thus far, we have had done some work with
- Getting repositories to automatically build execution environments
- Triggering AWX jobs via awxkit and awx.awx modules
- Updating projects after commits or merges
- Creating sets of templates that run against a branch
- Running ansible directly from execution environments pulled via image:
If you’re reading this, and you’re thinking “Wow, that’s pretty basic”. You’re exactly who I’d like to hear from. We are just starting with this, and I’m curious about the problems we are going to have in 6 months, with how we’re doing things now. You probably already know.
When I first started looking for a way to build an ee with a runner, it took me a week to find anything. It was a link to some repo on a private gitlab instance that was shared publicly. The method he was using was a little cumbersome, but I think it was built before a lot of the things were available. Anyway, we used it to reverse engineer a method of our own.
I’m really interested in Molecule tests. We have dabbled bit it, but our production environments are extremely legacy, most examples are using containers for the tests, we have fairly even split of Windows/Linux, in most cases both are required for any functional testing, and we would love to find a way to at least start moving the ball forward.
We’ve also been wondering about the nature of collection testing vs. role testing. If I commit a change to a role, it should test that role. However, that role might be a dependency, so one would think that the entire collection should be tested before the merge is permitted.