Figure 5.20. Merge results
5.4.2.4.3. Tags
When pushing tags, each tag can be named and chosen to be created if it does not exist (which fails
if it does already exist). Environment variables can be embedded in the tag name. Examples include
the process ID such as HUDSONBUILD$PPID or even a build number, if that is provided by a Jenkins
plugin, such as $HUDSONAUTOTAG$BUILDNUM. Tags can be targeted to a specific remote such as
origin or integrationrepo.
5.4.2.4.4. Branches
The current HEAD used in the Jenkins build of the application can be pushed to other remotes as an
after-step of the build. You only need to provide the destination branch name and remote name.
Names of remotes are validated against the earlier configuration of the plugin. If the remote doesn’t
exist, a warning is displayed.
5.4.2.5. GitHub plugin
The GitHub plugin offers two integration points. First, it offers an optional link to the project’s GitHub
home page. Just enter the URL for the project (without the tree/master or tree/branch part). For example,
http://github.com/matthewmccullough/git-workshop.
Secondly, the GitHub plugin offers per-file-changed links that are wired via the Repository browser
section of a job’s Source Code Management configuration (see Figure 5.21, “GitHub repository
browser”).