Azure pipeline fails for PRs in fork

[Mike McCready]

Problem description

The workflow azure-ci.yml fails if triggered by a PR submission from a fork.

Analysis

The record key used in the workflow azure-ci.yml is defined as a secret.

cypress-example-kitchensink/azure-ci.yml

Lines 65 to 66 in 164d6fd

           # map the secret Cypress record key as environment variable for this step 
           CYPRESS_RECORD_KEY: $(CYPRESS_RECORD_KEY) 

The project ID is defined in cypress.config.js

cypress-example-kitchensink/cypress.config.js

Line 2 in 164d6fd

 'projectId': '4b7344', 

Comparison with PR from parent

PRs from the parent repository are checked successfully. For example

PR #607
Job 12412776602

shows successful https://cloud.cypress.io/projects/4b7344/runs/23962

[Emily Rohrbough]

@MikeMcC399 Discussed with the team and we intend to remove running these in Azure and we intend to maintain these example configuration for reference. I'll close once we have updated CI to stop running these.

[Mike McCready]

@emilyrohrbough

Discussed with the team and we intend to remove running these in Azure and we intend to maintain these example configuration for reference. I'll close once we have updated CI to stop running these.

That sounds like a good move! Thank you! I will look forward to be able to submit PRs and see only green ticks ✅ instead of ❌!

[Mike McCready]

The issue is resolved now. For example, PR #608 shows

👍🏻

[Mike McCready]

• PR #644 follows up the action from this issue.

• After disabling the Azure Pipelines CI, the status badge in the README: CI Status table needs to be removed, since otherwise it is frozen on the status of the last day of operation (April 3, 2023).