1 / 30

Fully Automated Deployments in Stack 3.2

Using the ALM Module. Fully Automated Deployments in Stack 3.2. Disclaimer. This is a training NOT a presentation. Be prepared to learn and participate in lab Please ask questions Prerequisites: Maven Knowledge https://tech.lds.org/wiki/Java_Stack_Training.

manton
Download Presentation

Fully Automated Deployments in Stack 3.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using the ALM Module Fully Automated Deployments in Stack 3.2

  2. Disclaimer • This is a training NOT a presentation. • Be prepared to learn and participate in lab • Please ask questions • Prerequisites: • Maven Knowledge • https://tech.lds.org/wiki/Java_Stack_Training

  3. Build and Deployment History in ICS • In the beginning Maven and CruiseControl • Produced an .ear • Automated config and deploy Bundles • Produced a .zip with an .ear/.war and envconfig • DB Migrator produced a migration .zip • Anthill Pro replaces CruiseControl • Introduced secondary process execution

  4. Typical Deploy Process Today

  5. Problems with Deploy Process • Application Deploy only thing automated • Difficult to introduce other automations • Deployments initiated 3 different ways • Project build complex • Mixture of artifact build and deploy • Build fails if dev deploy fails (no artifact produced) • Changes to deploy process managed by build team • Testing automated in build but not in promotions

  6. Goals of Deploy Improvements • Support automating most any deploy task • Give team more power to customize deploy automation • Simplify build: separate build and deploy • Once per build vs. Many per build • Make deploy execution consistent (all lanes) • Leverage current investment in Maven • First class Anthill Pro Support • Flexible enough to execute outside of Anthill Pro

  7. Non-Goals for Deploy Improvements • Provisioning (created vs. updated) • Any asynchronous processes (e.g. Approvals)

  8. Introducing the ALM Module • What is the ALM Module? • Maven module packages itself up • Can be executed later • Includes its own dependencies • Contains all build promotion logic

  9. Possible Deploy Task Use Cases • Execute DB migration with build • Execute functional/acceptance tests • Deploy static resources separate from application • Expire cache/CDN on deploy • Push internationalization resources to DB • Update WAM policies (when Exposee is ready) • Deploy several applications at one time • Push shared library to Nexus only when app is promoted.

  10. ALM Module Demo

  11. Maven Lifecycles • Maven uses lifecycles to orchestrate goals • Phases represent steps in a lifecycle

  12. Executing a Lifecycle • Lifecycles are executed by calling a phase • Phase identifies where in lifecycle to stop • Examples: • mvn test • mvn install • mvn clean install • mvnsite-deploy clean • mvn clean compile package install clean

  13. Phases in Lifecycle • Phases in a lifecycle are mapped to plugin goals • Dictated by default, packaging type, and pomconfig

  14. Example Binding in Pom Config <project> … <packaging>war</packaging> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <version>1.0.1</version> <executions> <execution> <goals><goal>enforce</goal></goals> <phase>compile</phase> </execution> </executions> </plugin> </plugins> </build> </project>

  15. ALM the Lifecycle for Deployments • Default Lifecycle builds and managing artifacts • What might a lifecycle for application deployment look like? • Migrate database • Deploy app • Test deployed app • Quiz: • clean install • alm-promote • clean install alm-promote

  16. Packaging the ALM Module • ALM Module creates a .zip containing: • The project • All Dependencies • settings.xml file • Zip can be rerun • Same artifacts

  17. ALM Execution Configuration • Maven profiles represent environments • Profiles allow custom environment configuration • Choose deploy type/server • Execute different tests • Maven properties provide configuration • Deploy Username/Password • Skip test run • Skip DB migration • Defaults in profile->properties • Can be customized on command line “-Dsome=value”

  18. How to execute a post build promotion? • Download alm zip file for project • Execute: mvn -s settings.xml alm-promote • Optionally add appropriate ‘-D’ parameters • Specify env using a maven profile (e.g. -P stage)

  19. Lab 1 https://tech.lds.org/wiki/Using_the_ALM_Module#Lab_1

  20. Customizing ALM Execution

  21. How to Customize ALM Promotion • Maven Plugins (Preferred) • Simplify common complex processes • Cross Platform • Java Platform Scripts (OK) • Ant, Groovy, BeanShell, Java, etc. • Fully customizable • Cross Platform • Shell Scripts (Worst Case) • Executed using maven-exec-plugin • Not Cross Platform

  22. Maven Plugin Options • Stack Tomcat Plugin • Local and SSH Tomcat deploys • Stack Tcat Plugin • Stack DB Migrator Plugin • Stack Test Runner • Stack Was Deploy Plugin • Maven Deploy • Maven Wagon • Maven SCM Plugin

  23. Java Platform Scripts • Write custom scripts executed in Java • Cross Platform • More difficult to maintain • Common scripts will be candidates for plugins • Maven Ant and Antrun Plugins • Very simple to execute ant scripts • Gmaven Plugin • Maven Exec Plugin

  24. Shell Scripts • Custom shell scripts packaged with alm bundle • Executed with maven-exec-plugin • Can come in handy • Not cross platform

  25. Lab 2 https://tech.lds.org/wiki/Using_the_ALM_Module#Lab_2

  26. Executing ALM Promotion in Anthill Pro

  27. Executing through Anthill Pro • Anthill represents an excellent engine for executing ALM Modules • Securely store build artifacts • Can securely handle passwords • Easily add parameters to a maven build • Can track state of builds • Can record and store results from multiple test runs

  28. Roles of new Build System Project Team (Developers) Build Team Add Project to Anthill Take configurable properties from team add them to UI. Enable specified environments • Developer ALM pom.xml for project • Functional Tests? • DB Migration? • Test Groups? (smoke, full, etc) • Identify the Environments to enable • Test on local box • Identify Anthill configurable properties • Skip Plugins? • Usernames and passwords? Java Stack Team • Help developer ALM Module

  29. Demo ALM Module and Anthill Pro

  30. Conclusion • ALM Module provides promotion orchestration • Puts more control in hands of project team • Build process now separate from promotion • Anthill pro is an excellent promotion engine • We hope to see more automated promotions in the future!!!

More Related