You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now I am changing our CCI setup to trigger through a GH Action. This is to allow us to disable these system tests via a specific label. Now, this appears to be working for anything that runs directly on GH.
Using the action from this repo (Also upgraded manually to 1.1, please refactor the example!), I have changed our config.yml file to check if GH_Action matches. This appears to work; as now the tests don't run, and my new job that checks if it doesn't match runs succesfully:
Now my problem is that, the only reason these fail, is because the action itself returns a 404...
The action setup is as simple as it gets:
name: Run CircleCi testson:
pull_request:
types: [opened, synchronize, reopened]jobs:
trigger-circleci:
runs-on: ubuntu-lateststeps:
- name: run system testsid: cci_system_testsuses: CircleCI-Public/[email protected]env:
CCI_TOKEN: ${{ secrets.CIRCLE_CI_TOKEN }}
So I am not entirely sure how this is supposed to work.
Minimum reproduction code
Please see above
Steps to reproduce
No response
Expected behavior
It should correctly trigger the test with the right parameters, so that it can run the tests, and report back in the PR action if they are passing or not.
GitHub Action Version
1.1.0
Other
No response
The text was updated successfully, but these errors were encountered:
After further researching, the running test on CircleCI is from the old integration, so we can assume that the action itself does not trigger anything at all. But Once I visit the URL from the action, I get no error, just the commit history.
Is there an existing issue for this?
Current behavior
Right now I am changing our CCI setup to trigger through a GH Action. This is to allow us to disable these system tests via a specific label. Now, this appears to be working for anything that runs directly on GH.
Using the action from this repo (Also upgraded manually to 1.1, please refactor the example!), I have changed our
config.yml
file to check ifGH_Action
matches. This appears to work; as now the tests don't run, and my new job that checks if it doesn't match runs succesfully:Now my problem is that, the only reason these fail, is because the action itself returns a 404...
The action setup is as simple as it gets:
So I am not entirely sure how this is supposed to work.
Minimum reproduction code
Please see above
Steps to reproduce
No response
Expected behavior
It should correctly trigger the test with the right parameters, so that it can run the tests, and report back in the PR action if they are passing or not.
GitHub Action Version
1.1.0
Other
No response
The text was updated successfully, but these errors were encountered: