-
Bug
-
Resolution: Not A Defect
-
Blocker
-
Ubuntu Xenial 16.04, Jenkins up to date, Gitlab 10.8.2-ee going to be updated soon to last version.
Im now trying to integrate Gitlab with Jenkin's CI. I did an example pipeline, configured it with my GitLab's PR. If I manually build the pipeline its result is a success but when it's triggered by a push to my Gitlab's PR (this is how i really want it to be).
.- WebHook working fine.
.- Gitlab Plugin working fine.
I'd like to know any suggestion to do, any workaround, I would like to know if the XStream is getting whitelisted anytime soon since i need de CI/CD working fine asap.
The source code its in JAVA, using maven (Don't remember the version).
- relates to
-
-
- Open
-
[JENKINS-51691] JEP-200 Compatibility failing to serialize packages needed for successfully passing java pipeline triggered by push on Gitlab
Class being serialized: https://github.com/timols/java-gitlab-api/blob/master/src/main/java/org/gitlab/api/models/GitlabProject.java (fork, original repo is somewhere in Gitlab I'd guess). I will follow-up
oleg_nenashev Perfect Oleg. Let me know if you need any extra info
Just to set expectations here, I have reached out to the current maintainer and shared some insights about the issue.
Assigning the issue to him for now
exidon can you explain which plugin you are using for GitLab? Is it https://plugins.jenkins.io/gitlab-merge-request-jenkins or https://plugins.jenkins.io/gitlab-plugin ?
exidon which version of the plugin? We have not used the library that is referred to in your stack trace for a long time.
owenmehegan v1.1.32 a mate had a problem with v1.5 version and downgraded it and it works. I can update it to 1.5 if needed
exidon yes it's needed, that version is ancient and unsupported anyway, and now we see that is has this blocking bug. If you have problems with using the latest version, please raise them on the GitHub issues page for the plugin at https://github.com/jenkinsci/gitlab-plugin/issues Your mate is welcome to do that as well 
Also, if you were using this version of the plugin successfully before upgrading Jenkins, you may need to upgrade in two steps to deal with an old config migration bug. You would need to install 1.2.0, and then install the latest. See https://github.com/jenkinsci/gitlab-plugin/issues/473 If you have not been able to use it yet, then this would not impact you and you can just install the latest immediately (or perhaps uninstall, restart, then install).
I'm going to close this as Not A Defect.
Just had a quick look. The referenced class must not be serialized to the disk (GitlabProject) It is a defect in the plugin which needs to be fixed.
CC jglick