-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue 290: convert travis-ci to github-actions #294
Conversation
With this removed, the environment variables should no longer be needed.
…anch for coveralls
uses: actions/cache@v2 | ||
with: | ||
path: node_modules | ||
key: ${{ runner.os }}-cache-node_modules-${{ hashFiles('**/package.json', '**/package-lock.json') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we are caching dependencies with node modules and m2 it makes sense to have at least one generic restore key. If we upgrade one dependency there is no reason to not bring in the cache for the remaining dependencies and let npm and mvn fetch the upgrade dependency.
From @wwelling: "As we are caching dependencies with node modules and m2 it makes sense to have at least one generic restore key. If we upgrade one dependency there is no reason to not bring in the cache for the remaining dependencies and let npm and mvn fetch the upgrade dependency."
uses: actions/cache@v2 | ||
with: | ||
path: ~/.m2/repository | ||
key: ${{ runner.os }}-cache-maven-${{ hashFiles('**/pom.xml') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not what I meant. I don't think this is correct either. We still want to lookup exact cache if package.json has not changed. But if package.json or pom.xml change it should fall back to a restore key such as:
key: ${{ runner.os }}-cache-maven-${{ hashFiles('**/pom.xml') }}
restore-keys: ${{ runner.os }}-cache-maven-
and
key: ${{ runner.os }}-cache-node_modules-${{ hashFiles('**/package.json') }}
restore-keys: ${{ runner.os }}-cache-node_modules-
This reverts commit 4820e5f. This was a misinterpretation on my part.
resolves #290
resolves #293