Re: Is everything ok on our Jenkins cluster?
Done. Thanks for helping! Alessio On Thu, Jun 18, 2020 at 9:43 PM Paul Davis wrote: > Yap, just mention that restarting all Jenkins agents solved the issue. > > On Thu, Jun 18, 2020 at 2:40 PM Alessio 'Blaster' Biancalana > wrote: > > > > Hi, > > Looks like the issue is gone now. Sorry for bothering! Shall I close th > > Jira infra ticket? > > > > Alessio > > > > Il gio 18 giu 2020, 20:23 Joan Touzet ha scritto: > > > > > On 18/06/2020 13:19, Alessio 'Blaster' Biancalana wrote: > > > > Hi Joan, > > > > Hi opened the infra bug, could you please check I've done everything > > > > correctly? > > > > > > > > https://issues.apache.org/jira/browse/INFRA-20441 > > > > > > Looks fine. > > > > > > FYI Paul Davis just updated and restarted the agents on all of the > > > machines. Nick just got his PR through. Can you try restarting your > > > build now? > > > > > > -Joan > > > > > > > > > > > I also shared the link to the thread. Strange situation :/ > > > > > > > > @Paul could you check again? Definitely the issue wasn't fixed all > day > > > > long, and it looks like it's not a networking blurb. > > > > > > > > Alessio > > > > > > > > On Thu, Jun 18, 2020 at 12:48 AM Joan Touzet > wrote: > > > > > > > >> Can you try opening an Infra ticket on this? > > > >> > > > >> https://issues.apache.org/jira > > > >> > > > >> Open it against the Infra project and share with them the link(s). > You > > > >> can also link to this mailing list discussion via > > > >> https://lists.apache.org/ . > > > >> > > > >> -Joan > > > >> > > > >> On 2020-06-17 5:16 p.m., Alessio 'Blaster' Biancalana wrote: > > > >>> Thanks for the response Paul! > > > >>> Same stuff, I tried rerunning the job but it looks stuck with that > > > error > > > >>> > > > >>> > > > >> > > > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/6/pipeline > > > >>> > > > >>> I don't know why that happens, if you have any clue... > > > >>> > > > >>> Thanks, > > > >>> Alessio > > > >>> > > > >>> Il mer 17 giu 2020, 23:01 Paul Davis > ha > > > >>> scritto: > > > >>> > > > I looked at Jenkins and saw them all as connected and in sync. Is > > > there more to the report or was this some sort of networking burb? > > > > > > On Wed, Jun 17, 2020 at 2:20 PM Joan Touzet > > > wrote: > > > > > > > > IBM maintains these workers for us - will have to ask Paul Davis > to > > > >> take > > > > a look. > > > > > > > > -Joan > > > > > > > > On 17/06/2020 05:36, Alessio 'Blaster' Biancalana wrote: > > > >> Hey folks, > > > >> I have a job on Jenkins that is repeatedly giving me this error: > > > >> > > > >> < > > > > > > >> > > > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-1 > > > > [2020-06-17T09:09:49.584Z] > > > >> Recording test results > > > >> < > > > > > > >> > > > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-2 > > > > [2020-06-17T09:09:49.718Z] > > > >> Remote call on JNLP4-connect connection from > > > >> 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > > > >> < > > > > > > >> > > > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-3 > > > > Remote > > > >> call on JNLP4-connect connection from > > > >> 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > > > >> > > > >> I was wondering, is everything ok on our Jenkins cluster? Maybe > > > >> there's > > > >> some maintenance I'm not aware of? > > > >> > > > >> Cheers, > > > >> Alessio > > > >> > > > > > > >>> > > > >> > > > > > > > >
Re: Is everything ok on our Jenkins cluster?
Yap, just mention that restarting all Jenkins agents solved the issue. On Thu, Jun 18, 2020 at 2:40 PM Alessio 'Blaster' Biancalana wrote: > > Hi, > Looks like the issue is gone now. Sorry for bothering! Shall I close th > Jira infra ticket? > > Alessio > > Il gio 18 giu 2020, 20:23 Joan Touzet ha scritto: > > > On 18/06/2020 13:19, Alessio 'Blaster' Biancalana wrote: > > > Hi Joan, > > > Hi opened the infra bug, could you please check I've done everything > > > correctly? > > > > > > https://issues.apache.org/jira/browse/INFRA-20441 > > > > Looks fine. > > > > FYI Paul Davis just updated and restarted the agents on all of the > > machines. Nick just got his PR through. Can you try restarting your > > build now? > > > > -Joan > > > > > > > > I also shared the link to the thread. Strange situation :/ > > > > > > @Paul could you check again? Definitely the issue wasn't fixed all day > > > long, and it looks like it's not a networking blurb. > > > > > > Alessio > > > > > > On Thu, Jun 18, 2020 at 12:48 AM Joan Touzet wrote: > > > > > >> Can you try opening an Infra ticket on this? > > >> > > >> https://issues.apache.org/jira > > >> > > >> Open it against the Infra project and share with them the link(s). You > > >> can also link to this mailing list discussion via > > >> https://lists.apache.org/ . > > >> > > >> -Joan > > >> > > >> On 2020-06-17 5:16 p.m., Alessio 'Blaster' Biancalana wrote: > > >>> Thanks for the response Paul! > > >>> Same stuff, I tried rerunning the job but it looks stuck with that > > error > > >>> > > >>> > > >> > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/6/pipeline > > >>> > > >>> I don't know why that happens, if you have any clue... > > >>> > > >>> Thanks, > > >>> Alessio > > >>> > > >>> Il mer 17 giu 2020, 23:01 Paul Davis ha > > >>> scritto: > > >>> > > I looked at Jenkins and saw them all as connected and in sync. Is > > there more to the report or was this some sort of networking burb? > > > > On Wed, Jun 17, 2020 at 2:20 PM Joan Touzet > > wrote: > > > > > > IBM maintains these workers for us - will have to ask Paul Davis to > > >> take > > > a look. > > > > > > -Joan > > > > > > On 17/06/2020 05:36, Alessio 'Blaster' Biancalana wrote: > > >> Hey folks, > > >> I have a job on Jenkins that is repeatedly giving me this error: > > >> > > >> < > > > > >> > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-1 > > > [2020-06-17T09:09:49.584Z] > > >> Recording test results > > >> < > > > > >> > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-2 > > > [2020-06-17T09:09:49.718Z] > > >> Remote call on JNLP4-connect connection from > > >> 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > > >> < > > > > >> > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-3 > > > Remote > > >> call on JNLP4-connect connection from > > >> 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > > >> > > >> I was wondering, is everything ok on our Jenkins cluster? Maybe > > >> there's > > >> some maintenance I'm not aware of? > > >> > > >> Cheers, > > >> Alessio > > >> > > > > >>> > > >> > > > > >
Re: Is everything ok on our Jenkins cluster?
Hi, Looks like the issue is gone now. Sorry for bothering! Shall I close th Jira infra ticket? Alessio Il gio 18 giu 2020, 20:23 Joan Touzet ha scritto: > On 18/06/2020 13:19, Alessio 'Blaster' Biancalana wrote: > > Hi Joan, > > Hi opened the infra bug, could you please check I've done everything > > correctly? > > > > https://issues.apache.org/jira/browse/INFRA-20441 > > Looks fine. > > FYI Paul Davis just updated and restarted the agents on all of the > machines. Nick just got his PR through. Can you try restarting your > build now? > > -Joan > > > > > I also shared the link to the thread. Strange situation :/ > > > > @Paul could you check again? Definitely the issue wasn't fixed all day > > long, and it looks like it's not a networking blurb. > > > > Alessio > > > > On Thu, Jun 18, 2020 at 12:48 AM Joan Touzet wrote: > > > >> Can you try opening an Infra ticket on this? > >> > >> https://issues.apache.org/jira > >> > >> Open it against the Infra project and share with them the link(s). You > >> can also link to this mailing list discussion via > >> https://lists.apache.org/ . > >> > >> -Joan > >> > >> On 2020-06-17 5:16 p.m., Alessio 'Blaster' Biancalana wrote: > >>> Thanks for the response Paul! > >>> Same stuff, I tried rerunning the job but it looks stuck with that > error > >>> > >>> > >> > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/6/pipeline > >>> > >>> I don't know why that happens, if you have any clue... > >>> > >>> Thanks, > >>> Alessio > >>> > >>> Il mer 17 giu 2020, 23:01 Paul Davis ha > >>> scritto: > >>> > I looked at Jenkins and saw them all as connected and in sync. Is > there more to the report or was this some sort of networking burb? > > On Wed, Jun 17, 2020 at 2:20 PM Joan Touzet > wrote: > > > > IBM maintains these workers for us - will have to ask Paul Davis to > >> take > > a look. > > > > -Joan > > > > On 17/06/2020 05:36, Alessio 'Blaster' Biancalana wrote: > >> Hey folks, > >> I have a job on Jenkins that is repeatedly giving me this error: > >> > >> < > > >> > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-1 > > [2020-06-17T09:09:49.584Z] > >> Recording test results > >> < > > >> > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-2 > > [2020-06-17T09:09:49.718Z] > >> Remote call on JNLP4-connect connection from > >> 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > >> < > > >> > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-3 > > Remote > >> call on JNLP4-connect connection from > >> 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > >> > >> I was wondering, is everything ok on our Jenkins cluster? Maybe > >> there's > >> some maintenance I'm not aware of? > >> > >> Cheers, > >> Alessio > >> > > >>> > >> > > >
Re: Getting FDB work onto master
Restarting this thread. Can I get an update on where things are at? On 31/03/2020 13:13, Paul Davis wrote: There are a few other bits to `make check` that aren't included in `make check-fdb`. Updating `make check` should just be a matter of taking our test subset and applying them to `make check`. On Tue, Mar 31, 2020 at 11:04 AM Garren Smith wrote: On the fdb branch we have a make check-fdb which is a subset of all the tests that should pass. I think we should use that instead of make check On Tue, Mar 31, 2020 at 5:34 PM Joan Touzet wrote: Took a bit longer than expected, but it's been tested & validated, and then re-pushed. I'll push up the other platforms as well (except for CentOS 8, which still has a broken Python dependency). PR for the changes necessary was also merged to couchdb-ci. FDB should feel free to merge to master once `make check` is working. We can hammer out the wide matrix issues on a slower timeframe. -Joan On 2020-03-30 19:42, Joan Touzet wrote: OOPS, looks like I pushed the wrong image. I'll build the kerl-based version of the image and re-push. This will take a couple of hours, since I have to build 3x Erlangs from source. Good to know step 1 works! Next step for y'all: fix `make check`. -Joan On 2020-03-30 6:05 p.m., Robert Samuel Newson wrote: noting that https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2732/7/pipeline/ now fails because kerl isn't there. related? B. On 30 Mar 2020, at 22:11, Robert Samuel Newson wrote: Nice, make check-fdb passes for me on that branch (the 2nd time, the 1st time was a spurious failure, timing related). B. On 30 Mar 2020, at 22:04, Robert Samuel Newson wrote: Hi, Great timing, I merged something to prototype/fdb-layer without the check passing, I'm trying this now. First note, the kerl line doesn't work but it seems there's a system wide erlang 20 install instead. B. On 30 Mar 2020, at 19:50, Joan Touzet wrote: Hi everyone, hope you're all staying at home[1]. I've just pushed out a new version of our couchdbdev/debian-buster-erlang-all Docker image. This now includes the fdb binaries, as well as client libraries and headers. This is a necessary (but not sufficient) step to getting the fdb prototype merged to master. Can someone please test if this works correctly for them to build and test CouchDB (with fdb)? Here's instructions: docker pull couchdbdev/debian-buster-erlang-all docker run -it couchdbdev/debian-buster-erlang-all # then, inside the image: cd git clone https://github.com/apache/couchdb cd couchdb && git checkout . /usr/local/kerl/20.3.8.25/activate # you still need to fix make check, but Paul says this should work: make check-fdb The next step would be to fix `make check`. Then, you can merge the fdb branch to master. CI on master will be broken after fdb merge until we get answers to these questions: [2]. **REMEMBER**: Any 3.x fixes should land on the 3.x branch at this point. If they're backend specific, there's no need for them to land on master anymore. **QUESTION**: Now that we have a new feature (JWT), it's likely the next CouchDB release would be 3.1.0 - so, probably no need to land more fixes on 3.0.x at this point. Does everyone agree? -Joan "I miss restaurants" Touzet [1]: https://www.youtube.com/watch?v=rORMGH0jE2I [2]: https://forums.foundationdb.org/t/package-download-questions/2037
Re: Is everything ok on our Jenkins cluster?
On 18/06/2020 13:19, Alessio 'Blaster' Biancalana wrote: Hi Joan, Hi opened the infra bug, could you please check I've done everything correctly? https://issues.apache.org/jira/browse/INFRA-20441 Looks fine. FYI Paul Davis just updated and restarted the agents on all of the machines. Nick just got his PR through. Can you try restarting your build now? -Joan I also shared the link to the thread. Strange situation :/ @Paul could you check again? Definitely the issue wasn't fixed all day long, and it looks like it's not a networking blurb. Alessio On Thu, Jun 18, 2020 at 12:48 AM Joan Touzet wrote: Can you try opening an Infra ticket on this? https://issues.apache.org/jira Open it against the Infra project and share with them the link(s). You can also link to this mailing list discussion via https://lists.apache.org/ . -Joan On 2020-06-17 5:16 p.m., Alessio 'Blaster' Biancalana wrote: Thanks for the response Paul! Same stuff, I tried rerunning the job but it looks stuck with that error https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/6/pipeline I don't know why that happens, if you have any clue... Thanks, Alessio Il mer 17 giu 2020, 23:01 Paul Davis ha scritto: I looked at Jenkins and saw them all as connected and in sync. Is there more to the report or was this some sort of networking burb? On Wed, Jun 17, 2020 at 2:20 PM Joan Touzet wrote: IBM maintains these workers for us - will have to ask Paul Davis to take a look. -Joan On 17/06/2020 05:36, Alessio 'Blaster' Biancalana wrote: Hey folks, I have a job on Jenkins that is repeatedly giving me this error: < https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-1 [2020-06-17T09:09:49.584Z] Recording test results < https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-2 [2020-06-17T09:09:49.718Z] Remote call on JNLP4-connect connection from 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed < https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-3 Remote call on JNLP4-connect connection from 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed I was wondering, is everything ok on our Jenkins cluster? Maybe there's some maintenance I'm not aware of? Cheers, Alessio
Re: Is everything ok on our Jenkins cluster?
This was fixed by updating the agent on the FreeBSD machines. On 18/06/2020 11:20, Jan Lehnardt wrote: FWIW, I’m getting this here on the FreeBSD build: Remote call on JNLP4-connect connection from 67.223.99.43/67.223.99.43:61326 failed https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FFullPlatformMatrix/detail/master/178/pipeline Best Jan — On 17. Jun 2020, at 23:16, Alessio 'Blaster' Biancalana wrote: Thanks for the response Paul! Same stuff, I tried rerunning the job but it looks stuck with that error https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/6/pipeline I don't know why that happens, if you have any clue... Thanks, Alessio Il mer 17 giu 2020, 23:01 Paul Davis ha scritto: I looked at Jenkins and saw them all as connected and in sync. Is there more to the report or was this some sort of networking burb? On Wed, Jun 17, 2020 at 2:20 PM Joan Touzet wrote: IBM maintains these workers for us - will have to ask Paul Davis to take a look. -Joan On 17/06/2020 05:36, Alessio 'Blaster' Biancalana wrote: Hey folks, I have a job on Jenkins that is repeatedly giving me this error: < https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-1 [2020-06-17T09:09:49.584Z] Recording test results < https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-2 [2020-06-17T09:09:49.718Z] Remote call on JNLP4-connect connection from 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed < https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-3 Remote call on JNLP4-connect connection from 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed I was wondering, is everything ok on our Jenkins cluster? Maybe there's some maintenance I'm not aware of? Cheers, Alessio
Re: Is everything ok on our Jenkins cluster?
Hi Joan, Hi opened the infra bug, could you please check I've done everything correctly? https://issues.apache.org/jira/browse/INFRA-20441 I also shared the link to the thread. Strange situation :/ @Paul could you check again? Definitely the issue wasn't fixed all day long, and it looks like it's not a networking blurb. Alessio On Thu, Jun 18, 2020 at 12:48 AM Joan Touzet wrote: > Can you try opening an Infra ticket on this? > > https://issues.apache.org/jira > > Open it against the Infra project and share with them the link(s). You > can also link to this mailing list discussion via > https://lists.apache.org/ . > > -Joan > > On 2020-06-17 5:16 p.m., Alessio 'Blaster' Biancalana wrote: > > Thanks for the response Paul! > > Same stuff, I tried rerunning the job but it looks stuck with that error > > > > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/6/pipeline > > > > I don't know why that happens, if you have any clue... > > > > Thanks, > > Alessio > > > > Il mer 17 giu 2020, 23:01 Paul Davis ha > > scritto: > > > >> I looked at Jenkins and saw them all as connected and in sync. Is > >> there more to the report or was this some sort of networking burb? > >> > >> On Wed, Jun 17, 2020 at 2:20 PM Joan Touzet wrote: > >>> > >>> IBM maintains these workers for us - will have to ask Paul Davis to > take > >>> a look. > >>> > >>> -Joan > >>> > >>> On 17/06/2020 05:36, Alessio 'Blaster' Biancalana wrote: > Hey folks, > I have a job on Jenkins that is repeatedly giving me this error: > > < > >> > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-1 > >>> [2020-06-17T09:09:49.584Z] > Recording test results > < > >> > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-2 > >>> [2020-06-17T09:09:49.718Z] > Remote call on JNLP4-connect connection from > 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > < > >> > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-3 > >>> Remote > call on JNLP4-connect connection from > 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed > > I was wondering, is everything ok on our Jenkins cluster? Maybe > there's > some maintenance I'm not aware of? > > Cheers, > Alessio > > >> > > >
Re: Is everything ok on our Jenkins cluster?
FWIW, I’m getting this here on the FreeBSD build: > Remote call on JNLP4-connect connection from 67.223.99.43/67.223.99.43:61326 > failed https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FFullPlatformMatrix/detail/master/178/pipeline Best Jan — > On 17. Jun 2020, at 23:16, Alessio 'Blaster' Biancalana > wrote: > > Thanks for the response Paul! > Same stuff, I tried rerunning the job but it looks stuck with that error > > https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/6/pipeline > > I don't know why that happens, if you have any clue... > > Thanks, > Alessio > > Il mer 17 giu 2020, 23:01 Paul Davis ha > scritto: > >> I looked at Jenkins and saw them all as connected and in sync. Is >> there more to the report or was this some sort of networking burb? >> >> On Wed, Jun 17, 2020 at 2:20 PM Joan Touzet wrote: >>> >>> IBM maintains these workers for us - will have to ask Paul Davis to take >>> a look. >>> >>> -Joan >>> >>> On 17/06/2020 05:36, Alessio 'Blaster' Biancalana wrote: Hey folks, I have a job on Jenkins that is repeatedly giving me this error: < >> https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-1 >>> [2020-06-17T09:09:49.584Z] Recording test results < >> https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-2 >>> [2020-06-17T09:09:49.718Z] Remote call on JNLP4-connect connection from 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed < >> https://ci-couchdb.apache.org/blue/organizations/jenkins/jenkins-cm1%2FPullRequests/detail/PR-2893/4/pipeline/#step-117-log-3 >>> Remote call on JNLP4-connect connection from 76.9a.30a9.ip4.static.sl-reverse.com/169.48.154.118:7778 failed I was wondering, is everything ok on our Jenkins cluster? Maybe there's some maintenance I'm not aware of? Cheers, Alessio >> -- Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/
