{{ steps.cypress.outputs.dashboardUrl }}
# i-need-helpe
echoing-actor-29720
04/14/2023, 7:29 PMHello!
Using custom command to run cypress tests with cypress-io/github-action@v5 prevents printing the dashboardUrl. Is there any way to overcome this issue?
Here is how I use it:
- uses cypress-io/github-action@v5
with:
Install: false
record: true
command: $run-cypress-with-grepTags
I want to keep running cypress with tags so I guess I have to use custom command. The above approach doesn’t print {dashboardUrl}
m
many-airline-45402
04/14/2023, 8:11 PMHi @echoing-actor-29720 There was a similar discussion in https://github.com/cypress-io/github-action/issues/511. Also it's documented in https://github.com/cypress-io/github-action#outputs.
I guess if you have your project ID stored in a config file you could print out a URL based on that, but it would not know the run ID, so it would be something like https://cloud.cypress.io/projects/3tb7jn instead.
If the project ID is stored in a secret, that would be more difficult.
e
echoing-actor-29720
04/14/2023, 9:02 PMHi, that issue exactly where I’m coming from. Thanks for updating the documents. As you mentioned, I can print the url till project ID but I need complete url with run ID so I can link it another reporting tool I use.
echoing-actor-29720
04/17/2023, 10:09 PMHey! I no longer use custom commands in cypress action but I’m still not getting the value of {{ steps.cypress.outputs.dashboardUrl }}. I’m using action@5 with record:true. My cypress version 12.7.0
echoing-actor-29720
04/17/2023, 10:28 PMI use command-prefix if that matters.
echoing-actor-29720
04/17/2023, 10:29 PMWow, that was the issue. It doesn’t print dashboardUrl if you use command-prefix also.
m
many-airline-45402
04/18/2023, 8:00 AMThe issue https://github.com/cypress-io/github-action/issues/511 also mentioned
command-prefix