[ 
https://issues.jenkins-ci.org/browse/JENKINS-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161243#comment-161243
 ] 

Bertrand Latinville commented on JENKINS-11749:
-----------------------------------------------

I'm very interested in the Included regions feature for GitSCM plugin and have 
been testing it
via SCM polling and Git hook.

I could see that in some cases the jobs were not triggered whereas some changes 
have been made in the included regions.

After some more testing I discovered that if several commits are made, only the 
last commit seems to be taken into account.

Spying the gitcommand the plugin is using I could see : 

{code:xml}
git rev-parse --verify HEAD
git command : fetch -t https://url.git +refs/heads/*:refs/remotes/origin/* 
git tag -l master
git command : rev-parse origin/master^{commit} 
  -> Gives the new SHA1
git command : show --no-abbrev --format=raw -M --raw 'new sha1' 
{code}
The last command shows only diff from latest sha1, should't it be something 
like : 
{code:xml}
git show --no-abbrev --format=raw -M --raw 'old sha1'..'new sha1' 
{code}
'old sha1' beeing the sha1 of the latest build.

Can you confirm there is a bug or have I something wrong in my setup ?

Thanks, 

Bertrand
                
> Included regions feature for GitSCM plugin
> ------------------------------------------
>
>                 Key: JENKINS-11749
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11749
>             Project: Jenkins
>          Issue Type: New Feature
>          Components: git
>    Affects Versions: current
>            Reporter: Juerg Haefliger
>            Assignee: Juerg Haefliger
>            Priority: Minor
>
> For having several regions to be excluded from build its better to filter the 
> building process only for some included regions.
> [Description copied from http://issues.hudson-ci.org/browse/HUDSON-7294]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to