TODO-Plugin guidance

Hello, I could be living in the past, but I am trying to get the old `mvn hpi:...` to work and it seems it has changed. I found a page saying we should use this method here: mvn archetype:generate -B -DarchetypeGroupId=io.jenkins.archetypes -DarchetypeArtifactId=hello-world-plugin

Re: Heads up! Jenkins is on YouTube, with more videos coming soon!

This is great, thanks for doing this! On Tue, Apr 10, 2018 at 7:01 PM R. Tyler Croy wrote: > > The Jenkins project has been on YouTube for a while, but I recently > transitioned our channel to a "Brand Account", which means we can share > permissions to post videos _much_

Heads up! Jenkins is on YouTube, with more videos coming soon!

The Jenkins project has been on YouTube for a while, but I recently transitioned our channel to a "Brand Account", which means we can share permissions to post videos _much_ more easily: https://www.youtube.com/c/jenkinscicd I am hoping that we can share access, not only for the Jenkins

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

(replies inline) On Thu, 22 Mar 2018, R. Tyler Croy wrote: > > I have been looking at some of the great things the Kubernetes community has > been doing for ideas we can borrow, and one idea which really sticks out is: > Special Interest Groups (SIGs) >

Re: Need help designing a fix for JENKINS-50504

I meant "Thanks for pointing out JENKINS-41854" below. On Tuesday, April 10, 2018 at 5:42:20 PM UTC-7, m...@basilcrow.com wrote: > > Thanks for pointing out JENKINS-45294. That is exactly what I am facing, > at least twice a month. It causes severe disruption to my users, so I need > to come up

Re: Need help designing a fix for JENKINS-50504

Thanks for pointing out JENKINS-45294. That is exactly what I am facing, at least twice a month. It causes severe disruption to my users, so I need to come up with a plan. I see that the bug is unassigned. If it isn't fixed soon, I might have to try to fix it myself by necessity. I suppose the

Re: [Essentials] Instance Health Checking JEP: ready for first review

Jesse, Thanks for the reminder about that point around commenting. As an editor, I have no objections to having pre-draft discussions in whatever way contributors see fit. As a sponsor of JEP-1, it is important to me that when a sponsor submits a JEP for "Approval as Draft", that feedback they

Re: jep-200 issue

Why are you skipping the enforcer? On Tue, Apr 10, 2018 at 8:30 AM Eugen Horovitz < eugen.horov...@whitesourcesoftware.com> wrote: > Hi Jesse , > > I did all the changes and still got the same errors.. > I am probably still missing some important stuff... I am newbie in > jenkins plugin

Re: jep-200 issue

Hi Jesse , I did all the changes and still got the same errors.. I am probably still missing some important stuff... I am newbie in jenkins plugin development and I will be greatfull if you can have a look. https://gist.github.com/eugenhoro/f73f4d666c64ea809e6a6711a0e40ed3 maven fails to build

Re: [Essentials] Instance Health Checking JEP: ready for first review

On Tue, Apr 10, 2018 at 10:33 AM, R. Tyler Croy wrote: > Do you have some reasoning for this you could share? Merely that “nothing in particular is broken” is not news, so there is not much a client needs to know. -- You received this message because you are subscribed to

Re: [Essentials] Instance Health Checking JEP: ready for first review

(replies inline) On Tue, 10 Apr 2018, Jesse Glick wrote: > I for one would find it easier to comment on a PR, but IIRC JEP > editors have discouraged this for some reason > > > ???Healthness??? is not a word???it is just ???health???. > > > I would suggest

Re: [Essentials] Instance Health Checking JEP: ready for first review

I for one would find it easier to comment on a PR, but IIRC JEP editors have discouraged this for some reason…? “Healthness” is not a word—it is just “health”. I would suggest `/metrics/evergreen/healthcheck` just return an empty JSON document, or a simple “OK” marker by default—only listing

Re: Startup deadlock when using a GlobalConfiguration + Initializer < JOB_LOADED

While changing the initializer settings may have happened to solve the issue in this case, the advice is not generally applicable. Use JENKINS-50663 for discussion. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

Re: jep-200 issue

On Tue, Apr 10, 2018 at 2:25 AM, Eugen Horovitz wrote: > Could not resolve dependencies for project > org.jenkins-ci.plugins:whitesource:hpi:18.2.1-SNAPSHOT: > Failure to find org.jenkins-ci.main:jenkins-war:executable-war:2.102 in >

validating-string-parameter-plugin PR's

Based on the comments to a PR I created to fix the build of the validating-string-parameter-plugin, it looks like there is no maintainer [1]. I would like to take temporary maintainership to get some of the PR's merged and get the plugin into a better state. The only person in the repository

Re: [Essentials] Instance Health Checking JEP: ready for first review

Sorry, the right link is https://github.com/batmat/jep/tree/JENKINS-50294/jep/ 2018-04-10 14:09 GMT+02:00 Baptiste Mathus : > Hello everyone, > > Just published the draft of the JEP for the "Essentials Instance Client > Health Checking", it is ready for, and warmly

[Essentials] Instance Health Checking JEP: ready for first review

Hello everyone, Just published the draft of the JEP for the "Essentials Instance Client Health Checking", it is ready for, and warmly welcoming, review: https://github.com/batmat/jep/blob/JENKINS-50294/README.adoc To sum up, this will be the *component* used to decide if we trigger a rollback

Re: Startup deadlock when using a GlobalConfiguration + Initializer < JOB_LOADED

AIUI, interesting to read and related: https://www.cloudbees.com/blog/jenkins-plugin-developer-case-files-episode-1-when-extensions-bites-you-posterior 2018-04-10 12:26 GMT+02:00 Julien HENRY : > My point was to clarify the specific case of GlobalConfiguration. I'm

Re: Startup deadlock when using a GlobalConfiguration + Initializer < JOB_LOADED

> On 10. Apr 2018, at 10:39, Julien HENRY wrote: > > Could it be possible to improve the situation, by at least completing the > Javadoc, or maybe detecting and failing fast when a GlobalConfiguration tries > to use an Initializer earlier than JOB_LOADED ? > It

Startup deadlock when using a GlobalConfiguration + Initializer < JOB_LOADED

Hi, Our plugin uses a GlobalConfiguration extension, and to migrate old data, we added an Initializer. Following the javadoc of Initializer, I set

Re: Request to become maintainer of the statistics-gatherer-plugin

2 weeks sound good to me, and yes, I always avoid forks :-) Luca. > On 10 Apr 2018, at 08:02, Joseph P wrote: > > Usually the wait period is 2 weeks :) I would not recommend creating another > plugin. > > -- > You received this message because you are subscribed to the

Re: Request to become maintainer of the statistics-gatherer-plugin

Usually the wait period is 2 weeks :) I would not recommend creating another plugin. -- 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

Re: Request to become maintainer of the statistics-gatherer-plugin

> On 10. Apr 2018, at 08:45, Luca Milanesio wrote: > > What is the wait time for getting this escalated and giving the possibility > to fix bugs on the plugin? > Alternatively, should I just submit a brand-new plugin proposal? (which could > cause confusion: people

Re: Request to become maintainer of the statistics-gatherer-plugin

PIng ... any feedback from the current maintainer? What is the wait time for getting this escalated and giving the possibility to fix bugs on the plugin? Alternatively, should I just submit a brand-new plugin proposal? (which could cause confusion: people may not know which one is "active")

Re: jep-200 issue

Hi Jesse, Thanks a lot for your reply . now getting different error : Could not resolve dependencies for project org.jenkins-ci.plugins:whitesource:hpi:18.2.1-SNAPSHOT: Failure to find org.jenkins-ci.main:jenkins-war:executable-war:2.102 in https://repo.jenkins-ci.org/public/ was cached in the