[MDEPLOY-250] add documentation on managing network issues

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-M1
• Fix Version/s: 3.0.0-M2
• Component/s: deploy:deploy
• Assignee: Herve Boutemy
• Reporter: Herve Boutemy
• Created: 20/Jan/19 16:11
• Updated: 30/Dec/21 08:06
• Resolved: 29/Dec/21 12:30

Description

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:

// 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'

followed by:

// Deploy the artifacts using the wagon-maven-plugin.
sh 'mvn -f jenkins.pom -X -P deploy-snapshots wagon:upload'

sharing such strategy can be useful to many

Issue Links

• depends upon: WAGON-575 Retry for connection issues