Just last week, we shared the exciting news about the Flare-Jira integration, and today, we're delighted to introduce yet another powerful integration: GitLab.
Configuring GitLab
GitLab stands out for its remarkable self-hosting capabilities, allowing you to set up your instance for complete control. Alternatively, you can seamlessly leverage the cloud version by registering on gitlab.com. The best part? Flare effortlessly supports both options, granting you the freedom to choose the setup that suits your preferences:
For those opting for the cloud version, the process is as straightforward as authorizing the Flare application.
However, if you're venturing into self-hosting, worry not – we've prepared a comprehensive wizard to walk you through the process of creating a Flare app within your GitLab instance:
Once successfully connected, you can fine-tune which Flare projects engage with specific GitLab projects. Tailor settings to your liking, deciding what should occur with a linked issue when an error is resolved or is unresolved:
Creating and Managing Issues
With Flare configured to sync seamlessly with GitLab, a new button emerges on every error within the project, revealing linked issues:
From this panel, you can quickly create a new issue:
Or link an existing issue using its URL:
Two-way sync?
Our GitHub and Jira integration have a two-way sync, which means that if something happens on GitHub/Jira, Flare will react. For example, if you close an issue on GitHub with a Flare error linked to it, then Flare can automatically resolve the error for you.
Such functionality does not exist (yet?) for GitLab. We'll discuss it in a blog post later this month; stay tuned!
A Year of Integrations
That's it for now. This year, we've released two new integrations: Jira & GitLab, and we've completely rewritten our GitHub integration.
Are there any other integrations you love to see in Flare? Let us know, and your integration of choice might be our next project!
Continue reading
Create richer issues from your errors
When Flare creates an issue on GitHub, GitLab or Linear, you can now pick the assignee and labels right away.
Ruben
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
