Re: Approval to use the Jenkins logo

[Christopher Orr]

Hi there,

On Tue, 21 Apr 2020, at 13:30, Jenny Li Kam Wa wrote:
> I am the Development manager for IBM Netcool Agile Service Manager 
> (ASM) which is part of the Netcool product family. I need to seek 
> approval to include the Jenkins logo in the ASM configuration panel 
> which looks like this: 
> 
> So we essentially have a tile based configuration UI where each tile 
> enables you to configure a specific integration with a third party 
> product. The third party product logo is used to decorate the tile as 
> depicted in the above image. 
> 
> For Jenkins, we will use one of the logos available from 
> _https://jenkins.io/artwork/_ : 
> 
> Can you put me in touch with the appropriate person/contact who can 
> grant me approval to use the Jenkins logo in this way? 

Everybody should be able to use the Jenkins logo without prior approval, given 
the attribution requirements mentioned on the artwork page you mentioned — the 
logos are distributed under a Creative Commons licence.

I've also copied the Jenkins Developers' mailing list; someone there can maybe 
give you a more comprehensive answer, or you can ask ask about other terms, if 
need be.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8ec4efbf-9fe8-4acd-818b-5fef782cf3e6%40www.fastmail.com.

Re: Adoption of android-emulator-plugin

[Christopher Orr]

Yup


On Sat, 11 Apr 2020, at 14:00, Oleg Nenashev wrote:
> Thanks for the quick response!
> 
> > So yeah, a good time for somebody who has more interest in the future of 
> > the plugin to take charge Let me know if I can help with anything.
> 
>  If I interpret it correctly granting permissions to Nikolas is approved, 
> right?
> 
> On Sat, Apr 11, 2020 at 12:13 PM Christopher Orr  wrote:
> > Hi there,
> > 
> >  On Sat, 11 Apr 2020, at 00:46, Oleg Nenashev wrote:
> >  > Thanks for your interest! I will ping Chris to get his response.
> >  > Let's also start counting the 2-week response timeout from today.
> >  > 
> >  > 
> >  > On Thursday, April 9, 2020 at 10:38:41 AM UTC+2, Nikolas Falco wrote:
> >  > > Hi, I would adopt the android emulator plugin 
> > https://github.com/jenkinsci/android-emulator-plugin/
> >  > > 
> >  > > That plugin is not marked for adoption but seem fall in abandoned 
> > case. Last commit is on Dicember 2017, there are valid PRs that have no 
> > response and a long list of issues on JIRA without response.
> > 
> >  Yeah, I've definitely not been around this plugin for a long time — but I 
> > also always had very little feedback from users, so I was never sure 
> > whether it was just working fine, or whether nobody was using it… :)
> > 
> >  Anyway, I see that it's really falling apart at the moment with some 
> > changes in the Android SDK Tools, and there are a bunch of Jira issues I 
> > hadn't even seen before (explicit support for headless emulators added last 
> > year!), so it's definitely in need of attention.
> > 
> >  I also just noticed that I made the first release of this plugin almost 
> > exactly ten years ago! So yeah, a good time for somebody who has more 
> > interest in the future of the plugin to take charge.
> > 
> >  Let me know if I can help with anything. I have a bunch of notes (for 
> > Pipeline support, as also mentioned in JENKINS-33156), and I think for 
> > various ADB, snapshot, and emulator tricks that I'd picked up, but not 
> > implemented.
> > 
> >  Thanks,
> >  Chris
> > 
> >  -- 
> >  You received this message because you are subscribed to a topic in the 
> > Google Groups "Jenkins Developers" group.
> >  To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/jenkinsci-dev/Vfl7Jm3ZerI/unsubscribe.
> >  To unsubscribe from this group and all its topics, send an email to 
> > jenkinsci-dev+unsubscr...@googlegroups.com 
> > <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
> >  To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/jenkinsci-dev/1fd1cc9d-8b59-4492-ac30-5764de8b4644%40www.fastmail.com.
> 
>  -- 
>  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 jenkinsci-dev+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDwezyXK4b9zGdE6WvVHoJ5BiWHVKsqWtJgJsMx9Z4eQw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDwezyXK4b9zGdE6WvVHoJ5BiWHVKsqWtJgJsMx9Z4eQw%40mail.gmail.com?utm_medium=email_source=footer>.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2c2ada6f-043f-438c-be1a-15b143d41e29%40www.fastmail.com.

Re: Adoption of android-emulator-plugin

[Christopher Orr]

Hi there,

On Sat, 11 Apr 2020, at 00:46, Oleg Nenashev wrote:
> Thanks for your interest! I will ping Chris to get his response.
> Let's also start counting the 2-week response timeout from today.
> 
> 
> On Thursday, April 9, 2020 at 10:38:41 AM UTC+2, Nikolas Falco wrote:
> > Hi, I would adopt the android emulator plugin 
> > https://github.com/jenkinsci/android-emulator-plugin/
> > 
> > That plugin is not marked for adoption but seem fall in abandoned case. 
> > Last commit is on Dicember 2017, there are valid PRs that have no response 
> > and a long list of issues on JIRA without response.

Yeah, I've definitely not been around this plugin for a long time — but I also 
always had very little feedback from users, so I was never sure whether it was 
just working fine, or whether nobody was using it… :)

Anyway, I see that it's really falling apart at the moment with some changes in 
the Android SDK Tools, and there are a bunch of Jira issues I hadn't even seen 
before (explicit support for headless emulators added last year!), so it's 
definitely in need of attention.

I also just noticed that I made the first release of this plugin almost exactly 
ten years ago!  So yeah, a good time for somebody who has more interest in the 
future of the plugin to take charge.

Let me know if I can help with anything.  I have a bunch of notes (for Pipeline 
support, as also mentioned in JENKINS-33156), and I think for various ADB, 
snapshot, and emulator tricks that I'd picked up, but not implemented.

Thanks,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1fd1cc9d-8b59-4492-ac30-5764de8b4644%40www.fastmail.com.

Re: Validate Jenkinsfile while using oauth

[Christopher Orr]

FWIW, I had no problems setting it up with an API token last week (in place of 
a password), on a Jenkins instance that uses the Google Login plugin for 
authentication.


On Mon, 19 Nov 2018, at 13:29, domi wrote:
> Unfortunately this does not seem to work :(
> 
> > On 16 Nov 2018, at 20:18, Jesse Glick  wrote:
> > 
> > On Fri, Nov 16, 2018 at 8:12 AM domi  wrote:
> >> I really like the way I can validate my Jenkinsfile from within VS Code 
> >> now: https://jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/
> >> 
> >> But how can I do this when I use any of the Oauth-Plugins like the one for 
> >> Github[1] or Bitbucket [2]?
> > 
> > I presume that `jenkins.pipeline.linter.connector.pass` could be an
> > API token rather than a password. In fact, it really should be, even
> > if you are using a password-based security realm. Probably this is
> > just a matter of fixing the documentation to clarify that.
> > 
> > -- 
> > 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3xpZPi6qU%2BaEg37Ov7Bxn7GLAP29tdc7S1_d4SCAr-jw%40mail.gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1FB72438-6AB1-4EAD-AFBF-9540101F6424%40fortysix.ch.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1542659752.819570.1582362288.7C8253F4%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request temporary release permission for JUnit Attachments

[Christopher Orr]

Sure, go for it!


On Fri, 16 Feb 2018, at 15:28, Jesse Glick wrote:
> https://wiki.jenkins.io/display/JENKINS/JUnit+Attachments+Plugin
> 
> Andrew Bayer seems to have been the last to cut a release
> 
> https://github.com/jenkinsci/junit-attachments-plugin/commits
> 
> but denies any knowledge of this. Chris Orr says he is not an active
> maintainer. The other listed maintainer Tom Huybrechts who I believe
> is not active in Jenkins at all, and there was no other activity since
> 2012.
> 
> I am loath to become any kind of permanent maintainer but at least
> 
> https://github.com/jenkinsci/junit-attachments-plugin/pull/16
> https://github.com/jenkinsci/junit-attachments-plugin/pull/19
> 
> seem like safe fixes. The Jenkins core dev team does use this plugin a bit:
> 
> https://github.com/jenkinsci/acceptance-test-harness/blob/11d3549363207b71ce2a231b7df551162788261a/Jenkinsfile#L20
> 
> I have physical access to the repository, just making sure I am not
> stepping on any toes.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1518791378.833919.1273131768.4E2B7B77%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Replay pipeline from any predefined checkpoint(s). One Plugin to Rule them all.

[Christopher Orr]

On Fri, 29 Sep 2017, at 21:41, xuehao.hu wrote:
> Jenkins Enterprise already has an checkpoint
> plugin, that does exact thing, but open-sourced Jenkins is lack of this 
> essential plugin, so I recently started working this. (
> https://github.com/1TB/state-replay/blob/master/README.md), but it is
> a WIP, and still need to figure out many things to have a working thing. So 
> posting here to see if there is any folks also interested in doing this.

You will likely find interested people on the JIRA issue related to this
topic:
https://issues.jenkins-ci.org/browse/JENKINS-33846

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1506716658.3314150.1122898904.41C7CC71%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Topic: No such DSL method 'waitForQualityGate' found among steps

[Christopher Orr]

If it wasn't a Jenkins developer question, i.e. it should have been
posted on the users' mailing list, your original mail was likely
rejected.


On Wed, 30 Aug 2017, at 02:19, Michal Propílek wrote:
> Hi,
> I want to ask you when I can expected my topic "No such DSL method
> 'waitForQualityGate' found among steps" in group Jenkins Developers. I
> posted it one week ago and I haven't any status of it.
> 
> Thank you
> Michal Propílek
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAB-9pB%2BiW_zwq5roFy5s_eYRx_V9iMxk83%3D2%2BatC%3Did_Vyotqw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1504090043.1599571.1089652064.5B7BB645%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Request to join Jenkins Security Team

[Christopher Orr]

Hi there,

I'd like to request to join the security team.
I've got all the prerequisites listed (2FA, CLA, nickname on IRC).

Thanks,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1503941343.3112205.1087569072.66BA5581%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Overriding Jenkins version of parent POM

[Christopher Orr]

Sounds good to me, thanks — I'll submit a POM PR.


On Wed, 23 Aug 2017, at 23:43, Ullrich Hafner wrote:
> I’m already planning to base the next 2.0 release on a 2.x POM. Since
> this requires still some time, you can try to create a new analysis-pom
> PR on your own that uses a newer version and then base your plugin on
> that version. We can have several analysis-pom versions without problems.
> Or do you need a new analysis-core release?
> 
> Ulli
> 
> > Am 21.08.2017 um 19:19 schrieb Oleg Nenashev :
> > 
> > Hi Cristopher,
> > 
> > Added Ullrich to CC.
> > IMHO the best way is to update the Analysis POM to Parent POM 2.x. Once 
> > somebody does that, it will be possible to specify custom core baselines in 
> > child POMs. It also brings in improvements in dependency checks, static 
> > analysis, etc.
> > 
> > BR, Oleg
> > 
> > понедельник, 21 августа 2017 г., 18:52:57 UTC+2 пользователь Christopher 
> > написал:
> > Hi all,
> > 
> > The android-lint plugin is based on analysis-core, and is using
> > analysis-pom as its parent. That has an older version of the Jenkins
> > plugin as its parent and with it a (fairly understandably) conservative
> > minimum Jenkins baseline version.
> > 
> > However, I'd quite like to give my plugin a somewhat newer Jenkins
> > baseline, at least for testing, but likely also for release.
> > 
> > Is it possible to achieve this with Maven, or would analysis-pom need to
> > upgrade to the newer Jenkins plugin parent, which would (possibly?)
> > allow me to override the `jenkins.version`property in my POM?
> > 
> > Thanks,
> > Chris
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/B39330B3-DC4B-45C6-9215-582E8C26F1E1%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1503571432.82732.1083521080.4BF9C0A5%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Overriding Jenkins version of parent POM

[Christopher Orr]

Hi all, 

The android-lint plugin is based on analysis-core, and is using
analysis-pom as its parent. That has an older version of the Jenkins
plugin as its parent and with it a (fairly understandably) conservative
minimum Jenkins baseline version.

However, I'd quite like to give my plugin a somewhat newer Jenkins
baseline, at least for testing, but likely also for release.

Is it possible to achieve this with Maven, or would analysis-pom need to
upgrade to the newer Jenkins plugin parent, which would (possibly?)
allow me to override the `jenkins.version`property in my POM?

Thanks,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1503334357.2080574.1080260768.327B8DEC%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to map a container port to host port with kubernetes plugin.

[Christopher Orr]

On Thu, 8 Jun 2017, at 10:41, 李立 wrote:
> I want to map the container port to a host port with kubernetes plugin, but 
> I cann't find mapping port from kubernetes plugin. How should I do?

You're posting to the wrong mailing list:
https://jenkins.io/mailing-lists/

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1496919383.1109119.1002788184.4BBFFB78%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Job Configuration Code Questions

[Christopher Orr]

Javadoc: https://www.google.com/search?q=jenkins+buildwrapper

Implementations:
https://github.com/search?l=Java=user%3Ajenkinsci+buildwrapper=Code


On Fri, 5 May 2017, at 18:58, JordanGS wrote:
> The link to the javadoc 
>  is 
> also dead
> 
> and just like in the previous post for which you already have a ticket
> open according to danielbeck, you have
> 
> Unknown macro: {@code static}.
> 
> I don't know any plugin that uses a BuildWrapper, that's why i asked. I 
> don't mind getting familiar with one. Just need a starting place.
> 
> On Friday, May 5, 2017 at 12:14:58 PM UTC-4, Robert Sandell wrote:
> >
> > There are plenty of examples beneeth the "Implementations" tap on the 
> > Extension Points page on the wiki
> >
> > https://wiki.jenkins-ci.org/display/JENKINS/Extension+points#Extensionpoints-hudson.tasks.BuildWrapper
> > Pick a plugin that you are somewhat familiar with to start.
> >
> > On Fri, May 5, 2017 at 4:44 PM, Goran Dev  > > wrote:
> >
> >> Can you give me an example of a BuildWrapper please? Not familiar with it.
> >>
> >> Cheers, Goran.
> >>
> >> On May 5, 2017, 4:48 AM -0400, Robert Sandell  >> >, wrote:
> >>
> >> Answers inline 
> >>
> >>
> >> On Fri, May 5, 2017 at 9:09 AM, Goran Dev  >> > wrote:
> >>
> >>> I'm writing a plugin, it's already released as zap-plugin. 
> >>> GitHub.com/jenkinsci/zap-plugin
> >>>
> >>> On jenkins LTS, in a Job Configuration you have various tabs (sections) 
> >>> such as General, Source Code Management, Build Triggers, Build 
> >>> Environment, 
> >>> Bindings, Build, Post-build Actions.
> >>>
> >>> 1) is it possible for me to add a tab/section called "ZAP Environment" 
> >>> or no? If it's possible, how do I go about adding another section/tab.
> >>>
> >>
> >> JopProperty  
> >> goes under General, SCM 
> >>  under Source Code 
> >> Management, Trigger 
> >>  under Build 
> >> Triggers, BuildWrapper 
> >>  under 
> >> Build Environment etc.
> >> Maybe a JobProperty with an  would 
> >> add another tab I'm not sure.
> >>  
> >>
> >>>
> >>> 2) under the tab Build, you click on the drop down and you can add your 
> >>> plugins build step which in my case is called Execute ZAP. Once it's 
> >>> added, 
> >>> how do prevent the user from adding another Execute ZAP build step.
> >>>
> >>  
> >> No, Build Steps are intended to be added as many as the user needs, IIRC 
> >> a Recorder or Publisher can only be added once for Freestyle, but that 
> >> "limitation" is gone for pipelines. Sounds like it is more like a 
> >> BuildWrapper that you want to do.
> >>
> >>
> >>> Does that clarify it? If not, what else can I do to clarify the 
> >>> question. Thanks :)
> >>>
> >>> Cheers, Goran.
> >>>
> >>> On May 5, 2017, 2:31 AM -0400, Baptiste Mathus  >>> >, wrote:
> >>>
> >>> Please use the users list for such questions.  
> >>> If your question is about writing a plugin for this, I guess you need to 
> >>> be more specific.
> >>>
> >>> Cheers
> >>>
> >>>
> >>> Le 5 mai 2017 8:21 AM, "JordanGS"  
> >>> a écrit :
> >>>
> >>>
> >>>1. I can add my Job Build step which is called "Run ABC" from the 
> >>>drop down list, after it's added. How do i prevent the user from 
> >>> adding 
> >>>another Build Step "Run ABC"? 
> >>>2. How do i add a job configuration. Not a Post build step or a 
> >>>build step but rather a some options which are above the build step? 
> >>> It 
> >>>would be a text box for example and a checkbox, both of which could 
> >>>accessible from a build step / post build step. Would it be possible 
> >>> have 
> >>>these become environment variables / globally accessible variables 
> >>>throughout this job's config. 
> >>>
> >>> Thanks
> >>>
> >>> --
> >>> 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 jenkinsci-de...@googlegroups.com .
> >>> To view this discussion on the web visit 
> >>> https://groups.google.com/d/msgid/jenkinsci-dev/e78dd486-3b40-406b-baf0-41a31193c3c9%40googlegroups.com
> >>>  
> >>> 
> >>> .
> >>> For more options, visit https://groups.google.com/d/optout.
> >>>
> >>>
> >>> --
> >>> You received this message because you are subscribed to a topic in the 
> >>> Google Groups "Jenkins Developers" group.
> >>> To unsubscribe from this topic, visit 
> >>> 

Re: Due to the spam problem, we will need additional verification for your sign-up request.

[Christopher Orr]

On Thu, 27 Apr 2017, at 07:51, Dikla wrote:
> Please create my account:
> 
> User ID: dikla_sahar

This is the wrong place to post this; please read the instructions
again:
https://wiki.jenkins-ci.org/display/JENKINS/User+Account+on+Jenkins

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1493330161.1228270.958707952.780CC5ED%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Connecting software development tools to an e-learning platform

[Christopher Orr]

You asked this same question a few days ago and got some answers pretty
quickly:
https://groups.google.com/forum/#!msg/jenkinsci-dev/I45iPY9olzk/Yv-m7f4-BgAJ


On Mon, 24 Apr 2017, at 09:52, Jülide Dursun wrote:
> Hello Jenkins developers,
> 
> I hope you can help me. I am working on my bachelor thesis right now.
> Topic
> is: Connecting software development tools to an e-learning platform.
> 
> The e-learning platform in this case is Moodle. The software development
> tool is Jenkins.
> 
> I have to make following scenario true:
> Moodle-participant is taking a course in moodle for learning Jenkins.
> After
> watching the introduction slides, he has to do a task in Jenkins.
> Problem is: How does the moodle-trainer know that the task in the
> external
> tool Jenkins has been completed?
> 
> Is it possible to make a connection between the e-larning platform moodle
> and the software jenkins?
> 
> Which signals can Jenkins send? Maybe it is possible to check wether the
> task is done inside of Jenkins and if the task is done, there can be sent
> a
> mail to the moodle-trainer through jenkins?
> 
> I hope that my question is clear. I really don't know what to do and hope
> I'll get support.
> 
> Greetings
> Jüli

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1493111449.3896279.955334992.0F15E9E5%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: I used kubernetes plugin to build a pipeline job, but it need at least 10s to create pod since build job. Why?

[Christopher Orr]

On Mon, 24 Apr 2017, at 04:25, 李立 wrote:
> Why I use kubernetes cloud to build  which  need 8s at least and wait 6s 
> until k8s create pod.

Please use the jenkinsci-users mailing list for such questions:
https://jenkins.io/mailing-lists/

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1493111203.3895384.955330928.3A0F7D3F%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Wiki editing currently broken (was "Wiki downtime/maintenance window scheduled for 2017-04-01 16-18:00 UTC")

[Christopher Orr]

On Sun, 2 Apr 2017, at 17:47, JordanGS wrote:
> Congrats on the update! There seem to be some issues with the new system 
> tho. All of my old wiki pages cannot be modified or new edits saved. The 
> page throws a *Content Encoding Error*.
> 
> See wiki link .

Thanks for the notification; I've investigated and filed
https://issues.jenkins-ci.org/browse/INFRA-1120

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1491163410.769877.931683920.78CE6756%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cached Wiki Page

[Christopher Orr]

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. 
> 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,
> but 
> it needs an investigation. 
> 
> 
> воскресенье, 19 марта 2017 г., 8:40:26 UTC+1 пользователь JordanGS
> написал:
> >
> > For the last few months now, this page has been cached: 
> > https://wiki.jenkins-ci.org/display/JENKINS/Official+OWASP+Zed+Attack+Proxy+Jenkins+Plugin
> >
> > however, it doesn't exist anymore. It was renamed to 
> > https://wiki.jenkins-ci.org/display/JENKINS/zap+plugin.
> >
> > On the Official+OWASP+Zed+Attack+Proxy+Jenkins+Plugin page, if you click 
> > edit, it will open zap+plugin. So why is that cached version still there. 
> > Furthermore, it still appears as a google result.
> >
> > Is there any way to get rid of the cached version or force it to update 
> > itself.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1490608468.903596.924528328.4112094A%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit rights to matrix-auth-plugin

[Christopher Orr]

On Wed, 15 Mar 2017, at 11:23, Mathias Nyman wrote:
> >Mathias: You should have received an invite email from GitHub.  Enjoy!
> Thanks! I received an invite, but were only given read (pull) rights
> to matrix-auth-plugin, which I already had.. Maybe just a human error?

We've tried to eliminate human error by replacing ourselves with robots!
Specifically, I asked the IRC bot yesterday to make you a committer of
the plugin, which it claimed to have done.

I've asked the bot again just now, but it seems to be asleep.  Maybe a
GitHub admin can take a look:
https://github.com/jenkinsci/matrix-auth-plugin
https://github.com/mathias-nyman

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489573898.1129187.911949824.6AE60414%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit rights to matrix-auth-plugin

[Christopher Orr]

On Tue, 14 Mar 2017, at 23:42, Jesse Glick wrote:
> I am not maintaining this plugin so please do not wait for my opinion.

Jesse: Thanks.

Mathias: You should have received an invite email from GitHub.  Enjoy!

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489532014.4032427.911478760.7A36890C%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to call a groovy function from a Jenkinsfile?

[Christopher Orr]

On Tue, 14 Mar 2017, at 23:38, Daniel Beck wrote:
> 
> > On 14.03.2017, at 23:27, Christopher Orr <ch...@orr.me.uk> wrote:
> > 
> > Such a question is very unwieldy, and makes it harder for people to
> > answer.  Please reproduce the problem in a bare-minimum Pipeline and
> > update your question on SO.
> 
> On top of all that, it's been posted to the wrong mailing list.

Gahh… (╯°□°）╯︵ ┻━┻

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489531252.4028576.911465512.725847B1%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit rights to matrix-auth-plugin

[Christopher Orr]

On Mon, 13 Mar 2017, at 14:01, Mathias Nyman wrote:
> 10 days has passed. Is there something unusual or suspicious about my
> request?

No, it's fine.  We can give Jesse a wee bit more time to respond, but
otherwise I don't see anything against it.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489531080.4028350.911463712.55F63A30%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testing a plugin before release

[Christopher Orr]

On Mon, 13 Mar 2017, at 22:34, JordanGS wrote:
> Thanks for the reply, not what i meant tho. I know the project compiles
> and 
> builds fine but for whatever reason the command
> 
> mvn release:prepare release:perform 
> 
> 
> maybe due to a permission issue or it did the upload to maven but failed 
> the git push. I was hoping for a sanity test for this.

Once you're ready to release, the most common issue is permissions, but
if you didn't have upload permission then you didn't burn a version
number.  Just run perform again.

Everything is else is so rare or retryable that it's not worth worrying
about.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489530915.4027564.911461440.1709CA46%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to call a groovy function from a Jenkinsfile?

[Christopher Orr]

On Tue, 14 Mar 2017, at 20:17, Idan Adar wrote:
> (Cross-posting my question from Stack Overflow:
> http://stackoverflow.com/questions/42790966/how-to-call-a-groovy-function-from-a-jenkinsfile)

You *really* need to pare down your question to the minimum required to
reproduce the problem.

Between here and Stack Overflow, you have conflicting information about
what's in deployer.groovy.  On SO, the file apparently continues, yet
here it just ends after the method definition — but neither end with
`return this` as required:
https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#triggering-manual-loading
(linked from the docs of the Pipeline Remote Loader plugin you're using)

You say that the problem was *not* with loading the file (so presumably
most of the Jenkinsfile could have been omitted) — yet your stacktrace
suggests that the file failed to load, supposedly when you commented out
a line … in the file that fails to load?

Such a question is very unwieldy, and makes it harder for people to
answer.  Please reproduce the problem in a bare-minimum Pipeline and
update your question on SO.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489530449.4025867.911445776.2515567E%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: continuous-integration/jenkins/pr-merge check never ran for pull request

[Christopher Orr]

On Fri, 10 Mar 2017, at 15:51, JordanGS wrote:
> For the following pull request
> 
> https://github.com/jenkinsci/zap-plugin/pull/3, the 
> continuous-integration/jenkins/pr-merge never ran to test the build. 
> However, for https://github.com/jenkinsci/zap-plugin/pull/2 it did. Is
> this a bug or is there a particular reason that the build was never tested?

Jenkins needs to know a PR exists in order to build it.  There are many
reasons why this information might not reach Jenkins, e.g. GitHub might
have failed to send the webhook, or there was a network error somewhere,
or Jenkins was down at the time, or (most likely) the GitHub API rate
limit for ci.jenkins.io had been exceeded at the time.

You can see in the logs that Jenkins indeed failed to scan the repo due
to being rate limited:
https://ci.jenkins.io/job/zap-plugin/indexing/events

However, a build of that PR has since happened, so presumably the "poll
periodically" option of the multibranch project kicked in (at a time
when the rate limit hadn't been exceeded).

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489204895.4107096.907683624.199707E5%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Java Version on build-server for zap-plugin

[Christopher Orr]

Hi there,



On Fri, 10 Mar 2017, at 15:53, JordanGS wrote:

> Just wanted to ask, how do i check which version of java (7 or 8) is
> being used to compile the project on the build server.
> 

> https://ci.jenkins.io/job/Plugins/job/zap-plugin/



In the Jenkinsfile you provided for this plugin, you seem to be
specifying JDK 8:
https://github.com/jenkinsci/zap-plugin/blob/84e5e9b/Jenkinsfile#L30





> Also, is it possible for me to configure it myself or would i need to
> an admin to configure it for me?


The preferred method is to use the `buildPlugin` Pipeline step that
exists on ci.jenkins.io, which lets you configure the JDK version (among
other things):
https://github.com/jenkins-infra/pipeline-library#buildplugin



Regards,

Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1489198608.4083766.907644144.4406E636%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Christopher Orr]

Since last month, no special permissions are needed to upload SNAPSHOTs:
https://groups.google.com/d/msgid/jenkinsci-dev/53CC6ED4-3BBC-4FAD-A197-10AD7F922A34%40beckweb.net

The permissions look correct here, and match the groupId and artifactId 
from your logs, plus you said that you've logged into Artifactory, so 
that should be fine:

https://github.com/jenkins-infra/repository-permissions-updater/blob/176a269/permissions/plugin-sinatra-chef-builder.yml

So since the permissions look ok (and aren't needed for SNAPSHOTs 
anyway), and you've managed to log in to the Jenkins account app and 
Artifactory, I would guess that's something is wrong with your Maven 
security config.
But I don't know much about this stuff — maybe you've defined your 
id/password in multiple places, or perhaps Maven shows where it's 
reading the credentials from if you use --debug?


Regards,
Chris


On 14/01/17 17:56, Irfan Sayed wrote:

OK. Thanks
can you please give me those steps ?
May i request to take that please?

regards,


On Sat, Jan 14, 2017 at 10:12 PM, Slide > wrote:

One thing to try would be to add another user to the upload
permissions app and see if they can do a snapshot release.


On Sat, Jan 14, 2017, 09:37 Irfan Sayed > wrote:

Thanks Slide.
anyone has any other suggestions/workaround  ?
if this is not resolved, how will i be able to release my plugin ?

regards,




On Sat, Jan 14, 2017 at 10:04 PM, Slide > wrote:

I've been wondering the same thing but I am not sure. I
wonder if there is any sort of log on the server that
someone with those privileges could look at. I'm out of
ideas sadly.


On Sat, Jan 14, 2017, 07:09 Irfan Sayed
> wrote:

When i requested initially for hosting plugin in
jenkins-ci org, following was the original discussion:
https://issues.jenkins-ci.org/browse/HOSTING-59


we had changed the JIRA component and plugin name to
align the proper artifactID and all.
is this issue due to this ?

Regards,


On Sat, Jan 14, 2017 at 7:25 PM, Irfan Sayed
> wrote:

Yes i do have SNAPSHOT version in the POM.
mvn deploy command also failing with the same error ..
i am still not getting what is the issue

regards,


On Sat, Jan 14, 2017 at 7:14 PM, Slide
> wrote:

If your version has SNAPSHOT in it, you don't
need to add anything. Snapshots are
automatically deployed to the correct place I
believe.


On Sat, Jan 14, 2017, 05:52 Irfan Sayed
> wrote:

OK. i made the POM changes in my plugin and
added following:

   
   propSnap

https://repo.jenkins-ci.org/snapshots




 propRel

 https://repo.jenkins-ci.org/releases


  

run the same command: mvn clean package deploy
same error : "401 unauthorized"

regards,


On Sat, Jan 14, 2017 at 1:46 AM, Baptiste
Mathus > wrote:

Also, quick tip: you can stop trying to
release, but only do "mvn deploy" to see
if you can deploy snapshots, because
this is the thing that is failing for
you. Github pushes seem to work, only
artifacts have an in issue IIUC.

Le 14 janv. 2017 9:59 AM, "Irfan Sayed"

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[Christopher Orr]

On 29/10/16 16:01, Arnaud Héritier wrote:

Let's forget the maven job. Our statistics about its usage are useless
as it was installed by default and we may hope that its usage is
decreasing...


AFAIK, basic usage of job types has always been available in the 
statistics.  From the September CSV:


Job type Count %
IvyModuleSet6311   0.1
WorkflowMultiBranchProject 17229   0.2
InheritanceProject 20407   0.2
WorkflowJob   139976   1.5
MatrixProject 306274   3.2
MavenModuleSet   1236525  13.1
FreeStyleProject 7725160  81.7



It remains that upgrading the java version of master is one thing.
But you also need to upgrade the java version used by agents which
aren't supporting an automated deployment (hello JNLP slaves on windows
...).

My problem is (and was for years when I administrated many
instances) the readibilty of the changelog/roadmap to understand when an
important change was done. I have no problem to release a java 8 version
tomorrow in a Jenkins 3.0 release. But in a 2.38 or 2.51.1 (fictifs
versions) will be always really strange for me. A minor release
shouldn't enforce you to change your infrastructure deployment (and
possibly break many jobs but it's a different story)


Jenkins has never used some sort of semantic versioning, so I don't 
think it would make a difference.  In any case, things seemed to go 
fairly smoothly when Jenkins started to require Java 7, and the changes 
were clearly highlighted in the changelog, communicated with blog posts, 
and on Twitter.




Le samedi 29 octobre 2016, Baptiste Mathus > a écrit :


2016-10-29 14:52 GMT+02:00 Arnaud Héritier >:

From my POV the problem is that we don't know if we are talking
about 5% or 50% :(


Well, since yesterday, we do know some things

.

  * Java 8 as runtime represents 52% of the 133505 instances out
there (yes, it's ignoring the opted-out ones)
  * Maven-plugin is installed 118711 times (yes, ignoring on purpose
the fact it was auto-installed up to 2.x)
  * So, *at most* it's 46% of the users base who *might *be impacted
here, if they were to upgrade in the very short term (that is:
while also still using an EoLed JDK7 durably).

Now, looking at the trend of the number of installs of that plugin,
my guts feeling is that is less than that. And if you add that to
the trend of Java 7 JVM users (see link above), then it is most
probably going down even quicker.

An example I have in mind is my previous company, pretty sure they
didn't upgrade to Jenkins 2.x yet, so they still contribute to that
stats, but we migrated off that plugins years ago after so many
headaches and hours spent to debug different behaviours between
Maven CLI and using it in Jenkins.

Correlating with

http://stats.jenkins.io/plugin-installation-trend/jenkins-version-per-plugin-version.json


I think we would have even more data, but seems like that data is
wrong.
Gonna find the one who contributed that and hit him (I know him
pretty well).


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9158b3dc-5e6c-c6cf-82db-560a168a49ff%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: New Jenkins Plugin - Slack File Uploader. (Problems in releasing)

[Christopher Orr]

Hi there,

> On 10 Oct 2016, at 20:33, Shitij Goyal  wrote:
> So, I was able to solve the problem of git. But a new error has cropped up.
> Failed to deploy artifacts: Could not transfer artifact 
> org.jenkins-ci.plugins:slack-uploader:hpi:1.3 from/to maven.jenkins-ci.org 
>  
> (http://maven.jenkins-ci.org:8081/content/repositories/releases 
> ): Connect to 
> maven.jenkins-ci.org :8081 
> [maven.jenkins-ci.org/199.193.196.24 
> ] failed: Operation timed out.
> Maven execution failed, exit code: '1'
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> 
> Please help in the debugging! This occurs when the artifact is being 
> uploaded. The hpi file seems to have uploaded but pom file is failing.

Basically your POM looks a bit suspect — I’m not sure how you created it in the 
first place:
https://github.com/jenkinsci/slack-uploader-plugin/blob/aef07d9/pom.xml

The "maven.jenkins-ci.org :8081" URL indicates 
that you’re running into INFRA-588:
https://issues.jenkins-ci.org/browse/INFRA-588 


You’re using version 2.2 of the plugin parent POM, whereas you need to be using 
at least 2.5 (or the latest version: 2.17).

Furthermore:
- the file indentation and formatting is completely inconsistent,
- the  tag is commented out, meaning that the plugin won’t appear in the 
Update Centre (and the wiki page name should ideally be "Slack Uploader 
Plugin", rather than "Slack Uploader"),
- you have a  defined in the  section,
- there are references to Java 1.8, even although Jenkins plugins should 
ideally still support Java 1.7, and
- you have a reference to "hudson.plugin.version" which, for a brand new 
plugin, seems weird.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/086D8076-121F-4B13-B0C0-35A71B54E003%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request to Adopt Hudson Post Build Task Plugin

[Christopher Orr]

Done.  I believe you should have received an invite email from GitHub.

Happy maintaining!
Chris


> On 23 Sep 2016, at 10:33, Mads Nielsen  wrote:
> 
> Hi All,
> 
> I'd like to request commit access to the following plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/Post+build+task 
> 
> 
> GitHub repo: https://github.com/jenkinsci/postbuild-task-plugin 
> 
> 
> Im requestiing commit acces because i've fixed 
> https://issues.jenkins-ci.org/browse/JENKINS-12830 
> 
> 
> Jenkins wiki id: MadsNielsen
> Github id: MadsNielsen
> 
> Best regards,
> Mads

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/06D09CD5-F778-45ED-A566-B7E9D6A832CC%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Do we need to use the Jenkins jira?

[Christopher Orr]

Hi there,

> On 16 Sep 2016, at 21:02, Gavin Mogan  wrote:
> I know we are supposed to use the Jenkins org in github, but are we required 
> to use the the main jira?
> 
> We have issues all over the place and trying to figure out our options.

Yes, the Jenkins JIRA is the preferred place for filing bugs and feature 
requests.
See: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue 


Plugin repos should have GitHub issues disabled by default, and the majority 
do, though some maintainers do seem to accept issues via GitHub.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4BE7B7F8-F9FA-4D79-9B9C-67E13805FD64%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site prototype

[Christopher Orr]

Looks pretty cool!


> On 31 Aug 2016, at 13:31, Daniel Beck <m...@beckweb.net> wrote:
>> * the search for maintainers should be improved. I only maintain the Job DSL 
>> plugin, but the page shows 7 plugins and the most relevant (Job DSL) is 
>> shown last. 
>> http://cloudbees-plugin-site-staging.s3-website-us-east-1.amazonaws.com/?maintainers=Daniel%20Spilker
>>  
> 
> The plight of the common first name -- 'Spilker' works. should probably not 
> be clever and split search tokens. Or is searching for plugins with multiple 
> specified maintainers a relevant use case?

Yeah, it’s weird that the  POM  value rather than  value 
is used — searching ?maintainers= works fine.  e.g. "orrc" gives the 
expected results, but "Christopher Orr" returns multiple Christophers.


I also noticed a bunch of wiki HTML problems, some of which were already 
mentioned.  But mainly I was impressed how well the HTML display works already 
:)

For example on the android-emulator page: 
http://cloudbees-plugin-site-staging.s3-website-us-east-1.amazonaws.com/android-emulator
 
<http://cloudbees-plugin-site-staging.s3-website-us-east-1.amazonaws.com/android-emulator>
- The {expand} macro doesn’t work, so stuff like "View older versions" (at the 
very bottom) doesn’t work
- All Table of Contents links lead to the wiki, rather than an anchor within 
the page
- All plugin page links lead to the wiki, rather than the plugin page on this 
new site

Also, all install graphs seem to have a hardcoded minimum Y value of 1 
installs — way above that of most plugins.

I’m not sure why there’s a prominent "Download" button, given than nobody 
should ever be downloading plugins from this site.  There should preferably be 
a link to some instructions, telling people how to install plugins.

Overall, the design is nice, but I don’t like that the plugin details appear in 
a "popup" over the page — I have to close this popup with the small "X" or back 
arrow, before I can use the search field again.
If the plugin details appeared inline below the search bar, like search results 
do, it would be a lot nicer (IMO).

What does the "Recently installed" list on the home page mean?  The home page 
is also a bit bare — for what should be a big landing page, there’s a lack of 
title or information somehow.

Anyway, very nice — the searching, sorting and categorisation works really 
well.  Overall a huge improvement!

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/D4FA284F-9519-4E1A-A5C0-4FE591AC92A6%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Are backend crawlers still executed?

[Christopher Orr]

> On 03 May 2016, at 00:42, Daniel Beck  wrote:
> 
> 
>> On 26.04.2016, at 08:44, Rouke Broersma  
>> wrote:
>> 
>> Ah yes I was looking for the backend crawler job on the jenkins cloudbees 
>> last week and couldn't find it anywhere, but forgot to ask about it. Good 
>> thing you spotted it too.
> 
> FTR this works again, and has for almost a week.
> 
> The job runs on on a private machine. We'll look into making logs available 
> (*gasp* External Monitor Job?!). For now, if something doesn't work as 
> expected, file an INFRA issue.

The Jenkins job was reinstated (albeit on a private „trusted" machine, as 
mentioned) on the 22nd of April, however the generated files aren’t currently 
being pushed to the mirror network, so you’ll continue to see the old files 
from the 15th of April.
This problem is being tracked here: 
https://issues.jenkins-ci.org/browse/INFRA-662 


If you want to check whether a certain backend-crawler job is creating the 
expected output, you can see the up-to-date results here: 
https://updates.jenkins.io/updates/ 

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5BD48F87-29A7-40C1-9D8C-CCBC48BE4973%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: [2.0] slipping date

[Christopher Orr]

> On 20 Apr 2016, at 08:03, Daniel Beck  wrote:
> 
> 
>> On 29.03.2016, at 02:54, Kohsuke Kawaguchi  wrote:
>> 
>>  • April 3: 1.656 release, which will be the last 1.x release
>> 
> 
> FYI As a test run of the new infra, KK released 1.657 today, which will be 
> followed by 1.658.
> 
> 2.0 will be released later today or tomorrow, so these shouldn't matter too 
> much.

Will the lack of Update Centre files being generated affect the 2.0 release, if 
it happens today?

Regards,
Chris

PS. Yay! :)

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/A8C2468E-F4E0-499C-9F0C-BDE0081F88F9%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Linking to help files in war/src and including dynamic content

[Christopher Orr]

On 14/03/16 15:59, Jesse Glick wrote:

On Sun, Mar 13, 2016 at 7:53 PM, Christopher Orr <ch...@orr.me.uk> wrote:

I’m trying to work on some of the core documentation, and a lot of it seems to 
be kept away from the core source — in `war/src/main/webapp/help`, where all of 
the files are HTML-only.


Generally I would consider this a deprecated location; help files
should be moved to their conventional locations:

· `core/src/main/resources/pkg/SomeDescribable/help.html`, for the
object as a whole
· `core/src/main/resources/pkg/SomeDescribable/help-someField.html`,
for a particular property


Ahh.. ok, it's good to know that it's considered deprecated.



There are exceptions: help that is not (and cannot easily be)
associated with conventional form binding; or cases where the same
content must be shared between multiple forms.


Right, I've seen a bunch of this in core already.  Makes sense.



At any rate, for files in the recommended locations, it is possible to
replace `.html` with `.jelly` and use dynamic content.


Yup.

Thanks!
Chris


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56E9FA5E.5070709%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: YAML Project plugin unmaintained?

[Christopher Orr]

> On 14 Mar 2016, at 15:37, Jesse Glick  wrote:
> 
> The most recent release was in October, but neither of the two active
> developers (@astroilov, @mattmoor) seem to respond to requests for
> comment. Would CC them but they do not make their email address
> public.

Both are @google.com , but I haven’t seen any 
updates from them on issues in a long time, e.g. on the Google OAuth Plugin.

-Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/72593D59-764F-4DDF-BD6B-0ABDB8E3BC4F%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Linking to help files in war/src and including dynamic content

[Christopher Orr]

Hi all,

I’m trying to work on some of the core documentation, and a lot of it seems to 
be kept away from the core source — in `war/src/main/webapp/help`, where all of 
the files are HTML-only.

However, for one of these files, I would like to have some documentation 
followed by some dynamic content — specifically the contents of 
`Jenkins.getInstance().getMarkupFormatter()?.getDescriptor().getHelpFile()`.

Is there an easy way I can include .jelly content in the `war` directory, which 
then includes the contents of the markup formatter’s help file (which I can 
presumably somehow include somehow with `${app.markupFormatter.helpFile}`)?
Or what’s the best way to do this?

Thanks,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/465594E4-BAA6-4375-A431-6E5F35192507%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Insterested in Usage Statistics Analysis Project

[Christopher Orr]

Yes, I believe "jobs" contains the number of each job type present.

"version" should be the Jenkins version, e.g. "1.567.8"


On 10/03/16 16:31, Payal Priyadarshini wrote:

Hey Kohsuke & Daniel,

I fetched the fields of census data using mongodb and tried to document
it for the future use. Although, I have few questions about some of the
fields, which is marked in red.

Thanks.
Payal Priyadarshini


install-ID



is a list, where each element contains 7 fields.




stat



jobs



Contains 4 fields. Are these counts of the respective type ?




Hudson-model-ExternalJob



Hudson-model-FreeStyleProject



Hudson-maven-MavenModuleSet



Hudson-matrix-MatrixProject



timestamp



Job execution starting time.

version



Version of what ?  is it installation

install



Installation id

Plugins [list]



Contains 2 fields




version



Name



Nodes [list]



List of Nodes. Contains 4 fields




Master



true/false

jvm-version



jvm-vendor



executors




--
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 jenkinsci-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/7f882d36-97a0-4eda-a6e0-6a0c613e466f%40googlegroups.com
.
For more options, visit https://groups.google.com/d/optout.


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56E21860.6070807%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub Organization Folder polish

[Christopher Orr]

On 07/03/16 18:31, Kohsuke Kawaguchi wrote:

Once somebody attempts to implement another one, then that effort should
help drive identifying reusable pieces. I'd love to see that happen. I
think Domi is probably right that there's some opportunities for more
reuse, and I also agree with Bobby/Manuel that users should see the
terminologies specific to their services. Fortunately, none of these
code is API, so it's relatively easy to move things around later.

OTOH, it's likely that BitBucket Org Folder plugin maintainer won't care
about GH Org Folder and vice versa, so if the code is separate, they
will be able to make decisions on their own and innovate faster, whereas
reuse would require constant collaboration which hinders velocity of
development...


You say "innovate faster", I say "create a horrible mess of inconsistent 
and duplicated UIs, which is a large part of why people consider Jenkins 
to be a disaster in terms of user experience".


e.g. this image shows (part of) what a user will see on the system 
config page if they install the GitHub-related plugins that will be 
recommended by Jenkins 2.0:

http://i.imgur.com/0Iv5lF3.png


Having had to maintain a Jenkins instance where we regularly used both 
GitHub and BitBucket, I wouldn't like to imagine what the UI will look 
like if more GitHub and BitBucket plugins like this get created, with 
even the same or less amount of reusability than there is now.



I do think it's probably fair enough to let plugin authors do whatever 
they want for many use cases, but for the really commonly used stuff — 
especially SCMs — there ought to be a lot more effort put into the user 
experience, rather than just the developers' experience.


Regards,
Chris



2016-03-05 1:07 GMT-08:00 domi >:

Would it be possible to generalize this GH stuff a bit more? From
what I know, most git hosting services have the notion of
organizations,repos,PRs... eg. GH,Bitbucket,gitlab?,gitblit?
I know GH is the most prominent, but ... yeah...
/Domi

 > Am 05.03.2016 um 01:12 schrieb Daniel Beck >:
 >
 >
 >> On 05.03.2016, at 00:45, Kohsuke Kawaguchi > wrote:
 >>
 >> I've synced up with Jesse & Manuel offline, and now the work is
in here if anyone is interested.
 >
 > Correct link (not much to look at on master yet):
https://github.com/jenkinsci/github-organization-folder-plugin/pull/1


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56DE251F.6000903%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 initial setup plugin selection

[Christopher Orr]

Nice work!

I'm not sure whether `javadoc` (row 17, YES) is a useful suggestion;
it's seemingly only high on the list because it used to be part of core.

Having set up some jobs last week for various types of software
projects, the Javadoc- and Doxygen-specific plugins don't seem to offer
any obvious benefits compared to the generic HTML Publisher plugin (row
49, YES).

I also wonder whether people actually use PAM Authentication (row 15, YES)?

Is it useful to take up a spot in the list for the Translation
Assistance Plugin (row 21, YES) — will anybody really install that?
Do we merge in the unverified user-provided translations more often than
once every two years anyway?
If we want to keep on using this mechanism to get translations, it
should maybe remain bundled with Jenkins, rather than appearing in this
list.

Otherwise, it looks good.  Though I'd quite like to see
`throttle-concurrents` on the list, as I feel its usefulness isn't
reflected in its install stats :)

Regards,
Chris


On 23/02/16 23:20, Daniel Beck wrote:
> Hi everyone,
> 
> I added two additional criteria to the wiki: The plugin shouldn't require a 
> restart to work (otherwise it's not exactly a great getting started 
> experience), and it shouldn't be just a UI/theming plugins that replaces part 
> of the Jenkins UI (as including them in a list of suggested/recommended 
> plugins would just be weird).
> 
> Based on these criteria I tried to build a list of plugins to feature in the 
> initial setup wizard.
> 
> A reminder: All plugins are still available in the plugin manager. But with 
> 1100+ plugins now, it'd be great if we could provide a curated subset to get 
> new users started. This also means that particularly complex plugins, that 
> require knowledge of Jenkins internals, even though they may be useful, are 
> basically excluded by default.
> 
> To approximate popularity, I used the previous install count multiplied by 
> the growth in the previous year (as neither alone is a sufficient indicator 
> of popularity). Then I sorted by this value, and went through the list, being 
> mildly judgmental. This is the result:
> 
> https://docs.google.com/spreadsheets/d/1TKziW5oEfX9NYAPrZkz-wXPt5s-zG-znIB5-Jwt3tmw/edit#gid=0
> 
> This is the list of plugins I came up with for the initial setup dialog. If a 
> plugin wouldn't be used, the reason is stated. Regarding 'Unsafe': Wearing my 
> security officer hat, I consider every plugin with Groovy scripting that is 
> not using the Groovy Sandbox to be unsafe, even if it implements security 
> measures.
> 
> Please review the list, and let me know what you think.
> 
> 
> On 21.01.2016, at 19:56, Daniel Beck  wrote:
> 
>> Hi everyone,
>>
>> For Jenkins 2.0, we're aiming for a much better 'getting started' 
>> experience, aimed for users new to Jenkins.
>>
>> We already talked about this last year[1], but the discussion didn't really 
>> have a great result, so I'd like to start over by defining a list of 
>> guidelines on what kind of plugins qualify for inclusion first. My initial 
>> proposal is in the wiki[2]. Please take a look and provide feedback in this 
>> thread.
>>
>> Specific selection of plugins would be the next step.
>>
>> Daniel
>>
>> 1: 
>> https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
>> 2: 
>> https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>>
>> -- 
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%40beckweb.net.
>> For more options, visit https://groups.google.com/d/optout.
>>
> 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56CE3824.7010707%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 initial setup plugin selection

[Christopher Orr]

There's a demo video linked from the "Jenkins 2.0" wiki page:
https://www.youtube.com/watch?v=kzRR8XR8hu4

Though I have a feeling a saw a newer version at FOSDEM; not sure where
the code can be found (not that I've looked).

Regards,
Chris


On 24/02/16 22:14, Ullrich Hafner wrote:
> How is the initial selection presented to the user? Is there already a mockup 
> or screenshot available? Should the number of plug-ins per category be equal 
> sized? Or are all categories shown in one screen?
> E.g., if we have tabs for the categories then choosing e.g. just 3 plug-ins 
> per category makes no sense to me.
> 
> Wouldn’t it make more sense to have some kind of profiles like
> - Build Java Web Applications
> - Deploy to Application Servers
> - Analyze Source Code
> - Measure Code Coverage
>  and so on and provide a set of plug-ins per profile? Or is this not feasible 
> due to the enormous number of plug-ins?
> 
> While the UI of Eclipse normally is not a good reference for best UI 
> practices I think having something like the different eclipse versions is a 
> good thing (eclipse for java developers, eclipse for testers, etc.)
> 
>> Am 21.01.2016 um 19:56 schrieb Daniel Beck :
>>
>> Hi everyone,
>>
>> For Jenkins 2.0, we're aiming for a much better 'getting started' 
>> experience, aimed for users new to Jenkins.
>>
>> We already talked about this last year[1], but the discussion didn't really 
>> have a great result, so I'd like to start over by defining a list of 
>> guidelines on what kind of plugins qualify for inclusion first. My initial 
>> proposal is in the wiki[2]. Please take a look and provide feedback in this 
>> thread.
>>
>> Specific selection of plugins would be the next step.
>>
>> Daniel
>>
>> 1: 
>> https://groups.google.com/forum/#!msg/jenkinsci-dev/w-_18aYn4QQ/t_WT442bBwAJ
>> 2: 
>> https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Selection+for+the+Setup+Dialog
>>
>> --
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/044ECC6E-4C39-45B6-90E3-1A0C40BD5E9B%40beckweb.net.
>> For more options, visit https://groups.google.com/d/optout.
> 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56CE20F6.2090904%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Push request failed : The requested URL returned error: 403

[Christopher Orr]

Hi there,

Try again now; I explicitly added you as a committer to the plugin again.

If you're still having trouble, please let us know what command you're
trying and what the full output is.

Thanks,
Chris


On 21/02/16 13:24, anna.ro...@whitesourcesoftware.com wrote:
> Hi , 
> I've asked for a permission to
>  /https://github.com/jenkinsci/whitesource-plugin
>  //with the GitHub user
> name :annarozin /
> I've got this email from you and followed all the instruction. 
> Unfortunately I'm getting an error while running the command 'git push'
> : "The requested URL returned error: 403"
> 
>  The Email
> 
> Hi annarozin,
> 
> Jenkins admin has invited you to join the Jenkins organization on
> GitHub. Head over to https://github.com/jenkinsci to check out Jenkins's
> profile.
> 
> To join Jenkins, follow this link:
> 
> https://github.com/orgs/jenkinsci/invitation?via_email=1
> 
> 
> Some helpful tips:
> 
> - If you get a 404 page, make sure you’re signed in as annarozin.
> - You can also accept the invitation by visiting the organization page
> directly at https://github.com/jenkinsci
> 
> If you were not expecting this invitation, you can ignore this email.
> 
> Thanks,
> The GitHub Team
> 
> 
> 
> Thanks,
> Anna
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/a44f9100-5711-4d2c-bc17-ebb1a4b8a632%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56C9CED0.1070404%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins plugin for TrustWave Appscanner

[Christopher Orr]

Hi there,

> On 18 Feb 2016, at 09:12, vinaya vengurlekar  
> wrote:
> Recently I have been using Trustwave's Appscanner for Web Application 
> Security Scanning.
> It is Commercial product. The company for which I work has bought the license.
> 
> Basically , the Idea is integrating "Running of Scans" with CI server..
> AppScanner Enterprise provides us with Web services which can be used to 
> write a simple client (Jenkins) which runs Scans,
> 
> So, planning to create Jenkins plugin for this,
> which takes input as,
> Hostname, Base url of REST API, Application name, Assessment name
> and runs scans as we schedule them.
> 
> I tried finding Jenkins Plugin for this purpose, or similar to this idea, but 
> I did not get any.

Thanks for checking.

I don’t remember there being a Trustwave plugin, and taking a look at the 
Jenkins wiki, and a quick look at Google, I didn’t find anything either.

So it looks like you’re in the clear :)

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/EDC14087-2006-48A1-83CD-BDC3A2104B0A%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Unpublish, or prevent publishing, an in-progress plugin submission

[Christopher Orr]

On 16/02/16 23:03, Ryan Black wrote:
> I have a pressing requirement to prevent the advertisement for
> installation for a recently-submitted plugin. We have a need to make
> several branding, and a few functional, changes before this is viewable
> in the Available plugins list.

If you can provide the plugin ID and the version, we can blacklist it,
preventing it from being shown in the Update Centre.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56C3AD46.4070206%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Build not triggered when change is pushed to bitbucket

[Christopher Orr]

That sounds like a question for the jenkinsci-users mailing list:
https://jenkins-ci.org/content/mailing-lists/


On 21/01/16 12:30, Rohit Sharma wrote:
> Hello Everyone,
> 
> I am using the jenkins version 1.625.3. And i am facing issues in
> integrating jenkins with bitbucket. What all i need to do is to trigger
> a job when a change is pushed to bitbucket. But unfortunately its not
> working and I am continuously getting the 500 error response code on
> webhook configured on bitbucket.
> PLease help me out in this.
> 
> Thanks
> Rohit

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56A136F4.7050905%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: [Experiment] Translators team

[Christopher Orr]

On 20/01/16 18:08, Jesse Glick wrote:
> On Wed, Jan 20, 2016 at 6:39 AM, Daniel Beck  wrote:
>> The @-mention would be invoked whenever there's a change invalidating 
>> existing translations, or adding new strings that have no translations
> 
> Does it not suffice for a translator to have a mechanical tool listing
> all missing translations for their language? Seems more scalable than
> reminding every developer to use this alias, and having every
> translator read every message sent to it, not to mention the backlog
> of missing translations predating the introduction of this alias, or
> predating a translator joining the project.

Yeah, it could be nice to have displays like various large open source
projects do.  e.g. from Gnome and KDE:

https://l10n.gnome.org/releases/gnome-3-20/
https://l10n.gnome.org/languages/de/gnome-3-20/ui/
http://i18n.kde.org/stats/gui/trunk-kf5/team/


Though this would require most plugins to actually be internationalised
in the first place...

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56A02234.5060405%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Trademark Misusage - JenkinsCiSchool at Twitter

[Christopher Orr]

On 14/01/16 18:35, Oleg Nenashev wrote:
> Hi,
> 
> I've occasionally noticed this account on Twitter:
> https://twitter.com/jenkinscischool
> 
>   * Account name
>   o This account does not seem to be official
>   o There was no trademark usage permission request
>   o It has the "CI" suffix, from which we're trying to get rid of
>   * The logo is a bit... uncommon
>   o I suppose this artwork does not require permissions from the
> community
>   o BTW, it may cause a negative impression about Jenkins project
> 
> IMHO it's good to have more resources distributing the information about
> Jenkins, hence it would be great to make it aligned with the project
> policies and official resources.
> 
> I propose to contact the account's owner in order to discuss its
> adjustment & trademark permission. I'll send this link to this thread to
> @JenkinsCiSchool

It's a Twitter account posting some links, not "part of [a] trademark or
brand identifier for Jenkins-based software goods or services":
https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Trademark

I've seen a bunch of identical tweets like "thanks for following me,
Jenkins CI School" over the past few weeks, so something's a bit odd,
but I don't think it's anything to worry about, certainly not from a
trademark point of view.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5697FE8B.6060002%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Code of Conduct

[Christopher Orr]

Yeah, I'm on a couple of other lists where the meeting links get posted
to the list at the end.

Looks like we have a volunteer, Oleg! :)


On 12/01/16 14:39, Oleg Nenashev wrote:
> Maybe makes sense to just Governance meeting summaries to the mailing list.
> I mean the automatically generated log with decisions and TODOs
> 
> пятница, 8 января 2016 г., 20:18:43 UTC+3 пользователь R Tyler Croy написал:
> 
> 
> In case you don't regularly follow the Jenkins blog or twitter, we
> now have a
> code of conduct: https://jenkins-ci.org/conduct
> 
> 
> Some more information about it is in the blog post about it:
> https://jenkins-ci.org/blog/2016/01/07/official-code-of-conduct/
> 
> 
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
>  Code: 
>   Chatter: 
> 
>   % gpg --keyserver keys.gnupg.net 
> --recv-key 3F51E16F
> --
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/d27c7c4b-e1d5-4674-9adf-eabf822a9913%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56957645.6040909%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: publishing to experimental update center

[Christopher Orr]

Hey,

On 08/01/16 01:36, Michael Neale wrote:
> So I published pipeline-editor to the experimental update center repo
> (via using "alpha") as
> per https://jenkins-ci.org/blog/2013/09/23/experimental-plugins-update-center/
> 
> However it doesn't seem to be showing up. I have created a plugin wiki
> entry for
> it: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+editor+plugin
> 
> Can anyone point out what I am doing wrong?

>From the troubleshooting guide on the plugin hosting documentation:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter

We can take a look at the Update Centre build log:
https://ci.jenkins-ci.org/job/infra_update_center_v3/lastSuccessfulBuild/consoleText

Which says:
"Wiki page does not exist, or is not a child of the Plugins wiki page"

Indeed, the page is a child of the "CloudBees Docker Custom Build
Environment Plugin" page for some reason.

I've just moved it to the right place (i.e. to be a child of "Plugins"),
so the plugin will start appearing after the Update Centre next gets
updated :)

Regards,
Chris, Senior Update Centre Detective

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/568F088D.9080209%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Require Pull Requests for commits to Jenkins core

[Christopher Orr]

On 07/01/16 21:37, Jesse Glick wrote:
> On Wed, Jan 6, 2016 at 4:40 PM, Christopher Orr <ch...@orr.me.uk> wrote:
>> PRs opened in the future should be
>> reviewed and merged within a certain time period (1 month?), otherwise
>> they should get the "proposed-for-close" label
> 
> I do not like the idea of closing a PR merely because no reviewers
> have gotten to it yet.

Yeah, I can understand that.

Alternative proposals would be gratefully accepted, even if it is "PRs
may end up lying around for years, unmerged".

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/568EDCD5.1070808%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Proposal: Require Pull Requests for commits to Jenkins core

[Christopher Orr]

Hi all,

As raised previously on this mailing list
(https://groups.google.com/d/topic/jenkinsci-dev/d64UIypbzh0/discussion), and
discussed in the community meeting today
(http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-01-06-19.01.html),
there is a proposal saying that Git commits should not be made to
Jenkins core without adhering to the common and useful practice of going
through peer code review, via GitHub Pull Requests.

That discussion concluded that there wasn't a concrete proposal to be
agreed (or disagreed) with, so it was decided to try and form a set of
guidelines that can be voted on in the next meeting.

Therefore, I present for your discussion:

1. All code and translation commits to Jenkins core
(https://github.com/jenkinsci/jenkins) must be proposed via a Pull
Request (PR).

2. While other non-code commits (e.g. changelog.html and Javadoc
addition/fixes) may be made directly, using a PR is still encouraged.
Similarly, release-related commits (which are scripted by Kohsuke,
AFAIK) are also not required to go through PR.

3. PRs can be merged by any core committer after at least one other
person has reviewed the code.  i.e. it's against the spirit of the
proposal if committers immediately merge their own PRs; a reasonable
amount of time should be given for people to take a look at the code.

(I'm leaving this point intentionally vague; it's clear that this can be
gamed in 100 different ways, but we're proposing that code review should
be done *more often*, not exactly *how* those reviews should be done;
that process (if likely unwritten or unclear) exists already)

4. As this will result in an increase in the number of PRs, and there
already over 120 outstanding, PRs opened in the future should be
reviewed and merged within a certain time period (1 month?), otherwise
they should get the "proposed-for-close" label
(https://github.com/jenkinsci/jenkins/labels/proposed-for-close).

That last point isn't so clear to me.  Should such labelled PRs then be
closed after a further month?  We should also try and encourage more
people to volunteer to review PRs?

Now that we have the starting points for discussion, it's over to you :)

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/568D89BC.4010906%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for Comment: Jenkins Code of Conduct

[Christopher Orr]

Ahead of tomorrow's meeting, and as the wiki page is locked for editing,
I just wanted to mention a couple of quick (minor) things:

1. About emailing individual board members, it says "their emails should
be visible from their Confluence profile page" — the correct email
address seems to only be available for two of three members.

Maybe the addresses should be directly on the board page, or the code of
conduct page, to make things a little easier?  Or Dean can fix his
profile.. :)

2. I still find it weird that events not controlled by the Jenkins
project are listed as "spaces" where the code of conduct applies;
specifically "FOSDEM" and "Jenkins Area Meetups".

Both are independent events, and I think that "Other community hosted by
the Jenkins community whether online or offline" already covers things
like the Jenkins project being at FOSDEM/SCALE/etc.
(Should the first "community" in that sentence be "events"?)

What could be added instead is (again stolen from Go): "Other Jenkins
groups (such as conferences, meetups, and other unofficial forums) are
encouraged to adopt this Code of Conduct. Those groups must provide
their own moderators and/or reporting system."

i.e. we encourage independent JAMs and conferences (Jenkins World?) to
follow the same code.


Regards,
Chris


On 05/12/15 02:08, R. Tyler Croy wrote:
> 
> As the Jenkins community has grown, it has become clear that we need to write
> down what behaviors  we welcome in our community, but more importantly, what 
> is
> not welcome.
> 
> I would like to invite you all to review and provide feedback on the following
> wiki page: 
> 
> 
> I take responsibility for the board dragging their feet on this topic and wish
> to remedy that as soon as possible. I cannot stress the importance of this
> topic enough and while I hope that we do not find ourselves in a position 
> which
> needs addressing, I believe it is critical to the long-term health of the
> Jenkins community that this be defined.
> 
> 
> If you have questions or concerns that you do not wish to advertise publicly,
> please email me off-list.
> 
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
>  Code: 
>   Chatter: 
> 
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> --
> 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/568C5A3D.9070400%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Hosting Request: Violations Reboot Plugin

[Christopher Orr]

Hi all,

> On 04 Jan 2016, at 12:03, Daniel Beck  wrote:
> On 04.01.2016, at 11:29, Tomas Bjerre  wrote:
>> I am also developing plugins for Stash/Bitbucket Server and I must say that 
>> their approach is much better. They have the Atlassian Marketplace where 
>> plugins are published if they have a clear use case, the people at Atlassia 
>> can successfully test that use case and it is documented properly.
>> 
>> Having somilar plugins is a good thing. Then there will be competition!
> 
> FWIW I'm starting to wonder about this. It's definitely useful in the case of 
> accidental duplication, i.e. as a checklist item on the "So you want to write 
> a plugin" page, as well as pointing plugin authors to the similar plugins 
> once they request hosting -- some have then abandoned their efforts and moved 
> to the existing plugin once someone pointed them there -- but refusing 
> hosting for a plugin that already exists? This probably shouldn't happen.

I’m really not sure about this yet — when the discussions started about 
revamping plugin discovery and users being able to rate them etc., I could see 
that it might be a good thing to accept every plugin request, regardless of 
whether there are already existing similar plugins — competition is good.

On the other hand, having actually tried to use Jenkins lately, I’ve had an 
absolutely disastrous experience.  I created a new Jenkins instance on my 
machine to try and replicate part of a production environment, so I installed 
various plugins we use for Git, GitHub, pull-request building and so on, along 
with some workflow / multibranch / GitHub stuff.  In the end, I couldn’t get 
Jenkins to do what I needed — I gave up when I couldn’t figure out which of 
FOUR separate places to enter GitHub credentials I should use — three of which 
were on the global settings page, and none were fully documented — nor *which* 
credentials type was required.  In addition, it was often unclear which plugin 
was even providing the UI (the “(from X plugin)” text that shows up in help 
fields is sometimes useful, *if* the plugin has help text).

Last week, I tried to use three separate plugins (unrelated to GitHub this 
time), and NONE of them worked due to various bugs, and took a long time to 
even get set up due to poor documentation.  It was a *really* depressing 
experience.

With near-zero quality control, more and more overlapping plugins being 
written, maintainers being unaware of each other, or not wanting to cooperate, 
it seems like this will only get worse for users — so that’s an argument *for* 
refusing some hosting requests.
On the other hand, developing Jenkins plugins is a bit of a thankless task, so 
I can appreciate that we should maybe be nicer to plugin developers.  But 
plugin developers are strongly outnumbered by Jenkins users, who appear to be 
having a rough time, so I’d rather prioritise them having a good experience 
over developers (though yes, ideally we should make both camps happy somehow).

However, if the barrier is too high for people to take over or even improve 
existing plugins due to bad code, or too many bugs or whatever (the EC2 plugin 
has one open bug for every 15 users), maybe it does make sense to allow 
newcomers to write overlapping plugins or rewrites of existing plugins, and 
enable competition.
But in this case, the discovery and review / rating stuff really needs to be in 
place for end users, there needs to be more clarity about which UI comes from 
which plugins (so users can try competing plugins, then disable the useless 
ones), and there somehow needs to be (way more) documentation on plugin 
development best practices (i.e. don’t re-invent credentials, or the IM plugin, 
or whatever), and somehow we need to split out more stuff into libraries (e.g. 
GitHub / Docker / SSH / whatever server configuration).

I guess that was a long and ranty way of saying I don’t have a good answer as 
to what we should be doing with plugins.. :(

Regards,
Chris


> OTOH, there are a few arguments _for_ this, and I'd like to get your take on 
> these:
> 
> * Plugins get abandoned, but remain compatible with Jenkins for a long time. 
> AFAIU, Atlassian plugins often need to be replaced with a major version 
> update (at least I had acquaintances complain about how much effort some 
> major version updates are because plugins aren't compatible), so there seems 
> to be less chance of something that isn't actively maintained to linger 
> forever.
> * We emphasize community contributions compared to individual ownership. That 
> doesn't mean that the latter isn't possible, or even that it's discouraged, 
> but we'd like to have someone be able to take over in case the original 
> maintainer disappears or loses interest.
> * Users (and developers) complain about some clusters of plugins with similar 
> or overlapping features.
> 
> -- 
> You received this message because you are subscribed to the 

Re: Proposal: forbid direct commits to master for core

[Christopher Orr]

On 21/12/15 09:33, Oleg Nenashev wrote:
> Slightly hijacking this topic: would it be worthwhile having a similar
> rule (even if it's may not be technically enforceable) for creating new
> plugins?
> 
> 
> I'm +1 on it. My gut-feeling that there are misusages: forking of
> demo-only plugins, bad namings, etc.
> It's enforceable. We could restrict the create repo permission to admins
> only.
> The restriction of the IRC bot is also possible when we have a
> "community team".

I'm sure some admins are also guilty of forking their own plugins.. :)

> 
> The same for plugins, if *author* of plugin doesn’t want to use PRs,
> then you can’t enforce him do it (the reason why i left
> docker-plugin development). Core is critical for stability and
> relates to many devs/contributors, that’s why i created this
> topic/proposal.
> 
> 
> At least it's a good place to start.
> 
> I see lots of PRs languishing for ages with disagreement over what
> to do and no clear outcome one way or the other...]
> 
> 
> It's a complete off-topic in any case...
> Jenkins does not belong to CloudBees as well the company does not belong
> to the project. All Jenkins contributors including CB-employed ones can
> designate their review time as they want/can. Obviously we use our
> working time to review "our" PRs, but it does not mean that nobody from
> CB reviews other PRs during his spare time. Honestly I don't see much
> unreviewed PRs, but if there are such ones you can always ask for a
> review in the ML. The old pending PRs have been also classified.
> 
> We have no "formal" PR review process in the community. If somebody
> drafts a proposal, it would be a good topic for the discussion.
> 
> понедельник, 21 декабря 2015 г., 2:58:34 UTC+3 пользователь Stephen
> Connolly написал:
> 
> If we are going to go down the road of forbidding direct committing
> to master and forcing people to go through PRs (let's assume we can
> find a way to let release commits go through) we'd need a better
> criteria for when we can actually merge PRs.
> 
> I see lots of PRs languishing for ages with disagreement over what
> to do and no clear outcome one way or the other...
> 
> We have 25 PRs that are older than Jun 1st 2014...
> 
> 50 PRs that are at least 1 year old
> 
> 75 PRs that are 6 months or older
> 
> Now KS, it's not CloudBees place to decide what the community wants
> to have merged... the community has not defined how to address these
> PRs...
> 
> If we are to move to PRs without direct commit then I want to see a
> defined process whereby no PR goes more than say 1 month without the
> community deciding if it is a Go / No Go on the general idea.
> 
> I am quite sure that CloudBees would be willing to help get PRs into
> a better state for merging if we knew that those PRs were the
> direction the community wanted to go. Right now we seem to end up
> saying "ok this is what we think, here's our contribution, do you
> want it?" and there is no movement further... after a while we then
> remove our CloudBees hat and don our core contributors hat and say
> something like "ah for jebus's sake, nobody else has expressed an
> opinion either way for the past 2-3 weeks, let's just merge it" but
> don't for one second think that we like doing this.
> 
> I would say that the community needs to show interest in PRs before
> we can switch to a PR model as the route for change.
> 
> My suggestion is that when a PR has been open for a week or so, the
> community should start a vote thread to decide if the change is the
> right direction (Go) or the wrong direction (No Go). If No Go then
> close the PR providing the reason... if Go then the PR author can be
> helped to get the PR to a mergeable quality and then we merge the
> change and move forward.
> 
> If that process gets all the open PRs down such that most PRs are
> open for no more than 1 month, then and only then would I say that
> preventing direct core commits might be worth pursuing... 
> 
> Just my €0.02
> 
> -Stephen 
> 
> On 20 December 2015 at 17:22, Andrew Bayer  > wrote:
> 
> So, addressing a few aspects of this thread:
> 
> - I'd strongly oppose ICLA/push permission revocation for
> pushing directly to master. That's overly harsh.
> - I do support this policy overall - I'm personally a big fan of
> a "Review then Commit" policy.
> - There is a caveat/exception, of course - release-related commits. 
> 
> I think this is worth proposing for the next meeting - Kostya,
> could you add it to the agenda on the wiki? There's no need to
> name-and-shame specific cases of people pushing directly to
> master - this is a worthwhile policy to advocate even if no one
> was actually breaking it at 

Re: Tool Installation (and confluence Labels)

[Christopher Orr]

Hi there,

On 21/12/15 20:55, Gavin Mogan wrote:
> I just saw at the bottom
> of https://wiki.jenkins-ci.org/display/JENKINS/Tool+Auto-Installation
> specifically the more tools needed section. Is there a label for this?
> Is there a list of what labels automatically fill out what pages?

Not quite sure I fully understand the question, but I don't believe
there are any labels on the wiki relating to tool installers.


> So far I've been doing a bunch of grepping in github to figure out how
> the various pieces work. I think its a pretty nice little system, other
> than the ui. I had a few questions though.
> 
> For Installable, is there a way to make url dynamic? We have different
> installable urls per OS. I want one smart object that can be used for
> all nodes, so for now I've just overrode DownloadFromUrlInstaller
> Descriptor.getInstallable to create a new object every time with the
> proper url.

The URLs are stored in a JSON file, which is refreshed daily by Jenkins.
 The URL to a particular tool version is usually associated with a tool
ID and name.  In many cases, where the tool is cross-platform, the JSON
file is quite simple:
http://updates.jenkins-ci.org/updates/hudson.tasks.Ant.AntInstaller.json

However, some plugins provide multiple URLs for a given tool ID, where
multiple platforms and/or CPU architectures are supported, e.g.
http://updates.jenkins-ci.org/updates/org.jenkinsci.plugins.golang.GolangInstaller.json

i.e. The URL to use is decided at runtime, based on the type of machine
the build is running on.

The JDK installer goes a step further and groups the items by Java major
version, then individual releases, then individual installers per
platform and CPU architecture:
http://updates.jenkins-ci.org/updates/hudson.tools.JDKInstaller.json

So those might be good installer plugins to grep on (the JDK installer
is in Jenkins core).


> What happens if a specific version gets removed from the json file? Do
> we have to publish all versions forever using this?

If you don't want to break people's builds, yes, pretty much.

If one day the JSON file contains "Foobar 1.5" and somebody configures a
job with to install that tool, then if you remove "Foobar 1.5" from the
JSON in a later update, that user's build will likely fail in a
situation where the tool needs to be installed (though this isn't
something I've seen or tested myself).

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56789679.7060705%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: forbid direct commits to master for core

[Christopher Orr]

Slightly hijacking this topic: would it be worthwhile having a similar
rule (even if it's may not be technically enforceable) for creating new
plugins?

i.e. everyone should have to go through the hosting request process,
even if they already have, by whatever means, permission to create
themselves a new repo in the GitHub organisation?

Regards,
Chris


On 20/12/15 18:22, Andrew Bayer wrote:
> So, addressing a few aspects of this thread:
> 
> - I'd strongly oppose ICLA/push permission revocation for pushing
> directly to master. That's overly harsh.
> - I do support this policy overall - I'm personally a big fan of a
> "Review then Commit" policy.
> - There is a caveat/exception, of course - release-related commits. 
> 
> I think this is worth proposing for the next meeting - Kostya, could you
> add it to the agenda on the wiki? There's no need to name-and-shame
> specific cases of people pushing directly to master - this is a
> worthwhile policy to advocate even if no one was actually breaking it at
> this point.
> 
> A.
> 
> 
> On Sun, Dec 20, 2015 at 9:41 AM, Kanstantsin Shautsou
> > wrote:
> 
> 
>> On Dec 20, 2015, at 17:32, Baptiste Mathus > > wrote:
>>
>> +1 with all Oleg said... 
>> The subject might indeed be eligible to discussion, and I also
>> think we might want to proceed with only PRs, but the way you do
>> it... 
>> And the name you use for kk in CC is, well…
> Name was allowed, see meeting logs. 
>>
>> 2015-12-20 15:26 GMT+01:00 Oleg Nenashev > >:
>>
>> Hi Kostya, 
>>
>> I understand your concern, but messages of such kind can be
>> considered as a personal offense. 
> Any question can be transformed in any way you want.
>>
>> Kohsuke is not the only person committing in such way, so it's
>> definitely a wider problem, which requires a discussion. BTW
>> currently there is no policy prohibiting such approach, so the
>> direct commits are generally valid even if they smell bad.
> Never saw anybody else, could you share more examples?
>>
>>
>> I'm +1 on prohibiting direct pushes to the master branches for
>> everybody and in all repos. And Jenkins core core is not an
>> exception.
>> It makes the current release and changelogging approach a bit
>> problematic, but it's another story.
>>
>> if you signed ICLA and do some questionable changes into
>> master (here i see 2 violations) person should get core
>> access removal, right?
>>
>>
>> Nope. There is no such policy in Jenkins project. If you have
>> any concerns about particular contributors, raise the topic to
>> the governance meeting. It's the *ONLY* way for discussing
>> such topics.
> That what core committers said to me when i asked about ICLA and
> perms. Would be glad to see documented way without double standards. 
>>
>>
>>
>> воскресенье, 20 декабря 2015 г., 17:03:40 UTC+3 пользователь
>> Kanstantsin Shautsou написал:
>>
>> Situation: people doing reviews, blocking PRs for
>> weeks,months,years while some people do direct commits to
>> core master without any reviews. 
>> This ends to situations when master gets broken state that
>> reflects on PR builds verification,
>> i.e. 
>> https://github.com/jenkinsci/jenkins/commit/d86a88ab042cc55530d91e745af9e0886e8eeb79
>> Unreviewed changes adds chaos. While people reviewing and
>> close to get rid of unconfigurable settings
>> in https://github.com/jenkinsci/jenkins/pull/1914 one
>> person is doing direct master
>> changes 
>> https://github.com/jenkinsci/jenkins/commit/653fbdb65024b1b528e21f682172885f7111bba9
>> 
>> 
>>
>> Proposal: stop doing such unreviewed changes and forbid
>> direct master commits (either at all, either only for
>> mentioned person). 
>>
>> PS. AFAIR/AFAIK if you signed ICLA and do some
>> questionable changes into master (here i see 2 violations)
>> person should get core access removal, right?
>>
>>
>> -- 
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com
>> .
>> To view this discussion on the 

Re: CFLint plugin deployment failed?

[Christopher Orr]

Take a look at point #2 on the list here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help%5C%21Mypluginisnotshowingupintheupdatecenter.

Regards,
Chris


On 20/12/15 00:18, Ryan Eberly wrote:
> Hi, 
>   It's been a while, but I attempted a deployment of an update to the
> CFLint Jenkins plugin. following the how-to on
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
> 
> After some bumps it was "successful".  But I don't see the deploy out on 
> http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/.  The notes
> say to sent the output here:
> 
> thanks!
> 
> ...
> [INFO]  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> .java:207)
> [INFO]  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> .java:153)
> [INFO]  at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
> .java:145)
> [INFO]  at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
> ct(LifecycleModuleBuilder.java:116)
> [INFO]  at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
> ct(LifecycleModuleBuilder.java:80)
> [INFO]  at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThre
> adedBuilder.build(SingleThreadedBuilder.java:51)
> [INFO]  at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
> eStarter.java:128)
> [INFO]  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> [INFO]  at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> [INFO]  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> [INFO]  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> [INFO]  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> [INFO]  at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> [INFO]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [INFO]  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:62)
> [INFO]  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> [INFO]  at java.lang.reflect.Method.invoke(Method.java:497)
> [INFO]  at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
> cher.java:289)
> [INFO]  at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
> a:229)
> [INFO]  at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
> uncher.java:415)
> [INFO]  at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
> 356)
> [INFO] [INFO]
> [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @
> CFLint
> ---
> [INFO] [INFO] Installing
> C:\Users\Ryan\git\CFLint-plugin\target\checkout\target\
> CFLint.hpi to
> C:\Users\Ryan\.m2\repository\org\jvnet\hudson\plugins\CFLint\0.5.2
> -SNAPSHOT\CFLint-0.5.2-SNAPSHOT.hpi
> [INFO] [INFO] Installing
> C:\Users\Ryan\git\CFLint-plugin\target\checkout\pom.xml
>  to
> C:\Users\Ryan\.m2\repository\org\jvnet\hudson\plugins\CFLint\0.5.2-SNAPSHOT\
> CFLint-0.5.2-SNAPSHOT.pom
> [INFO] [INFO] Installing
> C:\Users\Ryan\git\CFLint-plugin\target\checkout\target\
> CFLint.jar to
> C:\Users\Ryan\.m2\repository\org\jvnet\hudson\plugins\CFLint\0.5.2
> -SNAPSHOT\CFLint-0.5.2-SNAPSHOT.jar
> [INFO] [INFO] Installing
> C:\Users\Ryan\git\CFLint-plugin\target\checkout\target\
> CFLint-sources.jar to
> C:\Users\Ryan\.m2\repository\org\jvnet\hudson\plugins\CFLi
> nt\0.5.2-SNAPSHOT\CFLint-0.5.2-SNAPSHOT-sources.jar
> [INFO] [INFO]
> [INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @
> CFLint ---
> [INFO] Downloading:
> http://maven.jenkins-ci.org:8081/content/repositories/snapsh
> ots/org/jvnet/hudson/plugins/CFLint/0.5.2-SNAPSHOT/maven-metadata.xml
> [INFO]
> [INFO] Uploading:
> http://maven.jenkins-ci.org:8081/content/repositories/snapshot
> s/org/jvnet/hudson/plugins/CFLint/0.5.2-SNAPSHOT/CFLint-0.5.2-20151219.230746-1.
> hpi
> [INFO] 2/210 KB
> [INFO] 4/210 KB
> [INFO] 6/210 KB
> [INFO] 8/210 KB
> [INFO] 10/210 KB
> [INFO] 12/210 KB
> [INFO] 14/210 KB
> [INFO] 16/210 KB
> [INFO] 18/210 KB
> [INFO] 20/210 KB
> [INFO] 22/210 KB
> [INFO] 24/210 KB
> [INFO] 26/210 KB
> [INFO] 28/210 KB
> [INFO] 30/210 KB
> [INFO] 32/210 KB
> [INFO] 34/210 KB
> [INFO] 36/210 KB
> [INFO] 38/210 KB
> [INFO] 40/210 KB
> [INFO] 42/210 KB
> [INFO] 44/210 KB
> [INFO] 46/210 KB
> [INFO] 48/210 KB
> [INFO] 50/210 KB
> [INFO] 52/210 KB
> [INFO] 54/210 KB
> [INFO] 56/210 KB
> [INFO] 58/210 KB
> [INFO] 60/210 KB
> [INFO] 62/210 KB
> [INFO] 64/210 KB
> [INFO] 66/210 KB
> [INFO] 68/210 KB
> [INFO] 70/210 KB
> [INFO] 72/210 KB
> [INFO] 74/210 KB
> [INFO] 76/210 KB
> [INFO] 78/210 KB
> [INFO] 80/210 KB
> [INFO] 82/210 KB
> [INFO] 84/210 KB
> [INFO] 86/210 KB
> [INFO] 88/210 KB
> [INFO] 90/210 KB
> [INFO] 92/210 KB
> [INFO] 94/210 KB
> [INFO] 96/210 KB
> [INFO] 98/210 KB
> [INFO] 100/210 KB
> [INFO] 102/210 KB
> [INFO] 104/210 KB
> [INFO] 106/210 KB
> [INFO] 108/210 KB
> [INFO] 110/210 KB
> 

Re: Request for hosting : vmware-vrealize-automation-plugin

[Christopher Orr]

Fair enough.

If you could remove the "-plugin" suffix from your artifact ID, that
would be great (it's listed in the prerequisites here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites)

Thanks,
Chris


On 17/12/15 18:46, Inky Sea wrote:
> VMware's vRealize Automation (vRA) is a cloud management platform that
> allows provisioning on various type of infrastructure.  For example,
>  vRA can provision workloads to vSphere, HyperV, AWS, Azure, etc...
> 
> The other VMware/VSphere plugins are for different products in the
> VMware suite.   Attempting to integrate with those plugins would be a
> challenge from a development perspective as each product does different
> things and it would be confusing to the end users. 
> 
> On Thursday, December 17, 2015 at 11:07:20 AM UTC-5, Baptiste Mathus wrote:
> 
> I don't know enough about it, but just to check: is this a product
> really different from VMWare/VSphere (both exist)? 
> Shouldn't/Couldn't it be integrated in one existing plugin as an
> extension or something?
> 
> (Not saying it should, again, just for the record trying to get your
> take/opinion about it before eventually forking)
> 
> Thanks!
> 
> 2015-12-17 16:15 GMT+01:00 Inky Sea :
> 
> What is the typical turn around on creating the project?  It's a
> busy time of year, I just want to ensure that this request did
> not get lost in the shuffle.
> 
> On Monday, December 14, 2015 at 2:13:58 PM UTC-5, Inky Sea wrote:
> 
> GitHub repository URL :
>  https://github.com/inkysea/vmware-vrealize-automation-plugin 
> 
> 
> GitHub user :  inkysea
> jenkins-ci.org  user : inkysea
> 
> Description:   The VMware vRealize Automation plugin allows
> Jenkins to provision virtual machines and application
> blueprints on vRrealize Automation v7+. 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/567313C7.502%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Commit access to job-node-stalker-plugin

[Christopher Orr]

Done!


On 17/12/15 15:31, Daniel Spilker wrote:
> Hi,
> 
> The last release (1.0.4) of job-node-stalker-plugin has been tagged but
> not properly released through Maven. So it's not available in
> Artifactory and the POM is still at 1.0.4-SNAPSHOT. I pinged the
> maintainer in September (see below) but got no response. Can I get
> commit access to job-node-stalker-plugin to do a proper release? I do
> not want to become the maintainer, so I put the plugin up for adoption.
> 
> My GitHub ID is daspilker.
> 
> Daniel
> 
> -- Forwarded message --
> From: *Daniel Spilker*  >
> Date: Mon, Sep 14, 2015 at 5:58 PM
> Subject: Jenkins Node Stalker Plugin
> To: fabio.ne...@datalex.com 
> 
> 
> Hi Fabio,
> 
> I saw on GitHub [1] that you tagged version 1.0.4 of the Node Stalker
> plugin, but that release never appeared in the Jenkins Update Center [2,
> 3]. Can you push the release to the Update Center? I desperately need
> the folder support which has been added in commit 435ed55. I verified
> the commit in our test environment, but I want to deploy an "official"
> release on production.
> 
> Regards,
> Daniel
> 
> [1]:
> https://github.com/jenkinsci/job-node-stalker-plugin/releases/tag/job-node-stalker-1.0.4
> [2]: https://wiki.jenkins-ci.org/display/JENKINS/Node+Stalker+Plugin
> [3]:
> http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/job-node-stalker/
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAKqW32Ac4-m6pLs0iXty441PMyQmYiTEGW-c-Kz0ni2LxLHpGg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56731249.8080806%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for hosting: CPWR-PDS-download

[Christopher Orr]

Good question.  CC'd Chad, who emailed me asking about the status here.

If it doesn't make sense to combine them, I think the plugins seem ready
to fork.

-Chris


On 14/12/15 16:24, Andrew Bayer wrote:
> Out of curiosity, would it make more sense to combine these into one
> compuware-download plugin rather than splitting it into two plugins? It
> seems like it'd make things a bit simpler for users.
> 
> A.
> 
> On Mon, Dec 14, 2015 at 9:40 AM, cpwr_jenkins
> > wrote:
> 
> We have changed the artifacts to compuware-pds-download and
> compuware-endevor-download. Please let us know if there is any more
> issues!

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5670A522.8000901%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request. codeclimate plugin.

[Christopher Orr]

Hi there,

You need to follow *all* of the "Prerequisites" and "Request hosting"
steps:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites

In particular:

* Give your plugin a sensible ID which does not include "jenkins" or
"plugin"

Your plugin ID is "codeclimate-plugin"; you need to fix this.

It probably doesn't matter too much, but the groupId and Java package
names are also a bit odd.

* Your jenkins-ci.org username

You haven't provided this.

* A description of what the plugin does

You haven't provided this, though it is at least fairly obvious (even if
the link in the GitHub README is a 404).

Regards,
Chris


On 12/12/15 23:56, Surya Gaddipati wrote:
> Hi Christopher, 
> 
> I went through those steps and   I've added the missing license file . 
> 
> Please let me know if I am missing anything else. 
> 
> Surya
> 
> On Thursday, November 26, 2015 at 9:04:07 PM UTC-6, Surya Gaddipati wrote:
> 
> 
> repo: https://github.com/suryagaddipati/codeclimate-plugin
>  
> github username: suryagaddipati
> 
> Thank you. 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/566D5DC2.3050104%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for hosting: CPWR-PDS-download

[Christopher Orr]

Hi there,

On 10/12/15 15:46, cpwr_jenkins wrote:
> Git Repository: https://github.com/Compuware-Corp/CPWR-PDS-download
> 
> Github Usernames: chadseippel, compharry, derek-rea, JerryWeis, jgoering41,
> kturetzky, pfhdzg0, RonVorndam, sallenCPWR, samjoe 
> 
> Jenkins-CI Username: cpwr_jenkins 
> 
> Description: 
> 
> The Compuware Topaz Plugin allows Jenkins users to download PDS members from
> the mainframe to the PC. Source can then be accessed on the PC, for example,
> for SonarQube analysis and reporting.

I don't really know what that means :)  But your two plugins seem ok,
except for the artifact IDs, which need to be a bit more descriptive.

"scm.endevor" should really be something like
"compuware-endevor-download"; similarly "compuware-pds-download" for the
other.

Do you really need 10 people to have direct write access to the repos,
or can most of those people live with using pull requests?  Either way
should be fine, though one is obviously more effort for us ;)

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/566A00DD.3040101%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: create-text-file plugin - New hosting reuest

[Christopher Orr]

On 06/12/15 19:45, Victor Martinez wrote:
> I didn't want sound rude at all, in case i was, sorry about it.
> 
> You can create it at anytime before releasing it, afaik there is already a 
> new upcoming policy which won't show any plugins without any wiki references 
> in the update center.

This has been enforced for all new plugins since June.

But it's best add the wiki page and the POM tag *after* the plugin has
been forked, since the plugin may be renamed (or merged into another).
This is why creating a wiki page isn't listed in the "Prerequisites" or
"Request hosting" sections of the plugin hosting wiki page.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56648594.5090005%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for Comment: Jenkins Code of Conduct

[Christopher Orr]

Hi there,

Thanks for the update!

While the Contributor Covenant seems reasonable, it also appears to be a
pretty generic template, and I find it leaves a lot of ambiguity that
could be expanded upon.

>From the first sentence, the Code of Conduct applies to "this project" —
which I would assume means Jenkins core, and I guess also its
infrastructure.  But that's not clear to me and, given that a large part
of Jenkins is its plugin ecosystem, I don't know where plugins, their
maintainers, and contributors fit into this.

"Project maintainers have the right and responsibility to ... ban
temporarily or permanently any contributor for other behaviors that they
deem inappropriate" — this reads as if any Jenkins core developer can
unilaterally ban somebody at any point based on their subjective opinion?

This seems out of place — I would expect only the board to have this
power, having followed the "Reporting" and "Handling of violations"
procedures mentioned later.

Similarly, "project spaces" is not further expanded upon — all jenkinsci
repos? jenkins-infra? plugin repos/wikis/websites?


I find the recently published Go Code of Conduct @
https://golang.org/conduct to be very clear about these points, as well
as approaching the entire topic from a more positive standpoint —
focussing more on the motivations, and the project's desired goals,
rather than sounding almost entirely negative.

In particular, I find the "Gopher values" are very well put, and cover
many of the topics that have come up on the Jenkins developers' mailing
list this year regarding being patient, thoughtful, and staying
constructive with criticism.

There is also a clear definition of what "project spaces" are, including
GitHub organisations, code review tools, a list of mailing lists and IRC
channels.  The statement about external groups and conferences is also
helpful, and would be useful for Jenkins given the growth of Jenkins
Area Meetups.

Reporting is covered slightly more in more depth, or at least the
timeline is a bit clearer than what we have at the moment, though the
Jenkins version does a good job about being clear on the possible
outcomes.  The change proposal process and summary at the end are also nice.

Anyway, for the Jenkins project, progress is certainly being made, and
thanks to Tyler for doing this! :)

Regards,
Chris


On 05/12/15 02:08, R. Tyler Croy wrote:
> As the Jenkins community has grown, it has become clear that we need to write
> down what behaviors  we welcome in our community, but more importantly, what 
> is
> not welcome.
> 
> I would like to invite you all to review and provide feedback on the following
> wiki page: 
> 
> 
> I take responsibility for the board dragging their feet on this topic and wish
> to remedy that as soon as possible. I cannot stress the importance of this
> topic enough and while I hope that we do not find ourselves in a position 
> which
> needs addressing, I believe it is critical to the long-term health of the
> Jenkins community that this be defined.
> 
> 
> If you have questions or concerns that you do not wish to advertise publicly,
> please email me off-list.
> 
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
>  Code: 
>   Chatter: 
> 
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> --
> 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5663013D.1080309%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for Comment: Jenkins Code of Conduct

[Christopher Orr]

On 05/12/15 16:22, Christopher Orr wrote:
> Similarly, "project spaces" is not further expanded upon — all jenkinsci
> repos? jenkins-infra? plugin repos/wikis/websites?

My previous email was a bit long, so I wanted to try and list the spaces
that I could think of, where it seems that adherence to a Code of
Conduct should probably be encouraged for participants:

Source control
- GitHub commits, PRs, issues, wikis
  - jenkinsci
- i.e. core, misc repos, plus all hosted plugins
  - jenkins-infra
  - jenkinsci-cert
- SVN commits [assuming SVN isn't read-only]
  - svn.jenkins-ci.org

Websites
- Everything hosted on jenkins-ci.org and its subdomains, including:
  - Issue tracker
  - Wiki page content
  - Wiki comments (we could simplify by finally disabling this ;)
  - Blog post comments

Mailing lists
- https://jenkins-ci.org/content/mailing-lists
- http://lists.jenkins-ci.org/mailman/listinfo

IRC channels
- #jenkins
- #jenkins-meeting
- #jenkins-infra
- #jenkins-community

Online events, e.g. Hangouts
- Office Hours


The Jenkins project is pretty big! :)

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/566308BC.3050400%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Hide from the update center plugins without source code under the Jenkinsci github organization?

[Christopher Orr]

On 01/12/15 16:52, 'Jesse Glick' via Jenkins Developers wrote:
> On Tue, Dec 1, 2015 at 5:32 AM, Baptiste Mathus  wrote:
>> plugins forked under the Jenkinsci org, BUT still maintained elsewhere
> 
> There are a number of such cases where the @jenkinsci fork is out of
> date. There are even cases where both the original and fork repository
> are configured to accept pull requests, which is quite confusing.
> 
> Also in some cases the GitHub issue tracker is enabled (inside or
> outside @jenkinsci), and there are some issues filed in JIRA too,
> which is again confusing.

I guess being able to make plugin releases (exclusively?) via
Jenkins-on-Jenkins would solve this problem? :)

In any case, it would definitely be good if clicking on "Source code" on
the wiki led to the place where the *most recent release* was made,
rather than pointing to some abandoned fork.  Whether that means source
code needs to be exclusively hosted under @jenkinsci, I'm not 100% sure,
but doing so would certainly have a lot of benefits.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/565E0F62.605%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Bugs in AWS Elastic Beanstalk Deployment Plugin and AWS Elastic Beanstalk Publisher Plugin

[Christopher Orr]

Hi there,

I see you already filed one of the issues on JIRA a week ago:
https://issues.jenkins-ci.org/browse/JENKINS-31705

It seems that there are two AWS EB plugins which do the same thing and
have similar names, so hopefully that's filed against the correct
plugin.. :)

Anyway, if you could file the other issues separately on JIRA as well,
that would be the best place to keep track of them.  Not all plugin
maintainers necessarilyt read this mailing list all the time.

This wiki page gives a good guide as to what information you should
include in your bug report / feature request:
https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue

Regards,
Chris


 01/12/15 09:17, kanungoamrit...@gmail.com wrote:
> Hi Team,
> 
> I found out some bugs while working on the AWS Elastic Beanstalk
> Deployment and AWS Elastic Beanstalk Publisher Plugin.
> 
> *1. AWS Elastic Beanstalk Plugin*
>  
> In this, 
>   
>   *a) The most vulnerable issue is that, AWS secret key is visible and
> its not hiding. So its a security issue.*
> 
>   And to avoid the above security issue, I used *AWS Elastic
> Beanstalk Publisher* Plugin which helped me to declare the IAM user and
> secret key globally in Jenkins. And the secret key also was being
> hidden. By this plugin, in the job level configuration, I need not have
> to mention the secret key anymore.
> 
>  *b) Another issue is, it does not take wild card character like ' * ' .*
> 
>  And because of this, I was unable to declare the value of the
> parameter ' Root Object (File/Directory) ' as target/ *.war
>  It did not filter out the war file. As a result of which when this
> plugin was trying to deploy the zip file to Elastic
>  Beanstalk, it threw *HTTP 404 Error, Resource not found. *
> *
> *
> * *And to avoid this above issue, I did another  work around like I
> filtered the particular war file to a new folder, then  
>  unzipped that war file there itself. After unzipping the war file, then
> I removed the war file from that location.
>  All these I did in the *Execute Shell* prompt.  
> 
>   Execute Shell
>   Command -#!/bin/bash
> 
>  mkdir -p ${WORKSPACE}/target/war
> 
>  cp -r ${WORKSPACE}/target/*.war
> ${WORKSPACE}/target/war/.
> 
>  echo War copied successfully !!!
> 
>  cd ${WORKSPACE}/target/war/
> 
>  unzip *.war
> 
>  rm *.war
>   After this above steps I mentioned the details in the plugin and then
> finally it got deployed in Beanstalk.
> 
>  *c) The " Includes " and " Excludes " doesn't take the wild card " * "
> character as well.*
> 
> *2. AWS Elastic Beanstalk Publisher Plugin*
> 
>In this,
> 
>  *a) It does not take wild card character like ' * ' .*
>   
>Work around is same as above.
> 
>  *b) The " S3 overwrite exisiting file " parameter is not working, it's
> not updating.*
> *
> *
> * c) The " Includes " and " Excludes " doesn't take the wild card " * "
> character as well.*

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/565E0AB7.30206%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for hosting: Git Relasenotes Plugin

[Christopher Orr]

Hi there,

On 20/11/15 22:56, Tomas Bjerre wrote:
> Repo: https://github.com/tomasbjerre/git-releasenotes-plugin
> Username: tomasbjerre
> JenkinsCI username: tomasbjerre
> 
> I made a pre-release here with some screenshots:
> https://github.com/tomasbjerre/git-releasenotes-plugin/releases
> 
> This plugin may look similar to Git Changelog Plugin, and I actually
> would have taken that name if it was not already taken. But its very
> different when you look at it.

Given that these two plugins are indeed similar, though clearly with
very different publishing mechanisms, would it make sense to merge the two?

If not, I think the plugin name definitely needs to be more descriptive.
 Having two near-identically named plugins isn't going to be helpful for
users.

Git Changelog Template Generator, or Git Changelog Publisher, or
something along those lines?

(The artifact ID would need to be changed as well in any case; see
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites)

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/565E055B.9080902%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: terraform-plugin

[Christopher Orr]

Done!  You should get an invite from GitHub by email.

Welcome aboard :)

Regards,
Chris


On 30/11/15 21:06, David Pires wrote:
> All,
> 
> I'm in the final steps of finishing off my plugin for Terraform (more
> testing, adding help files, writing documentation for wiki etc) and i'd
> like to host my plugin on jenkins-ci.org.
> 
>   * url: https://github.com/dpires/jenkins-terraform-plugin
>   * name: terraform
>   * github username: dpires
>   * jenkins-ci.org  username: dpires
>   * description: A Jenkins plugin that installs Terraform and provides a
> build wrapper for launching and/or destroying infrastructure
> 
> Thanks,
> David
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/8dbd46a0-276b-4ef5-8a68-cabaa823b29b%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/565E0808.1090101%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request. codeclimate plugin.

[Christopher Orr]

Please make sure you complete all the steps and provide all the
information listed in the "Prerequisites" and "Request hosting" sections
here:

https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites

Regards,
Chris


On 27/11/15 04:04, Surya Gaddipati wrote:
> 
> repo: https://github.com/suryagaddipati/codeclimate-plugin 
> github username: suryagaddipati
> 
> Thank you.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5658EC2E.3030402%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Deprecating the Jenkow-plugin?

[Christopher Orr]

On 20/11/15 15:29, Baptiste Mathus wrote:
> *Please note that adding the deprecation label will have the effect that
> the /Jenkow plugin/ will not be visible anymore from the Update Center.*

Note that this also means that the infobox will stop being populated soon.

Therefore the deprecation notice on the wiki page, which says "The code
is still available", won't be helpful, as the GitHub link will soon
disappear.

Just something to think about if you're considering making a standard
wiki macro for this stuff (I briefly saw an IRC conversation on that
topic earlier) :)

>From the good old Nabaztag example [0], a macro would probably need
something like this as configuration fields:

* Last known source code URL
* Archive link (just needs the artifact ID)
* Reason for removal (optional)
* Alternative plugins (optional)

Regards,
Chris

[0]:https://wiki.jenkins-ci.org/display/JENKINS/Nabaztag+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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/564F8B4C.7020007%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Process for deleting plugins?

[Christopher Orr]

On 14/11/15 16:45, Oleg Nenashev wrote:
> I think that we should not remove plugins from UC, because there can be
> OLD Jenkins versions using OLD service versions. We cannot track it.
> Printing warnings is a right option IMO.
> At least it increases the chance that somebody takes ownership of them.

I think if someone's using an old plugin version and has never upgraded,
removing it from the UC won't hurt them.

The original question was about removing plugins that no longer have any
use, so I think it's reasonable to remove plugins from the UC for
services that no longer exist, e.g. the Nabaztag plugin, the Gitorious
plugin, or the Hudson Google Desktop Gadget plugin.

What I did do, for example, on the Nabaztag page, was to add a link to
the archived plugin releases, in case somebody (for whatever weird
reason) needs to download a version in future.


>> When there is a wiki page, it seems enough to put a
>> "plugin-deprecated" label and a deprecated notice in the wiki page
>> like the Nabaztag plugin
> 
> +1

Adding "plugin-deprecated" to a wiki page prevents a plugin from
appearing in the UC, so your +1 here conflicts with your statement above
;) :D

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56475C5B.7010509%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: plugin without docu

[Christopher Orr]

This was a bit of a pain to track down — "package-parameter" isn't
hosted by jenkinsci; the source is here:
https://github.com/d3clan/package-parameter

It didn't help either that the new UI on repo.jenkins-ci.org is so slow,
and the search is now harder to use...

Anyway, it looks like a wiki page got added for that plugin this week,
but the wiki page override hadn't been removed.  I've done that now.

Now that it's been five months since wiki pages became mandatory, I
should probably run through the list again and see what else can be
removed from the current list:
https://github.com/jenkinsci/backend-update-center2/blob/4b535ec/src/main/resources/wiki-overrides.properties

Regards,
Chris


On 06/11/15 09:04, domi wrote:
> There are still tweets about plugin releases without a correct link to
> the documentation, the following Tweet leads to the “Plugin
> Documentation Missing” page
> Domi
> 
> 
>> Begin forwarded message:
>>
>> *From: *domi >
>> *Date: *4 November 2015 at 08:41:09 GMT+1
>> *To: *d...@fortysix.ch 
>> *Subject: **Tweet by Jenkins releases on Twitter*
>>
>>  *Jenkins releases (@jenkins_release
>> )*
>> 04.11.15 05:44
>> 
>> S3 package parameter plugin 1.7 dlvr.it/Cf0C2p
>>  #jenkinsci
>> 
>>
>>
>> Download  the
>> Twitter app

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/563C9569.7020603%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: 2.0 website: content track

[Christopher Orr]

Wasn't sure which of the many email threads to hang this off of, but
here's something that may be of interest...

I noticed last week that the Kotlin documentation is pretty nicely
structured, and is also a static website backed by a Git repository
(with GitHub "edit" links on each page).

>From whatever static site builder they use, they also build a
downloadable PDF version of the documentation (though I guess this is
more applicable to a programming language than it is to Jenkins).

https://kotlinlang.org/docs/reference/comparison-to-java.html
https://github.com/JetBrains/kotlin-web-site/blob/master/docs/reference/comparison-to-java.md

Regards,
Chris


On 10/10/15 01:01, Kohsuke Kawaguchi wrote:
> I'm dividing up the website conversation into several tracks. See this
> Wiki page  for
> the overall structure.
> 
> And in particular, in this thread let's focus on identifying pillars.
> 
> In the original proposal that I made, which is captured very well in
> Daniel's wiki page
> ,
> the key pillars of the website are:
> 
>   * Channels for us devs to engage the user community. Most notably blog.
>   * Documentation for new users till they get up & running; feature
> highlights and curated getting started guide
>   * Plugins, though I classified this under "things to do in the future"
> category
> 
> Gus made a pitch
> 
> that interaction among users should be the main pillar, which got a lot
> of push back. In the same pitch, he said downloads, plugins, and events
> are the other key pillars.
> 
> Bobby made a comment that he sees the extensibility part of the website
> a key pillar because it speaks to the principle & DNA of this community.
> 
> 
> Hopefully I captured it correctly. Let's keep the discussion going here.
> 
> -- 
> Kohsuke Kawaguchi
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xNDWM9bM1PGpDAzp_oeoRB8BY5gYHX4A2yvwJXt05%3Dqg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56379E92.4070107%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 proposal

[Christopher Orr]

It seems they're talking about both system configuration and job
configuration — in the next section, talking about Travis, they refer to
keeping job config in SCM (via `.travis.yml`) as a good thing.


On 23/10/15 23:39, Richard Bywater wrote:
> My impression was that they were talking about system configuration
> which presumably isn't touched in the areas you mention?
> 
> Richard.
> 
> 
> On Fri, 23 Oct 2015 10:13 pm Jesse Glick  > wrote:
> 
> On Fri, Oct 23, 2015 at 4:53 AM, d...@fortysix.ch
>   > wrote:
> > They have some points compared to jerkins:
> http://concourse.ci/concourse-vs.html#jenkins
> > ..specially:
> > - every configuration must be backed in a version control system
> > - first class support for pipelines
> 
> Yes, it is an interesting read. I think multibranch Workflow plus
> Docker integration starts to close the gap on these two bullet points.
> (See my recent webinar for background.) It is not the same as having a
> system designed according to these principles from the start.
> 
> --
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> 
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr11DM64CJYwBPga7YN3fRWz7tUqpqpgbKLucR-K2eZYpA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMui944Q9mBvbkzEx3DgQax%2Bum1UqxGG9R%2BfMV%2BVs1kV3LJctA%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/562B5F80.4050401%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: New token-macro release?

[Christopher Orr]

Excellent, thanks! :)


On 17/10/15 17:30, Oleg Nenashev wrote:
> Hi,
> 
> I've released the new version and added changelogs to the plugin's Wiki
> page.
> 
> Best regards,
> Oleg
> 
> пятница, 16 октября 2015 г., 1:54:27 UTC+3 пользователь slide написал:
> 
> I have been meaning to do a release for a while, but things have
> been CRAZY at work. You can feel free to cut a release if you want,
> I have no problems with that. It may take me a couple more weeks to
> get back to it.
> 
> slide
> 
> On Thu, Oct 15, 2015 at 3:50 PM Christopher Orr <ch...@orr.me.uk
> > wrote:
> 
> Hi all (well, this is probably most applicable to Slide),
> 
> Is there any chance of a new token-macro release coming up soon?
> 
> There are a couple of useful new features in there, which would
> be nice
> to have in a released version!
> 
> (IOW, I've added token-macro support to one of my plugins, and
> promised
> users shiny new goodness, which isn't actually available yet :)
> 
> Thanks,
> Chris
> 
> --
> 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 jenkinsci-de...@googlegroups.com .
> To view this discussion on the web visit
> 
> https://groups.google.com/d/msgid/jenkinsci-dev/56202D96.20302%40orr.me.uk
> 
> <https://groups.google.com/d/msgid/jenkinsci-dev/56202D96.20302%40orr.me.uk>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/8cee5f74-278b-4de7-aab6-e5f9bf882d38%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/8cee5f74-278b-4de7-aab6-e5f9bf882d38%40googlegroups.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5626485D.8020404%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin releases Twitter bot source?

[Christopher Orr]

Huh, true.  One post per plugin seems to come from https://dlvr.it/ and
another (very unreliably) is posted by http://twitterfeed.com/


On 20/10/15 15:09, domi wrote:
> and by the way: it also tweet every release twice…
> /Domi
> 
>> On 20 Oct 2015, at 15:07, Christopher Orr <ch...@orr.me.uk> wrote:
>>
>> Hi all,
>>
>> I just saw this, which claims Log Parser 2.0 is a new plugin:
>> https://twitter.com/jenkins_release/status/656450179571150849
>>
>> I know it's not a new plugin, and the artifactId hasn't changed, and the
>> Update Centre JSON looks good (i.e. we haven't accidentally released a
>> duplicate of the existing plugin).
>>
>> So I *assume* the Twitter bot flagged it as a new release because the
>> *groupId* changed in the POM since the last release?  It would be nice
>> to confirm this, but I don't know where the source code is, or where the
>> bot runs.
>>
>> This is just out of curiosity, so it's not really important — but I find
>> it quite a useful resource, so it would be nice to know where it runs,
>> and how contributions can be made.  Does anybody know? :)
>>
>> Regards,
>> Chris
>>
>> PS. If anyone knows where the JIRA SCM link daemon lives, that would
>> also be nice to know!
>>
>> -- 
>> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/56263C96.6070605%40orr.me.uk.
>> For more options, visit https://groups.google.com/d/optout.
> 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56264ED2.8070500%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Pull Request merge policy for core

[Christopher Orr]

On 20/10/15 13:26, Stephen Connolly wrote:
> On 20 October 2015 at 12:06, James Nord  wrote:
>>> I have some concerns about mandating a tidy-up (I note that Jesse is
>>> against rewriting the history of a PR branch as that means that GitHub
>>> hides the code review comments)
>>
>>
>> Can you explain this.  If I pushed a rebased commit the comments are still
>> there with "commented on an outdated diff" (and if the comment is still
>> applicable to the LOC is still shows) [1]
>> This is no different to comments on a commit being addressed in a future
>> commit and as such are still visible?
> 
> Well I will not speak for Jesse, so you would want to check with him
> as to his logic.
> 
> I have seen that the GitHub comment tracking feature can be
> unreliable... while it does the right thing and keeps the comments
> with the new rewritten history *most* (say 8 out of 10 times) of the
> time, there are times when it doesn't... so if you rewrite the history
> I cannot trust that all my comments will have been tracked correctly
> (especially if I have more than 10 of them... then there's a good
> chance that 2 of them were mis-tracked... and it's oh so fun trying to
> manually track comments, esp if they get "deleted" and you have to
> switch back to email threads) and I have to re-review all the changes
> to ensure that in rewriting the history you didn't inadvertently
> introduce some other side change

FWIW (I'm not involved in core dev), what I usually do with GitHub pull
requests is to squash them after the review is complete — I see no need
to pollute git history with ["wip", "cleanup", "cleanup", "address
review comments", "fix nitpicks"] — but I do this entirely locally.

i.e. I squash commits but don't then force-push that feature branch to
the remote, so I avoid wiping out the "who-committed-what-when"
notifications in the PR, and I avoid screwing up the GitHub comment
tracking.

That is, I do something like:

1. git checkout feature/whatever
2. git rebase -i HEAD~n
3. 
4. git checkout master
5. git merge feature/whatever
6. git push
7. Enter "Merged" and click "Comment & close" on the GitHub PR (if the
PR hasn't auto-closed)

In this case, the commit history and PR comments on GitHub should remain
as they were while the review was in progress.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56264C35.9070705%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin releases Twitter bot source?

[Christopher Orr]

On 20/10/15 15:15, Daniel Beck wrote:
> 
> On 20.10.2015, at 15:07, Christopher Orr <ch...@orr.me.uk> wrote:
> 
>> t would be nice
>> to confirm this, but I don't know where the source code is, or where the
>> bot runs.
>>
>> This is just out of curiosity, so it's not really important — but I find
>> it quite a useful resource, so it would be nice to know where it runs,
>> and how contributions can be made.  Does anybody know? :)
> 
> The Twitter bot just tweets the http://jenkins-ci.org/releases.rss feed.
> 
> Which gets generated here: https://ci.jenkins-ci.org/job/infra_release.rss/
> With sources here: https://github.com/jenkinsci/backend-release.rss
> 
> And that's where the group is relevant although it should not be:
> https://github.com/jenkinsci/backend-release.rss/blob/master/release.rss.groovy#L24

Nice, thanks.

Funnily enough, the release-history.json contains a `firstRelease` (and
`latestRelease`) flag, which seems to be generated correctly.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56264D8B.4070409%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: revisiting JUC in 2016

[Christopher Orr]

Yeah, I've had the same problem with trying to justify one-day
inter-continental conference trips, so being longer would help — though
note that this proposal would likely only be a two-day conference for
the majority of potential non-US participants (i.e. they're not likely
to care about Day 0).

Being adjacent to other events makes sense as well — much like happens
for a bunch of events before and after FOSDEM.


On 20/10/15 13:34, Robert Sandell wrote:
> I had a somewhat different problem, that it was hard to motivate the
> travel expense across the pond for a mere one day conference.
> A three day conference would be easier to motivate in my experience;
> previously working for a larger corporation with large investment in
> Jenkins at least.
> The first Jenkins user conference in 2011 was easy to motivate since it
> was adjacent to Java One. The others were harder.
> 
> Having one bigger one could perhaps also give some breathing room to
> other more local/smaller conferences 
> on the subject :)
> 
> /B
> 
> On Tue, Oct 20, 2015 at 1:22 PM, Manuel Jesús Recena Soto
> > wrote:
> 
> Hello James,
> 
> (reply in line)
> 
> 2015-10-20 12:03 GMT+02:00 James Nord  >:
> > Taking off my cloudbees hat and putting on my old hat being based in 
> Europe.
> >
> > Getting approval to attend conferences abroad (outside Europe) for me 
> was
> > not always easy - as it involves large travel and time lost due to 
> this.  As
> > such it was easier to go to a european conference.   I also feel that 
> yes
> > you get more people in USA-CA but that this could just a critical mass 
> and a
> > direct result of its much easier to go to something local than it is to
> > travel 9 hours around the globe.  Do you have stats of where people came
> > from in the last even - where they predominantly from the bay area?
> > In the London event I met people that where very basic users of Jenkins
> > (just starting) and it was easy for them to go to a local conference.  
> Would
> > these same users make the same investment to go somewhere accross the 
> globe
> > - I personally don't think so - which would be a big shame.
> >
> > The JAMs fill a gap - but I'm not sure that this gap is filled yet - or 
> that
> > it will be filled by next year  - certainly there is nothing in the UK 
> that
> > I know of - and even then we would need something based in the north 
> west as
> > well as somewhere around London.
> 
> I had the opportunity to attend JUG London and was a great experience.
> It would be a pity don't have this event in Europe.
> 
> As you pointed, JAM events can fill this gap.
> 
> In Spain, there are two JAM starting (Seville and Barcelona). Maybe
> someday, we can organize a bigger event. Another open source
> communities do something similar.
> 
> Regards,
> 
> > On Tuesday, October 20, 2015 at 4:51:39 AM UTC+2, Kohsuke Kawaguchi 
> wrote:
> >>
> >> Putting my CloudBees hat on, I'd like to discuss the following proposed
> >> changes to the events in 2016, where we are moving away from JUC into 
> a new
> >> model.
> >>
> >>
> >> 
> https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Revisiting+JUC+in+2016
> >>
> >> I put this up for the project meeting agenda in 1.5 week, but I hope to
> >> get discussions going well before that.
> >>
> >> --
> >> Kohsuke Kawaguchi

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56265384.20600%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: revisiting JUC in 2016

[Christopher Orr]

On 20/10/15 22:21, Kohsuke Kawaguchi wrote:
>> Yeah, I've had the same problem with trying to justify one-day
>> inter-continental conference trips, so being longer would help — though
>> note that this proposal would likely only be a two-day conference for
>> the majority of potential non-US participants (i.e. they're not likely
>> to care about Day 0).
> 
> OK, so sounds like we should brainstorm on additional activities in Day
> 0 that makes the event more attractive.

Well, it depends on how many international visitors you want or need to
attract :)


> Maybe hands on labs, plugin development class room?

Sure.  I've also been to a few conferences (mainly Android dev) where
there was a full- or half-day barcamp, which I found pretty good.


>> Being adjacent to other events makes sense as well — much like happens
>> for a bunch of events before and after FOSDEM.
> 
> OK. Do we know events in the bay area that we can piggyback on?

JavaOne, DockerCon, Velocity, perhaps?


> On 20/10/15 13:34, Robert Sandell wrote:
> > I had a somewhat different problem, that it was hard to motivate the
> > travel expense across the pond for a mere one day conference.
> > A three day conference would be easier to motivate in my experience;
> > previously working for a larger corporation with large investment in
> > Jenkins at least.
> > The first Jenkins user conference in 2011 was easy to motivate since it
> > was adjacent to Java One. The others were harder.
> >
> > Having one bigger one could perhaps also give some breathing room to
> > other more local/smaller conferences
> 
> > on the subject :)
> >
> > /B
> >
> > On Tue, Oct 20, 2015 at 1:22 PM, Manuel Jesús Recena Soto
> >   >> wrote:
> >
> > Hello James,
> >
> > (reply in line)
> >
> > 2015-10-20 12:03 GMT+02:00 James Nord  
> > >>:
> > > Taking off my cloudbees hat and putting on my old hat being
> based in Europe.
> > >
> > > Getting approval to attend conferences abroad (outside
> Europe) for me was
> > > not always easy - as it involves large travel and time lost
> due to this.  As
> > > such it was easier to go to a european conference.   I also
> feel that yes
> > > you get more people in USA-CA but that this could just a
> critical mass and a
> > > direct result of its much easier to go to something local
> than it is to
> > > travel 9 hours around the globe.  Do you have stats of where
> people came
> > > from in the last even - where they predominantly from the
> bay area?
> > > In the London event I met people that where very basic users
> of Jenkins
> > > (just starting) and it was easy for them to go to a local
> conference.  Would
> > > these same users make the same investment to go somewhere
> accross the globe
> > > - I personally don't think so - which would be a big shame.
> > >
> > > The JAMs fill a gap - but I'm not sure that this gap is
> filled yet - or that
> > > it will be filled by next year  - certainly there is nothing
> in the UK that
> > > I know of - and even then we would need something based in
> the north west as
> > > well as somewhere around London.
> >
> > I had the opportunity to attend JUG London and was a great
> experience.
> > It would be a pity don't have this event in Europe.
> >
> > As you pointed, JAM events can fill this gap.
> >
> > In Spain, there are two JAM starting (Seville and Barcelona).
> Maybe
> > someday, we can organize a bigger event. Another open source
> > communities do something similar.
> >
> > Regards,
> >
> > > On Tuesday, October 20, 2015 at 4:51:39 AM UTC+2, Kohsuke
> Kawaguchi wrote:
> > >>
> > >> Putting my CloudBees hat on, I'd like to discuss the
> following proposed
> > >> changes to the events in 2016, where we are moving away
> from JUC into a new
> > >> model.
> > >>
> > >>
> > >>
> 
> https://wiki.jenkins-ci.org/display/JENKINS/Proposal+-+Revisiting+JUC+in+2016
> > >>
> > >> I put this up for the project meeting agenda in 1.5 week,
> but I hope to
> > >> get discussions going well before that.
> > >>
> > >> --
> > >> Kohsuke Kawaguchi
> 
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop 

Plugin releases Twitter bot source?

[Christopher Orr]

Hi all,

I just saw this, which claims Log Parser 2.0 is a new plugin:
https://twitter.com/jenkins_release/status/656450179571150849

I know it's not a new plugin, and the artifactId hasn't changed, and the
Update Centre JSON looks good (i.e. we haven't accidentally released a
duplicate of the existing plugin).

So I *assume* the Twitter bot flagged it as a new release because the
*groupId* changed in the POM since the last release?  It would be nice
to confirm this, but I don't know where the source code is, or where the
bot runs.

This is just out of curiosity, so it's not really important — but I find
it quite a useful resource, so it would be nice to know where it runs,
and how contributions can be made.  Does anybody know? :)

Regards,
Chris

PS. If anyone knows where the JIRA SCM link daemon lives, that would
also be nice to know!

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56263C96.6070605%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

New token-macro release?

[Christopher Orr]

Hi all (well, this is probably most applicable to Slide),

Is there any chance of a new token-macro release coming up soon?

There are a couple of useful new features in there, which would be nice
to have in a released version!

(IOW, I've added token-macro support to one of my plugins, and promised
users shiny new goodness, which isn't actually available yet :)

Thanks,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56202D96.20302%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Hosting turbo plugin / Renaming

[Christopher Orr]

Hi there,

On 14/10/15 17:45, Roman Stoffel wrote:
> I would like to rename the  'SpoonScript Plugin'. From previous posts I
> think the procedure is to put up the plugin under the new name and then
> mark the old one as 'deprecated'.

That's more the procedure we have to go through when people needlessly
change their `artifactId` in their POM and make a release.


> The plugin is hosted here: https://github.com/turboapps/jenkins.
> However, previously that caused naming problems, so I've added a fork
> with a better name here: https://github.com/gamlerhart/turbo-script-plugin

It's not entirely clear to me what's going on here.  I *guess* you work
with the original spoonscript-plugin author (pmateusz)?  I don't think
we'd really want to deprecate any plugins without hearing from them
first.. :)

If you want to rename the plugin, the easiest thing to do isn't to
delete existing plugins and wiki pages and create everything again.  You
can just update the `` tag in the `pom.xml` file, rename the wiki
page, and update the `` tag in your POM.

In this case the `artifactId` would remain as `spoonscript`, but this
isn't really user-visible within Jenkins.  Plus that would allow
existing users to upgrade seamlessly to the renamed version.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/561E95EA.7050203%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin, attention-plugin

[Christopher Orr]

Yeah, this sounds like it should be an extension of the Claim plugin.

But it seems that getting a jenkinsci repo and following the regular
procedure has been ignored, and a version of the plugin has already been
released, and a wiki page created...

https://twitter.com/jenkins_release/status/652525957207592960


On 09/10/15 13:43, Baptiste Mathus wrote:
> Hi,
> 
> Trying to understand what your plugin does (a README could be added to
> give basic info + link to wiki ?)
> 
> IIUC, it is designed to let people tell they volunteer to fix a build?
> If so, how does it compare to the Claim Plugin? Or Warnings maybe? 
> 
> Cheers
> 
> 2015-10-09 13:25 GMT+02:00 Marcus Jacobsson  >:
> 
> Hi
> 
> We've are working on releasing a plugin we've used internally and
> making it public. We've committed it to my github account but would
> like to move it to the jenkinci github instead. Could someone help
> us setup an repository.
> 
> It's a plugin we use internally to help tracking red builds.
> 
> The current project URL:
> https://github.com/hanabishi/attention-plugin
> 
> Github IDs:
> hanabishi
> patrikha
> olofek
> miphip 
> 
> /Marcus

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5618BA21.2060504%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: [2.0] Website rebump

[Christopher Orr]

On 08/10/15 21:44, Baptiste Mathus wrote:
> 2015-10-08 20:36 GMT+02:00 Gus Reiber  >:
> Personally, I think the demonstration of Jenkins extensibility
> is more impressive than the saying of it. And, that demonstration is
> the plugins. Thus rather than an article that say 'hey look, we are
> extensible', I would think we would just want to go straight into
> showing off the plugins, just as http://getbootstrap.com/ goes
> straight into showing you Bootstrap or the Play store goes straight
> into showing you the Andoid apps or http://www.deviantart.com/ goes
> straight into showing you the art. To me, showing off the plugins
> screams extensibility and the content stays fresh by virtue of the
> fact that people are interacting with the plugins themselves. 
> 
> You convinced me Gus. 
> 
> IMO, we can indeed show off the plugins, showing the enormous numbers of
> themes where Jenkins can actually change its behaviour by being
> extensible and having been extended by plugins.

My question is: how do you "show off a plugin"?

Jenkins plugins aren't Bootstrap themes, nor are they Android apps — the
most you could show off for the vast majority of plugins would be a
screenshot of an ugly configuration form.

I'm not sure what "the content stays fresh" means in this context, and
who (and how) people are "interacting with the plugins" on the website?

Is the idea to have specially-written content (i.e. separate from the
wiki page that every plugin has), which highlights key plugins on the
main website?

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5616D1D0.4050609%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Deleting a renamed wiki page for Phabricator Plugin

[Christopher Orr]

Yeah, sorry, this is a known issue with the wiki caching:
https://issues.jenkins-ci.org/browse/INFRA-301


On 06/10/15 20:50, Aiden Scandella wrote:
> I renamed a month ago or so and it's still there.
> 
> On Tuesday, October 6, 2015 at 11:03:42 AM UTC-7, Daniel Beck wrote:
> 
> There's a caching layer in front of Confluence. Just give it a bit
> of time.
> 
> On 06.10.2015, at 19:47, Aiden Scandella  > wrote:
> 
> > Greetings,
> >
> > I renamed the "Phabricator Plugin" to "Phabricator Differential
> Plugin" to provide more clarity around what the plugin does. There
> are now two wiki pages, which is confusing:
> >
> > https://wiki.jenkins-ci.org/display/JENKINS/Phabricator+Plugin
> 
> >
> 
> https://wiki.jenkins-ci.org/display/JENKINS/Phabricator+Differential+Plugin
> 
> 
> 
> >
> > When I try to edit the old one
> (https://wiki.jenkins-ci.org/display/JENKINS/Phabricator+Plugin
> ) it
> redirects me to the new one, so I'm not sure how to fix this.
> >
> > Any JIRA experts/admins here?
> >
> > Thanks,
> > Aiden
> >
> > --
> > 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 jenkinsci-de...@googlegroups.com .
> > To view this discussion on the web visit
> 
> https://groups.google.com/d/msgid/jenkinsci-dev/b0012c9d-7df9-468b-bd52-7d8cf36dad1c%40googlegroups.com
> 
> .
> 
> > For more options, visit https://groups.google.com/d/optout
> .
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/94635ac5-8021-4d85-b015-41d3eaed1361%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56146430.10705%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Duplicate Code Scanner Plug-in

[Christopher Orr]

This happened because plugin names are now taken from the pom.xml rather
than the wiki page name.

So the better fix would be to update the  tag in the POM for the
next release.

Regards,
Chris


On 29/09/15 15:01, Arnaud Héritier wrote:
> Hi Ullrich,
> 
>   I just noticed that the plugin named in the update center `Duplicate
> Code Scanner Plug-in ` is in fact
> the DRY plugin : https://wiki.jenkins-ci.org/display/JENKINS/DRY+Plugin
> 
>   Maybe you could rename the wiki page to avoid look for a dry plugin in
> the update center (if you use the search feature of the update center
> you find it because it is returned from its identifier but in the UI
> it's not easy to find it)
> 
> 
> ​
>   cheers,
> 
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--RyuY-NKB3rV%2B%3D8K67OEThwFxx%2BgPZ67ttNcE1i6-gvw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/560D5002.1060300%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: get build number

[Christopher Orr]

Most likely the plugin has a perform() method with an AbstractBuild.

Call getNumber() on the build.

http://javadoc.jenkins-ci.org/hudson/tasks/BuildStepCompatibilityLayer.html#perform(hudson.model.AbstractBuild,
hudson.Launcher, hudson.model.BuildListener)
http://javadoc.jenkins-ci.org/hudson/model/Run.html#getNumber()


On 03/09/15 12:21, Thilina Madhusanka wrote:
> Hi
> 
> im trying to modify a plugin, that plugin generate a report i need to
> add the build number to the report name
> 
> thanks
> 
> On Thursday, September 3, 2015 at 3:41:50 PM UTC+5:30, Victor Martinez
> wrote:
> 
> Alright, 
> 
> Are you developing a new jenkins plugin? Or you mean configuring a
> jenkins job? If so, please refs the below page:
> 
> - 
> https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables
> 
> 
> 
> And also use jenkinsci-users mailing list or IRC for such topics
> since this mailing list is for Jenkins core and plugins development
> discussions
> 
> Cheers
> 
> 
> 
> On Thursday, 3 September 2015 10:27:42 UTC+2, Thilina Madhusanka wrote:
> 
> Hi
> 
> thanks for the reply
> 
> im new to this. my plugin will start as a post build option in
> jenkis so which  methods should i use? 
> 
> can u tell me how can i get the number in string or int format?
> 
> thanks.
> 
> On Thursday, September 3, 2015 at 12:10:49 PM UTC+5:30, Victor
> Martinez wrote:
> 
> Hi,
> 
>  It depends on what you need to do. Check the below javadoc:
> 
>  - From a particular Jenkins job you can query its latest
> build:
> 
> http://javadoc.jenkins-ci.org/hudson/model/AbstractProject.html#getLastBuild()
> 
> 
>  
>  - From a particular Job build you can query its current
> build number:
> http://javadoc.jenkins-ci.org/hudson/model/Run.html#number
> 
> 
> Cheers
> 
> 
> On Thursday, 3 September 2015 08:30:20 UTC+2, Thilina
> Madhusanka wrote:
> 
> hi
> 
> Is there a method to retrieve current  build number for
> a plugin to use. ?
> 
> thanks
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3ececc8d-e84b-4233-8ac6-104e1dc152f5%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55E83E7A.6030901%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Hosting a new Plugin - Percentage DiskSpace usage column

[Christopher Orr]

Or at least it could be part of the Extra Columns plugin, which is an
existing collection of various useful columns.
https://wiki.jenkins-ci.org/display/JENKINS/Extra+Columns+Plugin

If this does get added as a new plugin, it would really need to have a
different name, as "PercentageColumn" gives zero information.

Also, it seems like it would make more sense if the column was called "%
Free Disk Space", and showed the percentage of *remaining* disk space —
consistent with the other disk space and memory usage columns.


On 02/09/15 16:40, domi wrote:
> From an enduser perspective I think these two things provide similar
> information (one just more fine grained) and I would rather have both in
> the same plugin - the name DiskUsage Plugin just screens for this
> functionality
> …just my 2 cents
> /Domi
> 
> On 02 Sep 2015, at 16:31, Victor Martinez  > wrote:
> 
>> Exactly, it does provide a simple use case for monitoring total disk
>> space & percentage of usage since Jenkins doesn't provide those details
>> Víctor
>>
>> On Wednesday, 2 September 2015 13:52:22 UTC+2, Richard Bywater wrote:
>>
>> I'm not sure they are the same thing. If I read it correctly, one
>> (Disk Usage Plugin) appears to be the amount of usage a job uses,
>> whilst the % Disk Space plugin proposed here simply translates the
>> free/total disk space to a percentage on the Nodes list.
>>
>> Richard.
>>
>> On Wed, 2 Sep 2015 at 23:29 domi 
>> wrote:
>>
>> would this not make more sense to be included
>> in https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin
>>  ?
>> /Domi
>>
>> On 02 Sep 2015, at 11:58, Victor Martinez
>>  wrote:
>>
>>> I've already created the wiki
>>> page: 
>>> *https://wiki.jenkins-ci.org/display/JENKINS/PercentageColumn+Plugin
>>> 
>>> *
>>>
>>> Cheers
>>> *
>>> *On Tuesday, 1 September 2015 23:26:35 UTC+2, Victor Martinez
>>> wrote:
>>>
>>> Hi there,
>>>
>>> I've been working on some Jenkins automation to monitor
>>> those slaves and have some specific disk space cleanup
>>> policy, rather than using absolute diskspace usage
>>> metrics I wanted to use % disk space usage column in the
>>> Manage Nodes page.
>>>
>>>   * Github
>>> repo: *https://github.com/v1v/percentagecolumn-plugin
>>> *
>>>   * repository name:* percentagecolumn-plugin*
>>>   * Github user: *v1v*
>>>   * jenkins-ci.org : *v2v*
>>>   * Description: *This plugin just shows the percentage
>>> of disk space usage column on "Manage Nodes" page.*
>>>   * Wiki: 
>>> *https://wiki.jenkins-ci.org/display/JENKINS/PercentageColumn+Plugin
>>> 
>>>  (Not
>>> Yet)*
>>>
>>> Looking forward for having some feedback.
>>>
>>> Thanks,
>>>
>>> Víctor
>>>
>>>
>>> -- 
>>> 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 jenkinsci-de...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/11ecf834-9753-4fd7-a1a1-9311d69ccb57%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout
>>> .
>>
>>
>> -- 
>> 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 jenkinsci-de...@googlegroups.com
>> .
>> To view this discussion on the web visit
>> 
>> https://groups.google.com/d/msgid/jenkinsci-dev/7FE97DEE-386C-4931-8382-99E398FF26D7%40fortysix.ch
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout
>> .
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google
>> 

Re: New `Datadog Plugin` release 0.1.1 not showing up in Update Center

[Christopher Orr]

The plugin seems to be appearing on several of the mirrors, in the
regular update centre JSON.

Was the wiki page for this plugin always a child of the "Plugins" wiki
page?  It seems like it was, but the update centre generator was
complaining about this for a while.  Though looking through the past few
days of update centre logs didn't reveal anything strange.

But it seems like it should start appearing now.

Regards,
Chris


On 31/08/15 19:29, John Zeller wrote:
> Yeah, I noticed all those same things :/
> 
> To release 0.1.1, I used the command `mvn release:prepare
> release:perform`. Perhaps there is something awry in our pom.xml
> ? I too
> am new to plugin development, but it seems like I reproduced all the
> steps mentioned in the Hosting Plugins
>  wiki
> 
> On Monday, August 31, 2015 at 1:23:02 PM UTC-4, R Tyler Croy wrote:
> 
> (replies inline)
> 
> On Mon, 31 Aug 2015, John Zeller wrote:
> 
> > I tried to release our
> (https://github.com/jenkinsci/datadog-plugin
> ) new
> > plugin (version 0.1.1) on Friday, and I am still not seeing it in the
> > Update Center, or the `update-center.json`. However, it does show
> up in the
> > maven release repo... Our artifact ID is `datadog-build-reporter`.
> >
> > Does anyone have any idea what may have gone wrong here?
> 
> 
> The update center generation appears to be working fine from the
> infrastructure
> side of things.
> 
> I also see the artifact in updates.jenkins-ci.org
>  fwiw.
> 
> 
> 
> I see the datadog-build-reporter in the stable (LTS) update-center.json
> (http://ftp-nyc.osuosl.org/pub/jenkins/updates/stable/update-center.json
> )
> but
> not in the "normal" update-center.json. I'm not familiar enough with
> the
> current means of plugin deployment so perhaps you may have
> inadvertently only
> released it for LTS users?
> 
> Cheers
> - R. Tyler Croy
> 
> --
>  Code: 
>   Chatter: 
> 
>   % gpg --keyserver keys.gnupg.net 
> --recv-key 3F51E16F
> --
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3dc83451-10eb-4a2e-ad19-77c581120132%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55E4A31F.7080002%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Requesting hosting for plugin (Nouvola DiveCloud)

[Christopher Orr]

Hi there,

Your repo has been forked; you have commit access here:
https://github.com/jenkinsci/nouvola-divecloud-plugin

There's a JIRA component for your plugin, too.

You might want to look at either integrating your plugin with the
Credentials Plugin, or at least using
http://javadoc.jenkins-ci.org/byShortName/Secret instead of String to
store your credentials.

Regards,
Chris


On 26/08/15 07:35, Shawn MacArthur wrote:
 Any updates on this? Please let me know if any changes are needed before
 getting access, thanks!
 
 On Thursday, August 20, 2015 at 7:25:53 PM UTC-7, shawn.m...@nouvola.com
 wrote:
 
 Hi,
 
 I'm requesting hosting for a plugin. Here is the information:
 
   * The URL to your finished plugin repository on GitHub
 
 https://github.com/prossaro/Nouvola-DiveCloud-Jenkins-Plugin
 https://github.com/prossaro/Nouvola-DiveCloud-Jenkins-Plugin
 
   * The name the repository should have (if it doesn't already have
 a clear name), e.g. snapchat-notification-plugin
 
 nouvola-divecloud-plugin
 
   * Your personal GitHub username, if different from the username in
 the repo URL (GitHub organisation IDs are not supported)
 
 smacarth
 
   * Your jenkins-ci.org http://jenkins-ci.org username, so we can
 make you the default assignee for the JIRA issue tracker
 component for your plugin
 
 smacarthur
 
   * A description of what the plugin does, and what makes it
 different from other similar plugins
 
 The plugin enables you to create a build step which will run a
 performance test on Nouvola DiveCloud (www.nouvola.com
 http://www.nouvola.com). DiveCloud lets you test your site or app
 with a specific load and geolocation, and provides insight into
 performance issues.
 
 
 -
 
 Thank you!
 
 Best,
 
 Shawn
 
 -- 
 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 jenkinsci-dev+unsubscr...@googlegroups.com
 mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/16fc71df-3473-4392-9952-67be8ffb5645%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-dev/16fc71df-3473-4392-9952-67be8ffb5645%40googlegroups.com?utm_medium=emailutm_source=footer.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55DD6405.3020209%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Granting access to a plugin repository

[Christopher Orr]

Thanks. Also done!


On 26/08/15 23:54, Dawid Malinowski wrote:
 Hi
 
 Same as my github account: dawidmalina
 
 26 sie 2015 23:44 Christopher Orr ch...@orr.me.uk
 mailto:ch...@orr.me.uk napisał(a):
 
 Done!
 
 Dawid: If you give us your jenkins-ci.org http://jenkins-ci.org
 account username, we can make
 you the default assignee on JIRA for this plugin, too.
 
 Regards,
 Chris
 
 
 On 26/08/15 21:56, Jørgen Tjernø wrote:
  (Trying this again after rejoining jenkinsci-dev.)
 
  Could someone please grant commit access to
  jenkinsci/environment-script-plugin to
 https://github.com/dawidmalina? I
  have not worked on the plugin for three years, and I have not been
 using
  it for at least two, so it's about time someone else took over, and
  Dawid has expressed interest in updating it.
 
  Thank you!
 
  (Please include Dawid in CC on replies, as I don't know if he
 subscribes
  to jenkinsci-dev.)
 
  - Jørgen.
 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55DE35FB.5080006%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Granting access to a plugin repository

[Christopher Orr]

Done!

Dawid: If you give us your jenkins-ci.org account username, we can make
you the default assignee on JIRA for this plugin, too.

Regards,
Chris


On 26/08/15 21:56, Jørgen Tjernø wrote:
 (Trying this again after rejoining jenkinsci-dev.)
 
 Could someone please grant commit access to
 jenkinsci/environment-script-plugin to https://github.com/dawidmalina? I
 have not worked on the plugin for three years, and I have not been using
 it for at least two, so it's about time someone else took over, and
 Dawid has expressed interest in updating it.
 
 Thank you!
 
 (Please include Dawid in CC on replies, as I don't know if he subscribes
 to jenkinsci-dev.)
 
 - Jørgen.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55DE3335.10805%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub link issue

[Christopher Orr]

On 25/08/15 15:42, Aaron Johnson wrote:
 On this page
 (https://wiki.jenkins-ci.org/display/JENKINS/NeoLoad+Plugin) there's a
 link to GitHub that's incorrect. It's
 https://github.com/jenkinsci/neoload-jenkins-plugin; but it should be
 https://github.com/jenkinsci/neoload-plugin;
 
 I can't see where to change this directly because the whole Plugin
 Information section is generated by the line
 {jenkins-plugin-info:pluginId=neoload-jenkins-plugin}. Anyone know
 where I would go to update the link?

Plugin repositories are usually named like artifact-id-plugin, and
so that's what the infobox (generally) tries to link to by default.

But for plugins that have bad artifact IDs, the repository name can be
overridden via the sourceDir parameter.  I've updated this wiki page
to include this.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55DC73DC.6080307%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request hosting for plugin

[Christopher Orr]

On 21/08/15 12:44, Catalin Luta wrote:
 We do realize that some people would require the functionality that JIRA
 Test Result Publisher has, but there would be two options for that:
 - use both plugins concurrently
 - add the functionality of the Result Publisher plugin to our own

The second option could be possible — I believe there have been some
plugins that have replaced (or are intended to replace) existing
plugins, where the new plugin includes the existing plugin's features,
and takes over the existing plugin's artifact ID, allowing existing
users to upgrade.

But in this case, it needs to be made sure that the new plugin migrates
users' settings from the existing plugin correctly.


 I, for one, would suggest adding the functionality to our
 infrastructure, because that would take less time to achieve and we have
 a more robust infrastructure. 

Robust infrastructure and a GitHub repository with zero tests in it
don't really go together IMO ;)

I'm sure adding the existing code to your plugin without replacing the
existing plugin would take less time for *you*, but it would be
terrible for everyone else, and that's why we want to prevent plugin
proliferation.

So (if you want to release the plugin via the Jenkins update centre),
taking over the existing plugin and including its functionality might be
the best solution.

Regards,
Chris

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55D7AEF6.3060303%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: How to build a Maven project by Eclipse using Jenkins?

[Christopher Orr]

I agree with the question why?, but in any case, you're on the wrong
mailing list.  Try jenkinsci-users.


On 21/08/15 21:54, renatoalb12 wrote:
 I have to start a Jenkins Job when I build a project by Eclipse.
 
 Someone can help me?


-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55D7B105.7010709%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: ez-templates: Can a inheriting job override the build steps?

[Christopher Orr]

You're on the wrong mailing list.  Try jenkinsci-users.


On 21/08/15 19:17, pratibha natani wrote:
 Hi,
 
 
 My build has 10 build steps (Execute shell script ) out of which i want
 to keep the first 4 in a template (in section Build -execute shell  )
 as they are common for most of my builds and the remaining 6 in the
 implementing job itself in the Build section Execute Shell.
 
 But I noticed whenever i save the implementing job, its steps are
 overwritten by that of template. Is there a way to get around this while
 still using template for the common steps? 
 
 thanks
 pratibha

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55D7B079.6040405%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Jira Account verification

[Christopher Orr]

As you can see, sending unsubscribe to everyone on this mailing list
doesn't work.

To unsubscribe, follow the instructions that are included at the bottom
of every email.


On 18/08/15 17:58, Amedee Van Gasse wrote:
 Unsubscribe
 
 On Aug 18, 2015 15:27, Larry Shatzer, Jr. lar...@gmail.com
 mailto:lar...@gmail.com wrote:
 
 I'll have to leave that to Kohsuke to dig into.
 
 On Tue, Aug 18, 2015 at 4:33 AM, 'Lucy' via Jenkins Developers
 jenkinsci-dev@googlegroups.com
 mailto:jenkinsci-dev@googlegroups.com wrote:
 
 Interesting
 
 I am able to log in to https://jenkins-ci.org/account just fine
 with my account, but the same account in Jira gives me a Sorry,
 your username and password are incorrect - please try again. error.
 
 
 -Lucy-
 
 On Mon, Aug 17, 2015 at 2:51 PM, Larry Shatzer, Jr.
 lar...@gmail.com mailto:lar...@gmail.com wrote:
 
 Lucy,
 
 I see your username lucymhdavies, but the email address is
 l...@lucymhdavies.com http://lucymhdavies.com, is that
 correct? The account is already there, do you need the
 password reset?
 
 On Sat, Aug 15, 2015 at 3:55 PM, Lucy Davies
 strawberryuto...@googlemail.com
 mailto:strawberryuto...@googlemail.com wrote:
 
 Me too.
 
 I signed up on https://jenkins-ci.org/account/ with
 username: lucymhdavies and email address
 strawberryutopia (at) googlemail (dot) com
 
 On Saturday, 14 February 2015 12:30:12 UTC, Nikolaus
 Demmel wrote:
 
 Hi,
 
 I just wanted to sign up for an account on the
 Jenkins Jira.
 
 I was told that “due to the spam problem” there was
 need for additional verification and that I should
 contact this group.
 
 Can someone please enable my account?
 
 Email I signed up with: nikolaus (at)
 nikolaus-demmel (dot) de
 
 Thanks everyone!
 
 Kind regards,
 Nikolaus Demmel
 
 -- 
 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 jenkinsci-dev+unsubscr...@googlegroups.com
 mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CALhozi-cCgj4OPft1GSsHavy0k3aTz64Q%3DdyFaw-RGRZ%2BOB_yA%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-dev/CALhozi-cCgj4OPft1GSsHavy0k3aTz64Q%3DdyFaw-RGRZ%2BOB_yA%40mail.gmail.com?utm_medium=emailutm_source=footer.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55D357D8.800%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for hosting a plugin for QF-Test integration

[Christopher Orr]

This plugin doesn't seem to be a build tool, so it doesn't seem like
adding it to that section makes sense?

There probably should be a test tools category on that page, but I
don't believe that exists (yet).

In any case, plugins are shown on that page (and categorised in the
Jenkins Update Centre) based on the labels the wiki page has — take a
look at the other plugins in the relevant category.

Regards,
Chris


On 14/08/15 11:22, Thomas Max wrote:
 Hello Daniel,
 
 thanks for you help.
 I've added the original content of the wiki page again.
 
 How can I add my plugin to the
 https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Buildtools
 page.
 
 Best regards,
  Thomas
 
 
  Original Message 

 On 13.08.2015, at 16:25, Thomas Max thomas@qfs.de wrote:

 I've added the wiki page as described. Could you guide me how to make
 it available again? Should I republish the wiki page or can you fix
 the DB issue ?

 It's like the page never existed, the data has been lost. See:
 https://jenkins-ci.org/content/update-wiki-and-issue-tracker-outage

 I recreated it with a very short description to make the plugin
 available during the next update center generator run. It's probably
 best if you just add the content to it again. I archived the cached
 text before I recreated it, contact me directly and I'll send it to you.

 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55CDBA50.20503%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for Commit access[jigomerge-plugin]

[Christopher Orr]

Done.  You should probably get an email from GitHub inviting you to the
repo.

-Chris


On 06/08/15 16:27, Smruti Mohapatra wrote:
 Hi,
 
 I made a pull request for the jigomerge-plugin and have not seen any
 response in more than a week now. Would it be possible to grant me the
 commit access ? The fix is pretty straightforward and I already have the
 fix working for me on our jenkins instance.
 
 My github account name is smrutimo, and I would like to contribute to
 jenkinsci/jigomerge-plugin.
 
 Thanks  Regards,
 Smruti..
 
 -- 
 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 jenkinsci-dev+unsubscr...@googlegroups.com
 mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CABSoZfCpm%2BQ5fqh1qkEzhAithDrV-bW0czSb1fBPhva9D6MeWA%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-dev/CABSoZfCpm%2BQ5fqh1qkEzhAithDrV-bW0czSb1fBPhva9D6MeWA%40mail.gmail.com?utm_medium=emailutm_source=footer.
 For more options, visit https://groups.google.com/d/optout.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55CB216C.1080905%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.