[JIRA] [core] (JENKINS-34950) GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5
Title: Message Title Paulo Moreira updated an issue Jenkins / JENKINS-34950 GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5 Change By: Paulo Moreira Dear All,Facing an error related with the gitlab merge request plugin (*when updated Jenkins from 2.1 to 2.5*):ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Roll backed to 2.1 and its working! GitlabMerge Request: 2.0.1 (latest) The gitlab merge request plugin is the same version, so therefor the issue should be related with something else.using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress ssh://git@*** HIDDEN ***.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34950) GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5
Title: Message Title Paulo Moreira updated an issue Jenkins / JENKINS-34950 GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5 Change By: Paulo Moreira Dear All,Facing an error related with the gitlab merge request plugin (* when updated Jenkins from 2.1 to 2.5*):ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Roll backed to 2.1 and its working!The gitlab merge request plugin is the same version, so therefor the issue should be related with something else.using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress ssh://git@*** HIDDEN ***.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.Finished: FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34950) GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5
Title: Message Title Paulo Moreira created an issue Jenkins / JENKINS-34950 GitLab Merge Request with Error: Couldn´t find any revision to build, when updated Jenkins from 2.1 to 2.5 Issue Type: Bug Assignee: Unassigned Components: core, gitlab-merge-request-jenkins Created: 2016/May/19 11:16 AM Environment: Linux Ubuntu Priority: Blocker Reporter: Paulo Moreira Dear All, Facing an error related with the gitlab merge request plugin (updated from 2.1 to 2.5): ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Roll backed to 2.1 and its working! The gitlab merge request plugin is the same version, so therefor the issue should be related with something else. using GIT_SSH to set credentials > git -c core.askpass=true fetch --tags --progress ssh://git@*** HIDDEN **.git +refs/heads/:refs/remotes/origin/* > git rev-parse refs/remotes/origin/$ {gitlabSourceBranch}^{commit} # timeout=10 > git rev-parse refs/remotes/origin/refs/remotes/origin/${gitlabSourceBranch} ^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit}