Re: Maintainer request Gitlab Plugin

I will add you as a committer ASAP. Given that we now have a couple of people jointly maintaining the plugin, I suggest that we limit the use of direct commits to updating documentation. For code changes, please continue to use PRs, so we can have some code review. Thanks and welcome aboard! On

Re: Maintainer request Gitlab Plugin

Hi, I have been using this plugin quite extensively, especially with the new pipeline syntax. Submitted a pull request yesterday to support the new syntax #488. There's more to do though and I want to add a few more examples to the readme and pipeline based tests. If I can have commit access I

Re: Maintainer request Gitlab Plugin

Closing the PR and reopening it is usually enough to tickle the PR trigger. /B On Tue, Jan 17, 2017 at 9:53 PM, Posa Bogdan wrote: > Hello, > > I know that instance is only for CI checks. > I am asking to see how to job in configured in general. > > The real problem is

Re: Maintainer request Gitlab Plugin

Hello, I know that instance is only for CI checks. I am asking to see how to job in configured in general. The real problem is that I don't know how to re-trigger a build for a PR. For example this MR (https://github.com/jenkinsci/gitlab-plugin/pull/431) have an yellow flag and I want to see

Re: Maintainer request Gitlab Plugin

That instance does not build the plugin for release, it just runs the tests for visibility on Pull Requests. When releasing, I have always just run that locally, following the instructions here: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org

Re: Maintainer request Gitlab Plugin

Hello, Thanks for accepting me. How can I have access to the Jenkins instance which builds the plugin https://jenkins.ci.cloudbees.com/job/plugins/job/gitlab-plugin/ ? joi, 5 ianuarie 2017, 00:15:28 UTC+2, Owen B. Mehegan a scris: > > Thanks for your interest! I have given you commit access.

Re: Maintainer request Gitlab Plugin

Thanks for your interest! I have given you commit access. Please use it carefully :) Our practice thus far has been to make minor bugfix changes directly to master, but any more significant feature work in branches with a PR for discussion before merging. I have just caught up on a lot of the

Maintainer request Gitlab Plugin

Hello, I want to become a maintainer of GitLab plugin -> https://wiki.jenkins-ci.org/display/JENKINS/GitLab+Plugin GitHub ID: trance1st Jenkins ID: posabogdan Kind regards, Bogdan Posa -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.