Hallo Reinhold, I mean that using freestyle jobs in Jenkins we get for each Build a message like:
"Triggered by GitLab Merge Request #1: Tests/feature/1234567 => master" (and this is a link to gitlab) and in Gitlab merge request you get a message like: "Jenkins Robot @jenkins commented 2 mins ago Jenkins Build SUCCESS Results available at: Jenkins [xxxx mergeRequests #26] " (and this a link to Jenkins build) but based on your hint, I got all jenkins plugins up to date now and I set trigger for mergerequest events only (not push) and it works fine with pipelines :) Regards, Pablo On Tuesday, October 22, 2019 at 8:41:56 AM UTC+2, r.fuereder wrote: > > Hi Pablo, > > > > which Links? I am seeing Links to GitLab “Commits” in “Changes” section > (scripted pipeline; only “Push Events” is enabled for GitLab Triggers; Git > checkout has configured “gitlab” as repository browser; this requires Git > plugin in beta version IIRC; in addition the pipeline finally calls > “updateGitlabCommitStatus” step, but this is another story) > > > > HTH Reinhold > > > > > > *From:* jenkins...@googlegroups.com <javascript:> < > jenkins...@googlegroups.com <javascript:>> *On Behalf Of *Pa Y > *Sent:* Montag, 21. Oktober 2019 23:56 > *To:* Jenkins Users <jenkins...@googlegroups.com <javascript:>> > *Subject:* Re: declarative pipeline and gitlab > > > > Hi Gabriele, > > yes, you are right,thanks. The issue was the URL used (I need to RTFM > carefully)... as it seems you have experience with this: by using pipeline > so far I get in Jenkins only a note like "Started by GitLab push > by.." without any link to gitlab merg request.. by using freestyle job, > the links are overall there. did you manage to get this? > > > > Best Regards, > > Pablo > > > On Monday, October 21, 2019 at 1:48:03 PM UTC+2, Gabriele Bonetti wrote: > > Hi, > > Maybe it's a "mister obvious" answer but have you set up the build trigger > on the receiving pipeline? In the pipeline configuration you should have an > option "Build when a change is pushed to gitlab" that you can enable and > select the set of the events that would trigger the pipeline. > Also from here you can confirm that the webhook you are using is correct. > > > > On Tuesday, October 15, 2019 at 10:47:12 AM UTC+2, Pa Y wrote: > > Hello, > > has somebody managed successfully to use declarative pipeline and gitlab? > > > > I followed the instructions listed here: > https://docs.gitlab.com/ee/integration/jenkins.html and this works for > freestyle jobs. we use this already without problems. > > > > Now, I try to move to pipelines to have more options in general. > > > > So far, we get gitlab hook sent succcessfully but for this we need to > disable in Jenkins : Prevent Cross Site Request Forgery exploits , what I > don't really want... > > > > And anyway after hook was sent, Jenkins job can't be triggered > > > > can maybe somebody share a running example? > > > > Thanks for any help in advance! > > > > Pablo > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkins...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/708e7ee8-1651-40fb-b0c8-6f7a6368bef5%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/708e7ee8-1651-40fb-b0c8-6f7a6368bef5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b9eefaac-1097-41f5-9478-c186b91f534e%40googlegroups.com.
