-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI] Fixed container images packaging #6972
base: main
Are you sure you want to change the base?
Conversation
…tic-agent into ci_fix_packaging_containers
command: | | ||
buildkite-agent artifact download build/distributions/** . --step 'packaging-ubuntu-x86-64' --build ${BUILDKITE_TRIGGERED_FROM_BUILD_ID} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build matrix is not used because we need unique step keys
This pull request is now in conflicts. Could you fix it? 🙏
|
Build takes too long because of the emulation |
This pull request is now in conflicts. Could you fix it? 🙏
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
⏳ Build in-progress, with failures
Failed CI StepsHistory
cc @pazone |
|
@@ -108,7 +122,7 @@ steps: | |||
- integration-ess | |||
steps: | |||
- label: "x86_64:non-sudo: {{matrix}}" | |||
# only packaging-ubuntu-x86-64 artifact dependency is required | |||
depends_on: packaging-ubuntu-x86-64 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: let's stick with one style (can be done in a follow up) either like this, or like below using a list
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is about to be removed #7184
@@ -27,6 +27,8 @@ steps: | |||
- integration-ess | |||
steps: | |||
- label: "Win2022:sudo:{{matrix}}" | |||
depends_on: | |||
- packaging-windows |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious: how come we didn't need such explicit dependencies until now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. The integration tests trigger step depends on the entire int-packaging
group that wraps all the packaging steps. So these dependensies give no effect. On the other hand, they strictly outline the exact step dependencies
@@ -78,6 +84,9 @@ steps: | |||
provider: "gcp" | |||
machineType: "n1-standard-8" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: in a future PR let's get rid of those ancient n1 instance types in favor of n2.
key: "packaging-ubuntu-x86-64" | ||
# Build matrix is not used for packaging in favor to unique step keys | ||
# Packaging linux/amd64 | ||
- label: "Packaging: linux/amd64 rpm" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we update this to show rpm,deb,tgz since it's doing all three?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is still possible to use the build matrix with 2 axes for arm and x86. The comment is added for questions like this one
What does this PR do?
Fixed container image packaging by setting proper packaging variables
We now have 9 packaging steps:
Packaging: linux/amd64 rpm
Artifacts :
Packaging: linux/arm64 rpm
Artifacts :
Packaging: linux/amd64 deb
Artifacts :
Packaging: linux/arm64 deb
Artifacts:
Packaging: linux/amd64 tar.gz
Artifacts:
Packaging: linux/arm64 tar.gz
Artifacts:
Packaging: Containers linux/amd64
14 amd64 images. See the build
Packaging: Containers linux/arm64
14 arm64 images. See the build
Packaging: windows/amd64 zip
Why is it important?
The container images will be used by k8s integration tests instead of rebuilding them.
Checklist
./changelog/fragments
using the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself