Best practice to setup a development environment with source control,vscode and sandbox
up vote
2
down vote
favorite
i have been working on the traditional way of developing within salesforce using Force.comIDE / aside.io / developer console. i want to move to a more robust way of writing code using a source control(GIT?), VSCode, scratch orgs and sandboxes.
Here is how i think i want to go ( correct me if i am wrong )
- setup a sandbox for final QA
- Pull in all latest metadata into SB
- pull everything from SB into version control( need help setting this up)
- Each user will pull it from version control and work on his branch or scratch org and commit it back once they finish the work. ( Not worked too much with version control so any input would be welcome)
- Then push it from source control into Sandbox for QA
- Then move it to production
Is there a better way to do it? Does any one have reference to articles which can help set it up
salesforcedx-cli vs-code environment
asked 3 hours ago
Prady
6,5281985169
add a comment |
up vote
2
down vote
favorite
i have been working on the traditional way of developing within salesforce using Force.comIDE / aside.io / developer console. i want to move to a more robust way of writing code using a source control(GIT?), VSCode, scratch orgs and sandboxes.
Here is how i think i want to go ( correct me if i am wrong )
- setup a sandbox for final QA
- Pull in all latest metadata into SB
- pull everything from SB into version control( need help setting this up)
- Each user will pull it from version control and work on his branch or scratch org and commit it back once they finish the work. ( Not worked too much with version control so any input would be welcome)
- Then push it from source control into Sandbox for QA
- Then move it to production
Is there a better way to do it? Does any one have reference to articles which can help set it up
salesforcedx-cli vs-code environment
asked 3 hours ago
Prady
6,5281985169
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
i have been working on the traditional way of developing within salesforce using Force.comIDE / aside.io / developer console. i want to move to a more robust way of writing code using a source control(GIT?), VSCode, scratch orgs and sandboxes.
Here is how i think i want to go ( correct me if i am wrong )
- setup a sandbox for final QA
- Pull in all latest metadata into SB
- pull everything from SB into version control( need help setting this up)
- Each user will pull it from version control and work on his branch or scratch org and commit it back once they finish the work. ( Not worked too much with version control so any input would be welcome)
- Then push it from source control into Sandbox for QA
- Then move it to production
Is there a better way to do it? Does any one have reference to articles which can help set it up
salesforcedx-cli vs-code environment
asked 3 hours ago
Prady
6,5281985169
i have been working on the traditional way of developing within salesforce using Force.comIDE / aside.io / developer console. i want to move to a more robust way of writing code using a source control(GIT?), VSCode, scratch orgs and sandboxes.
Here is how i think i want to go ( correct me if i am wrong )
- setup a sandbox for final QA
- Pull in all latest metadata into SB
- pull everything from SB into version control( need help setting this up)
- Each user will pull it from version control and work on his branch or scratch org and commit it back once they finish the work. ( Not worked too much with version control so any input would be welcome)
- Then push it from source control into Sandbox for QA
- Then move it to production
Is there a better way to do it? Does any one have reference to articles which can help set it up
salesforcedx-cli vs-code environment
salesforcedx-cli vs-code environment
asked 3 hours ago
Prady
6,5281985169
asked 3 hours ago
Prady
6,5281985169
asked 3 hours ago
Prady
6,5281985169
asked 3 hours ago
Prady
6,5281985169
asked 3 hours ago
Prady
6,5281985169
6,5281985169
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
Your approach looks correct to me AFAIK. Now we can use SFDX with development orgs as well so if you want you can skip the scratch org part else everythings look good.
I suggest you check this trail. https://trailhead.salesforce.com/content/learn/trails/sfdx_get_started In this trail Salesforce shared step by steps of how we can setup the SFDX with existing org and move our code to version control and Continuous Integration.
I also suggest you to check the SFDX considerations with scratch org limitation to make your decision.
Here are some links for your reference.
Scratch Orgs
Limitations for Salesforce DX
SFDX: Use With Non Scratch Org
answered 2 hours ago
Tushar Sharma
24.3k52148
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242420%2fbest-practice-to-setup-a-development-environment-with-source-control-vscode-and%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Your approach looks correct to me AFAIK. Now we can use SFDX with development orgs as well so if you want you can skip the scratch org part else everythings look good.
I suggest you check this trail. https://trailhead.salesforce.com/content/learn/trails/sfdx_get_started In this trail Salesforce shared step by steps of how we can setup the SFDX with existing org and move our code to version control and Continuous Integration.
I also suggest you to check the SFDX considerations with scratch org limitation to make your decision.
Here are some links for your reference.
Scratch Orgs
Limitations for Salesforce DX
SFDX: Use With Non Scratch Org
answered 2 hours ago
Tushar Sharma
24.3k52148
add a comment |
up vote
3
down vote
Your approach looks correct to me AFAIK. Now we can use SFDX with development orgs as well so if you want you can skip the scratch org part else everythings look good.
I suggest you check this trail. https://trailhead.salesforce.com/content/learn/trails/sfdx_get_started In this trail Salesforce shared step by steps of how we can setup the SFDX with existing org and move our code to version control and Continuous Integration.
I also suggest you to check the SFDX considerations with scratch org limitation to make your decision.
Here are some links for your reference.
Scratch Orgs
Limitations for Salesforce DX
SFDX: Use With Non Scratch Org
answered 2 hours ago
Tushar Sharma
24.3k52148
add a comment |
up vote
3
down vote
up vote
3
down vote
Your approach looks correct to me AFAIK. Now we can use SFDX with development orgs as well so if you want you can skip the scratch org part else everythings look good.
I suggest you check this trail. https://trailhead.salesforce.com/content/learn/trails/sfdx_get_started In this trail Salesforce shared step by steps of how we can setup the SFDX with existing org and move our code to version control and Continuous Integration.
I also suggest you to check the SFDX considerations with scratch org limitation to make your decision.
Here are some links for your reference.
Scratch Orgs
Limitations for Salesforce DX
SFDX: Use With Non Scratch Org
answered 2 hours ago
Tushar Sharma
24.3k52148
Your approach looks correct to me AFAIK. Now we can use SFDX with development orgs as well so if you want you can skip the scratch org part else everythings look good.
I suggest you check this trail. https://trailhead.salesforce.com/content/learn/trails/sfdx_get_started In this trail Salesforce shared step by steps of how we can setup the SFDX with existing org and move our code to version control and Continuous Integration.
I also suggest you to check the SFDX considerations with scratch org limitation to make your decision.
Here are some links for your reference.
Scratch Orgs
Limitations for Salesforce DX
SFDX: Use With Non Scratch Org
answered 2 hours ago
Tushar Sharma
24.3k52148
answered 2 hours ago
Tushar Sharma
24.3k52148
answered 2 hours ago
Tushar Sharma
24.3k52148
answered 2 hours ago
Tushar Sharma
24.3k52148
24.3k52148
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f242420%2fbest-practice-to-setup-a-development-environment-with-source-control-vscode-and%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
