[chromium-dev] PSA: Renaming main chromium builders

[m***@chromium.org]

If you don’t care about the names of chromium builders, you can stop
reading now

Hi all!

We are in the process of renaming the main chromium builders to follow the
naming standards at bit.ly/chromium-build-naming. The new naming convention
is “target”-(optional-descriptors)-build_config"; an example of this is
“win-archive-rel”. https://crbug.com/905879 is the tracking bug.

If you have some script or process which relies on these names, they may be
affected. The main chromium builders which do build archival (listed here
<https://ci.chromium.org/p/chromium/g/chromium/builders>) have been renamed
once, and will be renamed again soon. Anything relying on the builds
uploaded by those builders shouldn’t break, but if you rely on builds from
other builders having certain names in Google Cloud Storage (or another
system), they might break.


Here are a few renames I’m going to be doing soon in
https://crbug.com/888810, as an example of what renames will look like:

-

android-{rel,dbg} -> android-archive-{rel,dbg}
-

mac-{rel,dbg} -> mac-archive-{rel,dbg}
-

mac_chromium_rel_ng -> mac-rel
-

win{,32}-{rel,dbg} -> win{,32}-archive-{rel,dbg}
-

win7_chromium_rel_ng -> win7-rel
-

linux-{rel,dbg} -> linux-archive-{rel,dbg}
-

linux_chromium_rel_ng -> linux-rel

The {} notation is bash brace expansion. android-{rel,dbg} means both
android-rel and android-dbg. These will respectively be renamed to
android-archive-rel and android-archive-dbg.

Reply to this thread, or comment on the tracking bug
<https://crbug.com/905879>, if you have any questions or comments.

Stephen

[Christian Biesinger]

Will data on the flakiness dashboard be migrated to the new names?

If you don’t care about the names of chromium builders, you can stop reading now
Hi all!
We are in the process of renaming the main chromium builders to follow the naming standards at bit.ly/chromium-build-naming. The new naming convention is “target”-(optional-descriptors)-build_config"; an example of this is “win-archive-rel”. https://crbug.com/905879 is the tracking bug.
If you have some script or process which relies on these names, they may be affected. The main chromium builders which do build archival (listed here) have been renamed once, and will be renamed again soon. Anything relying on the builds uploaded by those builders shouldn’t break, but if you rely on builds from other builders having certain names in Google Cloud Storage (or another system), they might break.
android-{rel,dbg} -> android-archive-{rel,dbg}
mac-{rel,dbg} -> mac-archive-{rel,dbg}
mac_chromium_rel_ng -> mac-rel
win{,32}-{rel,dbg} -> win{,32}-archive-{rel,dbg}
win7_chromium_rel_ng -> win7-rel
linux-{rel,dbg} -> linux-archive-{rel,dbg}
linux_chromium_rel_ng -> linux-rel
The {} notation is bash brace expansion. android-{rel,dbg} means both android-rel and android-dbg. These will respectively be renamed to android-archive-rel and android-archive-dbg.
Reply to this thread, or comment on the tracking bug, if you have any questions or comments.
Stephen
--
--
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/b133b1e0-7988-4f7f-aa09-d0a418761c75%40chromium.org.