[SERVER-80547] Add task to verify scons/bazel integration works Created: 30/Aug/23  Updated: 29/Oct/23  Resolved: 09/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: New Feature Priority: Major - P3
Reporter: Steve Gross Assignee: Steve Gross
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Participants:

 Comments   
Comment by Githook User [ 08/Sep/23 ]

Author:

{'name': 'Steve Gross', 'email': 'steve.gross@mongodb.com', 'username': 'stevegrossmongodb'}

Message: SERVER-80547 Verify scons/bazel build output is present
Branch: master
https://github.com/mongodb/mongo/commit/8a806a9540cba9556f86bdee14121ef599bb3dcd

Comment by Trevor Guidry [ 08/Sep/23 ]

steve.gross@mongodb.com I think it should be very easy. You can put bash commands in the evergreen.yml

 

In this case I think you just need to put 

test -f path/to/build/artifact

which will exit with 1 if the file does not exist and mark a failure

Comment by Zack Winter [ 07/Sep/23 ]

I don't think it's that likely of a failure mode, but checking that an artifact was actually created would verify that the bazel part of the scons build wasn't skipped. A couple examples of this could be skipping the bazel execution due to caching or the environment variable that triggers it changing. This could also verify that the final artifact is published to the proper location, at the cost of being a bit of a change-detector.

If it's easy to add in a bash `test -f "$filepath"` step to the evergreen task, it would be nice to have. If it's a pain then I'm fine without it.

Comment by Githook User [ 07/Sep/23 ]

Author:

{'name': 'Steve Gross', 'email': 'steve.gross@mongodb.com', 'username': 'stevegrossmongodb'}

Message: SERVER-80547 Fix scons/bazel build, and add it to Evergreen CI
Branch: master
https://github.com/mongodb/mongo/commit/0fbfd003fe27c33faf649e2a8fecc38786827075

Generated at Thu Feb 08 06:43:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.