[
https://issues.apache.org/jira/browse/NIFI-10749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated NIFI-10749:
--------------------------------
Fix Version/s: 1.19.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> GitHub Windows Builds missing NPM Cache
> ---------------------------------------
>
> Key: NIFI-10749
> URL: https://issues.apache.org/jira/browse/NIFI-10749
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 1.19.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> GitHub Actions running on Windows are failing to make use of the NPM cache
> during standard executions:
> {noformat}
> Run actions/cache@v3
> Cache not found for input keys:
> Windows-npm-237f376d8726b922bedf03586926e7aef2c284b5872b585cd564ad347bff7246
> {noformat}
> The Windows GitHub job uses a different approach to determine the NPM cache
> directory, but it appears that this approach does not use the NPM directory
> that the Maven plugin expects.
> In addition to this issue, the Windows GitHub job uses a set-output operation
> that GitHub has deprecated:
> {noformat}
> The `set-output` command is deprecated and will be disabled soon. Please
> upgrade to using Environment Files. For more information see:
> https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
> {noformat}
> This NPM caching approach on Windows should be changed to avoid the
> deprecated command and leverage expected NPM directories.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
