[SERVER-30415] Exclude new "evergreen" agent binary name from automatic process killing in Evergren Created: 28/Jul/17  Updated: 30/Oct/23  Resolved: 28/Jul/17

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.4.6, 3.5.10
Fix Version/s: 3.4.7, 3.5.11

Type: Improvement Priority: Critical - P2
Reporter: Ernie Hershey Assignee: Ernie Hershey
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Build Ready
Participants:

 Description   

Somewhere around c236f77b24c3cfe35c36f23777836142ca84fe90, the Evergreen agent binary name changed from "main" to "evergreen". This will prevent inadvertently killing new agent processes.



 Comments   
Comment by Githook User [ 28/Jul/17 ]

Author:

{'email': 'ernie.hershey@10gen.com', 'username': 'ehershey', 'name': 'Ernie Hershey'}

Message: SERVER-30415 Update Evergreen agent binary name

(cherry picked from commit 2a910e6c65327a71f6656ecacf6fbca66baeb517)
Branch: v3.4
https://github.com/mongodb/mongo/commit/49aed372a06b74db45c60071d6cc8b38c8efd63a

Comment by Ernie Hershey [ 28/Jul/17 ]

I checked and 3.0 and 3.2 don't have this logic in evergreen.yml, so I believe we only need to backport to 3.4. sam.kleinman I leave that less urgent commit in your hands but let me know if you want backup.

Comment by Githook User [ 28/Jul/17 ]

Author:

{'email': 'ernie.hershey@10gen.com', 'username': 'ehershey', 'name': 'Ernie Hershey'}

Message: SERVER-30415 Update Evergreen agent binary name
Branch: master
https://github.com/mongodb/mongo/commit/2a910e6c65327a71f6656ecacf6fbca66baeb517

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