dove PIPELINE_CONFIG è il file di configurazione della pipeline di importazione che hai appena modificato.
Risultati
Potresti non vedere i risultati previsti a causa del modo in cui Cloud Deploy tratta la relazione tra pipeline e target e le release che gestisce.
Ogni risorsa release e rollout è associata definitivamente alla
pipeline così come è stata definita al momento della creazione di release. Se modifichi una configurazione della pipeline di distribuzione (incluse le definizioni dei target) dopo la creazione di una release, la release non corrisponde più alle definizioni.
Preservare le risorse in questo modo garantisce che funzionino in modo coerente su tutti i target e che non vengano interrotte dalle modifiche alla configurazione. Tuttavia, questo comportamento potrebbe non essere quello che intendi, nel qual caso puoi creare una nuova release da eseguire il deployment utilizzando la pipeline aggiornata.
Cloud Deploy
restituisce avvisi se si verifica una mancata corrispondenza di questo tipo e provi a eseguire determinate
azioni, ad esempio promuovere la release.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-03 UTC."],[[["\u003cp\u003eThis guide details the process of modifying an existing delivery pipeline.\u003c/p\u003e\n"],["\u003cp\u003eUpdating a delivery pipeline involves editing the pipeline definition file and then re-registering it using the \u003ccode\u003egcloud deploy apply\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eReleases and rollouts are permanently linked to the pipeline definition as it was at the time of their creation, so changing the pipeline won't affect existing releases.\u003c/p\u003e\n"],["\u003cp\u003eTo have the delivery pipeline changes take effect, you must create a new release after updating the pipeline definition.\u003c/p\u003e\n"],["\u003cp\u003eCloud Deploy will issue warnings if there's a mismatch between the pipeline definition and an existing release, indicating that changes may not have been applied.\u003c/p\u003e\n"]]],[],null,["# Update a delivery pipeline that's already in use\n\nThis page describes how to update a delivery pipeline that's already in use.\n\nChange a delivery pipeline\n--------------------------\n\nTo change your delivery pipeline consists of the following steps:\n\n1. Edit the [delivery-pipeline definition](/deploy/docs/config-files).\n\n2. Re-register the delivery pipeline:\n\n gcloud deploy apply --file=\u003cvar label=\"config\" translate=\"no\"\u003ePIPELINE_CONFIG\u003c/var\u003e\n\n Where \u003cvar label=\"config\" translate=\"no\"\u003ePIPELINE_CONFIG\u003c/var\u003e is the delivery\n pipeline configuration file that you just edited.\n\nResults\n-------\n\nYou might not see the results you expect, because of how\nCloud Deploy treats the relationship between pipelines and targets\nand the releases they manage.\n\nEach `release` and `rollout` resource is permanently associated with the\npipeline as it was defined when the `release` was created. If you change a\ndelivery pipeline configuration (including target definitions) after a release\nis created, that release is now mismatched from the definitions.\n\nPreserving resources in this way ensures they function consistently across the\ntargets and they're not disrupted by configuration changes. However this\nbehavior might not be what you intend, in which case you can create a new\nrelease to deploy using the updated pipeline.\n\nCloud Deploy\nreturns warnings if there's such a mismatch and you try to perform certain\nactions, such as promote the release.\n\nFor more information, see [Pipeline instances per release](/deploy/docs/pipeline-instances).\n\nWhat's next\n-----------\n\n- Find out how to [view delivery pipelines](/deploy/docs/view-pipeline)\n that's already in use.\n\n- Learn how to [suspend a delivery pipeline](/deploy/docs/suspend-pipeline).\n\n- Find out how to [delete a delivery pipeline](/deploy/docs/delete-pipeline).\n\n- Learn how to [use service notifications](/deploy/docs/subscribe-deploy-notifications)"]]
