it pulls the latest code from snapshot-stable automatically every time. Can you elaborate the "clear upgrade process"?

What is left here to make sure we can use the environment to track performance regressions and address them. We need a clear upgrade process, is it implemented?

Thanks, . You are correct about the graphs. I've scheduled the job to be run daily.

, I believe the Performance graphs need at least two successful builds to show the trend. As for the job frequencies, I have been running it only once a day in our environment.

After some modifications to FOLIO Jenkins and the configuration in the repository, I'm able to get a successful run in FOLIO Jenkins.

https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-test/

I've merged branch into master.

Outstanding:

• It appears that the Performance graphs are not populated. Not sure why this is.

• How do we want to run and use this job? Daily? How will it be reviewed?