Semaphore preflight checks let teams validate branch names before a workflow begins.
With sem-ai 0.4.0, you can ask Claude Code to create these checks directly from your development environment.
In this example, Claude starts configuring a rule that:
• Accepts main and master
• Requires feature branches to use the feat/* pattern
• Blocks noncompliant branches before the pipeline begins
It is a practical way to turn delivery standards into enforceable safeguards while keeping the workflow inside your coding agent.
Watch the full sem-ai 0.4.0 demo on the Semaphore blog:
https://t.co/ITEfLriMxe
#CICD #ClaudeCode #DevOps #AICoding #Semaphore
A code map does not need to start with a complex tool.
Semaphore engineer Marcos began with structured Markdown files that helped his agents trace paths across microservices. The result was faster task startup and shorter prompts.
Watch more: https://t.co/UYN7a5wlX7
Code maps give AI agents a clearer view of code paths, services, and dependencies.
Semaphore engineers are using them to provide better context, reduce token consumption, and help agents make fewer incorrect assumptions.
Full discussion: https://t.co/UYN7a5wlX7
Traditional flaky test rules can miss problems that appear across branches or over time.
Semaphore is exploring a signal based model where reruns and changing results contribute to a flakiness score.
Watch the full update: https://t.co/UYN7a5wlX7
AI agents can generate code quickly. But when a test fails, they need complete context to understand what happened and what should change.
Semaphore is working on richer test reports that preserve more information from individual test runners, making failures easier for developers and AI agents to interpret.
Full product update coming out tomorrow. Stay tuned.
#Semaphore #AITesting #CICD #AICoding #SoftwareTesting
The hard part of a Jenkins migration is not just moving pipelines.
It is untangling legacy plugins, scripts, dependencies, and versions that may no longer be supported.
Try Semaphore: https://t.co/NEoYGDqC3Y
Watch the full talk: https://t.co/FlT3UcgIvt
#Jenkins#CICD#DevOps #DeveloperProductivity
AI agents are only as useful as the context they receive.
When a workflow fails, CI/CD can provide the signals agents need to understand the issue, help fix it, and keep developers moving.
Watch the full talk: https://t.co/y6Sg88i44I
Agentic development shifts the bottleneck from writing code locally to orchestrating agents reliably.
CI is becoming the execution layer: a scalable environment to run, test, and govern those workflows.
Watch the full talk: https://t.co/y6Sg88i44I @BretFisher
🎙️ Podcast drop:
❓ How should your coding agent interact with CI?
❓What do CI platforms need to rethink when our agents control them more than humans?
❓Do I really need to create a PR commit just to run remote testing workflows?
I discussed these questions and more with the @semaphoreci team (now open source) after they spent the last year retooling their platform for agents.
Watch it on YouTube or grab it in your podcast player - DevOps and Docker Talk podcast (we’re now video on Apple Podcasts). My guests: Marko Gacesa and Marcos Filipe.
https://t.co/0sCXBsTSZL
https://t.co/fP1gnHmbSq
#CICD #codingagents #aicicd #continuousintegration #devopsanddockertalk #devops
Rebuilding a pipeline no longer means rerunning every job in the block.
Now Semaphore rebuilds only the jobs that failed. Passing jobs and earlier ones are carried over and reused, keeping your workflow topology intact.
Need the full-block rebuild back? There's a new block_rebuild flag in the YAML for that.
See the full demo:
https://t.co/cZ3GJ4l3iL
The sem-ai engineers will be joining @BretFisher shortly to talk about AI-native CI/CD. Please join us for the live discussion and questions:
https://t.co/QI0g2uYGLF
Marko Gacesa, Head of Product at Semaphore, shares how our engineers shape up the features at Semaphore CI.
Watch the full conversation on CI/CD at Scale with Senors at Scale at:
Youtube: https://t.co/B3shWVULP1
Spotify: https://t.co/RRh1sp6rZd
New homepage. New era of CI. 🚀
Semaphore is now agent-native CI — built for the age of coding agents, not config files. Your agent sets up CI, validates changes before you push, and keeps pipelines fast as your codebase grows. Zero setup. Fully open source.
Give our sem-ai a try at https://t.co/NEoYGDqC3Y
Deployment failed because a CI secret was missing.
sem-ai creates the secret, updates the pipeline to use it, validates the config, and reruns the deployment without leaving the terminal.
https://t.co/SdFIvuVpRZ
https://t.co/5Dw6yq7gVf
#CICD#DevOps#Secrets#AI
Don't push just to see if CI passes.
sem-ai runs your uncommitted changes in a real CI environment using the same machine and image as your pipeline. Test first, push later.
Learn more about sem-ai:
https://t.co/SdFIvuVpRZ
https://t.co/5Dw6yq7gVf
#CICD#DevOps#AI
A flaky integration test failed.
sem-ai finds the failed job and reruns only that block. The passing jobs stay untouched.
Rerun the failure, not the pipeline. ⚡
Try sem-ai out at:
https://t.co/SdFIvuVpRZ
"How's our CI doing this week?"
Pass rate 71%. Avg run ~1 min. Slow ones: 3.5 min.
But the build itself is <30 sec. The rest is queue time. Fix: agent capacity, not the pipeline.
CI health check on demand. That's @semaphoreci
https://t.co/SdFIvuVpRZ