[JIRA] (JENKINS-58263) GitLabSCMFile cannot use api, needs heavy checkout

[parichay.barpanda@gmail.com (JIRA)]

Parichay Barpanda updated an issue

Jenkins / JENKINS-58263 GitLabSCMFile cannot use api, needs heavy checkout Change By: Parichay Barpanda Summary: GitLabSCMFile is unable to search for JenkinsFile during cannot use api, needs heavy checkout Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[parichay.barpanda@gmail.com (JIRA)]

Parichay Barpanda started work on JENKINS-58263

Change By: Parichay Barpanda Status: Open In Progress

Add Comment

[parichay.barpanda@gmail.com (JIRA)]

Parichay Barpanda updated an issue

Jenkins / JENKINS-58263 GitLabSCMFile cannot use api, needs heavy checkout

Change By: Parichay Barpanda Attachment: Screenshot from 2019-07-05 09-02-46.png

Add Comment

[parichay.barpanda@gmail.com (JIRA)]

Parichay Barpanda resolved as Fixed

Fixed it in 8e54481 of feature/branch-source branch. There is an inconsistency in gitlab4j. One method = `getFileInfo` took params in the sequence -> project, path, commit hash Second method = `getRawFile` took params in the sequence -> project, commit hash, path So I was mistaken to use the first method param sequence for second method which resulted in `Commit Not Found` exception. Now SCM API do not need to perform heavy checkout which helps in faster branch builds.

Jenkins / JENKINS-58263 GitLabSCMFile cannot use api, needs heavy checkout

Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed

Add Comment

[parichay.barpanda@gmail.com (JIRA)]

Parichay Barpanda updated an issue

Jenkins / JENKINS-58263 GitLabSCMFile cannot use api, needs heavy checkout Change By: Parichay Barpanda

Need to fix repository api in GitLabSCMFile to check for ` JenkinsFile Jenkinsfile ` in the root dir of the repository.

Add Comment