You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,15 @@ Triggers from push events may be filtered based on the branch name, i.e. the bui
61
61
62
62
This functionality requires accessing the Gitlab server (see [above](#configuring-access-to-gitlab)) and for the time being also a git repository url already saved in the project configuration. In other words, when creating a new project, the configuration needs to be saved *once* before being able to select the allowed branches. For existing projects, all branches are allowed to push by default.
63
63
64
+
Build Tags
65
+
================
66
+
67
+
In order to build when a new tag is pushed:
68
+
* In the ``GitLab server`` add ``Tag push events`` to the ``Web Hook``
69
+
* In the ``Jenkins`` under the ``Source Code Management`` section:
70
+
* select ``Advance...`` and add ``+refs/tags/*:refs/remotes/origin/tags/*`` as ``Refspec``
71
+
* you can also use ``Branch Specifier`` to specify which tag need to be built (exampple ``refs/tags/${TAGNAME}``)
LOGGER.log(Level.INFO, "Trying to get name and URL for job: {0} using project {1} (push)", newString[]{job.getName(), getDesc().project.getName()});
147
+
148
+
LOGGER.log(Level.INFO, "Trying to get name and URL for job: {0} using project {1} (push)", newString[]{job.getName(), job.getRootProject().getName()});
0 commit comments