[SYNCOPE-1489] Reorganize Travis CI to run the build suite in stages

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-M0
• Fix Version/s: 3.0.0-M0
• Component/s: build-tools
• Assignee: Francesco Chicchiriccò
• Reporter: Misagh Moayyed
• Created: 09/Sep/19 14:24
• Updated: 05/Aug/22 11:36
• Resolved: 16/Sep/19 10:52

Description

Per discussions on the dev mailing list, this Jira tracks improvements to the Travis CI process to split the build into multiple stages and jobs. The overall task list would include:

1. run the straight "mvn clean install" one normally performs on his /
   her laptop, which involves RAT checks, Checkstyle, modernizer, etc, all
   unit and integration tests
2. run integration tests with different content types [5]
3. run the Admin UI tests [4], currently not run by default under
   fit/core-reference
4. run the Enduser UI tests ([4] for master), currently not run by
   default under fit/core-reference
5. run integration tests under the other supported Java EE containers
   (besides Tomcat) [6]
6. run integration tests with the other supported DBMSes (besides H2)
7. run integration tests with Elasticsearch - not documented but available
8. run SAML 2.0 / OpenID Connect 1.0 login tests - not documented but
   available (only master)

Individual sub-tasks will be created to track the progress for the above list.

 

> [4] http://syncope.apache.org/building#All_integration_tests
> [5] http://syncope.apache.org/building#Other_Content-Type_values
> [6] http://syncope.apache.org/building#Java_EE_containers
> [7] http://syncope.apache.org/building#DBMSes

Issue Links

• links to: GitHub Pull Request #115
• links to: GitHub Pull Request #152
• links to: ML thread

Sub-Tasks

• Basic maven build to verify compilation correctness: Closed
• Add integration tests for DBMSes via Docker: Closed