You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/11/16 17:58:00 UTC
[jira] [Commented] (NIFI-10826) Separate Compile and Verify Steps for GitHub Workflow
[ https://issues.apache.org/jira/browse/NIFI-10826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634958#comment-17634958 ]
ASF subversion and git services commented on NIFI-10826:
--------------------------------------------------------
Commit 9e3987d04e78148a36c46f42a451290fe5813061 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9e3987d04e ]
NIFI-10826 Separated Maven Compile and Verify in ci-workflow
Signed-off-by: Matthew Burgess <ma...@apache.org>
This closes #6666
> Separate Compile and Verify Steps for GitHub Workflow
> -----------------------------------------------------
>
> Key: NIFI-10826
> URL: https://issues.apache.org/jira/browse/NIFI-10826
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The current GitHub ci-workflow configuration runs a single Maven {{verify}} command to run through the standard lifecycle phases for building the project. Separating initial code compilation from unit testing will provide a clearer indication of the time for code compilation and the time for unit testing. Unit tests can be more prone to errors when running in parallel, but running the {{compile}} command with multiple threads should be more reliable and provide some performance optimization for runners with multiple cores.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)