Jenkins Build Failure Alerts via Text: Reach On-Call Engineers in Seconds

No. Jenkins ships email and chat notifications, not SMS. The official Jenkins SMS Notification plugin at plugins.jenkins.io/sms is up for adoption (no active maintainers), and the TwilioNotifier plugin is also up for adoption. To send SMS from Jenkins reliably, point an existing notification channel like Email-ext at an email-to-SMS gateway like TextBolt. Address the build failure email to +1[phone]@sendemailtotext.com and the message arrives as an SMS from your business number.

The Jenkins SMS Notification plugin (plugins.jenkins.io/sms) and the TwilioNotifier plugin are both up for adoption with no active maintainers. Engineering teams running these in production have unmaintained code in their post-build actions. TextBolt is a maintained replacement: instead of a plugin, you add the TextBolt gateway address as a recipient in the Email-ext post-build action (or in the Jenkinsfile emailext step). The build failure email becomes an SMS on a registered 10DLC business number, and there’s no plugin to install or upgrade.

Configure Jenkins Email-ext SMTP first under Manage Jenkins, System, E-mail Notification. Most teams use smtp.gmail.com on port 465 with SSL or port 587 with TLS, authenticated with a Gmail App Password. Then add the TextBolt gateway address as a recipient in the Email-ext post-build action. The Email-ext plugin you already use sends the build failure email to that address, and TextBolt converts the email into an SMS to the on-call engineer. The same pattern works in the Jenkinsfile emailext step inside post failure, in the legacy Mailer plugin recipient list, and in shared pipeline libraries. No new Jenkins plugin is installed and no Groovy code is added.

Yes. TextBolt’s gateway address works as a recipient in any Jenkins notification channel that sends email. The Email Extension plugin (email-ext), the legacy Mailer plugin, the emailext step in declarative and scripted pipelines, shared pipeline libraries, and pipeline templates all accept the gateway address alongside existing email recipients. Multibranch jobs inherit the recipient list. The same applies to CloudBees CI Email Notifier configurations.

PagerDuty, Opsgenie, FireHydrant, and incident.io are full-stack incident response platforms with on-call schedules, escalation policies, post-mortems, runbook automation, and integrations across the SRE stack. They’re the right fit when on-call engineering is a formal program with rotation management. TextBolt covers a different, lighter job: just the SMS-to-on-call hop for the build failure, without the IRM platform layer. The two approaches each cover different SMS jobs and tend to be picked alongside, not instead of, TextBolt: small engineering teams pick TextBolt; mature SRE programs pick an IRM platform and may still use TextBolt for the lighter notification surface.

Yes. TextBolt registers your sender identity with The Campaign Registry as part of onboarding, so SMS sent from Jenkins through TextBolt routes through carrier-approved 10DLC infrastructure. This satisfies FCC business SMS requirements. Carrier 10DLC approval typically takes 1-2 business days, separate from the 30-minute hands-on setup.

Yes. When the on-call engineer texts back to acknowledge the page or escalate, the reply arrives as an email in the inbox of whoever the original Jenkins email-ext recipient list pointed to, threaded with the original build failure email when possible. The team lead and platform team see the acknowledgment in the same email thread Jenkins started. No webhook required.

Yes. Standard plan ($49/month) and Professional plan ($99/month) include multi-user access for up to 10 team members on a shared TextBolt account. The whole on-call rotation, release engineers, platform team, and engineering leads share one account and one toll-free business number. No per-seat fees inside the 10-engineer cap. Enterprise plans support custom team sizes for larger orgs.

About 30 minutes of hands-on configuration: TextBolt account creation, toll-free number selection, and adding the gateway address to the Email-ext post-build action or Jenkinsfile emailext step. Carrier 10DLC business verification runs in parallel and typically takes 1-2 business days. Once your number is approved, the on-call engineer gets a build failure SMS the next time a job fails.

Basic plan starts at $29/month for 500 SMS credits and a single user. Standard plan is $49/month for 1,000 credits with multi-user access for up to 10 team members on a shared account. Professional plan is $99/month for 2,500 credits with the same 10-user shared access. Enterprise plans cover 5,000+ credits with custom team sizes. There is a one-time $45/year setup fee for the toll-free business number. Annual plans include a 20% discount.

Slack and Microsoft Teams mobile push are great for the team channel and the daily build feed, and most engineering teams already run them. They become unreliable for the on-call hop because quiet hours, Do Not Disturb, presence rules, and per-channel mute deliberately silence notifications outside working hours, which is exactly when overnight pipelines fail. SMS bypasses chat-app silencing because the carrier delivers it as a phone alert that follows the on-call engineer’s phone ring rules. Most teams that adopt TextBolt for Jenkins keep their existing Slack or Teams build channel and add SMS as a second recipient on the failure trigger, not as a replacement.