jenkinsci / jenkinsci/gitlab-plugin

Error with Manual build

Open
#837 12 comments 1 reaction 0 assignees View on GitHub
awaiting feedback
Dominant language
Java
Stars
1.4k
Forks
615
Avg merge
4h 32m
Merged PRs (30d)
10

Description

## Issue
### Context
- **Gitlab plugin version**: 1.5.9
- **Gitlab version**: CE v11.1.4
- **Jenkins version**: 2.138
- **Job type**: Pipeline

### Logs & Traces

Jenkins Log for Gitlab plugin with all log levels enabled.

---
```
Sep 17, 2018 12:16:02 PM INFO com.dabsquared.gitlabjenkins.util.CommitStatusUpdater retrieveGitlabProjectIds
Retrieving gitlab project ids
Sep 17, 2018 12:16:02 PM INFO com.dabsquared.gitlabjenkins.util.CommitStatusUpdater retrieveGitlabProjectIds
Build does not contain SCM revision action.
Sep 17, 2018 12:16:02 PM INFO com.dabsquared.gitlabjenkins.util.CommitStatusUpdater retrieveGitlabProjectIds
Retrieving gitlab project ids
Sep 17, 2018 12:16:02 PM INFO com.dabsquared.gitlabjenkins.util.CommitStatusUpdater retrieveGitlabProjectIds
Build does not contain SCM revision action.
Sep 17, 2018 12:16:02 PM INFO com.dabsquared.gitlabjenkins.util.CommitStatusUpdater retrieveGitlabProjectIds
Retrieving gitlab project ids
Sep 17, 2018 12:16:02 PM INFO com.dabsquared.gitlabjenkins.util.CommitStatusUpdater retrieveGitlabProjectIds
Build does not contain SCM revision action.
```
---

### Problem description
I current have 2 jobs for 2 different Gitlab projects. Both are set up to be triggered via webhook, listening to merge request and notes hooks. They both work perfectly well and they update build status on Merge requests.
My current issue happens with trying to build the projects manually. The job is not parametrized and when triggering manually I just want to build master + post the commit status on the master branch.
One of those projects can be built manually and it successfully posts the commit status to the master branch, while the other fails to commit status updates with an error related to missing Build action in gitlabCommitStatus retrieveGitlabProjectIds (Show in Jenkins log above).
How would I go on about fixing an issue like that? I've compared the build.xml files of both projects and they're the same. I can post more info as needed

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.