You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our global pipeline library code is stored in a CodeCommit repository. It has a number of branches matching release* and a master branch.
The microservice pipeline is configured to trigger based on an event on the release branch in another CodeCommit repository. It has branches named release and master.
The SNS trigger is set to send notices for any change to the repository for any branch.
Expected Behavior
When a new branch release appears in the microservice repository, or when a commit is made to the release branch, the pipeline should trigger and build the microservice.
Actual Result
The trigger logic searches not only the microservice repository, but also the global pipeline repository for changes to the release branch. Because the global pipeline code has not changed, the pipeline is not triggered.
Output from Jenkins
Jan 14, 2020 6:13:27 PM [c.r.j.p.a.SQSTriggerBuilder][thread-0000B4]
INFO: Try to trigger the build for message: ce06e505-eb31-4e25-bd0e-d711a4578829
Using strategy: Default
[poll] Last Built Revision: Revision 007fad9741daa9118ad75099f9fa4b64170b6fe4 (origin/release-1.0)
using credential codecommit-service-account-id
git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repositories
git config remote.origin.url https://git-codecommit.us-west-2.amazonaws.com/v1/repos/microservice # timeout=10
Fetching upstream changes from https://git-codecommit.us-west-2.amazonaws.com/v1/repos/microservice
git --version # timeout=10
using GIT_ASKPASS to set credentials CodeCommit Service Account for DEV Team
git fetch --tags --progress https://git-codecommit.us-west-2.amazonaws.com/v1/repos/microservice +refs/heads/:refs/remotes/origin/
Polling for changes in
Seen branch in repository origin/master
Seen branch in repository origin/onelogin
Seen branch in repository origin/release
Seen branch in repository origin/release-1.0
Seen 4 remote branches
git show-ref --tags -d # timeout=10
Using strategy: Default
[poll] Last Built Revision: Revision 4a6ac4d96487bb83a236d3348f746841c950cd1c (refs/remotes/origin/release-build-promotion) <<< this is the global pipeline!
using credential codecommit-service-account-id
git --version # timeout=10
using GIT_ASKPASS to set credentials CodeCommit Service Account for DEV Team
git ls-remote -h https://git-codecommit.us-west-2.amazonaws.com/v1/repos/global-pipeline # timeout=10
Found 38 remote heads on https://git-codecommit.us-west-2.amazonaws.com/v1/repos/global-pipeline
[poll] Latest remote head revision on refs/heads/release-build-promotion is: 4a6ac4d96487bb83a236d3348f746841c950cd1c - already built by 13
ERROR: no such computer mypod-8864c0f2-2710-4b0a-b68a-3c9bf3f66f76-2lh3x-30p4j
Jan 14, 2020 6:13:31 PM [c.r.j.p.a.SQSTriggerBuilder][thread-0000B4]
INFO: Cancel the build since no change found
The text was updated successfully, but these errors were encountered:
Scenario
Our global pipeline library code is stored in a CodeCommit repository. It has a number of branches matching release* and a master branch.
The microservice pipeline is configured to trigger based on an event on the release branch in another CodeCommit repository. It has branches named release and master.
The SNS trigger is set to send notices for any change to the repository for any branch.
Expected Behavior
When a new branch release appears in the microservice repository, or when a commit is made to the release branch, the pipeline should trigger and build the microservice.
Actual Result
The trigger logic searches not only the microservice repository, but also the global pipeline repository for changes to the release branch. Because the global pipeline code has not changed, the pipeline is not triggered.
Output from Jenkins
The text was updated successfully, but these errors were encountered: