RE: Request for new Plugin hosting

[Olivier Picciotto]

Hello,



Plugin has been released on
https://github.com/jenkinsci/convertigo-mobile-platform-plugin/tree/convertigo-mobile-platform-1.0



Are other steps needed to make it appear on the Jenkins plugin repo ?



Thanks

Olivier





*De :* jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com]
*De la part de* Oleg Nenashev
*Envoyé :* mercredi 16 septembre 2015 10:42
*À :* Jenkins Developers 
*Objet :* Re: Request for new Plugin hosting



Seems Convertigo has several products, so probably it makes sense to add
something else to the plugin ID. "ci" seems to be also vague for me,
because the plugin could be used for CD and other methodologies and
marketing buzz-words.



What about "convertigo-madp" or "convertigo-mobile-platform"?


вторник, 15 сентября 2015 г., 7:50:39 UTC+3 пользователь Olivier Picciotto
написал:

Hello,



Any news about this request ?



Kind Regards

Olivier



-- 
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/lvi8CGnS9Bo/unsubscribe.
To unsubscribe from this group and all its topics, 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/4def2c83-8436-4ec1-ac7d-e0c59f1c8536%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/4c291ee58f4efc33706a0c634a481557%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Request for new Plugin hosting

[Olivier Picciotto]

Thanks,



Yes the Wikipage is here ;

https://wiki.jenkins-ci.org/display/JENKINS/Convertigo+Mobile+Platform+Plugin



We submitted yesterday…  I hope it will appear soon : )



Thanks

Olivier



*De :* jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com]
*De la part de* Oleg Nenashev
*Envoyé :* jeudi 24 septembre 2015 11:30
*À :* JenkinsCI Developers 
*Objet :* Re: Request for new Plugin hosting



Hi,



All steps are described here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins

At least there should be a valid Wiki Page for the plugin.



If everything is correct, it will appear in the update center within
several hours.



Best regards,

Oleg





On 24 Sep 2015, at 12:27, Olivier Picciotto  wrote:



Hello,



Plugin has been released on
https://github.com/jenkinsci/convertigo-mobile-platform-plugin/tree/convertigo-mobile-platform-1.0



Are other steps needed to make it appear on the Jenkins plugin repo ?



Thanks

Olivier





*De :* jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com
] *De la part de* Oleg Nenashev
*Envoyé :* mercredi 16 septembre 2015 10:42
*À :* Jenkins Developers 
*Objet :* Re: Request for new Plugin hosting



Seems Convertigo has several products, so probably it makes sense to add
something else to the plugin ID. "ci" seems to be also vague for me,
because the plugin could be used for CD and other methodologies and
marketing buzz-words.



What about "convertigo-madp" or "convertigo-mobile-platform"?


вторник, 15 сентября 2015 г., 7:50:39 UTC+3 пользователь Olivier Picciotto
написал:

Hello,



Any news about this request ?



Kind Regards

Olivier



-- 
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/lvi8CGnS9Bo/unsubscribe.
To unsubscribe from this group and all its topics, 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/4def2c83-8436-4ec1-ac7d-e0c59f1c8536%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
https://groups.google.com/d/topic/jenkinsci-dev/lvi8CGnS9Bo/unsubscribe.
To unsubscribe from this group and all its topics, 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/4c291ee58f4efc33706a0c634a481557%40mail.gmail.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
https://groups.google.com/d/topic/jenkinsci-dev/lvi8CGnS9Bo/unsubscribe.
To unsubscribe from this group and all its topics, 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/ED1BF323-FAF1-4CD6-BDE9-38CEB01BF664%40gmail.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/023ea6a18d965d85f012b82511def956%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Hosting a new Plugin - Percentage DiskSpace usage column

[Victor Martinez]

Hi,
   any news?
Thanks
On Saturday, 19 September 2015 13:44:52 UTC+2, Victor Martinez wrote:
>
> Alright, I've already renamed, further details:
>
>- Github repo: *https://github.com/v1v/percentage-du-node-column-plugin 
>*
>- Plugin name:* percentage-du-node-column*
>- 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/Percentage+Disk+Space+Node+Column+Plugin
>  
>
> *
>
> Let me know if you need anything else.
>
> Cheers
>
> On Saturday, 19 September 2015 01:52:31 UTC+2, Daniel Beck wrote:
>>
>> The general naming convention (often broken, but still) would result in 
>> percentage-du-node-column as the artifactID, and 
>> percentage-du-node-column-plugin as the GitHub repo name. 
>>
>> On 18.09.2015, at 21:05, Victor Martinez  wrote: 
>>
>> > It's exactly the same implementation as NodeMonitor except the % part 
>> without any threshold yet. I'll code that part later on. 
>> > 
>> > I believe the Percentage-du-node-column-plugin name is more 
>> descriptive, so thanks for that suggestion. If we agree about that name 
>> then I'll rename it again. 
>> > 
>> > Thanks again 
>> > 
>> > On Friday, 18 September 2015 16:33:27 UTC+2, Daniel Beck wrote: 
>> > It uses % rather than the absolute byte value, and is therefore more 
>> useful when you have vastly different nodes. 
>> > 
>> > E.g. the 50GB workspaces on the 2TB slave will require a different 
>> take-this-offline threshold than the 20MB workspaces on the 20GB VM. 
>> > 
>> > OTOH is doesn't tell you exactly how much is free. 
>> > 
>> > On 18.09.2015, at 16:30, Kanstantsin Shautsou  
>> wrote: 
>> > 
>> > > Have no time to read code, but isn't it the same that internal 
>> NodeMonitor do? It checks disk space on different OSs. 
>> > > 
>> > > -- 
>> > > 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/e14407cc-8a1b-49c0-a454-6df8164d5c06%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/817c2b9b-476d-4341-9e22-81506221b882%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/131ff600-a6e8-41d6-af4e-6cc18c80648f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new Plugin hosting

[Oleg Nenashev]

Hi,

All steps are described here: 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins 

At least there should be a valid Wiki Page for the plugin.

If everything is correct, it will appear in the update center within several 
hours.

Best regards,
Oleg


> On 24 Sep 2015, at 12:27, Olivier Picciotto  wrote:
> 
> Hello,
>  
> Plugin has been released on 
> https://github.com/jenkinsci/convertigo-mobile-platform-plugin/tree/convertigo-mobile-platform-1.0
>  
> 
>  
> Are other steps needed to make it appear on the Jenkins plugin repo ?
>  
> Thanks
> Olivier
>  
>   <>
> De : jenkinsci-dev@googlegroups.com  
> [mailto:jenkinsci-dev@googlegroups.com 
> ] De la part de Oleg Nenashev
> Envoyé : mercredi 16 septembre 2015 10:42
> À : Jenkins Developers  >
> Objet : Re: Request for new Plugin hosting
>  
> Seems Convertigo has several products, so probably it makes sense to add 
> something else to the plugin ID. "ci" seems to be also vague for me, because 
> the plugin could be used for CD and other methodologies and marketing 
> buzz-words.
>  
> What about "convertigo-madp" or "convertigo-mobile-platform"?
> 
> вторник, 15 сентября 2015 г., 7:50:39 UTC+3 пользователь Olivier Picciotto 
> написал:
>>> Hello, 
>>  
>> Any news about this request ?
>>  
>> Kind Regards
>> Olivier
>>  
> 
> -- 
> 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/lvi8CGnS9Bo/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/4def2c83-8436-4ec1-ac7d-e0c59f1c8536%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 
> https://groups.google.com/d/topic/jenkinsci-dev/lvi8CGnS9Bo/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/4c291ee58f4efc33706a0c634a481557%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/ED1BF323-FAF1-4CD6-BDE9-38CEB01BF664%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Slave Error

[Sunny Kumar]

Hello All,
I am getting an error in jenkins slave... " java.io.IOException: An 
existing connection was forcibly closed by the remote host"Please 
suggest possible solutions..Any help is highly 
appreciatedThanks in advanced

-- 
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/924cf090-84c3-442b-be42-a1325fcc99ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to become maintainer of SeleniumHtmlReportPublisher

[Stefan Lorenz]

Do I have to request something else or do I just have to wait?

2015-09-15 18:55 GMT+02:00 Stefan Lorenz :

>
> If there is something to improve or if there are issues to solve, I think
> can do that...
>
> Jglick mentioned that I should ask here for the maintainer role..
>
>
> Am Dienstag, 15. September 2015 13:48:25 UTC+2 schrieb Daniel Beck:
>>
>> Hi Stefan,
>>
>> it looks like the plugin has been abandoned with the last activity years
>> ago, so that should definitely be possible.
>>
>> Still, CCing the previous maintainer.
>>
>> Just to clarify, you'd like to become maintainer, i.e. work further on
>> improving the plugin rather than just merging your PR and moving on?
>>
>> Daniel
>>
>> On 15.09.2015, at 09:31, Stefan Lorenz  wrote:
>>
>> > Hi,
>> >
>> > I recently worked on the SeleniumHtmlReportPublisher plugin to extend
>> it for working together with Workflow plugin.
>> > It now implements SimpleBuildStep and has some more tests.
>> > The pull request is ready to merge but it seems that the current
>> maintainer has abandoned this project, he also didn't respond to email.
>> >
>> > So is it possible for me to become the maintainer?
>> >
>> > Regards,
>> > Stefan
>> >
>> >
>> > https://github.com/jenkinsci/seleniumhtmlreport/pull/4
>> > https://issues.jenkins-ci.org/browse/JENKINS-28388
>> >
>> > --
>> > 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/64db6761-9d64-4c8a-895f-7ca82a441179%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
> https://groups.google.com/d/topic/jenkinsci-dev/UGh5JSGvawc/unsubscribe.
> To unsubscribe from this group and all its topics, 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/e074008a-5c5a-4be3-86d2-553ff09540c5%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/CAA939myPLgWqRTeOiYdVMpXuVzPzpciRwVtRSdW8Fh4fe%2B0YdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using Windows Jenkins installer prevent multiple services and installations

[Claus Schneider]

Adding screen dump...

On Thursday, September 24, 2015 at 2:50:29 PM UTC+2, Claus Schneider wrote:
>
> Hi..
>
> I just tried to make two installations on the same Windows (10) machine 
> using the http://mirrors.jenkins-ci.org/windows/latest version. I use 
> this way as it makes it easy to manage the service (stop start install 
> uninstall ). 
>
> I have done it several times before where I 'only' came across the 'port', 
> service name and service id is fixed. Can we make this an option in the 
> installer that is then added/updated to the jenkins.xml file?
>
> .. But now it is impossible!! :( It looks like it is a change between 
> 1.605 and now 1.629 / 1.630. I cannot make two installation as the second 
> installation only offers to 'Repair' or 'Remove'. I could like detection if 
> a current is installed and provide an option to install an additional 
> instance setting a new app name(jenkins++, directory, port 
> ,service-id and service name.
>
> I am find with defaults setting it to what it is today, but just give the 
> option of changing it during installation.
>
> best regards
> Claus Schneider
> Praqma A/S, Denmark
>

-- 
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/8cb6229d-f336-40e5-bafe-1d104f4fe99f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Using Windows Jenkins installer prevent multiple services and installations

[Claus Schneider]

Hi..

I just tried to make two installations on the same Windows (10) machine 
using the http://mirrors.jenkins-ci.org/windows/latest version. I use this 
way as it makes it easy to manage the service (stop start install uninstall 
). 

I have done it several times before where I 'only' came across the 'port', 
service name and service id is fixed. Can we make this an option in the 
installer that is then added/updated to the jenkins.xml file?

.. But now it is impossible!! :( It looks like it is a change between 1.605 
and now 1.629 / 1.630. I cannot make two installation as the second 
installation only offers to 'Repair' or 'Remove'. I could like detection if 
a current is installed and provide an option to install an additional 
instance setting a new app name(jenkins++, directory, port 
,service-id and service name.

I am find with defaults setting it to what it is today, but just give the 
option of changing it during installation.

best regards
Claus Schneider
Praqma A/S, Denmark

-- 
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/37e091ff-45ec-4551-a98e-c17c46b1aa3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Hosting a new Plugin - Percentage DiskSpace usage column

[Daniel Beck]

Done: https://github.com/jenkinsci/percentage-du-node-column-plugin

I also created a JIRA component for you.

Daniel

On 24.09.2015, at 12:43, Victor Martinez  wrote:

> Hi,
>any news?
> Thanks
> On Saturday, 19 September 2015 13:44:52 UTC+2, Victor Martinez wrote:
> Alright, I've already renamed, further details:
>   • Github repo: https://github.com/v1v/percentage-du-node-column-plugin
>   • Plugin name: percentage-du-node-column
>   • 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/Percentage+Disk+Space+Node+Column+Plugin
> Let me know if you need anything else.
> 
> Cheers
> 
> On Saturday, 19 September 2015 01:52:31 UTC+2, Daniel Beck wrote:
> The general naming convention (often broken, but still) would result in 
> percentage-du-node-column as the artifactID, and 
> percentage-du-node-column-plugin as the GitHub repo name. 
> 
> On 18.09.2015, at 21:05, Victor Martinez  wrote: 
> 
> > It's exactly the same implementation as NodeMonitor except the % part 
> > without any threshold yet. I'll code that part later on. 
> > 
> > I believe the Percentage-du-node-column-plugin name is more descriptive, so 
> > thanks for that suggestion. If we agree about that name then I'll rename it 
> > again. 
> > 
> > Thanks again 
> > 
> > On Friday, 18 September 2015 16:33:27 UTC+2, Daniel Beck wrote: 
> > It uses % rather than the absolute byte value, and is therefore more useful 
> > when you have vastly different nodes. 
> > 
> > E.g. the 50GB workspaces on the 2TB slave will require a different 
> > take-this-offline threshold than the 20MB workspaces on the 20GB VM. 
> > 
> > OTOH is doesn't tell you exactly how much is free. 
> > 
> > On 18.09.2015, at 16:30, Kanstantsin Shautsou  wrote: 
> > 
> > > Have no time to read code, but isn't it the same that internal 
> > > NodeMonitor do? It checks disk space on different OSs. 
> > > 
> > > -- 
> > > 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/e14407cc-8a1b-49c0-a454-6df8164d5c06%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/817c2b9b-476d-4341-9e22-81506221b882%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/131ff600-a6e8-41d6-af4e-6cc18c80648f%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/D96E096B-9765-4C9F-BE94-D3DCBAC9B98B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

[Plugin Hosting Request]

[Татьяна Горецкая]

Hello, 


I’ve developed a new Jenkins plugin allows to integrate SonarQube with 
Gerrit. This plugin can send Sonar report to Gerrit as review, and 
SonarQube issues become comments in Gerrit. It is also allows user to 
filter issues by several attributes and customise review message and 
comment body.

This project is located on GitHub:  https://github.com/aquarellian/genar

I expect my Jenkins repository to be named “sonar-gerrit-plugin” 

My username in GitHub is aquarellian, as well as on jenkins-ci.

I've started to fill out wiki page for my plugin already: 
https://wiki.jenkins-ci.org/display/JENKINS/Sonar+Gerrit


Tatiana.

-- 
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/435a02a8-0990-4447-b905-7f3cece76d70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins Plugin (need guidance)

[umesh sharma]

Hi 
I want to write customize plugin as per need of my company. I want to show 
a new menu in the left pane in jenkins like "Perform maven release" 
I am still not sure which extension point I have to explore for this. Any 
guidance or link will be helpful.

-- 
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/77d1bd48-8c67-4767-acb1-916f26ccff37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Using Windows Jenkins installer prevent multiple services and installations

[Claus Schneider]

Additional info:
As you can see from the screen dump the 1.605 remains installed, but trying 
the second will replace 1.629/1.630 despite which version is already 
installed.

On Thursday, September 24, 2015 at 2:50:29 PM UTC+2, Claus Schneider wrote:
>
> Hi..
>
> I just tried to make two installations on the same Windows (10) machine 
> using the http://mirrors.jenkins-ci.org/windows/latest version. I use 
> this way as it makes it easy to manage the service (stop start install 
> uninstall ). 
>
> I have done it several times before where I 'only' came across the 'port', 
> service name and service id is fixed. Can we make this an option in the 
> installer that is then added/updated to the jenkins.xml file?
>
> .. But now it is impossible!! :( It looks like it is a change between 
> 1.605 and now 1.629 / 1.630. I cannot make two installation as the second 
> installation only offers to 'Repair' or 'Remove'. I could like detection if 
> a current is installed and provide an option to install an additional 
> instance setting a new app name(jenkins++, directory, port 
> ,service-id and service name.
>
> I am find with defaults setting it to what it is today, but just give the 
> option of changing it during installation.
>
> best regards
> Claus Schneider
> Praqma A/S, Denmark
>

-- 
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/61d4387f-cb47-4093-8d70-7ee8af7713bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Slave Error

[Victor Martinez]

I believe you already asked in the Jenkins User group, it is worth if you ask 
those questions in that group. 

-- 
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/96655255-2c79-48d3-95b9-be23310fdf60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

ERROR: Failed to parse POMs hudson.util.IOException2: java.lang.reflect.InvocationTargetException

[Barun Vishwakarma]

I am trying to build maven project using Jenkins
but I am getting this error

ERROR: Failed to parse POMshudson.util.IOException2 
: 
java.lang.reflect.InvocationTargetException



Console Output

Started by user anonymous 
Building in workspace /var/lib/jenkins/jobs/SpringHelloWorld/workspace
Parsing POMs
[workspace] $ /var/lib/jenkins/tools/hudson.model.JDK/jdk1.6.0_45/bin/java -cp 
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1/boot/plexus-classworlds-2.2.3.jar
 org.jvnet.hudson.maven3.agent.Maven3Main 
/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1 
/var/cache/jenkins/war/WEB-INF/lib/remoting-2.52.jar 
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar 
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar
 35334
<===[JENKINS REMOTING CAPACITY]===>channel started
ERROR: [JENKINS-18403] JDK 5 not supported to run Maven; retrying with slave 
Java and setting compile/test properties to point to 
/var/lib/jenkins/tools/hudson.model.JDK/jdk1.6.0_45[workspace] $ 
/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.9.x86_64/jre/bin/java -cp 
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.5.jar 
:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1/boot/plexus-classworlds-2.2.3.jar
 org.jvnet.hudson.maven3.agent.Maven3Main 
/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven_2.2.1 
/var/cache/jenkins/war/WEB-INF/lib/remoting-2.52.jar 
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.5.jar 
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.5.jar
 50557
<===[JENKINS REMOTING CAPACITY]===>channel started
Executing Maven:  -B -f 
/var/lib/jenkins/jobs/SpringHelloWorld/workspace/pom.xml clean package
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building spring3 mvc maven 1.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] *--- maven-clean-plugin:2.4.1:clean (default-clean) @ 
spring3-mvc-maven-xml-hello-world ---
*[INFO] Deleting /var/lib/jenkins/jobs/SpringHelloWorld/workspace/target
[INFO] 
[INFO] *--- maven-resources-plugin:2.4.3:resources (default-resources) @ 
spring3-mvc-maven-xml-hello-world ---
*[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, 
i.e. build is platform dependent![INFO] skip non existing resourceDirectory 
/var/lib/jenkins/jobs/SpringHelloWorld/workspace/src/main/resources
[INFO] 
[INFO] *--- maven-compiler-plugin:3.3:compile (default-compile) @ 
spring3-mvc-maven-xml-hello-world ---
*[INFO] Changes detected - recompiling the module![WARNING] File encoding has 
not been set, using platform encoding UTF-8, i.e. build is platform 
dependent![INFO] Compiling 1 source file to 
/var/lib/jenkins/jobs/SpringHelloWorld/workspace/target/classes
[INFO] 
[INFO] *--- maven-resources-plugin:2.4.3:testResources (default-testResources) 
@ spring3-mvc-maven-xml-hello-world ---
*[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, 
i.e. build is platform dependent![INFO] skip non existing resourceDirectory 
/var/lib/jenkins/jobs/SpringHelloWorld/workspace/src/test/resources
[INFO] 
[INFO] *--- maven-compiler-plugin:3.3:testCompile (default-testCompile) @ 
spring3-mvc-maven-xml-hello-world ---
*[INFO] No sources to compile
[INFO] 
[INFO] *--- maven-surefire-plugin:2.5:test (default-test) @ 
spring3-mvc-maven-xml-hello-world ---
*[INFO] No tests to run.
[JENKINS] Recording test results
[INFO] 
[INFO] *--- maven-war-plugin:2.1:war (default-war) @ 
spring3-mvc-maven-xml-hello-world ---
*[INFO] Packaging webapp
[INFO] Assembling webapp [spring3-mvc-maven-xml-hello-world] in 
[/var/lib/jenkins/jobs/SpringHelloWorld/workspace/target/spring3-mvc-maven-xml-hello-world-1.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources 
[/var/lib/jenkins/jobs/SpringHelloWorld/workspace/src/main/webapp]
[INFO] Webapp assembled in [32 msecs]
[INFO] Building war: 
/var/lib/jenkins/jobs/SpringHelloWorld/workspace/target/spring3-mvc-maven-xml-hello-world-1.0-SNAPSHOT.war
[INFO] WEB-INF/web.xml already added, skipping
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

Jenkins Plugin Build - Ivy Plugin

[Kevin Formsma]

Hi!

I'm working on migrating the Ivy plugin to use gradle. Can someone with 
permission to the Jenkin's build configuration give the plugin's job an 
update similar 
to 
https://groups.google.com/forum/#!searchin/jenkinsci-dev/gradle/jenkinsci-dev/7_FHhbo6epw/L80UqQdlBAAJ?
 

See the pull request with the gradle migration 
here: https://github.com/jenkinsci/ivy-plugin/pull/17

Thanks!
-Kevin

-- 
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/0688f7d0-6a71-4e0a-aa7b-4181787a9341%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Plugin Hosting Request]

[Kanstantsin Shautsou]

Hi, it probably makes sense to remove hpi binaries and filter-branch 
repository. It is usually a good tone to not commit binaries. 
(Hint: you can attach binaries to GH releases page).

https://github.com/aquarellian/genar/blob/master/src/main/java/org/jenkinsci/plugins/sonargerrit/SonarGerritPlugin.java
 
This class looks like not used?

On Thursday, September 24, 2015 at 4:49:44 PM UTC+3, Татьяна Горецкая wrote:
>
> Hello, 
>
>
> I’ve developed a new Jenkins plugin allows to integrate SonarQube with 
> Gerrit. This plugin can send Sonar report to Gerrit as review, and 
> SonarQube issues become comments in Gerrit. It is also allows user to 
> filter issues by several attributes and customise review message and 
> comment body.
>
> This project is located on GitHub:  https://github.com/aquarellian/genar
>
> I expect my Jenkins repository to be named “sonar-gerrit-plugin” 
>
> My username in GitHub is aquarellian, as well as on jenkins-ci.
>
> I've started to fill out wiki page for my plugin already: 
> https://wiki.jenkins-ci.org/display/JENKINS/Sonar+Gerrit
>
>
> Tatiana.
>

-- 
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/602b1391-4c4a-469b-992a-a7da64ec3ab5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: hosting request for new plugin

[Alexander Leibzon]

Ping?

(Sorry if I'm nagging, I'm not fully aware of the average waiting time, and 
from browsing the history I found that usually ppl reply within 2 days)

On Tuesday, September 22, 2015 at 2:39:34 AM UTC+3, Alexander Leibzon wrote:
>
> Github: https://github.com/alexanderlz/jenkins-pagerduty-plugin
> jenkins repo name: pagerduty
>
> Github Username: alexanderlz
> jenkins username: alexanderlz
>
>
> The plugin allows to trigger incidents on PagerDuty 
>  as a postbuild action
>
>
> 
>
>

-- 
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/c6df136c-ac86-4a79-9f17-2f82bfb91a40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Bad conduct investigation

[Slide]

Just out of curiosity, what are the possible outcomes of such an
investigation?

On Thu, Sep 24, 2015, 17:02 Kohsuke Kawaguchi  wrote:

>
> We have received complaints from multiple people that the conduct of
> Kanstantsin Shautsou (also known in the community as “KostyaSha”) has
> repeatedly overstepped the threshold of what is generally accepted as being
> “good conduct” in an open-source community.
>
> I have personally witnessed some of them as they have happened for more
> than half a year, and a number of people, including myself, had private
> conversations with him about the matter. As additional complaints have come
> in despite all those efforts, the board feels we have no options but to
> formally launch an investigation to look into this. We are approaching
> several prominent contributors in the community to join us to form a
> committee in order to look into this from all angles. Once we receive
> confirmations from them, we will share their names.
>
> While we have not formally adopted any code of conduct, our governance
> document
> 
> does lay out the vision of the community we thrive to be. This project
> derives a lot of power from constant influx of contributors, and
> maintaining a healthy and respectful environment is of utmost importance.
>
> The board will refrain from going into the details of the matter in a
> public forum to avoid a public circus, and the committee will not publicly
> discuss the matter for the same reason. If you have inputs to the matter,
> please send them to jenkinsci-bo...@googlegroups.com, and we will pass
> them all on to the committee.
>
> I’m hoping that the committee will come to a resolution in a week or so.
> We’ll publish the resolution when it concludes.
>
> I do not take a step like this lightly, and I do this with a heavy heart.
> However, given the duration in which this has been going on, the number of
> people impacted, and the failed attempts to resolve this issue less
> formally, I feel it is a duty of the board to act on the situation.
>
> The situation also shows that the project needs to formally bless a code
> of conduct. I’m going to work with Daniel Beck to propose one for us, and
> we will take it to the developers mailing list and project meeting for the
> discussion.
>
> --
> 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/CAN4CQ4z_X-Jcpvxz_%3DVV085XKJNZhodREf1tZPHT-3Ge_wEEUA%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/CAPiUgVdo4XMMYcw%3Dh6qo73VvNnmDL-Ky0KTSyfmSiXjwhZq_XQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins UX

[Michael Neale]

Yes those are good clear visualisations. You mention writing dashboards, 
but I think to get a view like that it would effectively be a "dashboard" 
in the sense that it would have to take over the whole Jenkins UI to allow 
that much information to "radiate" out. Would be nice if people didn't need 
bespoke plugins for such visualisations though. 

On Wednesday, September 16, 2015 at 5:25:07 AM UTC+10, Craig Rodrigues 
wrote:
>
>
>
> Two use cases that I use the Jenkins UI for are:
>   (1) configuring Jenkins and jobs
>   (2) reporting results of jobs
>
> For (2), the default reporting in Jenkins is OK, but not ideal.
> I've seen people write dashboards to report the results of Jenkins jobs, 
> instead of
> using the default Jenkins UI for reporting the status of jobs.
>
> With the stuff you are working on, would it be possible to generate 
> reports that
> look like the waterfall in Buildbot?  Something like:
>
> https://build.webkit.org/waterfall
> http://build.chromium.org/p/chromium/waterfall
>
> These are not the prettiest things, but for some things they quite 
> effectively
> report the status of build jobs in a concise view.
>

> --
> Craig
>
>

-- 
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/2b259de2-c48e-4a17-9b06-fb1c7c26af47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 proposal

[cactusman]

I generally agree, but what do you think for jelly and stapler?

I hope to replace that to make plugin more easily.

But I understand difficult to seamless upgrade.


2015-09-25 13:53 GMT+09:00 Kohsuke Kawaguchi :

> Jenkins is over 10 years old, and it came quite a long way. I still
> remember the first few plugins that I wrote by myself, and now we have
> close to 1100 plugins. What's started as a hobby project that had run under
> my desk today boasts more than 100K installations driving half a
> million-ish build machines.
>
> We collectively came quite a long way. When I started Jenkins, having a
> server building & testing on every commit was a cutting-edge practice. So
> are automatically capturing changelogs and analysing test reports. But now,
> those are tablestakes, and the frontier of automation has moved further.
> Now we are talking about building pipelines & workflows, continuously
> deploying to servers, leveraging containers, and/or testing pull requests
> before they get merged. I'm going to call this much bigger entangled
> automation "Continuous Delivery", to contrast this with more classical
> automated build & test executions (aka "Continuous Integration") that we
> set out to do.
>
> The other thing I'd like to point out is that the adoption of Jenkins
> continues to grow at the incredible pace of 30% year over year. That is, a
> lot of people are starting new with Jenkins, and they are looking for us to
> help them get Continuous Delivery done. Therefore, this is a good time to
> step back and think about whether we are addressing those current user
> demands.
>
>
> For example, despite this advance during the last 10 years and 1000+
> plugins we've created, messaging in our website hasn't changed much since
> the first version I wrote on java.net. It spends more space talking about
> JNLP and zero mention of Git, pipeline, or Docker.
>
> The fresh installation of Jenkins is not much better. The CVS support is
> available out of the box, but Git isn't. All the cool stuff that the
> community has done and its collective best practices still need be learned
> by each and every new user. It's bit like we are making everyone assemble
> LEGO blocks. That's not doing enough justice to the 30K+ users that will be
> joining us in this year.
>
> So I propose we do Jenkins 2.0 to fix this.
>
> There are three important goals that I see in Jenkins 2.0.
>
>1. We need to claim our rightful place in Continuous Delivery. We have
>lots of pieces that address these modern needs, but we are not
>communicating this very well.
>
>2. We need to revisit out of the box experience, so that Jenkins
>itself speaks that story and makes it clear what we are aiming for. Our
>software needs to speak for itself and tell people where we are going, so
>that the community can better focus efforts on the important parts.
>
>3. And we need to do this while keeping what makes Jenkins great in
>the first place, which are the ecosystem, the community, and the
>extensibility that recognizes that one size does not fit all and let people
>do what they want to do.
>
>
> Incrementing the major version sends a clear message to people that we are
> moving forward. That's why I think 2.0 is appropriate for this effort.
>
>
>
> Now, 2.0 can mean a lot of different things to a lot of people, so let me
> outline what I think we should do and we shouldn't do.
>
> It's very important for me to make sure that my fellow Jenkins developers
> understand the motivation and the goal of this proposal, because that
> drives much of what we should and shouldn't do. So instead of deep-diving
> into technical parts, please take time to try to understand why I am
> proposing this.
>
> We need to contain the scope. 2.0 has to have enough in it to justify the
> major version number increase, but it creates a period of pause and
> uncertainty, so it cannot keep dragging on for too long. 2.0 cannot be
> everything everyone ever wanted.
>
> We cannot do massively disruptive 2.0, because it ends up splitting the
> community. If users perceive that the upgrade to 2.0 is risky, enough of
> them will stay behind with 1.x, plugin authors would want to continue
> supporting them, which makes 1.x more liveable, which makes the transition
> slower. I do not want to end up in Python2/3 situation, and nobody wins.
>
> That means we cannot be really breaking plugins. We cannot do
> s/hudson/jenkins/g in the package names because doing that will break all
> the plugins. 2.0 does come with the expectation that it is more disruptive
> than usual 1.630 to 1.631 upgrade, so we have some "disruption budget", but
> we have to use it really wisely.
>
> Simiarly, for me it is an absolute requirement that we keep people's
> $JENKINS_HOME functioning. A lot of sweat, tear, and blood went into those
> right set of plugins and elaborate job configurations. When users upgrade
> to 2.0, they need to continue to 

Re: Hosting a new Plugin - Percentage DiskSpace usage column

[Victor Martinez]

Awesome, Thanks Daniel! 

On Thursday, 24 September 2015 14:08:19 UTC+2, Daniel Beck wrote:
>
> Done: https://github.com/jenkinsci/percentage-du-node-column-plugin 
>
> I also created a JIRA component for you. 
>
> Daniel 
>
> On 24.09.2015, at 12:43, Victor Martinez  > wrote: 
>
> > Hi, 
> >any news? 
> > Thanks 
> > On Saturday, 19 September 2015 13:44:52 UTC+2, Victor Martinez wrote: 
> > Alright, I've already renamed, further details: 
> > • Github repo: 
> https://github.com/v1v/percentage-du-node-column-plugin 
> > • Plugin name: percentage-du-node-column 
> > • 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/Percentage+Disk+Space+Node+Column+Plugin
>  
> > Let me know if you need anything else. 
> > 
> > Cheers 
> > 
> > On Saturday, 19 September 2015 01:52:31 UTC+2, Daniel Beck wrote: 
> > The general naming convention (often broken, but still) would result in 
> percentage-du-node-column as the artifactID, and 
> percentage-du-node-column-plugin as the GitHub repo name. 
> > 
> > On 18.09.2015, at 21:05, Victor Martinez  
> wrote: 
> > 
> > > It's exactly the same implementation as NodeMonitor except the % part 
> without any threshold yet. I'll code that part later on. 
> > > 
> > > I believe the Percentage-du-node-column-plugin name is more 
> descriptive, so thanks for that suggestion. If we agree about that name 
> then I'll rename it again. 
> > > 
> > > Thanks again 
> > > 
> > > On Friday, 18 September 2015 16:33:27 UTC+2, Daniel Beck wrote: 
> > > It uses % rather than the absolute byte value, and is therefore more 
> useful when you have vastly different nodes. 
> > > 
> > > E.g. the 50GB workspaces on the 2TB slave will require a different 
> take-this-offline threshold than the 20MB workspaces on the 20GB VM. 
> > > 
> > > OTOH is doesn't tell you exactly how much is free. 
> > > 
> > > On 18.09.2015, at 16:30, Kanstantsin Shautsou  
> wrote: 
> > > 
> > > > Have no time to read code, but isn't it the same that internal 
> NodeMonitor do? It checks disk space on different OSs. 
> > > > 
> > > > -- 
> > > > 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/e14407cc-8a1b-49c0-a454-6df8164d5c06%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/817c2b9b-476d-4341-9e22-81506221b882%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/131ff600-a6e8-41d6-af4e-6cc18c80648f%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/206aa17a-8499-46a6-9da7-3005959c00c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: hosting request for new plugin

[Daniel Beck]

Cool plugin!

What's a bit inconsistent is that the artifact ID is pager-duty, the repo is 
jenkins-pagerduty-plugin. Any particular reason for that?

Note that by convention, the JIRA component and GitHub repo would both be named 
foo-plugin, if 'foo' is your artifact ID.

Daniel

On 24.09.2015, at 20:54, Alexander Leibzon  wrote:

> Ping?
> 
> (Sorry if I'm nagging, I'm not fully aware of the average waiting time, and 
> from browsing the history I found that usually ppl reply within 2 days)
> 
> On Tuesday, September 22, 2015 at 2:39:34 AM UTC+3, Alexander Leibzon wrote:
> Github: https://github.com/alexanderlz/jenkins-pagerduty-plugin
> jenkins repo name: pagerduty
> 
> Github Username: alexanderlz
> jenkins username: alexanderlz
> 
> 
> The plugin allows to trigger incidents on PagerDuty as a postbuild action
> 
> 
> 
> 
> 
> -- 
> 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/c6df136c-ac86-4a79-9f17-2f82bfb91a40%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/BABC2E65-6B40-4D14-8C2C-308B523F4C44%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

[ANN] Bad conduct investigation

[Kohsuke Kawaguchi]

We have received complaints from multiple people that the conduct of
Kanstantsin Shautsou (also known in the community as “KostyaSha”) has
repeatedly overstepped the threshold of what is generally accepted as being
“good conduct” in an open-source community.

I have personally witnessed some of them as they have happened for more
than half a year, and a number of people, including myself, had private
conversations with him about the matter. As additional complaints have come
in despite all those efforts, the board feels we have no options but to
formally launch an investigation to look into this. We are approaching
several prominent contributors in the community to join us to form a
committee in order to look into this from all angles. Once we receive
confirmations from them, we will share their names.

While we have not formally adopted any code of conduct, our governance
document

does lay out the vision of the community we thrive to be. This project
derives a lot of power from constant influx of contributors, and
maintaining a healthy and respectful environment is of utmost importance.

The board will refrain from going into the details of the matter in a
public forum to avoid a public circus, and the committee will not publicly
discuss the matter for the same reason. If you have inputs to the matter,
please send them to jenkinsci-bo...@googlegroups.com, and we will pass them
all on to the committee.

I’m hoping that the committee will come to a resolution in a week or so.
We’ll publish the resolution when it concludes.

I do not take a step like this lightly, and I do this with a heavy heart.
However, given the duration in which this has been going on, the number of
people impacted, and the failed attempts to resolve this issue less
formally, I feel it is a duty of the board to act on the situation.

The situation also shows that the project needs to formally bless a code of
conduct. I’m going to work with Daniel Beck to propose one for us, and we
will take it to the developers mailing list and project meeting for the
discussion.

-- 
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/CAN4CQ4z_X-Jcpvxz_%3DVV085XKJNZhodREf1tZPHT-3Ge_wEEUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.0 proposal

[Kohsuke Kawaguchi]

Jenkins is over 10 years old, and it came quite a long way. I still
remember the first few plugins that I wrote by myself, and now we have
close to 1100 plugins. What's started as a hobby project that had run under
my desk today boasts more than 100K installations driving half a
million-ish build machines.

We collectively came quite a long way. When I started Jenkins, having a
server building & testing on every commit was a cutting-edge practice. So
are automatically capturing changelogs and analysing test reports. But now,
those are tablestakes, and the frontier of automation has moved further.
Now we are talking about building pipelines & workflows, continuously
deploying to servers, leveraging containers, and/or testing pull requests
before they get merged. I'm going to call this much bigger entangled
automation "Continuous Delivery", to contrast this with more classical
automated build & test executions (aka "Continuous Integration") that we
set out to do.

The other thing I'd like to point out is that the adoption of Jenkins
continues to grow at the incredible pace of 30% year over year. That is, a
lot of people are starting new with Jenkins, and they are looking for us to
help them get Continuous Delivery done. Therefore, this is a good time to
step back and think about whether we are addressing those current user
demands.


For example, despite this advance during the last 10 years and 1000+
plugins we've created, messaging in our website hasn't changed much since
the first version I wrote on java.net. It spends more space talking about
JNLP and zero mention of Git, pipeline, or Docker.

The fresh installation of Jenkins is not much better. The CVS support is
available out of the box, but Git isn't. All the cool stuff that the
community has done and its collective best practices still need be learned
by each and every new user. It's bit like we are making everyone assemble
LEGO blocks. That's not doing enough justice to the 30K+ users that will be
joining us in this year.

So I propose we do Jenkins 2.0 to fix this.

There are three important goals that I see in Jenkins 2.0.

   1. We need to claim our rightful place in Continuous Delivery. We have
   lots of pieces that address these modern needs, but we are not
   communicating this very well.

   2. We need to revisit out of the box experience, so that Jenkins itself
   speaks that story and makes it clear what we are aiming for. Our software
   needs to speak for itself and tell people where we are going, so that the
   community can better focus efforts on the important parts.

   3. And we need to do this while keeping what makes Jenkins great in the
   first place, which are the ecosystem, the community, and the extensibility
   that recognizes that one size does not fit all and let people do what they
   want to do.


Incrementing the major version sends a clear message to people that we are
moving forward. That's why I think 2.0 is appropriate for this effort.



Now, 2.0 can mean a lot of different things to a lot of people, so let me
outline what I think we should do and we shouldn't do.

It's very important for me to make sure that my fellow Jenkins developers
understand the motivation and the goal of this proposal, because that
drives much of what we should and shouldn't do. So instead of deep-diving
into technical parts, please take time to try to understand why I am
proposing this.

We need to contain the scope. 2.0 has to have enough in it to justify the
major version number increase, but it creates a period of pause and
uncertainty, so it cannot keep dragging on for too long. 2.0 cannot be
everything everyone ever wanted.

We cannot do massively disruptive 2.0, because it ends up splitting the
community. If users perceive that the upgrade to 2.0 is risky, enough of
them will stay behind with 1.x, plugin authors would want to continue
supporting them, which makes 1.x more liveable, which makes the transition
slower. I do not want to end up in Python2/3 situation, and nobody wins.

That means we cannot be really breaking plugins. We cannot do
s/hudson/jenkins/g in the package names because doing that will break all
the plugins. 2.0 does come with the expectation that it is more disruptive
than usual 1.630 to 1.631 upgrade, so we have some "disruption budget", but
we have to use it really wisely.

Simiarly, for me it is an absolute requirement that we keep people's
$JENKINS_HOME functioning. A lot of sweat, tear, and blood went into those
right set of plugins and elaborate job configurations. When users upgrade
to 2.0, they need to continue to work, or else Jenkins 2.0 will be Jenkins
in just the name only.

Therefore, we cannot make massive internal changes. In many ways, it has to
be evolutionary instead of revolutionary, when it comes to the code. This
is not a "let's redo everything from scratch" kind of 2.0. In any case, I
think it's a pitfall to focus too much on internals. We all have a long
list of things we want to fix and