[
https://issues.apache.org/jira/browse/MPOM-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703254#comment-17703254
]
Tamas Cservenak commented on MPOM-397:
--------------------------------------
IF we would do automated "push a button" releases, that's COMPLETELY different
thing, but we are not.
> Don not run ITs during release
> ------------------------------
>
> Key: MPOM-397
> URL: https://issues.apache.org/jira/browse/MPOM-397
> Project: Maven POMs
> Issue Type: Improvement
> Reporter: Tamas Cservenak
> Priority: Major
>
> As it makes no sense. As I did release m-install-p and m-deploy-p, at my
> amazement the {{release:prepare}} did end quickly (OK), while
> {{release:perform}} started to run ITs? What is the rationale here, *after*
> things were tagged? It really does not gives anything, but takes precious
> time. If relMgr is not cautious enough to ensure ITs are OK beforehand doing
> the release, that's it, a new release will happen.
> But running ITs in ANY of the release mojo makes no sense.
> Personally, I'd simply not run any kind of tests in any of two release Mojos,
> as it makes no sense, but in turn, makes release that is already too fragile,
> even more problematic and time consuming.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
