-
Notifications
You must be signed in to change notification settings - Fork 142
proxy: release CI #3634
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
base: master
Are you sure you want to change the base?
proxy: release CI #3634
Conversation
5e04363
to
d99a747
Compare
shasum -a 512 build/nimbus_verified_proxy > "nimbus_verified_proxy.sha512sum" | ||
- name: Upload release binary artifacts | ||
if: success() && startsWith(github.ref, 'refs/tags/') | ||
uses: actions/upload-artifact@v4 | ||
with: | ||
name: proxy-${{ matrix.os }}-${{ matrix.cpu }} | ||
path: | | ||
build/nimbus_verified_proxy* | ||
if-no-files-found: warn | ||
|
||
- name: Upload release checksum artifacts | ||
if: success() && startsWith(github.ref, 'refs/tags/') | ||
uses: actions/upload-artifact@v4 | ||
with: | ||
name: proxy-${{ matrix.os }}-${{ matrix.cpu }}-checksum | ||
path: | | ||
build/nimbus_verified_proxy.sha512sum | ||
if-no-files-found: warn |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this means the release will misbehave when the current verified proxy CI hasn't finished it's build?
i.e release might use stale artifacts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, I just realised github workflows are not pipelined. Should I go ahead and pipeline the workflows or should I just rebuild the verified proxy for the release job(rebuilding seems wasteful)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, I just realised github workflows are not pipelined. Should I go ahead and pipeline the workflows or should I just rebuild the verified proxy for the release job(rebuilding seems wasteful)?
Whatever gets selected here, please also think ahead in the sense that nimbus_portal_client will also need to be added to the release binaries eventually
@@ -133,9 +133,22 @@ jobs: | |||
cat linux-arm64-checksum/* >> release_notes.md | |||
echo '# Windows AMD64' >> release_notes.md | |||
cat windows-amd64-checksum/* >> release_notes.md | |||
echo '# macos ARM64' >> release_notes.md | |||
echo '# MacOS ARM64' >> release_notes.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Official capitalization is macOS
cat proxy-linux-arm64-checksum/* >> release_notes.md | ||
echo '# Windows AMD64' >> release_notes.md | ||
cat proxy-windows-amd64-checksum/* >> release_notes.md | ||
echo '# MacOS ARM64' >> release_notes.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also macOS
.
The expected correct way would to implement the VP distribution build into This currently generates EL build, but should also generate a VP build |
No description provided.