Updating a variable in a linked variable group with $(Build.BuildId) from a Linux pipeline
I'd like to update a variable in a linked variable group with $(Build.BuildId) from a Linux pipeline. I see a few examples using the @echo ##vso[task.setvariable command, but can't get it to work because I don't think I'm referencing the source or destination right.
The linked variable group is NightlyBuildID and the variable is LinuxBuildID.
Here's one of my many attempts:
@echo ##vso[task.setvariable variable=LinuxBuildID]$(Build.BuildId)
azure-devops asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
add a comment |
I'd like to update a variable in a linked variable group with $(Build.BuildId) from a Linux pipeline. I see a few examples using the @echo ##vso[task.setvariable command, but can't get it to work because I don't think I'm referencing the source or destination right.
The linked variable group is NightlyBuildID and the variable is LinuxBuildID.
Here's one of my many attempts:
@echo ##vso[task.setvariable variable=LinuxBuildID]$(Build.BuildId)
azure-devops asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
add a comment |
I'd like to update a variable in a linked variable group with $(Build.BuildId) from a Linux pipeline. I see a few examples using the @echo ##vso[task.setvariable command, but can't get it to work because I don't think I'm referencing the source or destination right.
The linked variable group is NightlyBuildID and the variable is LinuxBuildID.
Here's one of my many attempts:
@echo ##vso[task.setvariable variable=LinuxBuildID]$(Build.BuildId)
azure-devops asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
I'd like to update a variable in a linked variable group with $(Build.BuildId) from a Linux pipeline. I see a few examples using the @echo ##vso[task.setvariable command, but can't get it to work because I don't think I'm referencing the source or destination right.
The linked variable group is NightlyBuildID and the variable is LinuxBuildID.
Here's one of my many attempts:
@echo ##vso[task.setvariable variable=LinuxBuildID]$(Build.BuildId)
azure-devops azure-devops asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
asked Nov 24 '18 at 21:56
Gary SpinelliGary Spinelli
111
111
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The $(variable) syntax is only valid within the build editor interface. Within a script, you have to reference it as an environment variable. Periods are replaced with underscores.
Thus, in Linux, $(Build.BuildId) would be accessed as $BUILD_BUILDID.
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
OK. Thanks. Using that syntax, I can see the correct values of these variables in the log after execution, but I still can't modify the variable WINDOWSBUILDID in the variable group. I first manually set WINDOWSBUILDID to 99 in the Team Services UI, then run this script: echo $WINDOWSBUILDID echo $BUILD_BUILDID echo "##vso[task.setvariable variable=$WINDOWSBUILDID]$BUILD_BUILDID" echo $WINDOWSBUILDID The output is: 99 6100 99
– Gary Spinelli
Nov 25 '18 at 13:53
1
The correct syntax is##vso[task.setvariable variable=WINDOWSBUILDID;]$BUILD_BUILDID. Note the lack of a dollar sign in front of the variable name. Refer to the documentation: github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/…
– Daniel Mann
Nov 25 '18 at 15:08
add a comment |
Apparently, this can't be done, according to the link below. I'll have to come up with a work around, bummer.
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/32083207-allow-variables-in-variable-groups-to-be-settable
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
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%2f53462702%2fupdating-a-variable-in-a-linked-variable-group-with-build-buildid-from-a-linu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The $(variable) syntax is only valid within the build editor interface. Within a script, you have to reference it as an environment variable. Periods are replaced with underscores.
Thus, in Linux, $(Build.BuildId) would be accessed as $BUILD_BUILDID.
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
OK. Thanks. Using that syntax, I can see the correct values of these variables in the log after execution, but I still can't modify the variable WINDOWSBUILDID in the variable group. I first manually set WINDOWSBUILDID to 99 in the Team Services UI, then run this script: echo $WINDOWSBUILDID echo $BUILD_BUILDID echo "##vso[task.setvariable variable=$WINDOWSBUILDID]$BUILD_BUILDID" echo $WINDOWSBUILDID The output is: 99 6100 99
– Gary Spinelli
Nov 25 '18 at 13:53
1
The correct syntax is##vso[task.setvariable variable=WINDOWSBUILDID;]$BUILD_BUILDID. Note the lack of a dollar sign in front of the variable name. Refer to the documentation: github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/…
– Daniel Mann
Nov 25 '18 at 15:08
add a comment |
The $(variable) syntax is only valid within the build editor interface. Within a script, you have to reference it as an environment variable. Periods are replaced with underscores.
Thus, in Linux, $(Build.BuildId) would be accessed as $BUILD_BUILDID.
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
OK. Thanks. Using that syntax, I can see the correct values of these variables in the log after execution, but I still can't modify the variable WINDOWSBUILDID in the variable group. I first manually set WINDOWSBUILDID to 99 in the Team Services UI, then run this script: echo $WINDOWSBUILDID echo $BUILD_BUILDID echo "##vso[task.setvariable variable=$WINDOWSBUILDID]$BUILD_BUILDID" echo $WINDOWSBUILDID The output is: 99 6100 99
– Gary Spinelli
Nov 25 '18 at 13:53
1
The correct syntax is##vso[task.setvariable variable=WINDOWSBUILDID;]$BUILD_BUILDID. Note the lack of a dollar sign in front of the variable name. Refer to the documentation: github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/…
– Daniel Mann
Nov 25 '18 at 15:08
add a comment |
The $(variable) syntax is only valid within the build editor interface. Within a script, you have to reference it as an environment variable. Periods are replaced with underscores.
Thus, in Linux, $(Build.BuildId) would be accessed as $BUILD_BUILDID.
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
The $(variable) syntax is only valid within the build editor interface. Within a script, you have to reference it as an environment variable. Periods are replaced with underscores.
Thus, in Linux, $(Build.BuildId) would be accessed as $BUILD_BUILDID.
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
answered Nov 25 '18 at 5:29
Daniel MannDaniel Mann
39.1k66086
39.1k66086
OK. Thanks. Using that syntax, I can see the correct values of these variables in the log after execution, but I still can't modify the variable WINDOWSBUILDID in the variable group. I first manually set WINDOWSBUILDID to 99 in the Team Services UI, then run this script: echo $WINDOWSBUILDID echo $BUILD_BUILDID echo "##vso[task.setvariable variable=$WINDOWSBUILDID]$BUILD_BUILDID" echo $WINDOWSBUILDID The output is: 99 6100 99
– Gary Spinelli
Nov 25 '18 at 13:53
1
The correct syntax is##vso[task.setvariable variable=WINDOWSBUILDID;]$BUILD_BUILDID. Note the lack of a dollar sign in front of the variable name. Refer to the documentation: github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/…
– Daniel Mann
Nov 25 '18 at 15:08
add a comment |
OK. Thanks. Using that syntax, I can see the correct values of these variables in the log after execution, but I still can't modify the variable WINDOWSBUILDID in the variable group. I first manually set WINDOWSBUILDID to 99 in the Team Services UI, then run this script: echo $WINDOWSBUILDID echo $BUILD_BUILDID echo "##vso[task.setvariable variable=$WINDOWSBUILDID]$BUILD_BUILDID" echo $WINDOWSBUILDID The output is: 99 6100 99
– Gary Spinelli
Nov 25 '18 at 13:53
1
The correct syntax is##vso[task.setvariable variable=WINDOWSBUILDID;]$BUILD_BUILDID. Note the lack of a dollar sign in front of the variable name. Refer to the documentation: github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/…
– Daniel Mann
Nov 25 '18 at 15:08
OK. Thanks. Using that syntax, I can see the correct values of these variables in the log after execution, but I still can't modify the variable WINDOWSBUILDID in the variable group. I first manually set WINDOWSBUILDID to 99 in the Team Services UI, then run this script: echo $WINDOWSBUILDID echo $BUILD_BUILDID echo "##vso[task.setvariable variable=$WINDOWSBUILDID]$BUILD_BUILDID" echo $WINDOWSBUILDID The output is: 99 6100 99
– Gary Spinelli
Nov 25 '18 at 13:53
OK. Thanks. Using that syntax, I can see the correct values of these variables in the log after execution, but I still can't modify the variable WINDOWSBUILDID in the variable group. I first manually set WINDOWSBUILDID to 99 in the Team Services UI, then run this script: echo $WINDOWSBUILDID echo $BUILD_BUILDID echo "##vso[task.setvariable variable=$WINDOWSBUILDID]$BUILD_BUILDID" echo $WINDOWSBUILDID The output is: 99 6100 99
– Gary Spinelli
Nov 25 '18 at 13:53
1
1
The correct syntax is
##vso[task.setvariable variable=WINDOWSBUILDID;]$BUILD_BUILDID. Note the lack of a dollar sign in front of the variable name. Refer to the documentation: github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/…– Daniel Mann
Nov 25 '18 at 15:08
The correct syntax is
##vso[task.setvariable variable=WINDOWSBUILDID;]$BUILD_BUILDID. Note the lack of a dollar sign in front of the variable name. Refer to the documentation: github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/…– Daniel Mann
Nov 25 '18 at 15:08
add a comment |
Apparently, this can't be done, according to the link below. I'll have to come up with a work around, bummer.
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/32083207-allow-variables-in-variable-groups-to-be-settable
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
add a comment |
Apparently, this can't be done, according to the link below. I'll have to come up with a work around, bummer.
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/32083207-allow-variables-in-variable-groups-to-be-settable
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
add a comment |
Apparently, this can't be done, according to the link below. I'll have to come up with a work around, bummer.
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/32083207-allow-variables-in-variable-groups-to-be-settable
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
Apparently, this can't be done, according to the link below. I'll have to come up with a work around, bummer.
https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/32083207-allow-variables-in-variable-groups-to-be-settable
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
answered Nov 25 '18 at 16:39
Gary SpinelliGary Spinelli
111
111
add a comment |
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%2f53462702%2fupdating-a-variable-in-a-linked-variable-group-with-build-buildid-from-a-linu%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
