Инструменты пользователя

Инструменты сайта


ci:jenkins-build-latest-git-tag

Различия

Здесь показаны различия между двумя версиями данной страницы.

Ссылка на это сравнение

Предыдущая версия справа и слева Предыдущая версия
ci:jenkins-build-latest-git-tag [2016/09/07 12:33]
root
ci:jenkins-build-latest-git-tag [2016/09/07 12:34] (текущий)
root
Строка 1: Строка 1:
-http://​erics-notes.blogspot.com/​2013/​05/​jenkins-build-latest-git-tag.html +  * http://​erics-notes.blogspot.com/​2013/​05/​jenkins-build-latest-git-tag.html 
-https://​www.cloudbees.com/​blog/​advanced-git-jenkins +  ​* ​https://​www.cloudbees.com/​blog/​advanced-git-jenkins 
-http://​stackoverflow.com/​questions/​7805603/​is-it-possible-for-jenkins-to-automatically-detect-and-build-newly-created-tags+  ​* ​http://​stackoverflow.com/​questions/​7805603/​is-it-possible-for-jenkins-to-automatically-detect-and-build-newly-created-tags
  
 <​note>​ <​note>​
 In fact, you will get a detached HEAD whenever you checkout any commit by its SHA1, whether or not it's at the tip of a branch; the only kind of thing you can checkout without getting a detached HEAD is a branch name. For example, even though master is at ed489 on the diagram above, git checkout ed489 will give you a detached HEAD, while git checkout master will not. In fact, you will get a detached HEAD whenever you checkout any commit by its SHA1, whether or not it's at the tip of a branch; the only kind of thing you can checkout without getting a detached HEAD is a branch name. For example, even though master is at ed489 on the diagram above, git checkout ed489 will give you a detached HEAD, while git checkout master will not.
 </​note>​ </​note>​
ci/jenkins-build-latest-git-tag.txt · Последние изменения: 2016/09/07 12:34 — root