search

forcedotcom / devops-center-feedback

61 stars 2 forks source link

Pull Changes does not bring up custom fields deployed by change set. #78

Open TheMixDevOps opened 3 years ago

TheMixDevOps commented 3 years ago

Describe the bug I am not able to see custom fields which I deployed into the Sandbox using the change set.

To Reproduce Steps to reproduce the behavior:

  1. In Sandbox1 create a change set with fields you want to deploy to Org, validate and deploy in Sandbox2.
  2. In your work item, pull changes for Sandbox2. You will not be able to see your recently deployed custom fields.

Expected behavior See your changes deployed by change set, not just manual changes.

mouhabchi commented 3 years ago

If you try to pull sources with sfdx cli, do you have any results ?

TheMixDevOps commented 3 years ago

If I use other tools available in the market, I see those changes. I am not using cli or vs code if you ask me.

kfidelak94 commented 3 years ago

@TheMixDevOps I suspect that because a change set deployment is actually basically a package install technically, the changes are not tracked via the source tracking mechanism that we use to detect changes.

Can you elaborate on your use-case here? We have not optimized for using change sets in conjunction with DevOps Center so I'd like to understand the use case that has you attempting this.

TheMixDevOps commented 3 years ago

Why are we not tracking changes when it comes to change sets? Such a blocker, is this not defeating the core DevOps ideology of faster delivery of apps and services?

kfidelak94 commented 3 years ago

@TheMixDevOps Change Sets is an older technology and flow that was not built (sadly) with the notion of source-driven development. DevOps Center is actually being built as a modern alternative to Change Sets, and as such will support the ability to track changes from the start. But also as such, we haven't necessarily been thinking of these two products being used "together" so much. That is why I'd like to understand more about your use-case for how you are looking to use Change Sets with a DevOps Center-based flow.

TheMixDevOps commented 3 years ago

I.e. bringing changes from environments that are not part of the project and pipeline.

From: Karen Fidelak @.> Date: Friday, 6 August 2021 at 17:02 To: forcedotcom/devops-center-feedback @.> Cc: Viktor Vrabel @.>, Mention @.> Subject: Re: [forcedotcom/devops-center-feedback] Pull Changes does not bring up custom fields deployed by change set. (#78)

@TheMixDevOpshttps://github.com/TheMixDevOps Change Sets is an older technology and flow that was not built (sadly) with the notion of source-driven development. DevOps Center is actually being built as a modern alternative to Change Sets, and as such will support the ability to track changes from the start. But also as such, we haven't necessarily been thinking of these two products being used "together" so much. That is why I'd like to understand more about your use-case for how you are looking to use Change Sets with a DevOps Center-based flow.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/forcedotcom/devops-center-feedback/issues/78#issuecomment-894358972, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUBUCHMTZONZL55KBECFKDDT3QBSVANCNFSM5BIXW3GA.

YouthNet UK (legal name of The Mix) is a limited company registered in England and Wales. Company registration number: 3031098. Charity registration number 1048995.