Avoid multiple BT instances initialization #290
Comments
Simple partial solution which will already help if someone first gets IssueTracker object and than executes multiple requirests to it is just to declare |
For the record you will have to keep a reference to the |
I believe, multiple JIRA instances is kind of exceptional case. We implemented this WA in our fork and pretty happy with it. But of course there is always space for improvements |
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
in this way we create object to connect to the remote end only once, which should improve speed of work when working often with bugs directly from Kiwi TCMS. This also makes it possible to still have multiple IT integrations in the same instance b/c they will have unique base URLs.
Description of problem
Connection to BT is being established every time when object-child of IssueTrackerType is being created. For JIRA specifically, it means that every time new jira.JIRA object is being created and new connection is being established. Taking into account possibility of multiple requests it makes sense to extract establishing the connection to some kind of singleton or classmethod.
Actually, from the first sight I would say that all methods from IssueTrackerType should be static, so calls should look like:
JIRA.add_testcase_to_issue(case, bug)
Component (web, API, etc)
core
Additional info
The text was updated successfully, but these errors were encountered: