Re: Request to be a maintainer for the IvyTrigger Plugin

> On 10. Nov 2017, at 20:16, Bergquist, Brett wrote: > > https://wiki.jenkins.io/display/JENKINS/IvyTrigger+Plugin > > I have privately emails Gregory Boissinot about becoming a maintainer but > have not heard back. Here is what I had sent Gregory > > … > I have

Re: stack trace in configure system (docker, plugin development)

wow, I forgot 'checkout scm' step :D it was using the old workspace from previous version of Jenkinsfile, that was the source of conflict I guess thanks guys for pointing me the workspace as the source of problem, solved! On Friday, November 10, 2017 at 8:32:52 PM UTC+1, Ewelina Wilkosz wrote: >

Request to be a maintainer for the IvyTrigger Plugin

https://wiki.jenkins.io/display/JENKINS/IvyTrigger+Plugin I have privately emails Gregory Boissinot about becoming a maintainer but have not heard back. Here is what I had sent Gregory I am going to be using this plugin and have already figured out how it is mostly designed and working. I

Re: stack trace in configure system (docker, plugin development)

ok, when I build locally I do not get stack trace, something is messed up in my Jenkins job or agent :) On Friday, November 10, 2017 at 8:06:43 PM UTC+1, Ewelina Wilkosz wrote: > > right, it does look like a git merge, the thing is, I can't see any > conflicts in my repo > so it's just me not

Re: stack trace in configure system (docker, plugin development)

right, it does look like a git merge, the thing is, I can't see any conflicts in my repo so it's just me not understanding how docker build works, I guess I will have to dig more into the issue On Friday, November 10, 2017 at 6:27:29 PM UTC+1, Mark Waite wrote: > > That looks like a failed "git

Re: stack trace in configure system (docker, plugin development)

> On 10. Nov 2017, at 17:12, Ewelina Wilkosz wrote: > > And I don't understand where it comes from... Complete newbie here. Anyone > willing to help with troubleshooting? Judging from your Dockerfile, I expect that to already be in the file at

Re: stack trace in configure system (docker, plugin development)

That looks like a failed "git merge". No idea of the source of that failed merge, but those markers are used by git when it can't resolve a merge of a historical file into the current file. Mark Waite On Fri, Nov 10, 2017 at 10:14 AM Ewelina Wilkosz wrote: > I'm working

stack trace in configure system (docker, plugin development)

I'm working on dockerizing Configuration as Code plugin, which means I create a docker image, based on jenkins:2.60.3, I build the plugin and I install it in a Dockerfile: https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile It seems to be working, but I get

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

,.-'"...``~., .,.-"..."-., .,/...":,

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

> On 10. Nov 2017, at 17:54, Daniel Beck wrote: > > this is just spam And the text is just copied and pasted from a quora.com answer from 2011. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

> On 10. Nov 2017, at 16:53, jxpea...@godaddy.com wrote: > > since you asked They didn't, this is just spam. Just check where the 'Jenkins' link leads. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

The Jenkins Users list might be a better place for this question, but since you asked I can tell you what we're doing. I'm not sure what you mean by a Corporate Environment. I work for a medium size corporation, 800ish engineers (I think) and we use Jenkins for everything. We choose to manage

Re: Jenkins Plugin- License Policy

You can find the script in the below repo: - https://github.com/v1v/license-crawler Just to clarify, it takes about 50 minutes (main reason: it looks for license section in the pom.xml file, if it doesn't exit, then it does expand the effective-pom and look for the license section). It does

Backporting for LTS 2.89.1 started

Backporting has started and the RC is scheduled for 2017-11-22. Note that schedule for .2 might be modified as keeping the constant pace would require the RC testing during holidays. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed:

Re: [configuration-as-code] Descriptors configuration

Right, so hopefully we already have docs on best practices for plugin developers ;) An issue remain. Let's consider I refactor Mailer plugin to adopt this approach (see https://github.com/ndeloof/mailer-plugin/commit/ffc57e0ff1cb1b74dc1d6fdcb2329a5b9141daaa), with a new nested optionalProperty