Providing Technology Training and Mentoring For Modern Technology Adoption
Courseware: Available for sale
“Get the jar files out of version control”. “Get the deployable files out of version control”. These commands are a common theme in software development. Many developers have viewed binary artifacts in version control as a bad thing, regardless of the version control used. However, the alternative usually involves developers keeping a set of libraries, or the development organization keeping a “blessed” build machine that stores all the approved artifacts. Not to mention the inevitable folder of “Gold build” deployable files (jar, war, or exe files). Neither of these approaches nor the many combinations of these approaches is really satisfactory. Development and operations organizations need to have control over what dependency artifacts are used to build their software and central management of the resulting deployable artifacts.
Many newer build tools, like Apache Maven, integrate the concept of dependency management into the build process, including the ability to automatically download dependencies from a central repository. In addition, the Apache Ivy project adds similar dependency-management capabilities to build scripts created using the Apache Ant scripting tool.
This course will provide students with an understanding of the principles of using a central artifact repository in the enterprise environment to both mediate access to public repositories, and serve as a target where production artifacts can be stored for access by other development projects, or operational users.
We’ll touch on management of local and virtual repositories, release management, and integration of a local repository manager with two build tools, Apache Maven and Apache Ivy. We’ll talk about how to use artifact management with the Jenkins continuous integration tool. We’ll also talk about manual deployment of arbitrary artifacts.
We’ll talk about what should happen to “end-state” or deployable artifacts, like “.war” and “.ear” files, as well as other binary artifacts, and how version control is the wrong place for them.
While the course does talk about providing secure access to repositories, we’re dealing with authentication and authorization more from a management policy perspective than from an administrative perspective. This course should not be viewed as a Nexus or Jenkins administration course.
Attendees should have familiarity with Java development practices.
In this training, attendees will learn how to:
Execute a release process on deployable artifacts
2 days.