{"action":"opened","issue":{"url":"https://api.github.com/repos/Microsoft/vso-agent-tasks/issues/581","labels_url":"https://api.github.com/repos/Microsoft/vso-agent-tasks/issues/581/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/vso-agent-tasks/issues/581/comments","events_url":"https://api.github.com/repos/Microsoft/vso-agent-tasks/issues/581/events","html_url":"https://github.com/Microsoft/vso-agent-tasks/issues/581","id":107820222,"number":581,"title":"The \"Batch Script\" (and any other shell/posh/etc) task should set the build name to the BUILD_BUILDNUMBER environment variable on exit (upon completion).","user":{"login":"dmccaffery","id":1803684,"avatar_url":"https://avatars.githubusercontent.com/u/1803684?v=3","gravatar_id":"","url":"https://api.github.com/users/dmccaffery","html_url":"https://github.com/dmccaffery","followers_url":"https://api.github.com/users/dmccaffery/followers","following_url":"https://api.github.com/users/dmccaffery/following{/other_user}","gists_url":"https://api.github.com/users/dmccaffery/gists{/gist_id}","starred_url":"https://api.github.com/users/dmccaffery/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dmccaffery/subscriptions","organizations_url":"https://api.github.com/users/dmccaffery/orgs","repos_url":"https://api.github.com/users/dmccaffery/repos","events_url":"https://api.github.com/users/dmccaffery/events{/privacy}","received_events_url":"https://api.github.com/users/dmccaffery/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-22T23:07:16Z","updated_at":"2015-09-22T23:07:16Z","closed_at":null,"body":"In MsBuild scenarios, one could call the UpdateBuildNumberAndDropLocation task, which would set the name of the build and drop location on the server. I automatically generate a semantic build version in both MSBuild (and now in a build script) and would like the name of the build within VSO/TFS to match the build number I generated. This makes it easier to find, especially for testers using manual test scripts -- since the build number matches the assembly informational version of the assembly / nuget package, etc.\r\n\r\nIn most cases, the build format just isn't acceptable as it is impossible to maintain semantic version (SEMVER) using the available arguments.\r\n\r\nIf the script modifies the BUILD_BUILDNUMBER; the server should pick up this change and use it."}}