Jira import is not anymore synchronous. As of today three conditions are required to be able to import from Jira: * `display_jira_importer` must be truthy in forgeconfig * `sys_nb_backend_workers` must be > 0 in local.inc * `redis_server` must be set in redis.inc[0] Violate one of this condition and jira import will be switched off. This is a best effort. We currently have no easy way to detect if worker events will be processed. We consider previous conditions good enough for a first draft. We may improve this later. How to test: * Switch off jira import Go to plugins » tracker » create a new tracker => The option to create trackers from jira is not available * Switch on jira import Go to plugins » tracker » create a new tracker => The option to create trackers from jira is available Switch off jira import Select jira server, project, issue type, Just before submiting the last step (tracker name & co), switch off jira import. Submit your tracker creation. => An error message is displayed. * Switch on jira import Create a tracker from Jira. Wait for the worker event to be processed. => Jira is imported Part of story #14766: Have an import from jira structure [0] https://docs.tuleap.org/developer-guide/back-end/redis.html Change-Id: Ie8ea3375051a68a6663581f6dd109c860693c59a

+303 −173

Author

Nicolas Terray (nterray) 2020-05-15 16:07

Committer

Nicolas Terray (nterray) 2020-05-25 12:20

Hash 1fda1da9c8dff3f967e37edd3cb2de1e2623a9cf

Parent 46761acca2d4c57f47ac05bfa92a75d33a9b8048

Reference git #tuleap/stable/1fda1da9c8dff3f967e37edd3cb2de1e2623a9cf