-
Bug
-
Resolution: Fixed
-
Blocker
-
Jenkins 2.19.2
Java RunTime 1.8.0_111-8u111-b14-2ubuntu0.16.04.2-b14
AWS CodePipeline Plugin 0.20
When using multiple outputs the order the outputs are processed in doesn't match the order they're defined in the UI. I've found this occur with three outputs, though I could have just been lucky with two outputs.
The two attachments show the order in the pipeline and in the Jenkins job. When the job is executed, the log contains the following (emphasis mine):
08:20:06 [AWS CodePipeline Plugin] Uploading artifact: {Name: ReqMgrLog,Location: {Type: S3,S3Location:
{BucketName: ###, ObjectKey: EOT/ReqMgrLog/vDtEgfa}}}, file: /var/lib/jenkins/workspace/RequestManager/RequestManager/request-manager/bin/requestmanager
08:20:07 [AWS CodePipeline Plugin] Upload successful
08:20:07 [AWS CodePipeline Plugin] Uploading artifact: {Name: ReqMgrTags,Location: {Type: S3,S3Location:
}}, file: /var/lib/jenkins/workspace/RequestManager/build.log
08:20:07 [AWS CodePipeline Plugin] Upload successful
08:20:07 [AWS CodePipeline Plugin] Compressing directory '/var/lib/jenkins/workspace/RequestManager/identifiers' as a 'Zip' archive
08:20:07 [AWS CodePipeline Plugin] Uploading artifact: {Name: ReqMgrBin,Location: {Type: S3,S3Location:
}}, file: /tmp/RequestManager-7108802193708017228.zip
08:20:07 [AWS CodePipeline Plugin] Upload successful
What's worse is that I have three jobs set up in this way, and in each case the outputs are picked up in a different order.
[JENKINS-40604] Outputs processed in incorrected order in aws-code pipeline plugin
Labels | New: plugin |
Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
Assignee | Original: David Nasi [ awscodepipeline ] | New: Yin Huang [ maggiecopyaws ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Comment |
[ The release [aws-codepipeline-0.29 |https://github.com/awslabs/aws-codepipeline-plugin-for-jenkins/releases/tag/aws-codepipeline-0.29]adds an optional field Artifact Name to each Location, which allows explicitly specifying the Output artifact the Location will be uploaded. If no Artifact Name is entered, plugin behavior will be the same as before. ] |
This is now causing issues with a live project, as we are attempting to use templates to reduce duplication in jobs but we can't as the output lists are inconsistent as above.