[
https://issues.apache.org/jira/browse/NIFI-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-12177:
------------------------------------
Fix Version/s: 2.0.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
Merged into main branch.
The changes build on other recent Docker changes, so this does not apply
cleanly to the support branch. If you are inclined to backport the changes to
the support branch, feel free to open a separate Jira issue for that work.
> Docker builds (dockermaven) should include testing of the built images
> ----------------------------------------------------------------------
>
> Key: NIFI-12177
> URL: https://issues.apache.org/jira/browse/NIFI-12177
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Chris Sampson
> Assignee: Chris Sampson
> Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The NiFi, NiFi Toolkit & NiFi Registry {{dockermaven}} builds currently run
> an {{integration_test}} script once the image has been built in order to
> confirm a container can be started and the component can be contacted.
> The same (or similar) approaches should be considered for:
> * MiNiFi
> * MiNiFi C2
> This would help avoid situations such as NIFI-12175
> Also, the NiFi `dockermaven` test script fails if run with `macos-latest` in
> GitHub Actions (NIFI-12178), likely an incompatibility with the use of Colima
> to get Docker working within the runner, an alternative should be found (to
> the test assertions or the GitHub workflow - see NIFI-12191 as this is
> possibly an issue with the use of Colima)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
