MINIFICPP-2737 Add weekly CI workflow runs and status page#2128
MINIFICPP-2737 Add weekly CI workflow runs and status page#2128lordgamez wants to merge 2 commits intoapache:mainfrom
Conversation
e046003 to
ddc6f8a
Compare
.github/workflows/verify-package.yml
Outdated
| exit 1 | ||
| docker-tests: | ||
| name: "${{ matrix.platform.name }} (${{ matrix.arch }})${{ inputs.enable_fips && ' (FIPS Mode)' || '' }}" | ||
| name: "${{ matrix.platform.name }} (${{ matrix.arch }})${{ (github.event_name != 'workflow_dispatch' || inputs.enable_fips) && ' (FIPS Mode)' || '' }}" |
There was a problem hiding this comment.
Note: I think running workflow with both fips enabled and disabled can instantiate way too much jobs, so for automatic weekly runs running only fips enabled jobs should be sufficient.
ddc6f8a to
5e0835e
Compare
5e0835e to
b6d25a3
Compare
There was a problem hiding this comment.
I'd move this file elsewhere, as a CI status page is not really documentation. Maybe etc/status_page, or github_scripts/status_page, or a new directory called ci/status_page
There was a problem hiding this comment.
I checked and the default for Github Pages for github project pages is the /docs directory and the convention seems to be that the websites for projects are located there and their subdirectories. I moved the index.html to /docs/status to align with this convention as the main index.html is usually reserved for the project documentation page. This way the status page will be found at https://apache.github.io/nifi-minifi-cpp/status Updated in a4f5b8a
All Github Actions workflows are run weekly to avoid regression. The workflow run results are visible on the status page hosted on Github Pages.
3a814fc to
a4f5b8a
Compare
All Github Actions workflows are run weekly to avoid regression. The workflow run results are visible on the status page hosted on Github Pages.
Status page example can be checked at: https://lordgamez.github.io/nifi-minifi-cpp/status
https://issues.apache.org/jira/browse/MINIFICPP-2737
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.