Alias a Build No.
Why do I need a custom build number?
The default pipeline build number consists of a self-increasing number of 1. To increase recognition, we allow you to set an alias for the pipeline build number, which will give priority to your custom build number format on the page display.
Opening method
Just go to the pipeline base settings page and set the corresponding build number rules, e.g：
Rule Description
Available formats
| KEY | Example |
|---|---|
YEAR | 2020 |
DAY_OF_MONTH | 28 |
DAY_OF_YEAR | 285 |
DAY_OF_YEAR | 285 |
MINUTE | 55 |
MONTH_OF_YEAR | 3 |
BUILD_NO_OF_DAY | Increment from 1, reset daily |
DATE: "yyMMdd hh:MM" | 20201028 10:08 |
SECOND | 59 |
New field variable: ${BK_CI_BUILD_NUM_ALIAS}
The value contains a maximum of 256 characters
The maximum length of the actual string generated by this character is 256 characters
Strong reminder when configuring custom build numbers: parts that exceed the length limit will be truncated
Long build number does not affect pipeline construction
Allowed characters
The characters allowed by the rule are changed to: ^[\w-{}() +? :$"]{1,256}$, custom internal version number rules can only be made by [uppercase and lowercase letters, numbers, spaces, -, _,. , :, {, }, (,), ", +, ? , $] characters, and the length is between 1 and 256
The rules for formatting time in db should be configured as: DATE:"(. +? )", (. +? ) refers to the general rule, support user-configured rules consisting of upper and lower case letters, spaces, :, - and other characters, such as: yyyy-MM-dd HH:mm:ss 3, user-configured rules, by $ reference to specific rules xx
Effect show
Last updated
