New Gitlab Jenkins Plugin

[Daniel Brooks]

Hi,

I have a new Gitlab Jenkins plugin currently on GitHub here: https://github.com/DABSquared/gitlab-jenkins-plugin. My GitHub id is bassrock and would like to host it on Jenkins.

Thanks!

Daniel

[domi]

how does this plugin compare to the existing gitlab plugin? https://wiki.jenkins-ci.org/display/JENKINS/Gitlab+Hook+Plugin

/Domi

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniel Brooks]

This plugin emulates Jenkins to act like Gitlab CI to Gitlab. This allows those using GitLab CE to use Jenkins normally faked as GitLab CI. This plugin also doesn't use a single web hook which triggers a polling of the repo. It is also coded in Java instead of Ruby.

[Slide]

This looks great, I'll give it a shot when its released.

[Daniel Brooks]

Thanks! It definitely has some things I would like to change, like having to enter the merge info with a targetBranch and sourceBranch as a build parameter. But i think it's good for a V1.0!

[Sandell, Robert]

This looks interesting, we recently made two GitLab plugins (not released yet), one that lets you authenticate users towards GitLab and have the GitLab roles in Jenkins; one folder per group and users retain the roles they have in that group.

It would be cool if we can make these play well together.

The other plugin [1] is an API plugin, so if your plugin needs to talk to GitLab over the rest api, feel free to contribute to that.

 

[1] https://github.com/jenkinsci/gitlab-api-plugin

[2] https://github.com/jenkinsci/gitlab-auth-plugin

 

 

Robert Sandell

Software Tools Engineer - SW Environment and Product Configuration

Sony Mobile Communications

[Daniel Brooks]

Robert,

Very interesting, I'm not sure what I could use the API for yet in my plugin. But I am open to any thoughts! Those look good. Feel free to contribute to mine as well!

[Daniel Brooks]

All I tried to deploy it to Jenkins Plugin Hosting but for some reason it is not showing up. If anyone knows how or can help please let me know!

[Slide]

It can take several hours for it to show up in the update center and what not. I've seen it take as much as 12 hours sometimes.

--

You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Website: http://earl-of-code.com

[Daniel Brooks]

I deployed it probably a day or two ago which is why I think I did something wrong.

You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/iLjGgSv26l0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.

[Daniel Beck]

You only released snapshots, see http://repo.jenkins-ci.org/simple/snapshots/com/dabsquared/

Likely the first item here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

[Daniel Brooks]

I feel like I am missing something. I see I released the snapshots. I followed the guide there and had no errors. What item are you referring to on the troubleshooting issues?

Thanks!

[Slide]

Can you give the steps you took?

[Daniel Brooks]

Ok:

1) Added my jenkins credentials to ~/.m2/settings.xml

2) Made sure my origin is pointed to MY plugin repo, not jenkinsci on GitHub

3) Ran: mvn release:prepare release:perform

3) Accepted the prompts with he defaults

Is that correct what I did?

Thanks!

[Eddard Oberyn]

Hello Daniel

i just recently discovered your plugin, i launched a POC recently to demo this to my peers, the next step is to be able to convince those who call the shots at work,

i am still trying to understand what this plugin really does? To be more precise what do you mean when you say "This allows those using GitLab CE to use Jenkins normally faked as GitLab CI."

Does that mean it makes gitlab think it is a gitlab-ci runner? Does that mean i can use a gitlab-ci.yml file to describe the entire build job, instead of configuring it throug the jenkins interface?

As i need to justify this to my n+1, i am pretty sure i will get the question, why not just use gitlab-ci instead of this plugin and faking it?

Best regards