According to GitHub documentation:
> The schedule event can be delayed during periods of high loads of
> GitHub Actions workflow runs. High load times include the start of
> every hour. If the load is sufficiently high enough, some queued jobs
> may be dropped. To decrease the chance of delay, schedule your
> workflow to run at a different time of the hour.
During initial tests it turned out that during peak hours the schedule
didn't execute.
Change-Id: Idcbaed6fc43cf517f616842b7ed7acc7886bea13
Signed-off-by: Marek Pikuła <m.pikula@partner.samsung.com>
pull_request:
workflow_dispatch:
schedule:
- - cron: "0 0 * * 0"
+ - cron: "9 0 * * 0"
env:
REGISTRY: tizen-system-upgrade-tools-docker-local.bart.sec.samsung.net
pull_request:
workflow_dispatch:
schedule:
- - cron: "0 * * * *"
+ - cron: "11 * * * *"
env:
BART_REPO: tizen-system-upgrade-tools-generic-local
${{ env.MAIN_NEW }}
image_type: ${{ env.IMAGE_TYPE }}
run_name: ${{ env.RUN_NAME }}
+ target: ${{ matrix.target }}
arch: ${{ matrix.arch }}
output_repository: ${{ env.BART_REPO }}
output_directory: ${{ env.BART_OUTPUT_DIR }}
--- /dev/null
+.vscode-ctags
+images/
+*.zip
+asdf/