Expand my Community achievements bar.

CM deployment pipelines: Access to detailed logs about failures

Avatar

Community Advisor

6/23/23

Request for Feature Enhancement (RFE) Summary: Access to detailed logs of deployment pipelines
Use-case:

Debugging deployment issues can be a time-consuming process, especially when faced with vague deployment logs from pipelines. This lack of clarity often leads to significant delays in issue identification and resolution, particularly in multi-module projects where pipeline runtimes can range from 1 to 1.5 hours.

 

Example of a vague log: Failed deployment in abc-program-dev

Current/Experienced Behavior: Engaging with the support team to obtain relevant logs and resolving the issue through back-and-forth communication can be a lengthy and time-consuming process, often spanning multiple days.
Improved/Expected Behavior: While it may not always be possible to obtain detailed logs for the entire deployment, it is crucial to have access to information regarding the specific cause of the failure.
Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service
Customer-name/Organization name:  
Screenshot (if applicable):  
Code package (if applicable):  
1 Comment

Avatar

Administrator

7/13/23

@aanchal-sikka 

Thanks for proposing this idea
 
This has been reported to the engineering under the internal reference SITES-14682. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Status changed to: Investigating