StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19379722
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-15T11:09:02.180
FavoriteCount
0
LastActivityDate
2013-11-04T11:21:05.680
LastEditDate
2013-11-04T11:21:05.680
LastEditorUserId
366749
OwnerUserId
366749
ParentId
11385368
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You can use the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin" rel="nofollow">Build Name Setter Plugin</a> to change the name based on available Tokens. I'm not sure if a TOKEN exists for your Git branch name, but if all else fails, you can use a shell script build step and write it to a property file, and then use the macro: ${PROPFILE,..}, e.g.: <pre><code>#${BUILD_NUMBER}_${PROPFILE,file="parameters.properties",property="BUILD_TYPE"} </code></pre> Alternatively, you can use the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin" rel="nofollow">Description Setter Plugin</a> to change the build description (that also appears in the Build Executor status) based on the build output. Again, you can use the same trick and use a shell script to print out the branch name in the build output, and use a regex to parse it out of your build log. A small limitation: either of this will only update the name/description after the job completes, so for long-running jobs, it's not immediately visible. But for short ones, and for audit purposes, this works well. [EDIT] Some time later, I started using the <a href="https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin" rel="nofollow">EnvInject plugin</a>, which adds my build parameters to the environment early enough for the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin" rel="nofollow">Build Name Setter Plugin</a> to use them. This has the advantage of setting the build name immediately. Also, you can get the Git branch with ${GIT_BRANCH}. Here's the doc for it: <pre><code>${GIT_BRANCH} Expands to the name of the branch that was built. Parameters: all 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'. </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCustomizing "Build Executor Status" of Jenkins
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPatrice M.
UserOwnerUserId
1. USPatrice M.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.