search

amtrack / force-dev-tool

[DEPRECATED] Command line tool supporting the Force.com development lifecycle
MIT License
108 stars 37 forks source link

Change set deployment process #129

Closed sheldonleelazarus closed 6 years ago

sheldonleelazarus commented 6 years ago

Hi Amtrack

Currently the way force-dev-tool deploys using change set is : If there are destructive changes in a changeset the force-dev-tool will proceed with destructive changes first and then proceed with the actual deploy,

I have a quick question how can I set my destructive changes to happen after my actual deploy using force-dev-tool?

amtrack commented 6 years ago

Quoting the docs

To delete components after adding or updating other components, create a manifest file that’s named destructiveChangesPost.xml and include the components to delete.

So you just have to rename destructiveChanges.xml to destructiveChangesPost.xml.

sheldonleelazarus commented 6 years ago

Hi

Is there a way to automate it?

Kind Regards Sheldon Lazarus

From: Matthias Rolke [mailto:notifications@github.com] Sent: 19 April 2018 10:28 AM To: amtrack/force-dev-tool force-dev-tool@noreply.github.com Cc: Lazarus, Sheldon S (Grp IT) Sheldon.Lazarus3@standardbank.co.za; Author author@noreply.github.com Subject: Re: [amtrack/force-dev-tool] Change set deployment process (#129)

Quoting the docshttps://developer.salesforce.com/docs/atlas.en-us.daas.meta/daas/daas_destructive_changes.htm

To delete components after adding or updating other components, create a manifest file that’s named destructiveChangesPost.xml and include the components to delete.

So you just have to rename destructiveChanges.xml to destructiveChangesPost.xml.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/amtrack/force-dev-tool/issues/129#issuecomment-382653420, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AdwlYLB34AfpkRWGqRO4Z3YkJcJOB0yrks5tqEpzgaJpZM4TbU_R. Standard Bank email disclaimer and confidentiality note Please go to www.standardbank.co.za/site/homepage/emaildisclaimer.html to read our email disclaimer and confidentiality note. Kindly email disclaimer@standardbank.co.za (no content or subject line necessary) if you cannot view that page and we will email our email disclaimer and confidentiality note to you.

amtrack commented 6 years ago

@sheldonleelazarus Well, there is no flag in force-dev-tool itself yet. However you could just use unix commands, for example

$ git diff develop feature/foo | force-dev-tool changeset create foo && mv config/deployments/foo/destructiveChanges.xml config/deployments/foo/destructiveChangesPost.xml
sheldonleelazarus commented 6 years ago

Thanks so much will use this

From: Matthias Rolke [mailto:notifications@github.com] Sent: 19 April 2018 10:46 AM To: amtrack/force-dev-tool force-dev-tool@noreply.github.com Cc: Lazarus, Sheldon S (Grp IT) Sheldon.Lazarus3@standardbank.co.za; Mention mention@noreply.github.com Subject: Re: [amtrack/force-dev-tool] Change set deployment process (#129)

@sheldonleelazarushttps://github.com/sheldonleelazarus Well, there is no flag in force-dev-tool itself yet. However you could just use unix commands, for example

$ git diff develop feature/foo | force-dev-tool changeset create foo && mv config/deployments/foo/destructiveChanges.xml config/deployments/foo/destructiveChangesPost.xml

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/amtrack/force-dev-tool/issues/129#issuecomment-382658692, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AdwlYOHpr7MT5yJnd0gq8OXMDxr45VaXks5tqE7VgaJpZM4TbU_R. Standard Bank email disclaimer and confidentiality note Please go to www.standardbank.co.za/site/homepage/emaildisclaimer.html to read our email disclaimer and confidentiality note. Kindly email disclaimer@standardbank.co.za (no content or subject line necessary) if you cannot view that page and we will email our email disclaimer and confidentiality note to you.