lordgamez commented on code in PR #2128:
URL: https://github.com/apache/nifi-minifi-cpp/pull/2128#discussion_r2879230483


##########
.github/workflows/verify-package.yml:
##########
@@ -11,16 +11,31 @@ on:
         type: string
         description: The id of the create-release-artifacts workflow to 
download artifacts from
         required: true
-
+  workflow_run:
+    workflows: ["Create Release Artifacts"]
+    types:
+      - completed
+    branches: [main]
 
 env:
   DOCKER_CMAKE_FLAGS: -DDOCKER_VERIFY_THREAD=3 -DUSE_SHARED_LIBS= 
-DSTRICT_GSL_CHECKS=AUDIT -DCI_BUILD=ON -DENABLE_AWS=ON -DENABLE_KAFKA=ON 
-DENABLE_MQTT=ON -DENABLE_AZURE=ON -DENABLE_SQL=ON \
     -DENABLE_SPLUNK=ON -DENABLE_GCP=ON -DENABLE_OPC=ON 
-DENABLE_PYTHON_SCRIPTING=ON -DENABLE_LUA_SCRIPTING=ON -DENABLE_KUBERNETES=ON 
-DENABLE_TEST_PROCESSORS=ON -DENABLE_PROMETHEUS=ON \
     -DENABLE_ELASTICSEARCH=OFF -DENABLE_GRAFANA_LOKI=ON -DENABLE_COUCHBASE=ON 
-DDOCKER_BUILD_ONLY=ON
 
 jobs:
+  check-artifacts-workflow:
+    name: "Check Create Release Artifacts status"
+    if: github.event_name == 'workflow_run'
+    runs-on: ubuntu-24.04
+    steps:
+      - name: Check workflow conclusion
+        if: github.event.workflow_run.conclusion != 'success'
+        run: |
+          echo "Create Release Artifacts workflow failed with conclusion: ${{ 
github.event.workflow_run.conclusion }}"
+          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)' || '' }}"

Review 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.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to