Skip to content
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

AAE-17877 Reuse existing m2 cache in publish artifacts for veracode #410

Merged
merged 4 commits into from
Nov 28, 2023

Conversation

wojciech-piotrowiak
Copy link
Contributor

Checklist

  • Jira Reference (also in PR title):
  • README updated after adding/changing behaviour of an action
  • Proposed version increment for release:
    • Patch (bugfix)
    • Minor (new feature)
    • Major (breaking changes)
  • External PR link where changes has been tested:

Description

Right now action 'actions/setup-java' create a NEW m2 cache 'setup-java-Linux-maven-97f800f7d1fcdfc6b6fed3a8d7d7c549f23eda7caac4d91b606cef92d869660a' instead we can use common one with latest artifacts

@wojciech-piotrowiak wojciech-piotrowiak self-assigned this Nov 27, 2023
@wojciech-piotrowiak wojciech-piotrowiak marked this pull request as ready for review November 28, 2023 07:22
@wojciech-piotrowiak wojciech-piotrowiak requested a review from a team as a code owner November 28, 2023 07:22
@gionn gionn changed the title AAE-17877 using common m2 cache instead a new one AAE-17877 Reuse existing m2 cache in publish artifacts for veracode Nov 28, 2023
@gionn gionn merged commit 0b41430 into master Nov 28, 2023
3 checks passed
@gionn gionn deleted the AAE-17877-using-common-m2-cache branch November 28, 2023 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants