Skip to content

Revert changes from #334 on BuildPR workflow file#365

Closed
ADTC wants to merge 1 commit intogitx:masterfrom
ADTC:buildPR-revert-#334
Closed

Revert changes from #334 on BuildPR workflow file#365
ADTC wants to merge 1 commit intogitx:masterfrom
ADTC:buildPR-revert-#334

Conversation

@ADTC
Copy link
Copy Markdown
Contributor

@ADTC ADTC commented Feb 25, 2023

Pull requests opened from forks will not have access to secrets and variables. We don't need to notarize builds on the master branch or on pull requests. Only the builds from BuildRelease workflow file need to be notarized before making a release.

This reverts changes from #334 on BuildPR workflow file.

Pull requests opened from forks will not have access to secrets and variables. We don't need to notarize builds on the master branch or on pull requests. Only the builds from BuildRelease workflow file need to be notarized before making a release.
@ADTC
Copy link
Copy Markdown
Contributor Author

ADTC commented Feb 25, 2023

@hannesa2 please approve this so we can see whether the builds pass on this forked PR. Then kindly merge, and I can rebase my other PR on it. Thanks.

Note that releases will still have the Apple certificate and notarization as they are through the BuildRelease workflow. Only master and PRs will no longer have it.

BTW if you really want the notarization to happen on master branch, just let me know and I'll create a new workflow file for it. I think it's not necessary but you may have a different idea.

CC @insha

@ADTC
Copy link
Copy Markdown
Contributor Author

ADTC commented Feb 25, 2023

@claytonrcarter Can you please cancel and re-run the ARM64 build? Seems it's stuck waiting for over 2 hours:

image

@hannesa2
Copy link
Copy Markdown
Contributor

The auto start of arm actions-runner is broken. I've to start it manually in the meantime

@ADTC
Copy link
Copy Markdown
Contributor Author

ADTC commented Feb 25, 2023

@claytonrcarter please ignore my last comment. It has finally run. Thank you. All checks passed; ready to merge. @hannesa2

BTW, could you help me with #366?

Copy link
Copy Markdown
Contributor

@hannesa2 hannesa2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to see the usage on every pull request and on master too.

  • This prevent of "surprises" on a release
  • you can use any master builds without security concerns of MacOS

Yes, the disadvantage of this is a non-buildable-fork because of missing variables.

If you want to have a working fork build as well, I recommend a if-condition when variables are missing and skip step in pipeline.

@hannesa2 hannesa2 mentioned this pull request Feb 25, 2023
@ADTC
Copy link
Copy Markdown
Contributor Author

ADTC commented Feb 25, 2023

In that case I'll have a think of this tomorrow and open a new PR. Right now my brain is fried and I need to 💤 .

Closing this one because the requirements changed fully and these changes will have to be reverted anyway.

@ADTC ADTC closed this Feb 25, 2023
@ADTC ADTC deleted the buildPR-revert-#334 branch February 26, 2023 08:14
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