Skip to content

Build workflows fail for PRs opened with a fork #4545

@MarkAckert

Description

@MarkAckert

The current set of Zowe workflows are guaranteed to fail when a PR is opened from a fork due to permissions restrictions in the runner's github account.

We saw this in #4523 and the first failure in the build and packaging workflow was an inability to post a comment back to the PR itself (Comment would say: Build started, failed, ongoing, etc...). There may be more failures further in the workflow and into the cicd-integration workflow, which also posts comments to the originating PR.

We should consider how to improve the workflows so they'll pass from a fork & PR. It may be as simple as disabling comments when the head is a fork (see: label CICD_Quiet), but research is required so we can understand if any other workflow steps are likely to fail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    CI/CDTasks to improve CI/CD process, not related to install packagingPriority - LowenhancementNew feature or request

    Type

    No type

    Projects

    Status

    No status

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions