- CI/CD for BCDC api tests
- The Story... How I arrived at using Github Actions
- Workflow that was created
- Opportunities for Improvement
- Not going to have tests of tests, but can have a sonarscan, and build
- Build must only proceed if all of the following are true:
- Pull Request is on Master Branch
- Pull Request has been merged
- Pull Request is closed.
- Always builds on all Pull Requests, no sonar (1/2 day)
- Figure out how to get webhook to actually trigger jenkins
- build with parameter - requires two step with crumb
- Other methods require custom plugin
- github plugin doesn't get the payload.
- Trying to figure out how to send along the payload (1.5 days)
- Figure out workaround with events (.5 days)
- Upgrade code to python3
- realize can't build python3 on jenkins slave...
- could trigger another process on openshift
- Webhook trigger stops working
- figure out why? (2 days)
- no hair left... Git hub actions
- create a .github/workflow folder, see folder... Stick your workflow in there
- Trigger is configured in the workflow YML file
- monitor / debug using Actions tab.
- configure your secrets in settings tab
- Could do a containerized run of Sonar to reduce the number of times it needs to be downloaded. / efficiencies
- investigate separation of the sonar run, so it takes place on all pushes
- possibly use sonar cloud