| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Same change as done in https://github.com/InfiniTimeOrg/InfiniTime/commit/c3295d6d2a325f9a7418b15b943342635026926e
But for get-base-ref-size job
The variable substitution I introduced are bash features. So they don't work with sh.
Update the size job to use `bash` instead of `sh` as shell
|
| |
|
|
|
|
|
|
|
|
| |
Firmware build works. But the build size job afterwards fails.
The firmware build uses `shell: bash --noprofile --norc -e -o pipefail {0}` as shell.
The size job uses `shell: sh -e {0}`
The variable substitution I introduced are bash features. So they don't work with sh.
Update the size job to use `bash` instead of `sh` as shell
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This fixes CI on #2121.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
|
| | |
|
| |
|
|
|
| |
Used by script `lv_img_conv.py`, should be provided by docker image, but
until then explicitly install in workflow.
|
| |
|
|
|
| |
InfiniSim has removed the libpng submodule and moved it to a system
dependency.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous version failed, because it looked for the check from the
branch in the fork, but looked for it in the main repo. Now uses the sha
to get the commit on which checks were run.
Previous description
This works by uploading the data from the main workflow with low
permissions as an artifact, then downloading the data in a workflow with
higher permissions to post the comment.
Third party actions are fixed at a commit, in case they get compromised.
Also set the build-firmware VM to ubuntu-22.04, which was missed when
updating workflow deps earlier.
|
| |
|
|
| |
This reverts commit 012c3d25f313148734b4720e376ec24ff6089453.
|
| |
|
|
|
|
|
|
|
|
|
| |
This works by uploading the data from the main workflow with low
permissions as an artifact, then downloading the data in a workflow with
higher permissions to post the comment.
Third party actions are fixed at a commit, in case they get compromised.
Also set the build-firmware VM to ubuntu-22.04, which was missed when
updating workflow deps earlier.
|
| |
|
|
|
|
|
|
| |
The github.event.pull_request.base.sha in the workflow doesn't get
updated when there are new commits in the base branch. Instead always
checkout the branch to check the sha manually and cache only the build.
The ownership fix seems to still be necessary
|
| |
|
|
|
|
|
|
|
| |
* Update workflow dependencies
ubuntu-latest vm has been updated from 20.04 to 22.04.
To avoid sudden issues, use 22.04 explicitly.
CMake doesn't need to be updated on 22.04, but ninja must be installed separately in the simulator workflow.
actions/checkout@v2 uses deprecated Node.js 12.
Update to v3 which uses 16
|
| | |
|
| |
|
|
|
|
|
|
| |
Due to a security concern, comments can only be created in the context
of branches in the repo. PRs from forks can't get the comment.
https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#restrictions-on-repository-forks
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add .github/workflows/getSize.sh to extract sizes of sections from the
objfile
build-firmware uses getSize.sh to output the section sizes.
get-base-ref-size job added, which builds the base branch of the PR and
outputs the section sizes. Caches are used to avoid unnecessary builds
when the base branch hasn't been updated.
leave-build-size-comment job added, which creates or updates a comment
on the PR with the build size information from other jobs.
|
| |
|
|
| |
The workaround is no longer necessary
|
| | |
|
| |
|
|
| |
build artifacts.
|
| |\ |
|
| | | |
|
| |\| |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
| |
Also fix issue where workflow fails on pull requests when the
user who made the pull request doesn't have the secrets set.
Also allow other workflows to be triggered manually.
Also don't trigger any workflows on pull requests to master, as
there shouldn't be any pull requests against master.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
docker image to build the firmware. This allows to avoid the duplication of the build logic in Docker and Github workflow format.
The Dockerfile has been slightly adapted (remove the USER instructions). Docker images are now published in DockerHub (jf002/infinitime-build).
|
| | |
|
| | |
|
| |
|
| |
Rather than using generator-specific build commands (ex. `make` or `ninja`), the CI build now uses `cmake --build` for a more modern, best practices approach.
|
| |
|
| |
By switching the CI/CD workflow to use CMake's `ninja` backend, the build time goes down considerably (~4.5 minutes to ~2) compared to GNU Make
|
| |
|
|
|
|
| |
The recovery image "it is the last chance before a brick",
as described in https://github.com/InfiniTimeOrg/InfiniTime/issues/742#issuecomment-943665960
So just build it to make sure it doesn't silently break, but don't upload it.
|
| |
|
|
|
| |
The documentation https://github.com/JF002/InfiniTime/blob/develop/doc/contribute.md#how-to-submit-a-pull-request-
tells us to make pull requests against `develop` branch.
Update the CI to run on those pull requests to have a check if the PR breaks something unintentionally.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
When installing Cmake you get Error: The add-path command is deprecated and will be disabled on November 16th...
And the file pinetime-mcuboot-app-dfu.zip was being generated as pinetime-mcuboot-app-dfu.zip.zip
|
| |
|