Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 04 10:44

    baymac on master

    Fix exit condition for job scan… (compare)

  • Apr 04 10:44
    baymac closed #76
  • Apr 04 10:41

    baymac on git-scm-extension

    (compare)

  • Apr 04 10:41

    baymac on master

    [JENKINS-61760] Use git plugin'… (compare)

  • Apr 04 10:41
    baymac closed #81
  • Apr 04 10:29
    jetersen commented #81
  • Apr 04 10:29
    jetersen commented #81
  • Apr 04 10:27
    jetersen synchronize #81
  • Apr 04 10:27

    jetersen on git-scm-extension

    use the newer jcasc test-harness (compare)

  • Apr 04 10:20

    baymac on jetersen-patch-1

    (compare)

  • Apr 04 10:20

    baymac on master

    update developer name 😅 (#82) (compare)

  • Apr 04 10:20
    baymac closed #82
  • Apr 04 10:12
    jetersen synchronize #81
  • Apr 04 10:12

    jetersen on git-scm-extension

    indents (compare)

  • Apr 04 10:11
    jetersen labeled #82
  • Apr 04 10:11
    jetersen opened #82
  • Apr 04 10:11

    jetersen on jetersen-patch-1

    update developer name 😅 (compare)

  • Apr 04 10:09
    jetersen synchronize #81
  • Apr 04 10:09

    jetersen on git-scm-extension

    move joda-time back to dependen… (compare)

  • Apr 04 10:06
    jetersen synchronize #81
Kostas
@kostasns
Hello, question on Orphaned Item Strategy, at the moment branches/MRs are crossed out in UI and removed only when the 'Scan GitLab Group Now' is performed ... like so
image.png
Is it expected behavior or I have things misconfigured ? :)
Parichay Barpanda
@baymac
For the orphaned items to be removed you should either wait for the automatic scan trigger or manually trigger a scan. This is normal and is implemented that way in the branch api plugin in order to reduce the number of calls your Jenkins server make with every rescan.
@rachit3003 I think you could just ignore the error for now. It doesn't affect the end result. It is just an error due to resetting the same status again. I've not able to find time to fix this issue. Will try to fix it soon.
Kostas
@kostasns
@baymac Understood, thanks :)
Iaroslav Pleten
@ipleten
Is that any chance to get https://issues.jenkins-ci.org/browse/JENKINS-59753 fixed?
steven-terrana
@steven-terrana

Hello, i’ve submitted a pull request that resolves [JENKINS-60915] by adding additional support for the SCM API 2.0 spec.

jenkinsci/gitlab-branch-source-plugin#74

Just an FYI :) thank you for your work on this plugin!
rachit3003
@rachit3003

@rachit3003 I think you could just ignore the error for now. It doesn't affect the end result. It is just an error due to resetting the same status again. I've not able to find time to fix this issue. Will try to fix it soon.

Thanks @baymac for responding. I completely agree that it does not affect the end result. However, the list of stages associated wit the pipeline do not appear in Gitlab due to commit status update failures. Its not a showstopper but my lead expects the stage details to be accessible/visible in Gitlab to look more concise at one place. Do we've an issue raised for this? Do we've any tentative time lines available for the fix? Would you mind updating us in this forum when the fix is ready?

Thanks
Parichay Barpanda
@baymac
Unfortunately we decided on not displaying the stages on GitLab Status due to UX reasons. But I think we should add a trait that gives user to choose what they want. Will send a fix soon. Will update in the channel. @rachit3003
@steven-terrana thanks for the fix
@ipleten will look into it
rachit3003
@rachit3003
Thanks @baymac. Much appreciated!!
Liran Gabay
@liran.gabay_gitlab
Hi! Is there a way to Accept GitLab Merge Request automatically via Jenkins using gitlab-branch-source-plugin plugin ? similar to gitlab-plugin using acceptGitLabMR, thanks!
Mossroy
@mossroy

How can I scan a gitlab group from within a Jenkinsfile?
Here is my use-case. I have a Jenkinsfile with 2 steps :

  • create a tag on a project
  • run a job from the Gitlab Branch Source plugin, on the tag I just created ('my-main-gitlab-group-job/myproject/mytag')

If I do that this way, the second step fails because the tag has not been scanned yet, so the job for this branch does not exist.
So, between these 2 steps, I need to run a scan (and wait until it's finished).
I tried with build job: 'my-main-gitlab-group-job'but it says "ERROR: Waiting for non-job items is not supported"
I tried with build job: 'my-main-gitlab-group-job/computation'but it says "ERROR: No item named my-main-gitlab-group-job/computation found"
How can I do that?

Channy Tremblay
@4wire_gitlab
Hello group! When I try to setup credentials for the gitlab branch plugin, I only have a choice of "none" even if the new token does show up in the main gitlab server config. Any ideas on what I'm doing wrong?
Channy Tremblay
@4wire_gitlab
Nevermind. I was missing the read_repo option.
Cường Tuấn Nguyễn
@cuongdev
Hi all,
I want to define Jenkins pipeline whenever I comment on merge request It will build automatically
You guys can help me to get git comment body in Jenkins pipeline?
tritruong
@tritruong
hi @baymac , thank you for your work on this plugin. I have a question: I need to trigger Merge Request(MR) build only when a team member leaves a comment (E.g: /ok-to-test). Can I do this with gitlab-branch-source plugin? Thanks!
Parichay Barpanda
@baymac

hi @baymac , thank you for your work on this plugin. I have a question: I need to trigger Merge Request(MR) build only when a team member leaves a comment (E.g: /ok-to-test). Can I do this with gitlab-branch-source plugin? Thanks!

Yes you can by adding your custom comment on the mr comment trait. Also note it comes with the feature that ci can only be trigger by a repo maintainer/developer

Christoph Girstenbrei
@Girstenbrei_gitlab
Hey there! Awesome plugin, just switched from the other gitlab plugin to this one (beeing able to automatically create the MB-Projects for a Gitlab-Folder is really cool!). I just ran a few builds and everything works out fine, just have to get used to the small differences:
With the other plugin, Jenkins was notified on a closed MR and ran a pipeline with the info which branch was merged where. Is it possible to get this info with this plugin, too? My use case is to avoid rebuilding artifacts, they get tagged in the feature branches. But once merged, I would like to promote them. But I need to know which build to promote (aka which branch was merged).
PS: webhooks for Push and Merge Events are configured in Gitlab
Luis Fernandes
@zipleen
@baymac do you know that there might be a bug where the setting "enable logging sucessful builds" for the trait "Log build status as comment on GitLab" does not "stick". I enable it, save, and it never gets saved. and the message also never appears. I've tested this with 2 different jenkins installations with the 1.4.3 version of the plugin (I think this worked on previous versions, as I had this working previously)
Günter Kits
@gynter
Hey! I was wondering that if I have selected that Jenkins manages web hooks for Gitlab should Jenkins create web hooks to the project or does it still require manual intervention from me?
Basically to I need to set up a web hook to get Jenkins to scan the project when for example a MR is created in Gitlab?
Günter Kits
@gynter
Never mind :)
Günter Kits
@gynter
Whats the easiest way to test if env variables are seen by Jenkins via Gitlab MR?
Sadly Gitlab doesn't have a re-run successful pipeline button...
Jay Gabriels
@gabrie30
hi all, im using this plugin with jcasc. I've created the credential in jenkins manually, then added the unclassified.gitLabServers.servers referencing the credential. jcasc installs the plugin fine, however after sometime the credential in the plugin goes from being set to being unset...I think it has to do with jcasc "reverting" the credential...has anyone experienced this or have suggestions to prevent this behavior?
Jay Gabriels
@gabrie30
i can confirm its the jcasc plugin, when i manually run "reload configuration" from jcasc the credential is removed
Christoph Girstenbrei
@Girstenbrei_gitlab
:point_up: 10. März 2020 09:21
So I still haven't figured it out, but opened a Stackoverflow: https://stackoverflow.com/questions/60668643/avoid-rebuilding-artifacts-in-jenkins-multibranch-pipelines
Greets, Chris
AlexPol
@ixolt
Hello all, is somebody faced with issue like this?
2020-03-15 20:56:11.220+0000 [id=378] WARNING i.j.p.g.GitLabSCMSource#retrieve: Exception caught:org.gitlab4j.api.GitLabApiException: Cannot cast org.glassfish.jersey.inject.hk2.Hk2InjectionManagerFactory to org.glassfish.jersey.internal.inject.InjectionManagerFactory java.lang.ClassCastException: Cannot cast org.glassfish.jersey.inject.hk2.Hk2InjectionManagerFactory to org.glassfish.jersey.internal.inject.InjectionManagerFactory
Balaji Vijayakumar
@balajiv113
Hi, https://issues.jenkins-ci.org/browse/JENKINS-60530 any updates on this issue ??
Vincent Letarouilly
@Opa-
Hello,
First, thanks a lot for that plugin, it saved me a lot of time :)
Would someone know if there's a way to identify is the current running build is a Merge Request or a Tag (other than using the JOB_NAME prefix) ? Or have the Gitlab project ID ?
I think it would be really a great addition to have kinda the same variables as this plugin https://github.com/jenkinsci/gitlab-plugin#defined-variables made available during the build
Cheers :)
Vincent Letarouilly
@Opa-

We don't have support for 'project id' variable. We have extended branch API plugin to provide the variables for our plugin. Do you think you will be able to do the work with the path of the project instead of project id? You can also fetch project id of project by making an API call inside Jenkinsfile with the path of project (although I am not sure if that is the way to do it). Btw the path of project can be extracted from the URL variable. This are hacks but I think it's time we implement the variables feature to our plugin.

Ok just found this message, I guess it's still not implemented yet then

abogdanov37
@abogdanov37
Hi everyone! Thanks plugin is great! But I have annoying issue. Link is https://issues.jenkins-ci.org/browse/JENKINS-58466. Does anyone know how to resolve it?
Parichay Barpanda
@baymac
Hi @/all, I had been a bit busy with my personal life and couldn’t manage time to contribute to this plugin but perhaps I will start maintaining this plugin actively now. Since a lot of things have happened while I was inactive, it will take a bit of time to organize stuffs and resolve issues. I would like to request users of the plugin to request their urgent bug fixes required for the plugin and I will work on fixing them.
Luis Fernandes
@zipleen
where should we log the issues ? :P
my only one is that "logging trait" does not "save" the option to log successful builds as a comment (it always disables it)
Marky Jackson
@markyjackson-taulia
Parichay Barpanda
@baymac
@zipleen Will look into this
Yes, you can create an jira ticket and post the link here if it is of urgent priority
Luis Fernandes
@zipleen
not urgent, we're managing fine :P
Iaroslav Pleten
@ipleten
@baymac I'd like to bring your attention to https://issues.jenkins-ci.org/browse/JENKINS-59753 We have a pretty big Jenkins installation and this issue hits us each time we redeploy Jenkins.
Parichay Barpanda
@baymac
@ipleten okay, I'll investigate
Vincent Letarouilly
@Opa-

@baymac same as @ipleten about https://issues.jenkins-ci.org/browse/JENKINS-60143 & https://issues.jenkins-ci.org/browse/JENKINS-59753

I also created this one about GitLab info to environment variables https://issues.jenkins-ci.org/browse/JENKINS-61683

thanks :)

Vincent Letarouilly
@Opa-
I'll try to find time to do one of those