-
Description of the problem, including code/CLI snippetHey guys Im creating MR with python-gitlab. After creation i need to check for mr_conflicts and pipeline state.
But I dont get actual info with this requests! I have answer with data like MR was created just now and has no info about coflicts or pipelines. Same time if i start another script from different console only for checking MR status i got right actual information. Another moment. If in the script with MR creation i run cycle
still no updated info. How can i get actual info about MR inside script? Expected Behaviorget actual info about MR inside creation MR script Actual BehaviorI get data like MR was created just now and no updates in its state Specifications
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
My initial thought is that the Gitlab server needs more time. It takes time from when the MR is created until the Gitlab server has figured out if the MR has conflicts. For a test of this I would keep retrying to get the status for at least two minutes. If during two minutes that status does not get updated then that would seem strange. But if it does get updated within that time then you will need to figure out how long is a safe amount of time to wait to make sure you get the updated information. |
Beta Was this translation helpful? Give feedback.
-
In fact my cycle worked fine and status updated after 2-3 secs |
Beta Was this translation helpful? Give feedback.
In fact my cycle worked fine and status updated after 2-3 secs
I was confused by output of this string
mr_pipeline = getattr({get_mr}, 'pipeline', 'No pipeline')