This project showcases the implementation of four different Jenkins triggers for automating pipeline execution. All configurations are performed on a Jenkins instance hosted on an AWS EC2 machine.
⚠️ Note: The Remote Build Trigger is excluded due to security concerns related to exposing credentials.
-
Automatically starts the Jenkins job when changes are pushed to a GitHub repository.
-
Configured via GitHub Webhooks and Jenkins Git plugin.
-
✅ Ideal for real-time CI/CD pipelines.
Untitled.video.-.Made.with.Clipchamp.mp4
-
Periodically checks the Git repository for changes using CRON syntax.
-
Triggers a build only if changes are found.
-
🕒 Useful when webhooks are not permitted by network policy.
2nd.-.Made.with.Clipchamp.1.1.mp4
-
Uses Jenkins' built-in CRON feature to run jobs at fixed times.
-
Example: Daily at midnight or every 5 minutes.
-
📅 Ideal for routine tasks like backups, reports, or cleanup scripts.
scheduled.-.Made.with.Clipchamp.1.mp4
-
Automatically runs a downstream job after the upstream job finishes.
-
⛓️ Helps in maintaining a sequential flow of dependent jobs.
-
Configured using Post-build Actions → Build other projects.
oneafterother.-.Made.with.Clipchamp.1.mp4
- Jenkins Version: Version 2.516.1
- OS: Ubuntu (AWS EC2)
- Tools Used: Jenkins, GitHub, Cron, webhook
The Remote Build Trigger was not implemented because:
- It requires exposing an API token or Jenkins user credentials.
- If not properly secured, it can lead to unauthorized job exe.
- but i have added doc decribing how to do it.