-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
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
Error on terminus build:env:delete:pr
via GitHub Actions
#472
Comments
Well now the script is working again. Unsure what changed. 🤷 I'll close this for now and re-open if it happens again. |
Re-opening per Pantheon Support request. 👍 |
FWIW - I also see the same behavior happening on the
Clearly something is weird with my GitHub workflow. I added another gist with the updated workflow: https://gist.github.com/screid123/febbf4f81a405ef54565f03c58beedab |
Also getting the same error message on a CircleCI build, using the 'quay.io/pantheon-public/build-tools-ci:8.x-php8.1' image. |
(Opened initially as a Pantheon Support Ticket
752761
)We are using GitHub Actions to deploy/sync our code from GitHub to Pantheon. The workflow we had setup was working fine for weeks up until Thursday, 2-Feb (as far as we can tell), and largely mimics the CircleCI orb/workflow.
The error happens during the “create multidev” step which happens on Pull Request if the environment doesn’t exist. From what I can tell, it seems the
terminus build:env:delete:pr
command is causing problems where it’s requesting info from GitHub but does not submit the correct URL:The URL is malformed as it does not contain the correct repo owner or name, e.g.-
https://api.github.com/repos///pulls?state=all
. When I comment out this command, the workflow runs “normally”, so it really seems to be isolated to thebuild:env:delete:pr
process.Here’s a gist with the raw log output, verbose output from
terminus build:env:delete:pr -vvv
, and a copy of the workflow file. I have even gone as far as adding in all the output vars set by the docker build-tools script used in CircleCI workflows, but the same result.The text was updated successfully, but these errors were encountered: