-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipelines show log command #377
Comments
Why show-log? Isn't log enough? az pipelines build log? or is it because of the verb guidance? Let me just check guidelines once again |
I stand corrected. The guidelines do indicate that a verb is required. Including relevant except: All command names should contain a verb e.g. |
Hi guys! Any ETA on that feature? Thanks. |
|
@melezhik - We are right now working on a few high priority items and I do not have a conclusive ETA on this. I will keep this thread posted on the progress. We arrived at the command structure using the guidelines provided by Azure CLI. However, we are open to suggestions as well - what would be your ideal command for this look like? Would it work if you could just alias this command to your ideal command structure? |
Having access to logs in that way is still very interesting. |
Hi, any update on this? Is there a workaround available? |
Any update here? This would be a really useful command. Thanks! |
this is really helpful and standard in other CI systems like Concourse CI ... buildNumber=<build number>
organization=<organization>
# Get Azure Subscription ID
subscriptionId=$(az account show --query id -o tsv)
# Get Azure Access Token to authorize HTTP requests
azureAccessToken=$(az account get-access-token --query accessToken -o tsv)
curl -sL \
-H "authorization: bearer $azureAccessToken" \
-H "content-type: application/json" \
"https://$organization.visualstudio.com/$subscriptionId/_apis/build/builds/$buildNumber/logs" | jq '.value[].url'
|
The text was updated successfully, but these errors were encountered: