Target specific variables with Azure devops
I'm setting up deployment pools and release pipelines for my application in Azure devops. For my release, I'll have 3 stages: Dev, QA, and Prod. I see how I can take my variable group and apply it to a stage, which has a deployment pool assigned to it. That's great.
The confusing part is that, as an example, I have 3 servers(targets) in my Dev deployment pool, and they have different variables needed for each (different connection strings). I don't know how to make the variables target specific, rather than stage specific.
Should I abandon the idea of grouping my Dev servers into 1 Dev deployment group, and just separate them out? Like make a Dev1 group, and a Dev2 group, and then make a Dev1 stage and Dev2 stage, etc? Or is there a better way I'm missing?
azure-devops azure-pipelines azure-pipelines-release-pipeline
add a comment |
I'm setting up deployment pools and release pipelines for my application in Azure devops. For my release, I'll have 3 stages: Dev, QA, and Prod. I see how I can take my variable group and apply it to a stage, which has a deployment pool assigned to it. That's great.
The confusing part is that, as an example, I have 3 servers(targets) in my Dev deployment pool, and they have different variables needed for each (different connection strings). I don't know how to make the variables target specific, rather than stage specific.
Should I abandon the idea of grouping my Dev servers into 1 Dev deployment group, and just separate them out? Like make a Dev1 group, and a Dev2 group, and then make a Dev1 stage and Dev2 stage, etc? Or is there a better way I'm missing?
azure-devops azure-pipelines azure-pipelines-release-pipeline
add a comment |
I'm setting up deployment pools and release pipelines for my application in Azure devops. For my release, I'll have 3 stages: Dev, QA, and Prod. I see how I can take my variable group and apply it to a stage, which has a deployment pool assigned to it. That's great.
The confusing part is that, as an example, I have 3 servers(targets) in my Dev deployment pool, and they have different variables needed for each (different connection strings). I don't know how to make the variables target specific, rather than stage specific.
Should I abandon the idea of grouping my Dev servers into 1 Dev deployment group, and just separate them out? Like make a Dev1 group, and a Dev2 group, and then make a Dev1 stage and Dev2 stage, etc? Or is there a better way I'm missing?
azure-devops azure-pipelines azure-pipelines-release-pipeline
I'm setting up deployment pools and release pipelines for my application in Azure devops. For my release, I'll have 3 stages: Dev, QA, and Prod. I see how I can take my variable group and apply it to a stage, which has a deployment pool assigned to it. That's great.
The confusing part is that, as an example, I have 3 servers(targets) in my Dev deployment pool, and they have different variables needed for each (different connection strings). I don't know how to make the variables target specific, rather than stage specific.
Should I abandon the idea of grouping my Dev servers into 1 Dev deployment group, and just separate them out? Like make a Dev1 group, and a Dev2 group, and then make a Dev1 stage and Dev2 stage, etc? Or is there a better way I'm missing?
azure-devops azure-pipelines azure-pipelines-release-pipeline
azure-devops azure-pipelines azure-pipelines-release-pipeline
asked Nov 26 '18 at 5:25
PhilPhil
9501230
9501230
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Deployment groups in azure devops share the same configuration settings. Basically your dev servers are different environments so i guess the best approach is to have different deployment groups for every different server.
i was hoping for a different answer honestly. The main reason i asked this question was to avoid this solution, seems like there should be a better way.
– Phil
Dec 16 '18 at 11:41
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53475161%2ftarget-specific-variables-with-azure-devops%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
Deployment groups in azure devops share the same configuration settings. Basically your dev servers are different environments so i guess the best approach is to have different deployment groups for every different server.
i was hoping for a different answer honestly. The main reason i asked this question was to avoid this solution, seems like there should be a better way.
– Phil
Dec 16 '18 at 11:41
add a comment |
Deployment groups in azure devops share the same configuration settings. Basically your dev servers are different environments so i guess the best approach is to have different deployment groups for every different server.
i was hoping for a different answer honestly. The main reason i asked this question was to avoid this solution, seems like there should be a better way.
– Phil
Dec 16 '18 at 11:41
add a comment |
Deployment groups in azure devops share the same configuration settings. Basically your dev servers are different environments so i guess the best approach is to have different deployment groups for every different server.
Deployment groups in azure devops share the same configuration settings. Basically your dev servers are different environments so i guess the best approach is to have different deployment groups for every different server.
answered Nov 26 '18 at 15:35
Angel StankovskiAngel Stankovski
11
11
i was hoping for a different answer honestly. The main reason i asked this question was to avoid this solution, seems like there should be a better way.
– Phil
Dec 16 '18 at 11:41
add a comment |
i was hoping for a different answer honestly. The main reason i asked this question was to avoid this solution, seems like there should be a better way.
– Phil
Dec 16 '18 at 11:41
i was hoping for a different answer honestly. The main reason i asked this question was to avoid this solution, seems like there should be a better way.
– Phil
Dec 16 '18 at 11:41
i was hoping for a different answer honestly. The main reason i asked this question was to avoid this solution, seems like there should be a better way.
– Phil
Dec 16 '18 at 11:41
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53475161%2ftarget-specific-variables-with-azure-devops%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