2017-05-07 31 views
0

我在詹金斯有一個多分支管道項目。我有兩個主要分支(主人和生產)正確運行一段時間。但其中一個步驟是構建一個新版本的node碼頭圖像(在一個從屬Raspberry pi上),作爲生產系統的最終基礎。我覺得在自己的分支中隔離這個步驟會更好,這樣我們可以控制何時升級版本。如何調試Jenkins多分支掃描 - 不處理新分支

所以我做了一個名爲「節點」的分支,並將Jenkinsfile修改爲只有在其中構建節點的步驟。我還提高了它要構建的節點版本(到7.10.0)。

多分支索引查找新的分支,但是不會執行任何操作。我如何找出原因?

這裏是從掃描/索引運行

Started by timer 
[Sun May 07 21:43:00 BST 2017] Starting branch indexing... 
> git rev-parse --is-inside-work-tree # timeout=10 
Setting origin to [email protected]:dev/pasv5 
> git config remote.origin.url [email protected]:dev/pasv5 # timeout=10 
Fetching origin... 
Fetching upstream changes from origin 
> git --version # timeout=10 
using GIT_ASKPASS to set credentials 
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* 
using GIT_ASKPASS to set credentials 
> git ls-remote [email protected]:dev/pasv5 # timeout=10 
> git rev-parse --is-inside-work-tree # timeout=10 
Setting origin to [email protected]:dev/pasv5 
> git config remote.origin.url [email protected]:dev/pasv5 # timeout=10 
Fetching & pruning origin... 
Fetching upstream changes from origin 
> git --version # timeout=10 
using GIT_ASKPASS to set credentials 
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune 
Getting remote branches... 
Seen branch in repository origin/master 
Seen branch in repository origin/node 
Seen branch in repository origin/production 
Seen 3 remote branches 
Checking branch master 
     ‘Jenkinsfile’ found 
Met criteria 
No changes detected: master (still at 8c4fddfa66f26af0089f0e55afcd2ac9e13152ef) 
Checking branch production 
     ‘Jenkinsfile’ found 
Met criteria 
No changes detected: production (still at fa97e2fd76895c958a484b21fb4d4852ad000c9b) 
Checking branch node 
Done. 
[Sun May 07 21:43:01 BST 2017] Finished branch indexing. Indexing took 0.27 sec 
Finished: SUCCESS 

注意輸出上masterproduction它指出Jenkinsfile發現,但node事實並非如此。爲什麼?

回答

1

我的錯 - 在git的項目配置中的「高級」選項下,您可以列出要考慮的分支。我已經在那裏放了masterproduction而不是node。只要我改變它,它開始處理新的分支。