Expand my Community achievements bar.

SOLVED

Cloud Manager pipeline is not picking up latest changes from cloud repository

Avatar

Level 2

Hi Team,

We have cloned cloud repository to local and committed few changes on application code and pushed to cloud repository. It seems configured pipeline is not picking up latest changes. Is there any way we can make sure, its really picks up the latest changes. Please do the needful here as its really blocks our regular work. Thanks.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

I am afraid, that should be not the case. New branch should not be created evrytime

 

Ideally, development sprints or stories should be committed in Feature Branches. 

Developers would commit their stories or defects in their respective Feature Branches. End of a Sprint, these branches are merged into Develop Branch. 

Develop Branch can be deployed over Non - Prod env, where QA can validate the Stories and sign off.

As the Release approaches, Develop is merged into Master, which is deployed over Prod envs. 

 

Please follow below url to know about Cloud Manager GIT integration and preferred GIT Branching Strategy

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

 

 

View solution in original post

3 Replies

Avatar

Employee Advisor

@rgravisankar 

Hope you have configured your CI/CD Pipeline with Deployment Trigger as "On GIT Changes"

Can you add a screen shot of your CI/CD Pipeline Configuration and provide more info on your GIT Branching Strategy?
While below link might help you to verify the configuration for automatic deployment:
https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/content/using/pipelines/pro...

 

Avatar

Level 2

Hi, Looks like, we need to create new branch every time to push the new changes. With new branch we can able to push all our new changes. Thanks.

Avatar

Correct answer by
Employee Advisor

I am afraid, that should be not the case. New branch should not be created evrytime

 

Ideally, development sprints or stories should be committed in Feature Branches. 

Developers would commit their stories or defects in their respective Feature Branches. End of a Sprint, these branches are merged into Develop Branch. 

Develop Branch can be deployed over Non - Prod env, where QA can validate the Stories and sign off.

As the Release approaches, Develop is merged into Master, which is deployed over Prod envs. 

 

Please follow below url to know about Cloud Manager GIT integration and preferred GIT Branching Strategy

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...