-
Notifications
You must be signed in to change notification settings - Fork 3
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
Improvement/nsis on GitHub ci #8
base: master
Are you sure you want to change the base?
Changes from 2 commits
4b19710
59d51d5
7f76df1
fb41991
998f65f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
name: nsis | ||
|
||
on: | ||
workflow_run: | ||
workflows: [ Build ] | ||
types: [ completed ] | ||
workflow_dispatch: | ||
|
||
jobs: | ||
config: | ||
if: ${{ github.event.workflow_run.conclusion == 'success' }} | ||
runs-on: ubuntu-latest | ||
outputs: | ||
matrix: ${{ steps.files.outputs.matrix }} | ||
branch: ${{ steps.branch-ref.outputs.name }} | ||
steps: | ||
- uses: actions/checkout@master | ||
with: | ||
ref: ${{ github.event.workflow_run.head_branch }} | ||
|
||
- name: Return Branch | ||
id: branch-ref | ||
run: echo "::set-output name=${{ github.event.workflow_run.head_branch }}" | ||
|
||
- name: Get Script Files | ||
id: list-files | ||
uses: Rishabh510/Path-lister-action@master | ||
with: | ||
path: installers/ | ||
type: .nsi | ||
|
||
- name: Return Script Files | ||
id: files | ||
run: echo "::set-output name=matrix::$(echo "${{ steps.list-files.outputs.paths }}" | sed 's/\//\\/g' | jq --raw-input --compact-output '[splits(" ") | select(length > 0)]')" | ||
|
||
make-installer: | ||
runs-on: windows-latest | ||
needs: [ config ] | ||
strategy: | ||
fail-fast: false | ||
matrix: | ||
file: ${{ fromJson(needs.config.outputs.matrix) }} | ||
steps: | ||
- uses: actions/checkout@master | ||
with: | ||
ref: ${{ github.event.workflow_run.head_branch }} | ||
|
||
- name: Download artifact | ||
uses: dawidd6/action-download-artifact@v2 | ||
with: | ||
workflow: ${{ github.event.workflow_run.workflow_id }} | ||
workflow_conclusion: success | ||
name: hobovr-build-windows-latest | ||
path: ${{ github.workspace }} | ||
|
||
- name: Create nsis installer | ||
id: create-installer | ||
shell: powershell | ||
run: | | ||
"$CONDA\bin\conda.bat execute ${{ matrix.file }}" | ||
working-directory: ${{ github.workspace }}\installers\win | ||
|
||
- name: Upload artifacts | ||
uses: actions/upload-artifact@v3 | ||
with: | ||
name: "hobovr_setup.exe" # Get the Output Name | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This really needs to be a value extracted from the .nsi file in the future, especially if we have multiple outputs. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Honestly, this is a pretty big change already that's been in the works for about a week, so I think moving extra work into todos for after merging is a good idea. I'm not really sure how hard extracting the exe name from the nsi file and putting it in the yml will be though. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @SimLeek I've got this issue about 90% solved using SED in a separate branch already. Should I fold it into this PR? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I mean, if it's 100% solved, sure. From experience though, that last 10% can take 50% of the time. |
||
path: | | ||
hobovr |
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.
Let me know if I should limit this script running to Releases only.
Personally though, I would recommend having a separate Release workflow that executes after the build and nsis/etc workflows to retrieve artifacts from Release tagged builds and creates a proper release here on GitHub.
That way, we could refactor the online installers to always pull the latest release, or to pull specific releases if needed.
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.
I really like the idea of a proper release.
As to whether the script should be limited to releases only, the only reason I could think of for that is size. If one of the installers bundles too much together and pushes us towards some limit, then that could be bad. Otherwise, it'd be nice to click on a specific merge and be able to install it and test it quickly.