Azure DevOps builds (job)
A badge requires three pieces of information:
ORGANIZATION
, PROJECT_ID
and DEFINITION_ID
.
To start, edit your build definition and look at the url:
Then use the Azure DevOps REST API to translate the
PROJECT_NAME
to a PROJECT_ID
.
Navigate to https://dev.azure.com/ORGANIZATION/_apis/projects/PROJECT_NAME
Path Parameters |
---|
organization string — REQUIREDExample: totodem |
projectId string — REQUIREDExample: 8cf3ec0e-d0c2-4fcd-8206-ad204f254a96 |
definitionId string — REQUIREDExample: 5 |
Query Parameters |
---|
stage stringExample: Successful Stage |
job stringExample: Successful Job |
style stringOne of: flat (default), flat-square, plastic, for-the-badge, social Example: flat |
logo stringOne of the named logos (bitcoin, dependabot, gitlab, npm, paypal, serverfault, stackexchange, superuser, telegram, travis) or simple-icons. All simple-icons are referenced using icon slugs. You can click the icon title on simple-icons to copy the slug or they can be found in the slugs.md file in the simple-icons repository. Example: appveyor |
logoColor stringThe color of the logo (hex, rgb, rgba, hsl, hsla and css named colors supported). Supported for named logos and Shields logos but not for custom logos. For multicolor Shields logos, the corresponding named logo will be used and colored. Example: violet |
label stringOverride the default left-hand-side text (URL-Encoding needed for spaces or special characters!) Example: healthiness |
labelColor stringBackground color of the left part (hex, rgb, rgba, hsl, hsla and css named colors supported). Example: abcdef |
color stringBackground color of the right part (hex, rgb, rgba, hsl, hsla and css named colors supported). Example: fedcba |
cacheSeconds stringHTTP cache lifetime (rules are applied to infer a default value on a per-badge basis, any values specified below the default will be ignored). Example: 3600 |
link string[]Specify what clicking on the left/right of a badge should do. Note that this only works when integrating your badge in an |