I’ve been thinking about hosting some example Gitlab CI workflows that use SQLFluff in linting jobs. These could be similar to our sqlfluff-github-actions repo (https://github.com/sqlfluff/sqlfluff-github-actions), but use .gitlab-ci.yml syntax for use in Gitlab.
I think this is a worthwhile effort because many companies use Gitlab for enterprise source control and single-app CI/CD. Having example Gitlab CI workflows will help democratize the use of sqlfluff across more engineering organizations. I’ve already had a few people DM me about how to set up sqlfluff for CI/CD within Gitlab.
Thus, I propose to assign me a SPIKE issue to identify:
- Best way to manage CI workflow code (DONE, will house in this repo)
- CI workflow examples to provide (thinking to adapt the workflows in the sqlfluff-github-actions repo, for .gitlab-ci.yml syntax)
- Examples for importing the CI workflow examples into your own Gitlab project (using documentation here: https://docs.gitlab.com/ee/ci/yaml/includes.html)
Outcome of this SPIKE
- A gist that outlines my implementation roadmap for these workflows, approved by maintainers of this repo.
I’ve been thinking about hosting some example Gitlab CI workflows that use SQLFluff in linting jobs. These could be similar to our sqlfluff-github-actions repo (https://github.com/sqlfluff/sqlfluff-github-actions), but use .gitlab-ci.yml syntax for use in Gitlab.
I think this is a worthwhile effort because many companies use Gitlab for enterprise source control and single-app CI/CD. Having example Gitlab CI workflows will help democratize the use of sqlfluff across more engineering organizations. I’ve already had a few people DM me about how to set up sqlfluff for CI/CD within Gitlab.
Thus, I propose to assign me a SPIKE issue to identify:
Outcome of this SPIKE