We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Although currently you could write up a requester that would query for the status of the job, e.g.:
- name: Trigger CircleCI id: circle-ci uses: CircleCI-Public/[email protected] env: CCI_TOKEN: ${{ secrets.CCI_TOKEN }} - name: Wait for CircleCI uses: mydea/action-wait-for-api@v1 with: timeout: 3600 url: https://circleci.com/api/v2/project/gh/owner/projectjob/${{ steps.circle-ci.outputs.number }} expected-status: 200 expected-response-field: status expected-response-field-value: success
It is hard to generalize to check for other statuses like failed, etc.
failed
Instead it would be nice to have the code be re-used to wait for the pipeline to complete, e.g.:
- name: Trigger CircleCI id: circle-ci uses: CircleCI-Public/[email protected] env: CCI_TOKEN: ${{ secrets.CCI_TOKEN }} with: wait_for_pipeline: true
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
Although currently you could write up a requester that would query for the status of the job, e.g.:
It is hard to generalize to check for other statuses like
failed
, etc.Describe the solution you'd like
Instead it would be nice to have the code be re-used to wait for the pipeline to complete, e.g.:
The text was updated successfully, but these errors were encountered: