Hi Folks, The upgrade to the newest stable version of jenkins had a couple challenges, but went faster than I expected. A daily build and test is running now, as well as a pull-request check test. So far, so good.
--Steve > -----Original Message----- > From: Steve Varnau <[email protected]> > Sent: Thursday, May 23, 2019 9:12 AM > To: [email protected] > Subject: RE: Automated test problems > > External > > Following up on jenkins issues, the jenkins server was not sick on its own, > but > was being attacked with malware. We are running a bit older version of > jenkins, and it is exploiting a vulnerability there. I have not been able to > fully > close the hole without a major upgrade to the jenkins server and related > plugins. > > I'm babysitting the current test that we've tried to run for several days, but > after that, I plan to take jenkins offline and work on upgrade. It might > take a > few days to get everything working properly. > > In the mean time, I suggest contributors, reviewers, and committers have a > little more explicit conversations about what regression testing has been > done on changes coming in. There is nothing jenkins was doing that can't be > done with regular regression testing and reviews. > > --Steve > > > -----Original Message----- > > From: Steve Varnau <[email protected]> > > Sent: Wednesday, May 22, 2019 11:38 AM > > To: [email protected] > > Subject: Automated test problems > > > > External > > > > Hi folks, > > > > The automated testing has been very flakey over the past week or two. I > > had thought there were network communication issues in the hosting > > provider, but I now think the jenkins server itself was a bit sick. I am > hopeful > > that it is sorted out now and we are back to the stable environment we had > > before. > > > > --Steve
