You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very helpful to have a nightly workflow in our
actions. This could be run over night (well, someone's night),
ensuring that the reprobuilds always work. In addition it alleviates
the problem release captains face during every release:
The developer tags the release
Then uploads the tag
Builds the reprobuild, but during the build something got changed
The version string now is something like v24.02-modded due to
the dirty tree.
The CI could tell us ahead of time if a given reprobuild would result
in such a broken version string, and we would be able to always
cross-check the reprobuilds, avoiding accidental back and forth during
the release.
The text was updated successfully, but these errors were encountered:
It would be very helpful to have a nightly workflow in our
actions. This could be run over night (well, someone's night),
ensuring that the reprobuilds always work. In addition it alleviates
the problem release captains face during every release:
v24.02-modded
due tothe dirty tree.
The CI could tell us ahead of time if a given reprobuild would result
in such a broken version string, and we would be able to always
cross-check the reprobuilds, avoiding accidental back and forth during
the release.
The text was updated successfully, but these errors were encountered: