Re: Metrics & Figures about Jenkins Core and Jenkins Plug-ins

[Manuel Jesús Recena Soto]

Hello Mark,

Thanks so much for your feedback.

This is being the source of truth for Git and Git Client plugins:

https://api.zauf.io/plugins/search?q=groupId==org.jenkins-ci.plugins;artifactId=in=(git,git-client)

Disclaimer: I only count final versions, no beta, no alpha or RC.

Regards,


On Sun, Apr 5, 2020 at 4:04 PM Mark Waite  wrote:

> Thanks.
>
> I'm still not understanding the data that is presented on the first
> page.The title I see is "613 plugins released in the last year" and the
> drop down list shows 2020 as the selected year.  At the end of the list is
> "git client plugin" with 17 releases and last release date as 2020-03-10.
>
> I'm perplexed why git client plugin would appear in that location rather
> than git plugin appearing in that location or appearing somewhere higher on
> the list.  If presence on the list is based on total lifetime releases,
> then there have been more total lifetime releases of the git plugin (169)
> than the git client plugin (121).  If presence on the list is releases In
> the last 12 months, then I believe there have been more releases of the git
> plugin than the git client plugin in the last 12 months.  I did not count
> releases from the last 12 months specifically, I just confirmed that there
> were git plugin releases in the past 12 months which do not have a
> corresponding git client plugin release).
>
> Thanks very much for providing a visualization of the data.
>
>
> On Sun, Apr 5, 2020 at 7:26 AM Manuel Jesús Recena Soto 
> wrote:
>
>> Hello,
>>
>> We already have a domain and valid SSL certificate: https://stats.zauf.io
>>
>> Regards,
>>
>>
>>
>> On Mon, Mar 30, 2020 at 10:03 PM Manuel Jesús Recena Soto <
>> rec...@gmail.com> wrote:
>>
>>> Hello Oleg,
>>>
>>> On Mon, Mar 30, 2020 at 12:52 PM Oleg Nenashev 
>>> wrote:
>>>
 I think it would be a great addition to https://stats.jenkins.io/

>>>
>>> I don't know where this side-project will arrive, but it can be a great
>>> addition.
>>>
>>>
 Would be great to see the code/backend behind this visualization

>>>
>>> As I mentioned, there is a preliminary Data API version I use to render
>>> those figures.
>>>
>>> Regards,
>>>
>>>

 On Sunday, March 29, 2020 at 10:31:25 PM UTC+2, Mark Waite wrote:
>
> I'm not clear how you're calculating release counts in the table.  I
> initially assumed it was releases in that specific year, but exploring
> seemed to hint that wasn't the case.
>
> Any hints?
>
> On Sun, Mar 29, 2020 at 2:02 PM Mark Waite 
> wrote:
>
>> That is really interesting!  Nice work!
>>
>> On Sun, Mar 29, 2020 at 11:17 AM Manuel Jesús Recena Soto <
>> rec...@gmail.com> wrote:
>>
>>> Hello everyone,
>>>
>>> I really hope you are all safe from COVID-19 and stay at home.
>>>
>>> I'm currently working on a side-project related to Jenkins project.
>>> At this point of the project I want to provide a basic website with
>>> interesting information for end-users, administrator or plugin 
>>> developers.
>>> This website aims to provide some metrics and figures. Let me show you 
>>> some
>>> examples.
>>>
>>> Global figures
>>>
>>> Global information stored and managed by this system until now.
>>>
>>>- Number of plugins
>>>- Number of releases
>>>- Number of Jenkins releases (weekly & LTS)
>>>
>>>
>>> In order to see the evolving of these figures I would use a visual
>>> representation based on timelines.
>>>
>>> In the same context we could show the highlighted events:
>>>
>>>- Latest releases plugins
>>>- Most used baseline
>>>- Newest plugins
>>>- Most unreleased plugins
>>>
>>>
>>> And moreover, some specific reports, for example:
>>>
>>> See the distribution of plugins (latest release) according to their
>>> baseline. And vice versa, listing of plugins per baseline.
>>>
>>> I think this kind of information would be helpful for you.
>>>
>>> Don't hesitate to participate in this email thread or reach me out
>>> directly. I really appreciate your feedback.
>>>
>>> If you want to see a MVP, visit http://142.93.140.202:8084/
>>>
>>> Best regards,
>>>
>>> --
>>> Manuel Recena Soto
>>> * manuelrecena.com [/blog]
>>> * linkedin.com/in/recena
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>> send an email to jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CABa-UoeGVSyT5fd3LxWbYJ9SoJzigAkTKUrncoBA-8HsMBysJA%40mail.gmail.com
>>> 

Re: HA/clustered jenkins

[Mark Waite]

You've interpreted the documentation correctly.

https://stackoverflow.com/questions/36173214/how-to-setup-jenkins-with-ha
and several blog posts describe different alternative for an active/passive
HA setup.

On Sun, Apr 5, 2020 at 7:08 AM E.S. Rosenberg 
wrote:

> Hi all,
>
> We're looking at making our jenkins setup more resilient and I was reading
> the following page:
>
> https://jenkins.io/doc/book/architecting-for-scale/#resilient-jenkins-architecture
>
> This mentions the following:
> "Each Jenkins master needs to be set up such that it is part of a Jenkins
> cluster.
>
> A proxy (typically HAProxy or F5) then fronts the primary master. The
> proxy’s job is to continuously monitor the primary master and route
> requests to the backup if the primary goes down. To make the infrastructure
> more resilient, you can have multiple backup masters configured."
>
> There are 2 things that I'm trying to now understand upon rereading this
> section:
>
> 1. While the opening of this page mentions vertical vs. horizontal scaling
> it would seem that there is no true way to do horizontal scaling without
> creating mini-domains for which each jenkins master schedules.
>
> 2. There is no shared state between the machines other then maybe sharing
> NFS which is OK if only 1 machine is truly active at any given time.
>
> Lastly it would seem a master-master setup is at this time impossible.
>
> Am I correct in my interpretation of the docs?
>
> Thanks,
> Eli
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAHxFV_vaEwrWmSjEqdBhDGnEQdk9T-tTQ%3D%2B7SK9cGO3tyApsHw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGiLBnnKg%2Bt4HGADpZgfOo3sRngD_d-8-d%3DTw2q1gnVkQ%40mail.gmail.com.

Re: Metrics & Figures about Jenkins Core and Jenkins Plug-ins

[Mark Waite]

Thanks.

I'm still not understanding the data that is presented on the first
page.The title I see is "613 plugins released in the last year" and the
drop down list shows 2020 as the selected year.  At the end of the list is
"git client plugin" with 17 releases and last release date as 2020-03-10.

I'm perplexed why git client plugin would appear in that location rather
than git plugin appearing in that location or appearing somewhere higher on
the list.  If presence on the list is based on total lifetime releases,
then there have been more total lifetime releases of the git plugin (169)
than the git client plugin (121).  If presence on the list is releases In
the last 12 months, then I believe there have been more releases of the git
plugin than the git client plugin in the last 12 months.  I did not count
releases from the last 12 months specifically, I just confirmed that there
were git plugin releases in the past 12 months which do not have a
corresponding git client plugin release).

Thanks very much for providing a visualization of the data.


On Sun, Apr 5, 2020 at 7:26 AM Manuel Jesús Recena Soto 
wrote:

> Hello,
>
> We already have a domain and valid SSL certificate: https://stats.zauf.io
>
> Regards,
>
>
>
> On Mon, Mar 30, 2020 at 10:03 PM Manuel Jesús Recena Soto <
> rec...@gmail.com> wrote:
>
>> Hello Oleg,
>>
>> On Mon, Mar 30, 2020 at 12:52 PM Oleg Nenashev 
>> wrote:
>>
>>> I think it would be a great addition to https://stats.jenkins.io/
>>>
>>
>> I don't know where this side-project will arrive, but it can be a great
>> addition.
>>
>>
>>> Would be great to see the code/backend behind this visualization
>>>
>>
>> As I mentioned, there is a preliminary Data API version I use to render
>> those figures.
>>
>> Regards,
>>
>>
>>>
>>> On Sunday, March 29, 2020 at 10:31:25 PM UTC+2, Mark Waite wrote:

 I'm not clear how you're calculating release counts in the table.  I
 initially assumed it was releases in that specific year, but exploring
 seemed to hint that wasn't the case.

 Any hints?

 On Sun, Mar 29, 2020 at 2:02 PM Mark Waite  wrote:

> That is really interesting!  Nice work!
>
> On Sun, Mar 29, 2020 at 11:17 AM Manuel Jesús Recena Soto <
> rec...@gmail.com> wrote:
>
>> Hello everyone,
>>
>> I really hope you are all safe from COVID-19 and stay at home.
>>
>> I'm currently working on a side-project related to Jenkins project.
>> At this point of the project I want to provide a basic website with
>> interesting information for end-users, administrator or plugin 
>> developers.
>> This website aims to provide some metrics and figures. Let me show you 
>> some
>> examples.
>>
>> Global figures
>>
>> Global information stored and managed by this system until now.
>>
>>- Number of plugins
>>- Number of releases
>>- Number of Jenkins releases (weekly & LTS)
>>
>>
>> In order to see the evolving of these figures I would use a visual
>> representation based on timelines.
>>
>> In the same context we could show the highlighted events:
>>
>>- Latest releases plugins
>>- Most used baseline
>>- Newest plugins
>>- Most unreleased plugins
>>
>>
>> And moreover, some specific reports, for example:
>>
>> See the distribution of plugins (latest release) according to their
>> baseline. And vice versa, listing of plugins per baseline.
>>
>> I think this kind of information would be helpful for you.
>>
>> Don't hesitate to participate in this email thread or reach me out
>> directly. I really appreciate your feedback.
>>
>> If you want to see a MVP, visit http://142.93.140.202:8084/
>>
>> Best regards,
>>
>> --
>> Manuel Recena Soto
>> * manuelrecena.com [/blog]
>> * linkedin.com/in/recena
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to jenkins...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CABa-UoeGVSyT5fd3LxWbYJ9SoJzigAkTKUrncoBA-8HsMBysJA%40mail.gmail.com
>> 
>> .
>>
> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/4747c6e4-81bc-4740-913e-39ef8eb7919e%40googlegroups.com
>>> 

Re: Metrics & Figures about Jenkins Core and Jenkins Plug-ins

[Manuel Jesús Recena Soto]

Hello,

We already have a domain and valid SSL certificate: https://stats.zauf.io

Regards,



On Mon, Mar 30, 2020 at 10:03 PM Manuel Jesús Recena Soto 
wrote:

> Hello Oleg,
>
> On Mon, Mar 30, 2020 at 12:52 PM Oleg Nenashev 
> wrote:
>
>> I think it would be a great addition to https://stats.jenkins.io/
>>
>
> I don't know where this side-project will arrive, but it can be a great
> addition.
>
>
>> Would be great to see the code/backend behind this visualization
>>
>
> As I mentioned, there is a preliminary Data API version I use to render
> those figures.
>
> Regards,
>
>
>>
>> On Sunday, March 29, 2020 at 10:31:25 PM UTC+2, Mark Waite wrote:
>>>
>>> I'm not clear how you're calculating release counts in the table.  I
>>> initially assumed it was releases in that specific year, but exploring
>>> seemed to hint that wasn't the case.
>>>
>>> Any hints?
>>>
>>> On Sun, Mar 29, 2020 at 2:02 PM Mark Waite  wrote:
>>>
 That is really interesting!  Nice work!

 On Sun, Mar 29, 2020 at 11:17 AM Manuel Jesús Recena Soto <
 rec...@gmail.com> wrote:

> Hello everyone,
>
> I really hope you are all safe from COVID-19 and stay at home.
>
> I'm currently working on a side-project related to Jenkins project. At
> this point of the project I want to provide a basic website with
> interesting information for end-users, administrator or plugin developers.
> This website aims to provide some metrics and figures. Let me show you 
> some
> examples.
>
> Global figures
>
> Global information stored and managed by this system until now.
>
>- Number of plugins
>- Number of releases
>- Number of Jenkins releases (weekly & LTS)
>
>
> In order to see the evolving of these figures I would use a visual
> representation based on timelines.
>
> In the same context we could show the highlighted events:
>
>- Latest releases plugins
>- Most used baseline
>- Newest plugins
>- Most unreleased plugins
>
>
> And moreover, some specific reports, for example:
>
> See the distribution of plugins (latest release) according to their
> baseline. And vice versa, listing of plugins per baseline.
>
> I think this kind of information would be helpful for you.
>
> Don't hesitate to participate in this email thread or reach me out
> directly. I really appreciate your feedback.
>
> If you want to see a MVP, visit http://142.93.140.202:8084/
>
> Best regards,
>
> --
> Manuel Recena Soto
> * manuelrecena.com [/blog]
> * linkedin.com/in/recena
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkins...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CABa-UoeGVSyT5fd3LxWbYJ9SoJzigAkTKUrncoBA-8HsMBysJA%40mail.gmail.com
> 
> .
>
 --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/4747c6e4-81bc-4740-913e-39ef8eb7919e%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Manuel Recena Soto
> * manuelrecena.com [/blog]
> * linkedin.com/in/recena
>


-- 
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CABa-Uof6zDZ03kWkAiCK0dkVe%2B_6Qj-oBN4PXiB1wCgkGmNZTQ%40mail.gmail.com.

With more than one executors on a node, the builds often go bad with "hudson.remoting.ChannelClosedException".

[Fabio Marzotti]

With more than one executors on a node, the builds often go bad with 
"hudson.remoting.ChannelClosedException". When two different builds run 
togheter on two different executors, they go in failed state. Below you can 
see a log section. 

Instead if I set just  one executor on the same node, no problem at all.

I alsto tried these:

1) set the jvm option -Xmx1048m on the build but same problem!

2) remove the jvm option and double the ram (8gb) but same problem!

I'll really appreciate an help on this! Bye, Fabio

from build output:

Started by timerRunning as SYSTEMBuilding remotely on monauthbep01-auto in 
workspace /var/lib/jenkins/workspace/MONAUTH - INCAS - ISSUING - STANDIN 
[MONAUTH 
- INCAS - ISSUING - STANDIN] $ /bin/sh xe 
/tmp/jenkins5004094442920936653.shFATAL: Unable to delete script file 
/tmp/jenkins5004094442920936653.shjava.io.EOFException at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2680)
 
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3155)
 
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:861) 
at java.io.ObjectInputStream.(ObjectInputStream.java:357) at 
hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at 
hudson.remoting.Command.readFrom(Command.java:140) at 
hudson.remoting.Command.readFrom(Command.java:126) at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)
 
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused:
 
java.io.IOException: Unexpected termination of the channel  
<-!!! at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)Caused:
 
hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on 
monauthbep01-auto failed. The channel is closing down or has closed down

from journalctl:

Mar 26 10:36:00 monauthbep01 sshd[4891]: Received disconnect from 
10.102.132.70 port 47270:11: Closed due to user request. <--!!
Mar 26 10:36:00 monauthbep01 sshd[4891]: Disconnected from 10.102.132.70 
port 47270 <--!!
Mar 26 10:36:00 monauthbep01 sshd[4889]: pam_unix(sshd:session): session 
closed for user auto <--!!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/897b5cf9-a611-43f5-8a80-322be0ff8f3f%40googlegroups.com.

HA/clustered jenkins

[E.S. Rosenberg]

Hi all,

We're looking at making our jenkins setup more resilient and I was reading
the following page:
https://jenkins.io/doc/book/architecting-for-scale/#resilient-jenkins-architecture

This mentions the following:
"Each Jenkins master needs to be set up such that it is part of a Jenkins
cluster.

A proxy (typically HAProxy or F5) then fronts the primary master. The
proxy’s job is to continuously monitor the primary master and route
requests to the backup if the primary goes down. To make the infrastructure
more resilient, you can have multiple backup masters configured."

There are 2 things that I'm trying to now understand upon rereading this
section:

1. While the opening of this page mentions vertical vs. horizontal scaling
it would seem that there is no true way to do horizontal scaling without
creating mini-domains for which each jenkins master schedules.

2. There is no shared state between the machines other then maybe sharing
NFS which is OK if only 1 machine is truly active at any given time.

Lastly it would seem a master-master setup is at this time impossible.

Am I correct in my interpretation of the docs?

Thanks,
Eli

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAHxFV_vaEwrWmSjEqdBhDGnEQdk9T-tTQ%3D%2B7SK9cGO3tyApsHw%40mail.gmail.com.