Open jinty opened 8 years ago
Hi,
Do you still have access to the build logs?
Each Build will have a:
And some other logs that might be worth looking at:
I'll try to reproduce this running two pipelines at the same time.
I have been trying to replicate this since you replied. I used to be able to reliably cause the timeout, but cannot anymore. I can only assume that the inner workings of CodePipleine changed in the meantime.
I will continue trying to replicate the problem and close this issue if I cannot.
I am experiencing this problem now. It seems like multiple jobs are being acknowledged but only 1 build is being triggered. The polling log only shows 1 job ID being acknowledged. What I have noticed however is that the Job ID in the polling log is different from the Job ID in the console output. For example, this in the polling log:
Started on Aug 11, 2016 1:41:01 PM
[AWS CodePipeline Plugin] Polling for jobs for action type id: [Owner: Custom, Category: Build, Provider: Jenkins, Version: 4, ProjectName: My_Project_Name]
[AWS CodePipeline Plugin] Received job with ID: some-job-id
[AWS CodePipeline Plugin] Acknowledged job with ID: some-job-id
Done. Took 12 sec
Changes found
and then this in the console output:
[AWS CodePipeline Plugin] Job 'some-other-job-id' received
Hi,
I have 2 pipelines which both use the same Jenkins project for one of their actions. This works fine except when both pipelines start at the same time. When that happens one of the CodePipeline actions times out waiting for Jenkins to start executing the actions (jenkins never starts a build of the project). It seems random which code pipeline fails.
I am using version 0.11 of the AWS CodePipeline Plugin.