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
When we do a builder release today, we need to choose a set of fully qualified builder packages to give to operations. I think what we want is for operations to be able to perform a /expeditor promote habitat rc which will automatically promote packages in the rc channel to stable.
This would involve the following:
set up expeditor artifact channels. We want a unstable, rc and stable
Once we validate that acceptance (which consumes unstable) we use the /expeditor promote slack command to promote to rc which should trigger a script to hab pkg promote the builder-api, builder-api-proxy, and builder-jobsrv packages at the head of unstable to rc
Promoting from the rc channel should promoye to stable both in expeditor and builder.
This is similar (not identical) to the habitat release process.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.
When we do a builder release today, we need to choose a set of fully qualified builder packages to give to operations. I think what we want is for operations to be able to perform a
/expeditor promote habitat rc
which will automatically promote packages in therc
channel tostable
.This would involve the following:
unstable
,rc
andstable
unstable
) we use the/expeditor promote
slack command to promote torc
which should trigger a script tohab pkg promote
thebuilder-api
,builder-api-proxy
, andbuilder-jobsrv
packages at the head of unstable torc
rc
channel should promoye tostable
both in expeditor and builder.This is similar (not identical) to the habitat release process.
The text was updated successfully, but these errors were encountered: