On Oct 23 17:03, Honza Horak wrote: > I'm seeing the same error today: > jenkins.JenkinsException: Error in request. Possibly authentication failed > [403]: Forbidden > > Is it possible that it was not fixed for sclo-sig user? or is the problem > back for everybody? Or could it be problem on my side? > > Honza > > On 06/01/2016 05:12 PM, Brian Stinson wrote: > > On May 31 20:43, Brian Stinson wrote: > > > On May 31 13:00, Colin Walters wrote: > > > > > > > > > > > > On Fri, May 27, 2016, at 01:01 PM, Brian Stinson wrote: > > > > > > > > > We had a hotfix to re-enable plugin lists but it looks like I missed one > > > > > of the permission checks. I'll investigate, re-patch and report back > > > > > here. > > > > > > > > Anything we can do to help with this? At the moment this is > > > > a blocker for continuing to use CentOS CI, and while no time > > > > is opportune for CI to break, I've been in the middle of increasing > > > > investment in it and trying to bring others on board. > > > > > > Issuing a Jenkins saferestart as soon as the currently running jobs are > > > finished to get the hotfix in. Can you verify tomorrow or later this > > > week? > > > > > > --Brian > > > > This should be done now. > > > > --Brian > > _______________________________________________ > > Ci-users mailing list > > Ci-users at centos.org > > https://lists.centos.org/mailman/listinfo/ci-users > > Hi Honza, The appropriate fix for this was announced here (set query_plugins_info = False in your jjb.ini): https://lists.centos.org/pipermail/ci-users/2016-October/000420.html If you enable this setting and still run into trouble let us know. Cheers! -- Brian Stinson