SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Adding Concurrency with `cancel-in-progress` to GitHub Actions CI to Cut Build Minutes

0
·7 views

Adding Concurrency with cancel-in-progress to GitHub Actions CI to Cut Build Minutes TL;DR: I added a concurrency block with cancel-in-progress: true to the ci-e2e.yml workflow, preventing overlapping runs on the same branch. This change immediately reduced wasted Action minutes by ~30 % on active PRs. Our CI pipeline (.github/workflows/ci-e2e.yml) was triggered on every push to a branch and on a cron schedule. When a developer pushed multiple commits quickly, GitHub started a new workflow run before the previous one finished. Since each run executes the full end‑to‑end test suite, overlapping

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

OverTheWire Bandit Level 2 Writeup — Read a Filename With Spaces

The password file is named spaces in this filename. The shell splits unquoted arguments on whitespace, so the filename has to be quoted or escaped to be treated as one argument. Platform: OverTheWire Bandit Category: Linux Fundamentals Level: 2 → 3 Difficulty: Beginner Technique: Shell quoting and escaping Level 2's home directory has one file, but its name contains spaces. In a shell, unquoted spaces separate arguments — so typing the filename as-is splits it into several nonsense arguments instead of one filename. "Level Goal: The password for the next level is stored in a file called spaces

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

Refined Sites for Jira Service Management: The Honest Assessment

Refined Sites for Jira Service Management: The Honest Assessment When an employee needs to report a broken laptop, submit a leave request, or raise an IT incident, the last thing they should be thinking about is how to navigate the tool. They should be thinking about their problem. The moment your service portal becomes the obstacle — confusing layout, corporate-grey aesthetic, request forms buried three clicks deep — you've already lost the self-service argument before a single ticket is filed. Jira Service Management is technically capable. The backend — queues, SLAs, automations, approvals

0 comments Read more at DEV Community