[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm edited a comment on JENKINS-61850
Re: TFS pull request verification build uses wrong branch
Strangely, the build succeeds when the commit to be merged has been committed in the TFS Git repository itself. When the change is pushed into the TFS Git repository from a clone using a different user name and e-mail address, the pull request verification build fails as described above. Once user.name and user.email on the clone are set to be identical to the TFS Git repository, the pull request verification build after the push succeeds. This seems really strange!Another thing is that the build fails if it is triggered by a TFS branch policy validation build:{noformat}Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/verification-build@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pull/* # timeout=10skipping resolution of commit 03420e8348cfad32cb7916e537a83b4654fbce9b, since it originates from another repository > git rev-parse refs/remotes/origin/merge^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/merge^{commit} # timeout=10 > git rev-parse origin/merge^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.ERROR: Maximum checkout retry attempts reached, abortingFinished: FAILURE{noformat}However, it succeeds when it is triggered by a Jenkins Service Hook in TFS but it fails if it :{noformat}Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/verification-build@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse -- is -inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pull/* # timeout=10 > git rev-parse c607f67f5388726e9b8aa8f04768214e8f5ba5c4^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains c607f67f5388726e9b8aa8f04768214e8f5ba5c4 # timeout=10Checking out Revision c607f67f5388726e9b8aa8f04768214e8f5ba5c4 (origin/pull/19/merge) > git config core.sparsecheckout # timeout=10 > git checkout -f c607f67f5388726e9b8aa8f04768214e8f5ba5c4 # timeout=10Commit message: "Merge pull request 19 from feature-one into master"First time build. Skipping changelog.Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/verification-build[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutusing credential
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Gan Ainm edited a comment on JENKINS-61850 Re: TFS pull request verification build uses wrong branch Strangely, the build succeeds when the commit to be merged has been committed in the TFS Git repository itself. When the change is pushed into the TFS Git repository from a clone using a different user name and e-mail address, the pull request verification build fails as described above. Once user.name and user.email on the clone are set to be identical to the TFS Git repository, the pull request verification build after the push succeeds. This seems really strange! Another thing is that the build succeeds when it is triggered by a Jenkins Service Hook in TFS but it fails if it is triggered by a TFS branch policy validation build. The error message is produced by the Jenkins Git plugin, so I assume _that_ is the source of the strange behavior. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.12569.1587051720192%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Gan Ainm edited a comment on JENKINS-61850 Re: TFS pull request verification build uses wrong branch Strangely, the build succeeds when the commit to be merged has been committed in the TFS git Git repository itself. When the change is pushed into the TFS git Git repository from a clone using a different user name and e-mail address, the pull request verification build fails as described above. Once user.name and user.email on the clone are set to be identical to the TFS git repo Git repository , the pull request verification build after the push succeeds. This seems really strange! The error message is produced by the Jenkins Git plugin, so I assume _that_ is the source of the strange behavior. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.11688.1586957520133%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Gan Ainm updated an issue Jenkins / JENKINS-61850 TFS pull request verification build uses wrong branch Change By: Gan Ainm Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.11686.1586957340134%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Gan Ainm commented on JENKINS-61850 Re: TFS pull request verification build uses wrong branch Strangely, the build succeeds when the commit to be merged has been committed in the TFS git repository itself. When the change is pushed into the TFS git repository from a clone using a different user name and e-mail address, the pull request verification build fails as described above. Once user.name and user.email on the clone are set to be identical to the TFS git repo, the pull request verification build after the push succeeds. This seems really strange! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.11684.1586957040130%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commits are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier {{\*/merge}} to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the {{merge}} branch with the error message _skipping resolution of commit ..., since it originates from another repository_ but builds with the {{HEAD}} commit of the {{master}} branch instead of {{origin-pull/3/merge}} . Here is an excerpt of *git log --oneline --graph --decorate --all*:{noformat}* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master|\ | * 37f0c7d (origin/feature-one) Test* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5{noformat}Here is the console log:{noformat}Lightweight checkout support not available, falling back to full checkout.Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repositorySeen branch in repository origin-pull/2/mergeSeen branch in repository origin-pull/3/mergeSeen branch in repository origin/feature-oneSeen branch in repository origin/masterSeen 4 remote branches > git show-ref --tags -d # timeout=10Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Commit message: "Merged PR 2: change 5" > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/pull-request-verification[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commits are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier {{\*/merge}} to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the {{merge}} branch with the error message _skipping resolution of commit ..., since it originates from another repository_ but builds with the {{HEAD}} commit of the {{master}} branch. Here is an excerpt of *git log --oneline --graph --decorate --all*:{noformat}* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master|\ | * 37f0c7d (origin/feature-one) Test* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5{noformat}Here is the console log:{noformat}Lightweight checkout support not available, falling back to full checkout.Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfileusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git > git --version # timeout=10using GIT_ASKPASS to set credentials > git fetch --tags --progress -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repositorySeen branch in repository origin-pull/2/mergeSeen branch in repository origin-pull/3/mergeSeen branch in repository origin/feature-oneSeen branch in repository origin/masterSeen 4 remote branches > git show-ref --tags -d # timeout=10Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Commit message: "Merged PR 2: change 5" > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/pull-request-verification[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutusing credential c0c927b7-0a3a-4051-af13-91ef394cd497 > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commints commits are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier " {{\ */merge " }} to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the " {{merge}} " branch with the error message _skipping resolution of commit ..., since it originates from another repository_ but builds with the {{HEAD}} commit of the {{master}} branch.Here is an excerpt of *git log --oneline --graph --decorate --all*:{ { noformat} * 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master }} \{{ |\ }} {{ | * 37f0c7d (origin/feature-one) Test }} {{ * | c7e2002 (HEAD, origin/master) Merged PR 2: change 5 {noformat } } Here is the console log:{ { noformat} Lightweight checkout support not available, falling back to full checkout. }} {{ Checking out git [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile }} {{ using credential c0c927b7-0a3a-4051-af13-91ef394cd497 }} \{{ > git rev-parse --is-inside-work-tree # timeout=10 }} {{ Fetching changes from the remote Git repository }} {{ > git config remote.origin.url [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] # timeout=10 }} {{ Fetching upstream changes from [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ]}} \{{ > git --version # timeout=10 }} \{{ using GIT_ASKPASS to set credentials }} {{> git fetch --tags --progress – [ -- http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10 }} {{ skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repository }} {{ Seen branch in repository origin-pull/2/merge }} {{ Seen branch in repository origin-pull/3/merge }} {{ Seen branch in repository origin/feature-one }} {{ Seen branch in repository origin/master }} {{ Seen 4 remote branches }} \{{ > git show-ref --tags -d # timeout=10 }} {{ Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master) }} \{{ > git config core.sparsecheckout # timeout=10 }} \{{ > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10 }} {{ Commit message: "Merged PR 2: change 5" }} \{{ > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10 }} {{ Running in Durability level: MAX_SURVIVABILITY }} {{ [Pipeline] Start of Pipeline }} {{ [Pipeline] node }} {{ Running on Jenkins in
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commints are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier "*/merge" to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the "{{merge}}" branch with the error message {{ _skipping resolution of commit ..., since it originates from another repository_ }} but builds with the {{HEAD}} commit of the {{master}} branch.Here is an excerpt of *git log --oneline --graph --decorate --all*:{{* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master}} \{{|\ }} {{| * 37f0c7d (origin/feature-one) Test}} {{* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5}}Here is the console log:{{Lightweight checkout support not available, falling back to full checkout.}} {{Checking out git [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git] into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile}} {{using credential c0c927b7-0a3a-4051-af13-91ef394cd497}} \{{ > git rev-parse --is-inside-work-tree # timeout=10}} {{Fetching changes from the remote Git repository}} {{ > git config remote.origin.url [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git] # timeout=10}} {{Fetching upstream changes from [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git]}} \{{ > git --version # timeout=10}} \{{using GIT_ASKPASS to set credentials }} {{ > git fetch --tags --progress – [http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git] +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10}} {{skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repository}} {{Seen branch in repository origin-pull/2/merge}} {{Seen branch in repository origin-pull/3/merge}} {{Seen branch in repository origin/feature-one}} {{Seen branch in repository origin/master}} {{Seen 4 remote branches}} \{{ > git show-ref --tags -d # timeout=10}} {{Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master)}} \{{ > git config core.sparsecheckout # timeout=10}} \{{ > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}} {{Commit message: "Merged PR 2: change 5"}} \{{ > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}} {{Running in Durability level: MAX_SURVIVABILITY}} {{[Pipeline] Start of Pipeline}} {{[Pipeline] node}} {{Running on Jenkins in /var/jenkins_home/workspace/pull-request-verification}} {{[Pipeline] {}} {{[Pipeline] stage}} {{[Pipeline] { (Declarative: Checkout SCM)}} {{[Pipeline] checkout}} {{using credential
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm updated an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Change By:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of [https://github.com/jenkinsci/tfs-plugin.] The pull request commints are found on branches named {{remotes/origin/pull/n/merge}}, so I added an additional branch specifier {{ " */merge }} " to the *Branches to build* section of my Jenkins job definition.However, when the build runs, Git refuses to accept the commit from the " {{merge }} " branch with the error message {{ _skipping resolution of commit ..., since it originates from another repository_ }} but builds with the {{HEAD}} commit of the {{master}} branch.Here is an excerpt of *git log --oneline --graph --decorate --all*:{{* 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master}} \ {{|\ }}{{| * 37f0c7d (origin/feature-one) Test}}{{* | c7e2002 (HEAD, origin/master) Merged PR 2: change 5}}Here is the console log:{{Lightweight checkout support not available, falling back to full checkout.}}{{Checking out git [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile}}{{using credential c0c927b7-0a3a-4051-af13-91ef394cd497}} \ {{ > git rev-parse --is-inside-work-tree # timeout=10}}{{Fetching changes from the remote Git repository}}{{ > git config remote.origin.url [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] # timeout=10}}{{Fetching upstream changes from [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] }} \ {{ > git --version # timeout=10}} \ {{using GIT_ASKPASS to set credentials }}{{ > git fetch --tags --progress -- – [ http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git ] +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin-pull/* # timeout=10}}{{skipping resolution of commit 7fcad293a558164c074986e0746a79eee02ba79d, since it originates from another repository}}{{Seen branch in repository origin-pull/2/merge}}{{Seen branch in repository origin-pull/3/merge}}{{Seen branch in repository origin/feature-one}}{{Seen branch in repository origin/master}}{{Seen 4 remote branches}} \ {{ > git show-ref --tags -d # timeout=10}}{{Checking out Revision c7e2002a890151347a6bf38c5fbd423756149d1a (origin/master)}} \ {{ > git config core.sparsecheckout # timeout=10}} \ {{ > git checkout -f c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}}{{Commit message: "Merged PR 2: change 5"}} \ {{ > git rev-list --no-walk c7e2002a890151347a6bf38c5fbd423756149d1a # timeout=10}}{{Running in Durability level: MAX_SURVIVABILITY}}{{[Pipeline] Start of Pipeline}}{{[Pipeline] node}}{{Running on Jenkins in /var/jenkins_home/workspace/pull-request-verification}}{{[Pipeline] {}}{{[Pipeline] stage}}{{[Pipeline] { (Declarative: Checkout SCM)}}{{[Pipeline] checkout}}{{using
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title
Gan Ainm created an issue
Jenkins / JENKINS-61850
TFS pull request verification build uses wrong branch
Issue Type:
Bug
Assignee:
redsolo
Components:
tfs-plugin
Created:
2020-04-09 12:40
Environment:
Jenkins 2.222.1, TFS plugin 5.157.1
Priority:
Minor
Reporter:
Gan Ainm
I configured a Jenkins job for TFS PR verification builds as described in the Git section of https://github.com/jenkinsci/tfs-plugin. The pull request commints are found on branches named remotes/origin/pull/n/merge, so I added an additional branch specifier {{/merge }}to the *Branches to build section of my Jenkins job definition. However, when the build runs, Git refuses to accept the commit from the merge }}branch with the error message skipping resolution of commit ..., since it originates from another repository but builds with the {{HEAD commit of the master branch. Here is an excerpt of git log --oneline --graph --decorate --all: * 7fcad29 (origin-pull/3/merge) Merge pull request 3 from feature-one into master {{|\ }} | * 37f0c7d (origin/feature-one) Test * | c7e2002 (HEAD, origin/master) Merged PR 2: change 5 Here is the console log: Lightweight checkout support not available, falling back to full checkout. Checking out git http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git into /var/jenkins_home/workspace/pull-request-verification@script to read Jenkinsfile using credential c0c927b7-0a3a-4051-af13-91ef394cd497 {{ > git rev-parse --is-inside-work-tree # timeout=10}} Fetching changes from the remote Git repository {{ > git config remote.origin.url http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git # timeout=10}} Fetching upstream changes from http://10.0.2.2:8080/tfs/DefaultCollection/Jenkins-Git-Test/_git/testit.git {{ >
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem with the *cdrx/pyinstaller-linux:python2* container (described in WEBSITE-726, see [ ^ corresponding logfile|https://issues. jenkins -ci . org/secure/attachment/50348/50348_jenkins. log]).However, in my case the container process was not detected at all by {{docker top}}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.3256.1582185601159%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ ^ link title|https://issues. jenkins -ci . org/secure/attachment/50348/50348_jenkins. log]).However, in my case the container process was not detected at all by {{docker top}}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.3188.1582185481904%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ link title|https://issues. ^ jenkins -ci . org/secure/attachment/50348/50348_jenkins. log]).However, in my case the container process was not detected at all by {{docker top}}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.3190.1582185481925%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ title ^ jenkins.log |https://issues.jenkins-ci.org/secure/attachment/50348/50348_jenkins.log ]).However, in my case the container process was not detected at all by {{docker top}}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.3119.1582185420811%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [ title jenkins.log| [^ https://issues. jenkins -ci . org/secure/attachment/50348/50348_jenkins. log] ] ).However, in my case the container process was not detected at all by {{docker top}}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.3117.1582185361324%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see https://issues [jenkins . log|[^ jenkins -ci . org/secure/attachment/50348/50348_jenkins. log ]] ).However, in my case the container process was not detected at all by {{docker top}}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.3047.1582185300942%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title
Gan Ainm edited a comment on JENKINS-49278
Re: cat command in docker agents not detected correctly
I encountered a similar problem (described in WEBSITE-726, see [jenkins https://issues . log|[^ jenkins -ci . org/secure/attachment/50348/50348_jenkins. log ] ) ,] . However, in my case the container process was not detected at all by {{docker top}}.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.3011.1582185240777%40Atlassian.JIRA.
[JIRA] (JENKINS-49278) cat command in docker agents not detected correctly
Title: Message Title Gan Ainm commented on JENKINS-49278 Re: cat command in docker agents not detected correctly I encountered a similar problem (described in WEBSITE-726, see [jenkins.log|[^jenkins.log]),] However, in my case the container process was not detected at all by docker top. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188136.1517348633000.2975.1582185180802%40Atlassian.JIRA.
