Using Jenkins to Automate Artifact Builds and Security
Security breaches often slip through weak CI/CD pipelines—and manual artifact management is a bottleneck you can’t afford. This course teaches you to automate artifact builds and embed security controls directly into Jenkins, eliminating manual handoffs and catching vulnerabilities before production.
AIU.ac Verdict: Ideal for DevOps engineers and platform teams needing to harden their build pipelines without sacrificing speed. You’ll walk away with production-ready Jenkins configurations. Note: assumes basic Jenkins familiarity; pure beginners may need foundational Jenkins knowledge first.
What This Course Covers
You’ll configure Jenkins pipelines to automate artifact creation, versioning, and storage whilst integrating security scanning at each stage. The course covers declarative and scripted pipelines, artifact management best practices, and embedding SAST/DAST tools into your build workflow. You’ll learn how to fail builds on security policy violations and implement approval gates for sensitive deployments.
Practical modules walk you through real-world scenarios: securing credentials in Jenkins, scanning container images before registry push, and auditing artifact provenance. By the end, you’ll have hands-on experience building a complete CI/CD chain that balances automation with compliance—exactly what enterprise teams demand.
Who Is This Course For?
Ideal for:
- DevOps Engineers: Need to accelerate builds whilst maintaining security controls and audit trails.
- Platform/SRE Teams: Building shared CI/CD infrastructure and enforcing security policies across multiple teams.
- Security-Focused Developers: Want to shift-left by embedding vulnerability scanning into the build pipeline, not post-deployment.
May not suit:
- Jenkins Beginners: This assumes you’re comfortable with Jenkins basics; start with Pluralsight’s Jenkins fundamentals course first.
- Non-Technical Stakeholders: This is hands-on technical training, not a management overview of CI/CD strategy.
Frequently Asked Questions
How long does Using Jenkins to Automate Artifact Builds and Security take?
2 hours 43 minutes. Designed for focused, practical learning—you can complete it in one or two sittings.
Do I need Jenkins experience before starting?
Yes, basic Jenkins knowledge is assumed. You should be comfortable with job creation, pipelines, and plugins. If you’re new to Jenkins, complete a fundamentals course first.
Will I get hands-on labs?
Yes. Pluralsight includes interactive sandboxes where you’ll configure real Jenkins pipelines, integrate security tools, and test artifact workflows.
What security tools are covered?
The course covers integration patterns for common SAST/DAST scanners, container image scanning, and credential management—you’ll learn the principles to integrate tools your organisation already uses.
Course by George Smith on Pluralsight. Duration: 2h 43m. Last verified by AIU.ac: March 2026.
