Sean Jones

| Software | Working | Not Working | | --- | --- | --- | | GitLab | 7.12 | 8.2.2 | | Jenkins | 1.609.2 | 1.625.2 | |...

@ajohnson-ventera Yeah, your right that error is from 1.2.2, I downgraded the plugin on my Jenkins instance. Which version of Jenkins did you test this on?

I have upgrade the plugin back to 1.2.4 This is the error I am getting, I have assignee set to an empty string. ``` org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run() failed for com.cloudbees.plugins.flow.BuildFlow@77fd7db6[foo-project] java.lang.NullPointerException at...

It was set to jenkins when it upgrade (default from the username I guess) then I set it to empty so it would trigger for any commit. I am testing...

1.2.4 is working! Not 100% sure what was going on but I have updated some jobs which used the plugin to have the assignee set to an empty string and...

I've been bitten by this as well. I my Jenkins logs I did find ``` rg.gitlab.api.GitlabAPIException: {"message":"400 (Bad request) \"body\" not given"} ``` So in theory commit 3ebec021ad4a125971356f978b0ea00df93ae6d3 should fix...

+1

I've been hit with this as well. Strange enough though, on smaller tests I did everything worked out fine 🤔. I could take a look at this in a few...

I've been experiencing the 403 as well but testing the changes on `hysds:master` doesn't seem to have addressed the issue.

Running the echo command and it didn't seem to help. I ended up just restarting my laptop and that seemed to work.