[SERVER-23818] Include Evergreen task id in metadata sent to logkeeper Created: 19/Apr/16  Updated: 05/Jan/19  Resolved: 16/Feb/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.4.19, 3.5.4

Type: New Feature Priority: Major - P3
Reporter: Shraya Ramani Assignee: Yves Duhem
Resolution: Done Votes: 1
Labels: tig-resmoke
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: TIG 2017-02-13, TIG 2017-03-06
Participants:

 Description   
  1. Add a --taskId command line option to resmoke.py and add a new variable to the resmokelib.config module. The etc/evergreen.yml project configuration should then be updated to use the ${task_id} expansion in all resmoke.py invocations in order to propagate the task_id from Evergreen to resmoke.py.
  2. The task id should be sent along in POST requests to logkeeper when creating builds and tests via the "/build/" and "/build/<build_id>/test/" routes as a parameter called task_id.


 Comments   
Comment by Githook User [ 05/Jan/19 ]

Author:

{'username': 'syev', 'email': 'yves.duhem@mongodb.com', 'name': 'Yves Duhem'}

Message: SERVER-23818 Send Evergreen task Id to logkeeper

(cherry picked from commit e94d22e96718528197e82d053c37ff4ba49b42a4)
Branch: v3.4
https://github.com/mongodb/mongo/commit/cfcc7dde618e1be37fd6ab524e46b700bd372ad9

Comment by Githook User [ 16/Feb/17 ]

Author:

{u'username': u'syev', u'name': u'Yves Duhem', u'email': u'yves.duhem@mongodb.com'}

Message: SERVER-23818 Send Evergreen task Id to logkeeper
Branch: master
https://github.com/mongodb/mongo/commit/e94d22e96718528197e82d053c37ff4ba49b42a4

Comment by Shraya Ramani [ 27/Apr/16 ]

In the testParameters and buildParameters that are set, there's a new parameter task_id to be passed in.

This can be done in resmoke.py's logkeeper client by adding the task_id to the data POST'd to the "/build/" route and to "/build/<build_id>/test/" route when the build and test are created, respectively.

Comment by Max Hirschhorn [ 20/Apr/16 ]

shraya.ramani, can you update this ticket to include which logkeeper route accepts the task_id in the POST request, the name of the parameter, etc.? I think that'll make it easier to describe the necessary resmoke.py changes in the resmokelib.logging.buildlogger module.

Additionally, we should add a --taskId command line option to resmoke.py and add a new variable to the resmokelib.config module. The etc/evergreen.yml project configuration should then be updated to use the ${task_id} expansion in all resmoke.py invocations in order to propagate the task_id from Evergreen to resmoke.py to logkeeper.

Generated at Thu Feb 08 04:04:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.