chore: Bump nifi version for 25.11.0 (#314) #17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| --- | |
| name: Build and publish NiFi for signal-processing demo | |
| on: | |
| workflow_dispatch: | |
| push: | |
| branches: | |
| - main | |
| # TODO (@NickLarsenNZ): Also build on release branches, but with a stackable0.0.0-dev or stackableYY.M.X tag. | |
| # The current problem is that we don't know the patch level, so do we always build for `.0`, or just drop that | |
| # (eg: stackableYY.M), but then do we do the same for main (eg: 0.0-dev)? | |
| # - release-* | |
| paths: | |
| - demos/signal-processing/Dockerfile-nifi | |
| - .github/workflows/dev_nifi.yaml | |
| jobs: | |
| build_image: | |
| name: Reusable Workflow | |
| uses: ./.github/workflows/reusable_build_image.yaml | |
| secrets: | |
| harbor-robot-secret: ${{ secrets.HARBOR_ROBOT_DEMOS_GITHUB_ACTION_BUILD_SECRET }} | |
| slack-token: ${{ secrets.SLACK_CONTAINER_IMAGE_TOKEN }} | |
| with: | |
| image-name: nifi | |
| # TODO (@NickLarsenNZ): Use a versioned image with stackable0.0.0-dev or stackableXX.X.X so that | |
| # the demo is reproducable for the release and it will be automatically replaced for the release branch. | |
| image-version: 2.6.0-postgresql | |
| containerfile-path: demos/signal-processing/Dockerfile-nifi |