forcedotcom / forcedotcom/NextGeneration-DevOpsCenter

Pipeline stage going into PROD must be bundled?

Open
#45 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
7
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Hi team, our team has been using DevOps Center installed packaged for the last 2 years and I am excited for the native one and been actively testing it.

It seems the pipeline stage going into PROD must be bundled. This is a pretty significant behavior change from the legacy package. For our use case, we have to allow individual work items being promoted to prod so we cannot bundle the stage going into PROD.
Is this an enforced deliberate decision or will we be able to toggle that setting in the future?

Image

Image

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with issue #45 and its two attached screenshots, then review the native DevOps Center pipeline-stage behavior described by the reporter. Confirm whether bundling the production stage is intentional and identify the scope of a configurable alternative; done means the behavior or its supported configuration is clearly established.

Written by the indexing model from the issue text.

Assessment

Domain
devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.