#jenkins-devops

Articles tagged with #jenkins-devops

Storing Build Artifacts in AWS S3 and Nexus Repository Manager via Jenkins
After Jenkins builds your Java application and produces a WAR file, that artifact needs to go somewhere safe and retrievable. Leaving it in the Jenkins workspace is not a real option, workspaces get cleaned, servers get terminated, and builds get replaced. Every time a new build runs, the previous artifact is overwritten. This post covers two artifact storage options: AWS S3 (simple, cloud-native) and Nexus Repository Manager (enterprise-grade, self-hosted). Both integrate with Jenkins, and understanding both gives you flexibility to use whichever fits your project's needs.
Jun 11, 20269 min read
Jenkins Master-Worker Architecture: Scaling Your Builds Across Multiple Nodes
As you get more comfortable with Jenkins and your team grows, one server handling all your builds starts to show its limits. Builds slow down, the server gets overloaded, and eventually things start failing or timing out. The solution is the Jenkins master-worker architecture (also called master-agent architecture). This post explains why it exists, how it works, and exactly how to set it up.
Jun 10, 20269 min read