Azure / Azure/apiops

Support to deploy all changes between two deployments instead of limiting it to last commit or entire repo content

Offen
#154 10 Kommentare 0 Reaktionen 1 zugewiesene Person Beansprucht von @guythetechie Auf GitHub ansehen
enhancement
Vorherrschende Sprache
C#
Sterne
448
Forks
247
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### Please describe the feature.

As per my understanding, the publisher currently supports two scenarios:
1. Deployment based on a single Commit ID
2. Deployment based on entire repo content

If a team is following GitHub Flow branching strategy and each environment based deployment is defined as 'Stages' within pipeline, how does a deployment in higher environment can support the delta commits between what was deployed last time and all the commits that happened afterwards. For example,

1. Developer made two separate commits and both commits are deployed in Dev environment. For both these runs, deployment to higher environment was cancelled
2. Now Developer made another commit, fixing an issue with last two commits and this commit should now be deployed to higher environment, does the last commit option automatically picks the delta between what's already deployed and what's new OR the only available option is to deploy entire repo content

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.