Using Jenkins to Build WebSphere Portal Applications for the Enterprise
summary
Jenkins automates builds for WebSphere Portal projects by pulling from Subversion, invoking Ant/Maven and producing portlet WARs, theme artifacts, Java libraries and a single portal application archive (PAA) zip. A Maven parent POM defines modules, a dedicated PAA module uses the resources and assembly plugins to collect artifacts last, and Jenkins jobs trigger snapshot and release builds. Teams hand the PAA to deployment scripts today and plan to have Jenkins push the PAA and run Selenium tests for automated deployments.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:09Agenda
- 2:00Project characteristics
- 3:43Portal artifacts
- 6:16Jenkins
- 6:39Ease of Use
- 7:10Source Control Management
- 7:36Agile Development
- 9:30Maven Release
- 9:52Continuous Deployment
- 10:52Dedicated Maven Project
- 12:01Conclusion
related talks
44mCombining Jenkins with Deployment Automation - Scaling Application
40mIntegrated Pipeline for Private & Public Clouds w/Jenkins, &
04mIntegrating Maven with Jenkins
42mJenkins: Enabling Agility and Efficiency
27mWhy we provisioned 37 Jenkins servers...
44mImproving Software Quality with Jenkins
52mContinuous Delivery of Microservices using Jenkins and Gradle
49mJenkins Workflow: What's Up?
