Re: Seeking new lead maintainer for the GitLab plugin

We've had a few volunteers, but more would be welcome! Right now there are several open PRs which could use a review and +1, and a number of open issues as well. Some are marked as known bugs or feature requests, which anyone would be welcome to work on, and a few other unmarked ones need more inve

Re: Seeking new lead maintainer for the GitLab plugin

I would love to help you out! contact me if you're interested Le mardi 13 décembre 2016 19:45:00 UTC, Owen B. Mehegan a écrit : > > We are seeking new maintainers for the GitLab plugin! The existing > codebase is clean and well-tested thanks to a lot of hard work done by > Robin, the former lead

Re: Commit rights to cobertura-plugin

On 2017-03-27 09:44, Oleg Nenashev wrote: +1 for adding Michael and Steven Please guys go for it. The plugin was unmaintained for too long. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and s

Re: I'd like to adopt the logstash plugin

Thanks, I have write perms on GitHub now On Mar 26, 2017 3:36 AM, "Daniel Beck" wrote: > > > On 23.03.2017, at 17:12, Jakub Bocheński > wrote: > > > > I still have no write access there though. > > Should be resolved now. > > -- > You received this message because you are subscribed to a topic

Re: Plugin Pipeline Environment Variables

So I extended Step, and was able to get my run() method to print out text in a pipeline project. However, my plugin no longer appears in a Freestyle project under Build Steps because I am not extending Builder nor implementing SimpleBuildStep anymore. Do you think that I can have this plugin wo

Re: Plugin Pipeline Environment Variables

Thanks Daniel, I will take a crack at it! On Monday, March 27, 2017 at 9:50:59 AM UTC-4, Daniel Beck wrote: > > > > On 27.03.2017, at 15:47, David Brooks > > wrote: > > > > However, I do not see any documentation around Step and BuildStep has > been deprecated. I just need a little nudge in th

Re: Plugin enforce Java7

It makes sense change to Java8 but I plan to resolve some issues before and release one last release with Java7. Thanks. On Mon, Mar 27, 2017 at 10:20 AM Oleg Nenashev wrote: > Yes, the default restrictions define the minimal version. If you need the > plugin to compile on Java 7 only, you wou

Plugin Pipeline Environment Variables

Hey all, I have been working on an internal plugin for our company and currently having it working for Freestyle projects. However, I would like to update it to support Pipelines and have a question about Environment Variables. I implemented SimpleBuildStep, but according to a fellow dev (here

Re: Plugin Pipeline Environment Variables

> On 27.03.2017, at 15:47, David Brooks wrote: > > However, I do not see any documentation around Step and BuildStep has been > deprecated. I just need a little nudge in the right direction, not the full > solution. I think https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/RE

Re: Plugin enforce Java7

Yes, the default restrictions define the minimal version. If you need the plugin to compile on Java 7 only, you would have to define the enforcer rules explicitly. BTW, it definitely makes sense to fix the Java 8 build flow then. Jenkins is going to deprecate Java 7 soon, and it may become an issue

Re: Plugin enforce Java7

This property also exists in the version I'm using '1.609.3' I tried with '1.625' but the same happens it doesn't valid the jdk version and it would allow compile with jdk 8. On Mon, Mar 27, 2017 at 4:41 AM Oleg Nenashev wrote: > Maybe you also want to upgrade Jenkins core to 1.625+. > In such

Re: Ownership plugin - automatically assigning ownership in multibranch projects

Hi Oleg, Thanks for the reply. Of course, I wouldn't want any change I might introduce to change the current behavior or state of ownership on any item. Since you do not see the action for branches in Multi-Branch Pipeline, it > likely means that the TransientActionFactory extension point is n

Re: Repository access nodejs-plugin

> On 27.03.2017, at 12:56, Nikolas Falco wrote: > > my user name for jenkins JIRA is nfalco, I will appreciate a lot your help > for default assignee of NodeJS component becuase since now I have to look up > every day for new issues Done. -- You received this message because you are subscri

Re: Repository access nodejs-plugin

my user name for jenkins JIRA is nfalco, I will appreciate a lot your help for default assignee of NodeJS component becuase since now I have to look up every day for new issues Il giorno martedì 22 novembre 2016 15:18:44 UTC+1, Daniel Beck ha scritto: > > > > On 22.11.2016, at 12:29, 'Nikolas Fa

Re: Cached Wiki Page

Add ?nocache (or similar) to the end of the URL, and you'll see that the the page was removed. However, it somehow remains in the cache, which is a known issue: https://issues.jenkins-ci.org/browse/INFRA-301 On Mon, 27 Mar 2017, at 10:24, Oleg Nenashev wrote: > Added the Jenkins Infra team to Cc

Re: Naming convention for sprints in Jira

Which project in JIRA do you mean? I do not recall such statuses in the JENKINS project. If you mean labels, than it is a separate story. среда, 15 марта 2017 г., 22:03:51 UTC+1 пользователь Kanstantsin Shautsou написал: > > Triangle and etc, or it finally removed? > > On Wednesday, March 15, 20

Re: Cached Wiki Page

Added the Jenkins Infra team to Cc. Something weird is going on, because Official+OWASP+Zed+Attack+Proxy+Jenkins+Plugin is not a full mirror of the page though "Page History" shows the same page history. I would assume that it is a kind of the splitbrain caused by one of the Confluence outages,

Re: How to grab full map of EnvVars in pipeline?

Thank you, Oleg. On Mon, Mar 27, 2017 at 11:19 AM, Oleg Nenashev wrote: > Just in case some of the 50 variables get contributed by EnvInject's Job > and Node properties, keep in mind the plugin is not fully integrated with > Pipeline (JENKINS-42614 >

Re: How to grab full map of EnvVars in pipeline?

Just in case some of the 50 variables get contributed by EnvInject's Job and Node properties, keep in mind the plugin is not fully integrated with Pipeline (JENKINS-42614 ), so the variables may be missing independently of the call approach you

Re: Ownership plugin - automatically assigning ownership in multibranch projects

Hello Jordan, // Added Jesse to Cc As an Ownership plugin maintainer, I feel quite biased regarding this feature. Though is seems to be a useful addition to the plugin functionality, the plugin has been mostly created to empower the Ownership-based security strategy (including integrations with

Re: Commit rights to cobertura-plugin

+1 for adding Michael and Steven пятница, 24 марта 2017 г., 23:55:28 UTC+1 пользователь Daniel Beck написал: > > > > On 24.03.2017, at 22:18, Steve Christou > wrote: > > > > Would anyone else object to me taking ownership of the cobertura plugin > also? I am currently the core maintainer of c

Re: Plugin enforce Java7

Maybe you also want to upgrade Jenkins core to 1.625+. In such case you will be able to just remove the enforcer property and to use the `java.level=7` property in the POM specification суббота, 25 марта 2017 г., 0:36:39 UTC+1 пользователь Janario Oliveira написал: > > Thanks :) > > > On Fri, Ma

Re: I'd like to adopt the logstash plugin

It would be great to see this plugin moving forward. Thanks a lot for taking ownership! Best regards, Oleg Nenashev воскресенье, 26 марта 2017 г., 3:36:56 UTC+2 пользователь Daniel Beck написал: > > > > On 23.03.2017, at 17:12, Jakub Bocheński > wrote: > > > > I still have no write access t

Re: Do plugins do anything to support Jenkins agents?

Thanks for doing it. When I was trying the plugin, it also was a serious issue in my case. I have added several comments to the pull-request. Best regards, Oleg воскресенье, 26 марта 2017 г., 11:49:07 UTC+2 пользователь Christian McHugh написал: > > That was helpful to get started. Based on tha

Re: Integrate EsLint wint Jenkins

Hi Raul. Can you elaborate on what you mean by "integrate with the Jenkins tool" please? You might be talking about writing a Jenkins plugin specific to eslint, or just wanting to know how to run it in a maven build env. On 25 March 2017 at 22:07, Baptiste Mathus wrote: > I know close to nothing