Skip to content

ci: Make macOS static bitcoin-qt available from CI task #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 28, 2021

Conversation

hebasto
Copy link
Member

@hebasto hebasto commented Oct 27, 2021

This PR makes bitcoin-qt available for downloading from CI for each PR.

Being downloaded it is required to make it executable with chmod +x bitcoin-qt.

Similar to #71.

A link to download: https://api.cirrus-ci.com/v1/artifact/build/5223626531143680/macos_bitcoin_qt.zip

@hebasto
Copy link
Member Author

hebasto commented Oct 27, 2021

cc @GBKS

@promag promag mentioned this pull request Oct 27, 2021
@promag
Copy link
Contributor

promag commented Oct 27, 2021

Tested ACK b1baa79.

Copy link
Member

@jarolrod jarolrod left a comment

Choose a reason for hiding this comment

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

ACK b1baa79

Tested by downloading and running. This works very nicely! Will add notes on how to get the download link and how to run the downloaded binary in a productivity doc.

@hebasto hebasto merged commit 85dd4d9 into bitcoin-core:main Oct 28, 2021
@hebasto hebasto deleted the 211027-mac-art branch October 28, 2021 03:58
@GBKS
Copy link
Contributor

GBKS commented Oct 28, 2021

@jarolrod thanks for documenting this. Something I've found useful to do is to link to the build preview from the main PR comment. AFAIK, the checks and build info is not visible if you're not logged in to Github. So to make it easier for anyone to preview and give feedback, adding the links directly to the comment can go a long way. Here's an example (the "Peek the preview" link): BitcoinDesign/Guide#537

@@ -267,6 +267,8 @@ task:
env:
<< : *CIRRUS_EPHEMERAL_WORKER_TEMPLATE_ENV
FILE_ENV: "./ci/test/00_setup_env_mac.sh"
macos_bitcoin_qt_artifacts:
Copy link
Contributor

Choose a reason for hiding this comment

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

wouldn't it be good to prefix the artifact name with insecure_, as the CI can't be trusted?

@@ -267,6 +267,8 @@ task:
env:
<< : *CIRRUS_EPHEMERAL_WORKER_TEMPLATE_ENV
FILE_ENV: "./ci/test/00_setup_env_mac.sh"
macos_bitcoin_qt_artifacts:
path: "ci/scratch/build/bitcoin-x86_64-apple-darwin19/src/qt/bitcoin-qt"
Copy link
Contributor

Choose a reason for hiding this comment

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

Wouldn't it be a better UX to move the file to a top level directory first?

Wouldn't it be better to name the file insecure_gui.exe or so?

hebasto added a commit that referenced this pull request Oct 29, 2021
…trusted

319db69 ci: Prefix artifacts names with insecure_ as CI cannot be trusted (Hennadii Stepanov)

Pull request description:

  #73 (comment):
  > wouldn't it be good to prefix the artifact name with `insecure_`, as the CI can't be trusted?

  #73 (comment):
  > Wouldn't it be a better UX to move the file to a top level directory first?
  >
  > Wouldn't it be better to name the file `insecure_gui.exe` or so?

  All of the comments above are addressed in this PR.

  Links to compressed executable binaries for this PR:
  - Windows: https://api.cirrus-ci.com/v1/artifact/build/4507530693967872/insecure_win_gui.zip
  - macOS: https://api.cirrus-ci.com/v1/artifact/build/4507530693967872/macOS%2010.15%20[gui,%20no%20tests]%20[focal]/insecure_mac_gui/insecure_mac_gui.tar.gz

ACKs for top commit:
  MarcoFalke:
    review ACK 319db69
  promag:
    ACK 319db69.
  jarolrod:
    ACK 319db69

Tree-SHA512: b16c98e95c7bbc4d5162434b753f1f08535be6e09106c1f3db6174baef850213f6433cf02569dc46a023b509745b9538339db05ac762c4cb0e189b46ae06794f
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.

5 participants