GitLab Triage Bot

Over the past few months we have been moving projects over to GitLab. For the most part this process has been pretty smooth. Of course, no tool is going to have everything you need to completely transition nor be an immediate replacement for a workflow that you are used to. However, I will say with GitLab’s APIs it has made it pretty easy.

The first order of business was to migrate out of Jira, which is I scripted and wrote up in this article. Then we needed to bring items out of Aha into GitLab, the script and process in this article.

GitLab Triage uses the CI/CD pipelines to run the automations. This makes life quite easy as it all just fits in place with how everything else works and it easily extended by adding additional stages.

As you saw from the GitLab Blog, by default, GitLab Triage looks for the .triage-policies.yml file with its config and this file should be in the root of your project’s repository. I use this as my testing ground. After a policy gets proved out it gets move to the correct location for constant running.

I have a few different config files and associated .gitlab-ci.yml entries so that different policies can be applied at different levels and the config files don’t become too confusing.

I created a triagepolicies directory where my policies live. I created a…

Related posts:

Did you make it till here? Well, pat on your back, your ASpan (we shall abbreviate the word, you know just because) is more than 60% of the people around your vicinity right now. But it has been more…

Teman-teman pengembang aplikasi android pasti sudah tidak asing lagi dengan sebutan WebView. Buat yang belum familiar, WebView adalah view di Android untuk menampilkan sebuah tampilan HTML yang…

A user persona is also known as a customer avatar. You can have a great marketing strategy, great sales funnel and a fantastic offer but if you’re not getting the right people into your funnel then…