build: build layers with latest versions of ddtrace for system-tests to consume #629
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
florentinl
changed the title
purple4reina
approved these changes
Jul 10, 2025
Yes exactly using the github API, the system-tests already have a helper function to fetch these: https://github.com/DataDog/system-tests/blob/636c04e8a2e887983fc7c57a58cfc94d95ec6ca7/utils/scripts/load-binary.sh#L120 |
florentinl
deleted the
florentinl/APPSEC-58014/publish-build-artifacts-for-system-tests
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds a github workflow to build layers on each update on the
mainbranch. It uses themainbranch ofdd-trace-pyas well to really provide thelatestdev version available.Note: the job takes around 7m (building ddtrace takes the majority of the time)
Motivation
The goal is to have artifacts for up-to-date development version of the layers for the system-tests to consume easily.
This allows the system-tests repo to just fetch a layer without needing any knowledge on how to build layers.
Testing Guidelines
I tested this workflow on my development branch. You can find the execution here: https://github.com/DataDog/datadog-lambda-python/actions/runs/16189728626
Additional Notes
This PR adds a build matrix for every combination of architecture and python version. I don't aim on running system-tests for all of them.
On the one hand I find it practical to have all variants available in the same place and since they all built in parallel adding more combinations doesn't make the CI longer. On the other hand, It also makes sense to just build what is going to be used. I can remove some targets if you think this is too much.
Types of Changes
Check all that apply