找回密码
 我要加入

QQ登录

只需一步,快速开始

   

Normally, builds are named by their sequential numbers, but you can change that here by    setting what name new build gets. This field can contain the following macros:   
${FAILED_TESTS}Displays failing unit test information, if any tests failed.showStackShows stack trace in failing test output. Defaults to true.showMessageShows error message in failing test output. Defaults to true.maxTestsDisplay at most this many tests. No limit is set by default.onlyRegressionsDisplay only the failing tests that are different from previous builds. Defaults to false.
${TEST_COUNTS,var="TYPE"}Displays the number of tests based on the type (var) passed in (total, pass, fail, skip). Defaults to total.
${GIT_BRANCH}    Expands to the name of the branch that was built.  Parametersall      If specified, all the branches that point to the given commit is listed.      By default, the token expands to just one of them.    fullName      If specified, this token expands to the full branch name, such as 'origin/master'.      Otherwise, it only expands to  the short name, such as 'master'.   
${GIT_REVISION}    Expands to the Git SHA1 commit ID that points to the commit that was built.  Parameterslength=N (optional, default to 40)      Specify the commit ID length. Full SHA1 commit ID is 40 character long, but it is common      to cut it off at 8 or 12 as that often provide enough uniqueness and is a lot more legible.   
${ADMIN_EMAIL}Displays the email address for the Jenkins administrator
${BUILD_CAUSE} ${CAUSE}Displays the cause of the build.
${BUILD_LOG_EXCERPT}Displays an excerpt from the build log.startRegular expression to match the excerpt starting line (matching line is excluded).endRegular expression to match the excerpt ending line (matching line is excluded).See java.util.regex.Pattern
${BUILD_LOG}Displays the end of the build log.maxLinesDisplay at most this many lines of the log. Defaults to 250.escapeHtmlIf true, HTML is escape. Defaults to false.
${BUILD_LOG_MULTILINE_REGEX}Displays build log segments that match the regular expression.regexjava.util.regex.PatternSegments of the build log that match this regular expression are included.  See also null. No default. Required parametermaxMatchesThe maximum number of matches to include. If 0, all matches will be included. Defaults to 0.showTruncatedLinesIf true, include [...truncated ### lines...] lines. Defaults to true.substTextIf non-null, insert this text into the email rather than the entire segment. Defaults to null.escapeHtmlIf true, escape HTML. Defaults to false.matchedSegmentHtmlStyleIf non-null, output HTML. Matched lines will become <b style="your-style-value">html escaped matched lines</b>. Defaults to null.
${BUILD_LOG_REGEX}Displays lines from the build log that match the regular expression.regexLines that match this regular expression are included. See also java.util.regex.Pattern.Defaults to "(?i)\\b(error|exception|fatal|fail(ed|ure)|un(defined|resolved))\\b"linesBeforeThe number of lines to include before the matching line. Lines that overlap with another match or linesAfter are only inlcuded once. Defaults to 0.linesAfterThe number of lines to include after the matching line. Lines that overlap with another match or linesBefore are only included once. Defaults to 0.maxMatchesThe maximum number of matches to include. If 0, all matches will be included. Defaults to 0.showTruncatedLinesIf true, include [...truncated ### lines...] lines. Defaults to true.substTextIf non-null, insert this text into the email rather than the entire line. Defaults to null.escapeHtmlIf true, escape HTML. Defauts to false.matchedLineHtmlStyleIf non-null, output HTML. Matched lines will become <b style="your-style-value"> html escaped matched line</b>. Defaults to null.addNewlineIf true, adds a newline after subsText. Defaults to true.defaultValueThis value will be used if nothing is replaced.
${BUILD_NUMBER}    Expands to the current build number, a sequential auto-incrementing unique number that identifies the build, such as "125"  
${BUILD_STATUS}Displays the status of the current build. (failing, success, etc...)
${BUILD_URL}Displays the URL for the current build
${CHANGES_SINCE_LAST_BUILD} ${CHANGES}Displays the changes since the last build.showDependenciesIf true, changes to projects this build depends on are shown. Defaults to falseshowPathsIf true, the paths, modified by a commit are shown. Defaults to falseformatFor each commit listed, a string containing %X, where %x is one of:%aauthor%ddate%mmessage%ppath%rrevisionNot all revision systems support %d and %r. If specified showPaths argument is ignored. Defaults to "[%a] %m\\n"
pathFormatA string containing %p to indicate how to print paths. Defaults to "\\t%p\\n"regexA regular expression.replaceA replacement for all sub-strings of the change message that match the given regular expression.defaultMessage to use when no changes are detected. Defaults to "No changes\n"
${CHANGES_SINCE_LAST_SUCCESS}Displays the changes since the last successful build.reverseIf true, show most recent builds at the top instead of the bottom. Defaults to false.formatFor each build listed, a string containing %X, where %X is one of%cchanges%nbuild numberDefaults to Changes for Build #%n\n%c\n
changesFormatFor each change in a build. See ${CHANGES_SINCE_LAST_BUILD} for placeholders.Following Parameters are also supported: showPaths, pathFormat, showDependencies, dateFormat, regex, replace, default. See ${CHANGES_SINCE_LAST_BUILD} details.
${CHANGES_SINCE_LAST_UNSTABLE}Expands to the changes since the last unstable or successful build. reverseIf true, show most recent builds at the top instead of the bottom. Defaults to false.formatFor each build listed, a string containing %X, where %X is one of%cchanges%nbuild numberDefaults to Changes for Build #%n\n%c\n
changesFormatFor each change in a build. See ${CHANGES_SINCE_LAST_BUILD} for placeholders.Following Parameters are also supported: showPaths, pathFormat, showDependencies, dateFormat, regex, replace, default. See ${CHANGES_SINCE_LAST_BUILD} details.
${ENV,var="VARIABLENAME"}    Expands to an environment variable (specified here as VARIABLENAME) from the build environment. Note that this does not include any variables set by the build scripts themselves, only those set by Jenkins and other plugins.  
${JENKINS_URL}Displays the URL to the Jenkins server. (You can change this on the system configuration page.)
${JOB_DESCRIPTION}Displays the description of the job.

${LOG_REGEX}Uses a regular expression to find a single log entry and generates a new output using the capture groups from it. This is partially based on the description-setter plugin (https://github.com/jenkinsci/description-setter-plugin).
${PROJECT_NAME}Displays the project's full name. (See AbstractProject.getFullDisplayName)${PROJECT_DISPLAY_NAME}Displays the project's display name. (See AbstractProject.getDisplayName)
${PROJECT_URL}Displays a URL to the project's page.
${PROPFILE,file="FILENAME",property="PROPERTYNAME"}    Expands to the value of a property in a property file. The filename is relative to the build workspace root.  
${FILE,path="PATH"}    Expands to the contents of a file. The file path is relative to the build workspace root.  
${XML,file="FILE",xpath="XPATH"}    Expands to the result(s) of an XPath expression run against the given XML file.
    If the XPath evaluates to more than one value, then a semicolon-separated string is returned.
    The file path is relative to the build workspace root.  
In addition to the tokens, you can modify the result of the token expansion using parameter expansions. They follow similar rules as bash Parameter Expansions. The supported expansions are: ${#TOKEN} which resolves to the length of the expanded token value, ${TOKEN:offset:length} which takes a substring of the token result (length is optional and offset and length can both be negative), ${TOKEN#pattern} which matches the pattern against the start of the expanded token and removes it if it, ${TOKEN%pattern} which matches the pattern against the end of the expanded token and removes it it if matches.


本帖子中包含更多资源

您需要 登录 才可以下载或查看,没有帐号?我要加入

x
分享至 : QQ空间
收藏
您需要登录后才可以回帖 登录 | 我要加入
关闭

站长推荐 上一条 /2 下一条