Blog
Blog
Engineering notes, product updates, and the occasional postmortem.
- by The Exlogare team GitFlic Integrations Release Russia
Exlogare now supports GitFlic — the Russian Git hosting with built-in CI/CD
Connect GitFlic in minutes: OAuth, automatic failed-pipeline analysis, and root-cause notifications. Works with gitflic.ru cloud and self-hosted.
- by Exlogare Team GitHub Marketplace Integrations Release
Exlogare is on GitHub Marketplace — install in 60 seconds
Two ways to connect: OAuth (recommended) for individual users and the GitHub App for org-policy / fine-grained access. Plus a standalone GitHub Action for ad-hoc log pushes.
- by Exlogare Team CLI Go DevOps Release
Launching `exl` — the Exlogare CLI is now generally available
Our command-line interface for ingesting CI logs and querying AI root-cause analyses is out. One Go binary, GitHub Releases, deb/rpm package assets, and Docker — no runtime dependencies.
- by Exlogare Team CI/CD security logs DevOps
How to send CI logs to an external service without leaking secrets
A practical checklist for junior and mid-level engineers: which parts of a CI log are safe to send, what to redact first, and how to avoid turning debugging into a token leak.
- by Exlogare Team CI/CD security logs secrets
CI log secrets: 10 places where teams usually forget them
Docker login, npm verbose logs, Terraform debug, kubectl, echoing variables, and test artifacts: where secrets commonly leak into CI logs and how to stop it.
- by Exlogare Team CI/CD logs redaction security
Redacted logs: what to remove from CI logs and what not to redact blindly
Tokens and private keys must be hidden, but job IDs, versions, service names, and exit codes are often required for RCA. Here is the balance between safety and diagnosability.
- by Exlogare Team GitLab CI/CD troubleshooting rules
GitLab CI: `rules`, `workflow`, and why your job did not start
Why a GitLab job is skipped or missing: workflow rules, rules:if, rules:changes, merge request pipelines, and schedules explained for junior and mid-level engineers.
- by Exlogare Team GitLab runner CI/CD troubleshooting
GitLab Runner: docker, shell, and kubernetes executor failure classes
Why the same GitLab job behaves differently on docker, shell, and kubernetes executors: registry auth, volumes/cache, DNS, permissions, and pod scheduling.
- by Exlogare Team CI/CD GitLab GitHub Bitbucket
GitLab, GitHub, and Bitbucket statuses: a mini glossary for DevOps
Pending, running, success, failed, skipped, canceled, required checks, and commit status: what CI statuses mean and why a MR/PR can be red in surprising places.
- by Exlogare Team GitHub Actions CI/CD reusable workflows troubleshooting
GitHub Actions reusable workflows: is the caller or workflow_call at fault?
How to debug reusable workflow failures in GitHub Actions: inputs, secrets, permissions, called workflow SHA, matrix cells, and job IDs without tab-hopping.
- by Exlogare Team Jenkins CI/CD shared library troubleshooting
Jenkins shared library: why the stack trace points to `vars/`, not Jenkinsfile
How to read Jenkins Pipeline failures from shared libraries: `vars/`, `src/`, CPS stack traces, sandbox errors, and what to tell the MR author instead of pasting raw console logs.
- by Exlogare Team monorepo CI/CD logs troubleshooting
Monorepo CI: one pipeline, many packages — how to read the log
How to triage CI logs in a monorepo: affected packages, workspace paths, matrix jobs, cache noise, and why you need the package name, not only a red pipeline.
- by Exlogare Team runner CI/CD troubleshooting DevOps
Self-hosted runner vs shared runner: what changes in CI logs
Why failures on self-hosted runners differ from shared runners: network, registry, disk, cache, tool versions, permissions, and contaminated host state.
- by Exlogare Team CI/CD artifacts security logs
CI artifacts and logs: what to keep, and what not to upload to S3 as-is
Retention, PII, test dumps, screenshots, junit.xml, and env archives: how to store CI artifacts safely without turning S3 into a secret archive.
- by Exlogare Team GitLab CI/CD troubleshooting DevOps
GitLab CI/CD log triage: stop burning time on every red pipeline
GitLab pipelines fail—that is normal. Spending thirty minutes per red job is not. Common failure classes, the usual workarounds, and how to shrink RCA to under a minute.
- by Exlogare Team DORA DevOps CI/CD metrics
The hidden cost of red CI/CD: DORA metrics and time to market
Lead time for changes often stalls not on code but on red pipelines. How context switching hits DORA, why manual log triage risks time to market, and why automating the first triage step matters.
- by Exlogare Team Exlogare CI/CD GitLab product
Why we stopped grepping logs: how Exlogare came to be
A red GitLab pipeline is routine: tens of thousands of log lines and one engineer who knows where to look. Why we built Exlogare and why we believe log triage belongs in software—not the night shift.