I have these three distinct stages [1] that have concurrency 1 as they
should only run one and one - however they are also consumers of each
other ( a chain of events).
This strongly indicates that it should be a single stage (which would solve
my problem) - but at the same time they are independent meaningful
stages/events - so it's also meaningful to stage label them.
Is there any way to make a block with concurrency 1 and individual stage
steps within that block?
The chain is: deployToMavenRepo -> deployOntoAppserves ->
runATestSuiteAgainstNewlyDeployedServers
[1]
stage name: 'deployToMavenRepo', concurrency: 1
// have to actually rebuild in order to be able to deploy...:
sh "${mvnCmd} -Dpackaging=true -Dmaven.test.skip=true clean deploy"
step([$class: 'ArtifactArchiver', artifacts: '**/target/*.tar.gz',
fingerprint: true])
stage name: 'deployToServers', concurrency: 1
//have the deployment script as a separate workflow so we can invoke
isolated, but also call it directly here to deploy
def deployscript = load 'deploy.groovy'
deployscript.deploy( 'systest' )
stage name: 'soapUi test', concurrency: 1
def soapUiFlow = load 'soapuitest.groovy'
soapUiFlow.soapUiTest()
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c9601dfe-d854-42de-abbe-7c5b30702f09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
