Adding support for github actions for PKP applications

[withanage]

Github Actions support for PKP applications

Application	Validation	Min	Cypress	Min	Unittests	Min	Upgrade	Min
OJS	✔️	1-2	✔️	25-45	✔️	1-2	✔️	7-8
OPS	✔️	1-2	✔️	20-25	✔️	1-2	✔️	3-2
OMP	✔️	1-2	✔️	57-60	✔️	1-2	✔️	3-20

---

PRS

• pkp/pkp-lib#9214 GA Support ojs#4098
• pkp/pkp-lib#9214 GA Support omp#1483
• pkp/pkp-lib#9214 GA Support ops#594

--

Remarks

• OPS: validation failed on 3 / 10 runs
• OMP: one integration test failed and had to be restarted (similar to Travis) 3 / 8 runs
• GA usage: 50 containers were started randomly and placed in a queue

---

Disucss

1. Shall we run upgrade tests only in pull requests and each upgrade parallaly in its own container ?
   Currently save 7-8 minutes ?

   • Pros:
     • clean code, can easily add windows machines etc. at a later time
   • Cons:
     • uses only one container and installs the pkp application only once
     • have to maintain the variables in yml seperately

2. Validation errors current problem

   • Reason: Linter seems to use a library which only support python 2.7 and no more maintained.
     Easier solution: fork the repository and create python 3.x support (travis 3.8 , GA 3.11 currently)
     Otherwise: look for alternative tools

3. Are the steps explainable enough ?

---

Next steps

1. create the datasets and write back to the dataset repository

---

Early testing

• After merge of pkp/pkp-lib#9214 Cypress move Cypress.env('baseUrl') to Cypress.config('baseUrl') #9216
• copy the following files https://github.com/withanage/ojs/tree/issue%239214/.github/workflows to your repository
  after creating the floder .gihub/workflows

---

Ideas

• Rename Cypress data tests to user names to reflect actions they perform
• Create a configuration to run certain integration tests during development
• Should we run for different database versions to give better recommendations, especially for prs
• Run all application tests in a pkp-lib pull request (we can get rid of commit naming for submodule updates)
• Get rid of all shell scripts
• Regression for each step (calculate mean time per step)