[jira] [Commented] (MDEPLOY-250) add documentation on managing network issues

["Michael Osipov (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MDEPLOY-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252542#comment-17252542 ] 

Michael Osipov commented on MDEPLOY-250:
----------------------------------------

There is a conceptual proposal how to solve this with HTTP-based wagon.

> add documentation on managing network issues
> --------------------------------------------
>
>                 Key: MDEPLOY-250
>                 URL: https://issues.apache.org/jira/browse/MDEPLOY-250
>             Project: Maven Deploy Plugin
>          Issue Type: Task
>          Components: deploy:deploy
>    Affects Versions: 3.0.0-M1
>            Reporter: Herve Boutemy
>            Priority: Major
>             Fix For: 3.0.0
>
>
> network issues are happening sometimes, then there are strategies that have been found to workaround, from simple retries, to 2-steps deploy through local staging, like done by plc4x:
> see in [https://github.com/apache/incubator-plc4x/blob/develop/Jenkinsfile]:
> {noformat}
> // We'll deploy to a relative directory so we can save
> // that and deploy in a later step on a different node
> sh 'mvn -P${JENKINS_PROFILE},development ${MVN_TEST_FAIL_IGNORE} ${JQASSISTANT_NEO4J_VERSION} -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir clean deploy'
> {noformat}
> followed by:
> {noformat}
> // Deploy the artifacts using the wagon-maven-plugin.
> sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload'
> {noformat}
> sharing such strategy can be useful to many



--
This message was sent by Atlassian Jira
(v8.3.4#803005)