[FOLIO-2574] Create folio-integration-tests github repository Created: 29/Apr/20  Updated: 03/Jun/20  Resolved: 11/May/20

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

Type: Story Priority: P3
Reporter: Yauheni Kuzmianok Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by FOLIO-2586 mvn fails on Linux, but okay on macOS... Closed
Relates
relates to FOLIO-2586 mvn fails on Linux, but okay on macOS... Closed
relates to FOLIO-2575 New CI/CD pipeline for Integration tests Closed
Sprint: DevOps: sprint 87, DevOps: sprint 88
Development Team: FOLIO DevOps

 Description   

New module should be created to use new approach for api testing with karate framework

Acceptance Criteria:

The repository folio-integration-tests is created and added to the (Acquisitions github team)
Members of (Acquisitions github team) team can create and merge branches
CI has been setup for the repository, including Jenkins builds and SonarQube analysis



 Comments   
Comment by David Crossley [ 30/Apr/20 ]

I created a new empty repo: https://github.com/folio-org/folio-integration-tests
and configured Team access.

So it is ready for you to add initial code.
Then the Jenkinsfile can be committed directly to master branch. That will do the base Sonar scan.

See some guidelines at https://dev.folio.org/guidelines/create-new-repo/

Comment by Yauheni Kuzmianok [ 30/Apr/20 ]

Hi David Crossley
Additional repo files has been added

Comment by Wayne Schneider [ 01/May/20 ]

David Crossley will add a Jenkinsfile to run mvn package and unit tests.

Is there further CI integration required for this ticket? E.g.: SonarCube analysis, Docker image publishing, etc. Yauheni Kuzmianok, please let us know.

Comment by David Crossley [ 06/May/20 ]

Adding initial basic Jenkinsfile is blocked by FOLIO-2586 Closed .

Comment by Yauheni Kuzmianok [ 07/May/20 ]

David Crossley I've changed the PoC directory to poc to avoid Jenkins issue.
Currently we need only CI integration with Jenkins.
Could you also specify default run command:
mvn test -DargLine="-Dkarate.env=testing"

Comment by David Crossley [ 11/May/20 ]

The basic Jenkinsfile is added. It just ensures that dependencies and declared sub-projects are configured, and that software will build.

The mvn command for running the actual tests will be handled by FOLIO-2575 Closed .

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