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
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
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.
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
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,
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
Yeikel, Lesterp, many thanks!
On Friday, April 3, 2020 at 6:58:54 PM UTC+3, lesterp wrote:
>
> There was an excellent post on the Jenkins blog that had some great
> examples, here:
>
> https://jenkins.io/blog/2017/02/15/declarative-notifications/
>
> On Thursday, April 2, 2020 at 4:40:18 AM
