pipelines-as-code
pipelines-as-code copied to clipboard
Improve e2e tests
- [ ] Test for failures: https://github.com/openshift-pipelines/pipelines-as-code/issues/572
- [ ] Check that PAC has not fail. We currently go in a endless loop for 10mn waiting for a repo update but we don't check if PAC has fail or not.
Check that PAC has not fail
you means like failed to report the status?
If the controller has started the PR, we may need to check the logs for patterns?
If the controller has started the PR, we may need to check the logs for patterns?
ah I see. may be we should add the event = sha in logs so that we can filter them
as they are in json we might be able to do it 🤔
yes exactly! we had this other thread on slack about it : https://coreos.slack.com/archives/C0382KN768J/p1650877373441779?thread_ts=1650876346.239519&cid=C0382KN768J
adding event = sha would be nice but if we configure for push and pull_request both
then on an event logs would be mixed for a sha
may be event = sha & event-type = <> in the logs?
wdyt?
event-type = PullRequest/Push/Comment so that we can user can easliy filter using them