[FOLIO-1703] Add Jenkins Job which supports running (JMeter) performance tests from test branches Created: 15/Jan/19 Updated: 03/Jun/20 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P3 |
| Reporter: | Carole Godfrey | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ci, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
|
Members of the spitfire development team and other EPAM teams are contributing to JMeter performance tests as part of this project — https://github.com/folio-org/folio-perf-test There is a Jenkins job https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/ which pulls from above GitHub repo (Master branch) daily at 4:40 PM to run these tests. While creating tests, the developers work on a branch and run locally against a vagrant box to test things out. Prior to committing to master, they would like to execute these tests against a Jenkins job (which execute against their branch instead of master) to confirm that there are no issues with the Jenkins Job execution of the test Would like to understand if there would be any options for a revised or separate job to support testing of test branches of JMeter tests for this purpose |