Giter Club home page Giter Club logo

Comments (6)

neowit avatar neowit commented on June 1, 2024

Do you mean deploying all files under current project as opposed to deploying only the changed ones?

If we are deploying the project to a new org then how do we specify the target SFDC Org to deploy to?

Do you have a step-by-step process of such deployment in mind? From user's point of view.

from vim-force.com.

cwarden avatar cwarden commented on June 1, 2024

Yes, all files rather than just the changed ones.

I keep the directory that contains my ant property files in git with separate branches for different types of orgs. So I have a dev branch that contains my credentials for a dev org, a package branch with the credentials for a dev org in which a managed package is packaged, etc.

I was setting up a new dev org, and I had to run ant directly to deploy everything. It would have been nice to be able to simply call :ApexDeployAll from within vim.

A more typical example would be developing in a dev org, deploying multiple times, then switching to a packaging org (or a sandbox or production if you're not developing a managed package), and deploying everything since none of the metadata files have changed in the filesystem since your last deploy, but they've changed since you last deployed to this org.

from vim-force.com.

neowit avatar neowit commented on June 1, 2024

I see. Thanks for the details.
Will look into this (unless you want to have a go yourselves of course).

Meanwhile - in order to mark some/all files in the project to be picked up by ApexDeploy you could just run touch on all *-meta.xml files.
ApexDeploy just checks modification date of "-meta.xml" and its code counterpart (.cls, .trigger, etc) to establish if that file is "modified".

from vim-force.com.

cwarden avatar cwarden commented on June 1, 2024

Touching all of the non--meta.xml files is actually what I did first, and that reminds of another problem. I want to deploy components that don't have -meta.xml counterparts: objects, workflows, etc. The all mode should deploy everything within the src directory.

from vim-force.com.

neowit avatar neowit commented on June 1, 2024

There is now :ApexDeployAll command available
Do not expect too much from it though. There are some limitations imposed by Salesforce.com Metadata API. For details see
:help ApexDeployAll

from vim-force.com.

cwarden avatar cwarden commented on June 1, 2024

Thanks!

from vim-force.com.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.