forcedotcom / devops-center-feedback

61 stars 2 forks source link

Stalled Commit #216

Open jbambrick-cgi opened 1 year ago

jbambrick-cgi commented 1 year ago

I have set up Salesforce DevOps Center, created a pipeline, and seeded my development environment with metadata from a change set. There are 500 components that were in the change set that I added to the work item. After several hours there is an error "Stalled Commit". Clicking details provides no information. Rerunning the Commit Changes results in the same error.

To Reproduce Steps to reproduce the behavior:

  1. Create a change set in an old development environment not part of the new pipeline
  2. Upload the change set to the new development environment and deploy (successfully)
  3. Select all changed components, add a comment, and click Commit Changes

Expected behavior All metadata was retrieved successfully and the work item ready to review\promote

andresrivas-sf commented 1 year ago

Hi @jbambrick-cgi,

I'm sorry you had that problem. Could you please share your DevOps Center Organization ID so we can check and try to help you?

Thanks!

jbambrick-cgi commented 1 year ago

Thanks for the response. Here is the org id for the DevOps Center: 00D4x000007smC6

andresrivas-sf commented 1 year ago

Thanks @jbambrick-cgi,

from our logs, it seems that the application is unable of handling that amount of records. Nice catch!

While we work on resolving this, as a workaround, could you try sending fewer changes on multiple work items? try a set of 200 at max.

jbambrick-cgi commented 1 year ago

My team tried that approach but end up with circular dependency errors. Another issue is the time it takes to select fields manually. When the list is greater than 1000, the UI struggles to load (custom fields as an example). Is there any advice on how to migrate metadata + profiles from a non-source tracked environment into a source tracked environment that is part of our DevOps Center pipeline?

git2gus[bot] commented 1 year ago

This issue has been linked to a new work item: W-11810468

NiteshJain-Moodys commented 10 months ago

Has this been resolved... I'm getting the same error now