You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because this option is used, we are forced to run mvn twice in our CI:
We first run mvn verify to make sure that all our tests pass. This is necessary to ensure that the release will be ok.
Then, mvn is called a second time indirectly when we call npx semantic-release.
In some cases, calling maven twice can add significant delays to a build. Ideally, it would be possible to only call npx semantic-release to both run the tests and deploy the pacakge.
So what do you think of adding an option so that -DskipTests can be added or not to the mvn deploy invocation? This would shave many minutes for several projects that I am working on.
Thanks for considering this change and for maintaining the tool 👍
The text was updated successfully, but these errors were encountered:
When this plugin executes the
deploy
maven target, it uses the-DskipTests
option as shown here:Because this option is used, we are forced to run
mvn
twice in our CI:mvn verify
to make sure that all our tests pass. This is necessary to ensure that the release will be ok.mvn
is called a second time indirectly when we callnpx semantic-release
.In some cases, calling maven twice can add significant delays to a build. Ideally, it would be possible to only call
npx semantic-release
to both run the tests and deploy the pacakge.So what do you think of adding an option so that
-DskipTests
can be added or not to themvn deploy
invocation? This would shave many minutes for several projects that I am working on.Thanks for considering this change and for maintaining the tool 👍
The text was updated successfully, but these errors were encountered: