Install
CI/CD Pipelines
Build/test/deploy across GitHub Actions, GitLab, Jenkins, and progressive delivery.
- 4 Tracked terms
- Last 30 days Feed window
What this topic collects on
An article joins this feed when it matches these terms. Each one is also a search of its own.
Related topics
Latest in CI/CD Pipelines
1538 Jenkins, 169 Harbor and 32 SonarQube Results: The Build Chain Has a Public Address
1+ day, 1+ hour ago (596+ words) Build and release tooling holds the credentials that deploy to production. It is also frequently reachable from the internet, because it was stood up quickly for a project and never moved behind the perimeter. A ZoomEye query set collected on…...
Asking my CI "why did it fail?" — a Jenkins connector for cognee
1+ day, 6+ hour ago (267+ words) I'm a developer from Vietnam, and this is my contribution to WeMakeDevs Mergetober: a new data-source connector for cognee. When a Jenkins build fails, the reason is usually a few lines at the bottom of a long console log. A…...
When GitHub Is Blocked but You Still Need to Push
3+ day, 10+ hour ago (979+ words) Corporate firewalls are rarely all-or-nothing. They are usually the result of a proxy policy, a TLS inspection rule, or a category filter that someone applied years ago and forgot about. That is why you can end up in a situation…...
Stateless GitHub App installation tokens rolled out - GitHub Changelog
6+ day, 16+ hour ago (157+ words) Installation tokens still start with the ghs_ prefix, but they’re now about 520 characters long instead of 40. Token permissions, repository scoping, the one-hour expiration, and the installation access token REST API endpoint are unchanged. Tokens minted before the change continue to work…...
Adding Concurrency Cancellation to GitHub Actions Workflows to Save CI Minutes
6+ day, 19+ hour ago (336+ words) TL;DR: I added the concurrency feature with cancel-in-progress to the CI and E2E GitHub Actions workflows of the lavanderia-crm repo. This prevents overlapping runs on the same branch/PR, cutting down wasted minutes and keeping the pipeline fast. Our CI…...
Actions retention now covers checks, runs, and statuses - GitHub Changelog
1+ week, 20+ hour ago (136+ words) Actions retention now covers checks, runs, and statuses The GitHub Blog As previously announced, checks, workflow runs, and statuses are now governed by the same GitHub Actions retention setting that controls how long artifacts and logs are kept. These records…...
GitHub Just Killed SHA-1 Over HTTPS
1+ week, 4+ day ago (444+ words) On September 15, 2026, GitHub turned off SHA-1 for HTTPS and TLS on github.com and its CDNs. They had been warning about it since April. If your client can't do a TLS handshake without SHA-1, you now get a connection error....
GitHub Actions re-enabled with Mini Shai-Hulud payload still active
1+ week, 6+ day ago (431+ words) Two third-party GitHub Actions previously compromised in a Mini Shai-Hulud campaign were re-enabled by their maintainer and remained accessible for more than a week despite still pointing to malicious code. According to researchers at application security company Socket, starting September…...
Compromised GitHub Actions Came Back Online and Resumed Executing Mini Shai-Hulud Malware
1+ week, 6+ day ago (521+ words) Two actions-cool GitHub Actions have been disabled for a second time after the repositories became accessible last week, months after they were compromised during the May 2026 Mini Shai-Hulud campaign. The affected GitHub Actions are listed below - "On September 16, 2026, both repositories…...
Node 20 is no longer available in GitHub Actions - GitHub Changelog
2+ week, 1+ day ago (150+ words) This is the final notification that Node 20 is no longer available on GitHub Actions runners. Runners now use Node 24 for JavaScript actions. The temporary ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION opt-out is no longer available. If you maintain a JavaScript action, update its runs.using value…...