unified autobuild github-action#978
Conversation
This will support macOS < 10.13. Fixes jamulussoftware#959
|
Thank you very much for your work again ;-). Can you also include #964? Edit: seems we had the exact same idea ;-). |
|
will need #962 |
- consistently in three steps: prepare-build-copy - artifacts stored for limited amout of days with the github-action-run - files named by githash/release - auto-creation of releases
e4a12d1 to
a0a2f12
Compare
|
Finally, my work is done! One open question: currently a pull request triggers code-QL warnings ("Please make sure that every branch in on.pull_request is also in on.push so that Code Scanning can compare pull requests against the state of the base branch") For proof of working, see: checks will likely need retriggering, when the submodule issue is solved |
|
Hm. Might need another rebase to pick up the submodule changes, I'm afraid. |
|
Repeating the action would suffice, can someone click „rerun all jobs“ please? |
|
I did. It failed the same. Hence suggesting a rebase might help. |
|
I think the rebase on master is required in order to have #985 included in this PR. |
This comment has been minimized.
This comment has been minimized.
|
I used a normal merge... less effort since i merged ann0see's contributions earlier |
ann0see
left a comment
There was a problem hiding this comment.
First a few overview. I'll look into the functionality soon.
| if: ${{ matrix.config.cmd1_prebuild }} | ||
| run: ${{ matrix.config.cmd1_prebuild }} | ||
| env: | ||
| ACTIONS_ALLOW_UNSECURE_COMMANDS: 'true' # allow setting environment variables |
There was a problem hiding this comment.
Sounds a bit dangerous. Can't you just output environment variables via echo?
There was a problem hiding this comment.
this allos the use of ::set-env name=xxxxxx::${xxxxxxx}
My problem was that autobuild_apk_1_prepare.sh sets a lot of variables, and I dont know which ones are necessary for building then. Doint special treatment for 15 variables via output and mentioning them as environment of next step is not clean any more. I'm open for suggestions.
There was a problem hiding this comment.
Hmm. If you think this is the best way to do it, I would just leave it like that for now.
ann0see
left a comment
There was a problem hiding this comment.
Almost finished. Will look into changing a few things here (and I'll update the branch to the current master branch because of the broken headless build). Afterwards I'll do a new beta release.
| ################### | ||
|
|
||
| echo "Install dependencies..." | ||
| brew install qt5 |
There was a problem hiding this comment.
Todo (not blocking): use aqt and the same process as in the release process.
There was a problem hiding this comment.
There should only be one "Install Qt" (per platform). If it's always needed, always run it (as a workflow step). One workflow. Some steps always run (i.e. those that prepare for what happens later). Some steps only run under certain conditions (branch name, action, target - CodeQL only runs sometimes, publish only runs sometimes).
("target" - this doesn't just mean platform, it includes combinations like "headless server on debian x64".)
835f304 to
edf66a6
Compare
There was a problem hiding this comment.
Aside from the slow CodeQl build, I'd say this is ready once the comments above are answered. There are still some open points, but they're not part of this PR (nefarius2001#6). Therefore I'll approve this. After this (or even now) I think, we could even try it by releasing a new version of Jamulus?
|
|
||
|
|
||
| echo "Building... qmake" | ||
| if [-x /Users/runner/work/jamulus/jamulus/Qt/5.15.2/clang_64/bin/qmake] |
There was a problem hiding this comment.
Did you try it without specifying the full path like this? I found it worked just doing qmake, after running the install in the CodeQL workflow. If it does, it would make it less painful moving from 5.15.2 to 5.9 for the MacOS build.
|
I think there's more to do - but it can wait till after this gets merged. Continuous Improvement means taking "good enough" and making it better, later. This is definitely good enough and better that we have. |
|
#964 though. Is that covered? |
|
Yes. This is included as far as I know. |
|
@pljones I'd wait a bit until @nefarius2001 is finished and afterwards, you can merge it. |
Ah - the confusion is around the CodeQL vs main build - one uses 5.12.2, the other 5.9.9. That can wait (we've been using 5.12.2 for CodeQL up until now) but needs fixing, as we need to verify against the same library base as the build. |
|
Ok. Will merge this now. |
|
There are still some todo items, but I think it's ready. Next big step: Start the release process! |
Work for #854:
single workflow