Course #:WA2404 Managing Software Dependencies and Artifacts with Nexus, Apache Maven, and Apache Ivy Training Download Sample Labs 11/09/2020 - 11/10/2020 USD$1,195.00 Instructor Led Virtual 11/16/2020 - 11/17/2020 USD$1,195.00 Instructor Led Virtual 11/23/2020 - 11/24/2020 USD$1,195.00 Instructor Led Virtual 01/04/2021 - 01/05/2021 USD$1,195.00 Instructor Led Virtual 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. Prerequisites Attendees should have familiarity with Java development practices. Objectives In this training, attendees will learn how to: Install and configure Jenkins and Nexus in a servlet container Create Nexus repositories of various kinds Configure Maven projects to use Nexus repositories Create and configure Apache Ivy/Ant build scripts to access Nexus repositories. Configure and use Apache Ant and Apache Maven with Jenkins Execute a release process on deployable artifacts Duration 2 days. Outline of Managing Software Dependencies and Artifacts with Nexus, Apache Maven, and Apache Ivy Training Chapter 1. Introduction to Dependency Management Terminology and Basic Concepts Artifacts Build Process Source Code and Source Code Management Development Process Managing Code Dependencies Repeatable Build Dependency Management Historical Dependency Management Practices Dependencies in Version Control? Modern Practices Conclusion Chapter 2. Introduction to Continuous Integration and Jenkins-CI Agile Development Agile Development (cont'd) What is Continuous Integration What is Continuous Integration (cont'd) What is Continous Integration (cont'd) Typical Setup for Continuous Integration Jenkins Continuous Integration Jenkins Features Running Jenkins Summary Chapter 3. Repository Management Maven's Approach to Artifacts Publishing Artifacts Summary of Maven's Artifact Handling Repository Repository Manager Proxy Remote Repositories Types of Artifacts Release Artifacts Snapshot Artifacts Reasons to Use a Repository Manager Repository Coordinates Addressing Resources in a Repository Summary Chapter 4. Installing and Running Jenkins Downloading and Installing Jenkins Running Jenkins as a Stand-Alone Application Running Jenkins on an Application Server Installing Jenkins as a Windows Service Summary Chapter 5. A Jenkins Job Different types of Jenkins job Configuring Source Code Management(SCM) Working with Subversion Build Triggers Schedule Build Jobs Polling the SCM Maven Build Steps Summary Chapter 6. Apache Ivy What is Apache Ivy Using Ivy Basic Operation Typical Dependency Life Cycle Ivy.xml Using Maven Dependencies The 'build.xml' file When You Run the Build Script... Reporting Dependencies Installing Ivy Ivy Settings File Conclusion Chapter 7. Introduction to Apache Maven Build Tools for Java Build Tools for Java (cont'd) History of Build Tools Traditional Scripting 'make' Problems with Make Manual Build with JavaC ANT Pros and Cons of Ant Apache Maven Goals of Maven What is Apache Maven? What is Apache Maven (cont'd) Why Use Apache Maven? The Maven EcoSystem Consistent Easy-to-Understand Project Layout Convention Over Configuration Maven is Different Maven Projects have a Standardized Build Effect of Convention Over Configuration Importance of Plugins A Key Point on Maven! Summary – Key Features of Maven Chapter 8. Installing and Running Apache Maven Downloading Maven Installing Maven Run From Command Line Running Inside an IDE Settings.xml Local Repository Summary Chapter 9. Getting Started With Maven Terminology and Basic Concepts Artifacts Lifecycle Default Lifecycle Plugins Running Maven - the Story So Far Running Maven from an IDE Common Goals pom.xml Example Example (cont'd) Artifact Coordinates Standard Layout for Sources Summary Chapter 10. Nexus Repositories Sonatype Nexus Nexus Editions Types of Repositories Publishing Artifacts – From Maven Publishing Artifacts – Manually Lab Chapter 11. Release Management What is release Management? Release Management with Nexus Release Management with Maven Summary Chapter 12. Introduction to DevOps DevOps Collaboration of People Convergence of Process DevOps Builds on Process Theory DevOps Tools Conclusion We regularly offer classes in these and other cities. Atlanta, Austin, Baltimore, Calgary, Chicago, Cleveland, Dallas, Denver, Detroit, Houston, Jacksonville, Miami, Montreal, New York City, Orlando, Ottawa, Philadelphia, Phoenix, Pittsburgh, Seattle, Toronto, Vancouver, Washington DC. View Course Outline Share This Request On-Site or Customized Course Info Lab Setup Guide REGISTER FOR A COURSEWARE SAMPLE x Sent First Name Last Name Email Request On-Site or Customized Course Info x Sent First Name Last Name Phone Number Company Name Email Question
Course #:WA2404 Managing Software Dependencies and Artifacts with Nexus, Apache Maven, and Apache Ivy Training Download Sample Labs 11/09/2020 - 11/10/2020 USD$1,195.00 Instructor Led Virtual 11/16/2020 - 11/17/2020 USD$1,195.00 Instructor Led Virtual 11/23/2020 - 11/24/2020 USD$1,195.00 Instructor Led Virtual 01/04/2021 - 01/05/2021 USD$1,195.00 Instructor Led Virtual 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. Prerequisites Attendees should have familiarity with Java development practices. Objectives In this training, attendees will learn how to: Install and configure Jenkins and Nexus in a servlet container Create Nexus repositories of various kinds Configure Maven projects to use Nexus repositories Create and configure Apache Ivy/Ant build scripts to access Nexus repositories. Configure and use Apache Ant and Apache Maven with Jenkins Execute a release process on deployable artifacts Duration 2 days. Outline of Managing Software Dependencies and Artifacts with Nexus, Apache Maven, and Apache Ivy Training Chapter 1. Introduction to Dependency Management Terminology and Basic Concepts Artifacts Build Process Source Code and Source Code Management Development Process Managing Code Dependencies Repeatable Build Dependency Management Historical Dependency Management Practices Dependencies in Version Control? Modern Practices Conclusion Chapter 2. Introduction to Continuous Integration and Jenkins-CI Agile Development Agile Development (cont'd) What is Continuous Integration What is Continuous Integration (cont'd) What is Continous Integration (cont'd) Typical Setup for Continuous Integration Jenkins Continuous Integration Jenkins Features Running Jenkins Summary Chapter 3. Repository Management Maven's Approach to Artifacts Publishing Artifacts Summary of Maven's Artifact Handling Repository Repository Manager Proxy Remote Repositories Types of Artifacts Release Artifacts Snapshot Artifacts Reasons to Use a Repository Manager Repository Coordinates Addressing Resources in a Repository Summary Chapter 4. Installing and Running Jenkins Downloading and Installing Jenkins Running Jenkins as a Stand-Alone Application Running Jenkins on an Application Server Installing Jenkins as a Windows Service Summary Chapter 5. A Jenkins Job Different types of Jenkins job Configuring Source Code Management(SCM) Working with Subversion Build Triggers Schedule Build Jobs Polling the SCM Maven Build Steps Summary Chapter 6. Apache Ivy What is Apache Ivy Using Ivy Basic Operation Typical Dependency Life Cycle Ivy.xml Using Maven Dependencies The 'build.xml' file When You Run the Build Script... Reporting Dependencies Installing Ivy Ivy Settings File Conclusion Chapter 7. Introduction to Apache Maven Build Tools for Java Build Tools for Java (cont'd) History of Build Tools Traditional Scripting 'make' Problems with Make Manual Build with JavaC ANT Pros and Cons of Ant Apache Maven Goals of Maven What is Apache Maven? What is Apache Maven (cont'd) Why Use Apache Maven? The Maven EcoSystem Consistent Easy-to-Understand Project Layout Convention Over Configuration Maven is Different Maven Projects have a Standardized Build Effect of Convention Over Configuration Importance of Plugins A Key Point on Maven! Summary – Key Features of Maven Chapter 8. Installing and Running Apache Maven Downloading Maven Installing Maven Run From Command Line Running Inside an IDE Settings.xml Local Repository Summary Chapter 9. Getting Started With Maven Terminology and Basic Concepts Artifacts Lifecycle Default Lifecycle Plugins Running Maven - the Story So Far Running Maven from an IDE Common Goals pom.xml Example Example (cont'd) Artifact Coordinates Standard Layout for Sources Summary Chapter 10. Nexus Repositories Sonatype Nexus Nexus Editions Types of Repositories Publishing Artifacts – From Maven Publishing Artifacts – Manually Lab Chapter 11. Release Management What is release Management? Release Management with Nexus Release Management with Maven Summary Chapter 12. Introduction to DevOps DevOps Collaboration of People Convergence of Process DevOps Builds on Process Theory DevOps Tools Conclusion We regularly offer classes in these and other cities. Atlanta, Austin, Baltimore, Calgary, Chicago, Cleveland, Dallas, Denver, Detroit, Houston, Jacksonville, Miami, Montreal, New York City, Orlando, Ottawa, Philadelphia, Phoenix, Pittsburgh, Seattle, Toronto, Vancouver, Washington DC. View Course Outline Share This Request On-Site or Customized Course Info Lab Setup Guide REGISTER FOR A COURSEWARE SAMPLE x Sent First Name Last Name Email Request On-Site or Customized Course Info x Sent First Name Last Name Phone Number Company Name Email Question
