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.
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
Pipeline and scripts for custom node 18 build (with glibc 2.17) #4
Pipeline and scripts for custom node 18 build (with glibc 2.17) #4
Changes from 62 commits
ddddc28
7e1ef7a
b1fc304
36f5f9f
4dd173c
260f10c
84e6a42
8f86ed5
545d8d1
2104c0c
d0ac37f
3cca249
5ac745d
ef3d7bc
07a3796
f375c10
10c26eb
4859c07
4e53748
17acf35
4583258
b45822e
15e9c59
43d3007
1e0e916
046ef03
5d3db88
6e887aa
a3c45fa
a7bac4e
7a08d5d
c3dd54d
c63603b
fa10326
9b0d9f9
a20eefc
000e638
805e765
d3e6284
75354d2
6b71765
3eb5955
2e589f5
3eb345d
b9916d1
2785d83
c037b40
133ccff
1813dec
922dec3
42b4990
c13eb22
07f47df
edd9232
bdd64e8
7a61c2e
702ca66
58f0c0a
e85ade7
7dde65d
fecc714
a05224f
1656a11
21f14c0
68d258e
ab58662
9957258
12ed8d8
00a8b2f
8997a62
983da3e
c18809e
8e0ae33
5c1d41e
8c34500
7ce4d9b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we want to remove this file?
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 -
This is part of the elastic's
ci-systems
build pipeline from the research where I tried to pre-build docker images, and use those as agents in buildkite. It seems that wasn't the ultimate direction, so if we're going with this kibana-buildkite pipeline, then I can clean up this other pipeline.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.
@brianseeders just to double check here, can we move on for now without using the ci-systems pipeline ?
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's up to you, but you'll have to migrate eventually. What are you not able to do?
Also, just FYI, I'm not on the CI systems team anymore
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.
I'll wait on @delanni to let you know about the challenges he found on using the ci-systems but in case we are allowed to continue with the kibana pipeline, I think we can proceed like that until we are forced to migrate eventually.
Thanks for letting me know Brian, I didn't realised before you have changed teams 🙌
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.
The track using this pipeline was a bit different than what we ultimately took. I think the ci-systems way would have been a bit better modularised in the sense that we build the agent images separately, and the build job only builds the binaries, and not the images.
I got stuck because with
drivah
, I couldn't really build multiarch images, and building separate images for separate platforms was also difficult, becausedocker
didn't find the right base images for the centos:7/arm64 combination (whereas it worked locally). This is when I back-tracked, and went on another route.The two approaches are probably mostly orthogonal, so if we're eventually moving over, then maybe I'll keep the pipeline in place, and try to work out the docker/centos issue later.
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.
I believe what you're trying to do with docker should work fine with the ci-systems agents, as long as you are using a vm-based agent and not a k8s one.
You may need to create a custom agent image with the dependencies installed to do multiarch (if you didn't already), and you might also need
enableNestedVirtualization: true
on youragents:
config in your pipeline. I'm guessing the multiarch virtualization stuff in Docker would need it.You can also just install the dependencies at runtime to test to see if it works before committing to it.
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.
For the record, we agreed with @mistic that it would be probably a waste as of now to try to fit this build on the ci-systems agents. It's probably not going to live for more than 1 year, we'll probably still have the kibana CI available to create new patch versions if needed, and hopefully the unofficial node releases will take over. (nodejs/unofficial-builds#83)