feat: fetch channel information from Hydra#1146
Draft
fricklerhandwerk wants to merge 13 commits into
Draft
Conversation
fricklerhandwerk
force-pushed
the
fetch-channels-from-hydra
branch
8 times, most recently
from
a56773b to
aaf61e4
Compare
Since the source of truth for latest evaluations and builds is in Hydra, from now on we're only using the infrastructure team's `channel.nix` for information about the release state of channels. This change also reduces the number of evaluations to one per release branch. We hard-code tracking the small channel variants, since those advance fastest.
fricklerhandwerk
force-pushed
the
fetch-channels-from-hydra
branch
from
4c84165 to
d52c30e
Compare
Collaborator
Author
|
Reviewed with @florentc |
- Make even more explicit what we're getting from Hydra - Test parsing actual live samples - Business logic now separates channel tips from branch tips
Collaborator
Author
|
This took quite a while. Touching the concept just a bit required a ton of rework in detail. But also, doing this diligently revealed how many moving parts there actually are, which we were generously papering over previously. I was particularly paranoid about testing things, since we'll have fun if something goes wrong in a live deployment. That produced most of the change, because making it both robust and sustainable is not really straightforward. There are were so many loose ends there, spend days chasing them, and now I just realized the integration test is probably still broken. Though right now I'm stuck figuring out why |
fricklerhandwerk
force-pushed
the
fetch-channels-from-hydra
branch
2 times, most recently
from
4f744ff to
0435fe9
Compare
fricklerhandwerk
force-pushed
the
fetch-channels-from-hydra
branch
from
0435fe9 to
4f1e07f
Compare
fricklerhandwerk
force-pushed
the
fetch-channels-from-hydra
branch
from
c70d439 to
a329d01
Compare
fricklerhandwerk
force-pushed
the
fetch-channels-from-hydra
branch
from
1b3f101 to
625763b
Compare
fricklerhandwerk
force-pushed
the
fetch-channels-from-hydra
branch
from
a2ad711 to
d5798e5
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Further towards #864
Since the source of truth for latest evaluations and builds is in Hydra,
from now on we're only using the infrastructure team's
channel.nixfor information about the release state of channels.