Menu

1 / 2

Beyond GitHub: Universal Clients, Code Quality, and Bitbucket Traps

DEV Community: gitlab·Flude team·3 days ago
#IuOKCmhI
#devtogitlab#devto#dev#gitlab#client
Reading 0:00
15s threshold

Our core was working perfectly, and the SaaS cloud was ready to accept requests. But for third-party developers to easily start using Flude, they needed convenient entry points—integrations with their CI/CD pipelines.

Initially, we wrote a plugin exclusively for GitHub Actions. However, a huge number of projects and commercial teams prefer GitLab and Bitbucket. It became obvious that we needed to extract the logic into a universal "thin client" that would work equally well on the "big three" platforms.

The Thin Client Philosophy

We moved all the base logic into clean, independent JavaScript files ( control-plane-client.js , poll.js , download.js ). No heavy builds or node_modules folders.

Our CI client became as dumb as possible: it simply zips the source code, sends it via API to our SaaS cloud, pings the task status at a set interval, and downloads the final ZIP archive with the generated documentation.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.