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
While debugging a recently nightly build failure, we ran into a few issues:
Notifications from dev and tag builds are mixed together in our pudl-deployments slack channel which caused confusion around which logs to look at. Instead we should have a thread for each build so the sequence of messages for builds don't get mixed together.
We should make our build ids more human readable to it's easier to find logs and outputs. Currently its gitsha-branch but it could be something like YYYY-MM-DD-{config}-{sha}-{branch}.
The nightly-build-output.catalyst.coop bucket contains assets from our nightly dev builds, our manually triggered branch and tag builds. We should probably rename the bucket to be more general. Something like pudl-builds.catalyst.coop.
The text was updated successfully, but these errors were encountered:
While debugging a recently nightly build failure, we ran into a few issues:
pudl-deployments
slack channel which caused confusion around which logs to look at. Instead we should have a thread for each build so the sequence of messages for builds don't get mixed together.gitsha-branch
but it could be something likeYYYY-MM-DD-{config}-{sha}-{branch}
.nightly-build-output.catalyst.coop
bucket contains assets from our nightly dev builds, our manually triggered branch and tag builds. We should probably rename the bucket to be more general. Something likepudl-builds.catalyst.coop
.The text was updated successfully, but these errors were encountered: