kfidelak94
commented
3 years ago Thanks for the feedback @KomalIsampelliwar! Here are some responses:
Case 1: I don't think I'm seeing what you're seeing here. Are you selecting existing branches or new branches to be created? Could you maybe record a short screen video showing what you're seeing so I can understand it and try to reproduce it?
Case 2: We don't have Delete project capability yet in this Pilot. It's on the roadmap. This was also reported in https://github.com/forcedotcom/devops-center-feedback/issues/69 and I offered a possible alternative to help clean up your project list that you might want to check out if haven't yet.
Case 3: It's not currently possible to deactivate a pipeline after any work items have been promoted. Can you clarify the need you have to deactivate it? Is it because you want to make a modification to the pipeline settings? If so can you provide more info on what you are looking to modify? This will help us understand use cases better to try to provide a better solution in the future.
Case 4: If I'm understanding you correctly, I believe you're looking for a way to move a change from QA to Staging, for instance, without first going QA to UAT to Staging? Right now the promotions much be done in sequence left to right. We are trying to promote a stricter process of ensuring all work moves through each stage of the pipeline. Can you elaborate on your use-case for wanting to skip a stage? We do know there are some use-cases where this may make sense and so again, we just want to ensure we understand the use-case correctly.
Case 5: Right now in the Pilot you can either Run all tests, or run no tests. We'll be adding additional options in the next release to allow for running local tests only and running specified tests.
Case 6: Yes, unfortunately there are currently some issues/limitations with the communication of the underlying commands' output to our application, and we are working to try to get these resolved so that we can provide as much information as possible directly in the application.
Case 7: It's currently possible to remove environments from the settings tab only if they haven't been assigned to a work item or pipeline yet. Once that's happened there's a lot more "cleanup" that becomes necessary due to the relationships between the environments and these other parts of the data model, and so we haven't yet tackled trying to do this. Again can you elaborate on the scenario you are wanting this feature for?
Thanks again.
Sandbox details: Dev: https://devops-center-basalt-0155--devopdev.lightning.force.com/ Qa: https://devops-center-basalt-0155--devopqa.lightning.force.com/ Uat: https://devops-center-basalt-0155--devopuat.lightning.force.com/ Staging: https://devops-center-basalt-0155--devstaging.lightning.force.com/
Case 1: If we select staging branch first, next uat, then branch field blanks out first time. And also specify branch does not enable in sequence.
Case 2: How to delete an existing project
Case 3: Not able to deactivate pipeline in one go :So basically deactivating is blocked
Case 4: How to skip one environment deployment in between.
Case 5: Is there a way to skip Run all apex tests while deploying even for adding object fields in lower envs.?? How to select which test cases to run
Case 6: Errors are not intuitive. We have to go to setup: deployment?? To check the failure
Case 7: Not able to remove environments from settings tab.