Demos

Hi, Everyone. Those of us at CloudBees working on Jenkins features wanted to show some of the features we have added in the last month (released since just before Jenkins World). We're hosting a session on Youtube Live tomorrow at 7:30 am PDT (2:30 PM UTC). I realize this is short notice but the

Re: Two waiting pull requests - please review or consider granting commit access

Just as a reference I've got write-access to redmine-plugin - the screenshot from chat: -- You received this message because you are subscribed to

Re: Writing a coala Jenkins Plugin

I got the answer. On Monday, October 24, 2016 at 1:56:34 PM UTC+5:30, Ullrich Hafner wrote: > > Well the simplest way would be to write a parser for the warnings plug-in ( > https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin), then you do > not need to write a new plug-in at all. > > If

Re: Writing a coala Jenkins Plugin

URL under the section "Defining a new parser using the user interface" in this page (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin ) i

Re: RFH: Pipeline support for saltstack build plugin

> On 24.10.2016, at 18:58, Christian McHugh wrote: > > - add readResolve compatibility code so existing job configs can be read > successfully > I don't know what this means. Do you have an example? Currently, existing projects will have all the configuration

Re: RFH: Pipeline support for saltstack build plugin

Thanks all! I've been trying to reconcile this version with what I had going in https://github.com/jenkinsci/saltstack-plugin/tree/classing. I'll keep poking at it. At the moment, I'm attempting to discern how to get my dropdown selection to instantiate my class. So if the dropdown displays

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 24 Oct 2016, Jesse Glick wrote: > On Sun, Oct 23, 2016 at 10:52 AM, Alexandru Somai > wrote: > > it uses the GitHub Org plugin > > for this, so when I have the Jenkinsifle in the repository, the project > > should be automatically created in

Re: RFH: Pipeline support for saltstack build plugin

> On 24.10.2016, at 16:04, Jesse Glick wrote: > > You are trying to use low-level controls and making it unnecessarily > hard. KISS and use `f:dropdownDescriptorSelector`. Also see > `ui-samples-plugin` for examples of doing things the straightforward > way. Well, I

Plugin PR Feedback

I recently submitted a pull request for the credentials binding plugin: https://github.com/jenkinsci/credentials-binding-plugin/pull/27 would appreciate any feedback :) Thanks, -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: RFH: Pipeline support for saltstack build plugin

On Sun, Oct 23, 2016 at 5:17 PM, Daniel Beck wrote: > https://github.com/daniel-beck/saltstack-plugin/commits/refactor I.e., https://github.com/daniel-beck/saltstack-plugin/compare/master...refactor though filing a WiP PR is the best way to solicit line-by-line feedback (for

Re: Writing a coala Jenkins Plugin

Hi, thanks. That looks like what I've been looking for. Hacking together a parser for the warnings module shouldn't be too hard, probably best we simply use JSON. Sincerely, Lasse Schuirmann la...@schuirmann.net http://coala.io/ - http://viperdev.io/ - http://gitmate.com/ On 24 October 2016

Re: Writing a coala Jenkins Plugin

Well the simplest way would be to write a parser for the warnings plug-in (https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin ), then you do not need to write a new plug-in at all. If this is not sufficient for you (e.g. you

Re: Writing a coala Jenkins Plugin

Hi I'm not from cloudbees. But I think that you are looking for something like: https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins Br, Alex On Sunday, 23 October 2016 23:47:16 UTC+2, Lasse Schuirmann wrote: > > Hi, > > a lot of coala users have asked us to provide a

Re: Plugin to add a custom build step.

Hi, I am willing to put three windows batch command option (one in each optionalblock segment) in custom build step which I have developed. Please find my config,jelly and java code below. What changes I need to done to achieve the same. JAVA File import

Re: Plugin to add a custom build step.

Thanks for suggestions. I am able to build a custom build step now successfully. Final code looks like this. JAVA File import org.kohsuke.stapler.DataBoundConstructor; import org.kohsuke.stapler.QueryParameter; import hudson.Extension; import hudson.model.AbstractProject; import