Automating the process from code commit to deployment and it saves time, reduces errors, and ensures that your applications are always up-to-date. In this project, we will go through a step-by-step journey of setting up a Jenkins pipeline to automate the deployment of our application, which starts with a developer pushing code to GitHub.
active 2023-10-10 → 2024-09-13 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 340 days from 2023-10-10 to 2024-09-13. Pushes: 13 total, peak 10 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| amar-m-cloud | 13 | 13 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
No issue or PR events — this repo's activity is pushes only.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.