You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2025/04/15 20:09:43 UTC
(airflow) branch v3-0-test updated (94f0dc53602 -> 91dd2a32689)
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 94f0dc53602 Remove provider tests as dependencies in v3 branch
new 91dd2a32689 Add condition in finalize that allows to skip some jobs
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (94f0dc53602)
\
N -- N -- N refs/heads/v3-0-test (91dd2a32689)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/workflows/ci.yml | 6 ++++++
1 file changed, 6 insertions(+)
(airflow) 01/01: Add condition in finalize that allows to skip some jobs
Posted by po...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 91dd2a326896e65f2793ffd2ae6d13cfc5dfbdb6
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Tue Apr 15 22:03:20 2025 +0200
Add condition in finalize that allows to skip some jobs
GitHub Actions has this weird behaivour that even if you have
composite workflow and matrix inside that workflow is "empty", the
whole job (rather than composite workflow) gets skipped.
Since there is no 'skipped' condition in GitHub Actions (yes, weird)
seems that the condition to run on "successful or skipped" is
that weird.
---
.github/workflows/ci.yml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index f0af454b70b..a334d3480f9 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -785,6 +785,8 @@ jobs:
permissions:
contents: write
packages: write
+ # This will fire when all the jobs from "needs" are either successful or skipped
+ if: always() && !failure() && !cancelled()
needs:
- build-info
- generate-constraints