kw80
commented
2 years ago Because the MAVEN_OPTS is stripped, I cannot increase the java memory heap size. For large builds, this may result in build failures.
Open deeptisjfrog opened 2 years ago
kw80
commented
2 years ago Because the MAVEN_OPTS is stripped, I cannot increase the java memory heap size. For large builds, this may result in build failures.
Is your feature request related to a problem? Please describe. Defining MAVEN_OPTS as a variable inside an artifactory_maven task is not working.We were able to overcome the heap memory error after defining the MAVEN_OPTS as a global variable which is having the scope of all tasks. Here we defined the variable in our environment, removing it from Maven@3 task .
Pipeline snippet:- variables:
Describe the solution you'd like to see As it is just a work around with defining the MAVEN_OPTS as a global variable and outside the ARTIFACTORY_MAVEN task ,we are looking for a scenario where if there is a scope where we can define a variable inside the maven task with MAVEN_OPTS.
Describe alternatives you've considered Scope where we can define a variable inside the maven task
Additional context Add any other context or screenshots about the feature request here.
variables: