[JIRA] (JENKINS-47882) Unable to connect MongoDB with MONGODB-CR authentication

1 view
Skip to first unread message

timjacomb1@gmail.com (JIRA)

unread,
Nov 2, 2018, 2:18:02 PM11/2/18
to jenkinsc...@googlegroups.com
Tim Jacomb assigned an issue to Tim Jacomb
 
Jenkins / Bug JENKINS-47882
Unable to connect MongoDB with MONGODB-CR authentication
Change By: Tim Jacomb
Assignee: Tomas Westling Tim Jacomb
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

timjacomb1@gmail.com (JIRA)

unread,
Nov 2, 2018, 2:18:03 PM11/2/18
to jenkinsc...@googlegroups.com
Tim Jacomb started work on Bug JENKINS-47882
 
Change By: Tim Jacomb
Status: Open In Progress

timjacomb1@gmail.com (JIRA)

unread,
Nov 2, 2018, 2:26:01 PM11/2/18
to jenkinsc...@googlegroups.com

timjacomb1@gmail.com (JIRA)

unread,
Nov 2, 2018, 2:54:02 PM11/2/18
to jenkinsc...@googlegroups.com
Tim Jacomb edited a comment on Bug JENKINS-47882
Branch here that can be tested out:
https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/master...timja:upgrade-minimal-changes

As far as I can tell it works,
I'm currently working on test failures

kingsley.chan@oocl.com (JIRA)

unread,
Nov 4, 2018, 8:23:01 PM11/4/18
to jenkinsc...@googlegroups.com

Thanks Tim.

timjacomb1@gmail.com (JIRA)

unread,
Nov 23, 2018, 10:07:01 AM11/23/18
to jenkinsc...@googlegroups.com
Change By: Tim Jacomb
Status: In Progress Review

timjacomb1@gmail.com (JIRA)

unread,
Nov 23, 2018, 10:07:03 AM11/23/18
to jenkinsc...@googlegroups.com
Tim Jacomb commented on Bug JENKINS-47882
 
Re: Unable to connect MongoDB with MONGODB-CR authentication

PR has been complete for awhile, it is awaiting review...

timjacomb1@gmail.com (JIRA)

unread,
Nov 23, 2018, 10:08:02 AM11/23/18
to jenkinsc...@googlegroups.com

In the meantime i have forked it and am publishing hpi's here:
https://github.com/hmcts/build-failure-analyzer-plugin/releases

will@nowhereetc.com (JIRA)

unread,
Dec 12, 2018, 12:38:02 PM12/12/18
to jenkinsc...@googlegroups.com

Note; I am able to connect just fine with mongo v3.4.18 and BFA v1.20.0, but after upgrading to BFA v1.21.0 it can no longer connect.

Rolling back, the connection returns.

I'm guessing there may be some migration instructions that are required?

 

timjacomb1@gmail.com (JIRA)

unread,
May 25, 2019, 4:46:03 PM5/25/19
to jenkinsc...@googlegroups.com
Change By: Tim Jacomb
Status: In Review Closed
Resolution: Fixed
Released As: 1.21.0
Reply all
Reply to author
Forward
0 new messages