[FOLIO-342] Run Jenkin's Maven Project inside Docker container Created: 29/Sep/16  Updated: 12/Nov/18  Resolved: 06/Oct/16

Status: Closed
Project: FOLIO
Components: Continuous Integration
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1 day, 2 hours
Original estimate: Not Specified

Sprint:

 Description   

Running a Maven build in Jenkins utilizing a Maven Project job type inside a Docker container would give us the benefits of both the Maven Project job type as well as an isolated build environment. However, attempts to combine the two has been problematic. Figure out how to use the Maven project type with Cloudbee's Custom Build environment plugin.



 Comments   
Comment by John Malconian [ 29/Sep/16 ]

The first problem I'm running into seems to be the location of MAVEN_HOME. The location of Maven is different on the Jenkin's host than it is in the Maven container. The Maven project job type seems to want to use the Maven configured on the host. Configuring a second Maven location (as it exists in the container) in Jenkin's Global Tools Settings results in a 'maven not found' error. It appears the Maven plugin searches the Jenkin's host for MAVEN_HOME instead of searching inside the container.

Comment by John Malconian [ 06/Oct/16 ]

Have the right combination of Jenkin's Docker plugins installed and configured and a dedicated "slave" Docker image for Maven builds. Converted all module Jenkins builds and pull-requests to run inside container.

Generated at Thu Feb 08 23:05:03 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.