[FOLIO-538] CI mod-users maven integration-test Created: 04/Apr/17  Updated: 12/Nov/18  Resolved: 13/Apr/17

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

Type: Bug Priority: P3
Reporter: Julian Ladisch Assignee: John Malconian
Resolution: Done Votes: 0
Labels: sprint12
Remaining Estimate: Not Specified
Time Spent: 2 hours
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-532 mod-users runtime failure Closed
Sprint:

 Description   

Jenkins does not run mod-users' integration tests because maven is invoked with "clean package":
https://jenkins-aws.indexdata.com/job/mod-users-pull-request/12/consoleFull



 Comments   
Comment by John Malconian [ 04/Apr/17 ]

Julian Ladisch What should be invoked here?

Comment by Julian Ladisch [ 04/Apr/17 ]

maven clean integration-test

Other modules like raml-module-builder invoke maven clean deploy -DdeployAtEnd=true

Comment by Julian Ladisch [ 05/Apr/17 ]

That pull request has changed some unit tests to become integration tests. Maven runs unit tests before the package phase and integration tests after the package phase. It runs the deploy phase after the integration-test phase:

https://maven.apache.org/ref/3.3.9/maven-core/lifecycles.html

Comment by John Malconian [ 13/Apr/17 ]

'mvn clean integration-test' implemented for mod-users and mod-users-pull-request Jenkins jobs. Needed to update Postgresql to 9.6 on build node.

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