[FOLIO-1285] create new repository for aut perf test infrastructure and perf tests/benchmarks Created: 13/Jun/18  Updated: 12/Nov/18  Resolved: 24/Jul/18

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

Type: Task Priority: P3
Reporter: Jakub Skoczen Assignee: John Malconian
Resolution: Done Votes: 0
Labels: ci, sprint40, sprint41, sprint42, sprint43
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-1245 create automated performance testing ... Closed
Sprint:

 Description   

Hongwei Ji John Malconian Guys please update the description of this issue with detail (links) when this is completed.

Wayne Schneider as discussed please review the automation scripts/pipelines when they are available in the repository (e.g especially stuff related to loading data, upgrading modules, etc).

shale99 please review the jUnit tests/benchmarks when available in the repository in order to understand that the issue we are addressing in circ and inv are covered.



 Comments   
Comment by Hongwei Ji [ 13/Jun/18 ]

With help from John Malconian, a new repo is created: https://github.com/folio-org/folio-perf-test. The first PR https://github.com/folio-org/folio-perf-test/pull/1 is up for review by John Malconian, Wayne Schneider and shale99.

Comment by Wayne Schneider [ 13/Jun/18 ]

I made extensive comments on the PR referenced above. This is really great work, Hongwei Ji! I asked for input (on the PR) from David Crossley and John Malconian, once they've weighed in, I think we should merge and close this issue, then figure out where to go from here (i.e., get the job set up in the FOLIO Jenkins instance, add a frontend build step, refine the data loading step, etc.).

Comment by John Malconian [ 13/Jun/18 ]

We'll need to make modifications to the Jenkinsfile so that it works with FOLIO Jenkins. Don't merge just yet, otherwise Jenkins will automatically attempt to run it.

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