Cleanup on standardizing elasticsearch classifier in artifact names #130473
Conversation
breskeby
added
:Delivery/Build
|
Pinging @elastic/es-delivery (Team:Delivery) |
breskeby
added
the
:Delivery/Packaging
|
Linking here the follow-up infra PR: https://github.com/elastic/infra/pull/42419 for reference (I'll add soon a commit to also update for the recently added 9.1 branch) |
|
@alina-bacalete fyi. this is a bit more complex in elasticsearch as our update tests use code from other version branches. I'm not sure we can migrate all branches at ones. I initially try to get main running and we can see from there. |
breskeby
force-pushed
the
standardize-amd64-artifact-names
branch
2 times, most recently
from
f82d90b to
bc8e3ed
Compare
breskeby
force-pushed
the
standardize-amd64-artifact-names
branch
2 times, most recently
from
db63da4 to
5547c10
Compare
breskeby
changed the title
|
@alina-bacalete this ended up being way more refactoring in our interrnals than just renaming the docker context artifacts. I stepped back again and took another look and decided to cover the plain renaming in a simpler PR here: #130643 The idea is that we can easily apply this fix with a way smaller surface easier on all active branches and not block you with our shenigans on cleaning up / refactoring build internals |
breskeby
force-pushed
the
standardize-amd64-artifact-names
branch
from
2eb2e0e to
610108c
Compare
We want to sync across the stack on architecture naming and artifact names containing architecture information
breskeby
force-pushed
the
standardize-amd64-artifact-names
branch
from
610108c to
ae901ea
Compare
We want to sync across the stack on architecture naming and artifact names
containing architecture information