Skip to content

Conversation

sorindumitru
Copy link
Collaborator

@sorindumitru sorindumitru commented Jan 16, 2023

Pull Request check list

  • Commit conforms to CONTRIBUTING.md?
  • Proper tests/regressions included?
  • Documentation updated?

Affected functionality
Nightly builds

Description of change
Only run the nightly build job when repository owner (or org) is 'spire'.

Which issue this PR fixes
The nightly build job was triggered from personal forks of this repo. It didn't have access to the necessary secrets so it was failed leading to daily build failure email spam for fork owners.

@sorindumitru sorindumitru changed the title Create nightly_build.yaml Don't run nightly builds from fork Jan 16, 2023
@sorindumitru sorindumitru changed the title Don't run nightly builds from fork Don't run nightly builds from forks Jan 16, 2023
Otherwise this ends up being run on personal forks of projects. It's not a big issue, but fork owners will get nightly messages about build failures.

Signed-off-by: Sorin Dumitru <[email protected]>
@azdagron
Copy link
Member

Thanks @sorindumitru. This won't be needed once #3785 is merged, since it removes publishing to GCR. Nightly will work fine on your fork after that. I'll go ahead and close this in favor of 3785.

@azdagron azdagron closed this Jan 19, 2023
@sorindumitru
Copy link
Collaborator Author

Thanks @sorindumitru. This won't be needed once #3785 is merged, since it removes publishing to GCR. Nightly will work fine on your fork after that. I'll go ahead and close this in favor of 3785.

That sounds ok to me, but that PR still has the login and publish steps in the nightly build, will those be removed?

@azdagron
Copy link
Member

The nightly still publishes to GHCR. Only the publishing of GCR will be removed. Your fork should have no problems publishing the images to GHCR for your org.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants