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
we'd need a workItemPlannerApprove() function we could use in pipelines - along with maybe a configuration option on the fabric8-pipelines ConfigMap to know if we should use planner or stick with jenkins approvals on a per project basis.
Then the workItemPlannerApprove() step would create a new WIT issue for the current BuildConfig namespace + name + space; with the build number (Build.name) and wait for it to be approved using however many +1s as required using RBAC and whatnot; then when the issue is approved/closed the workItemPlannerApprove() would continue. So like the default jenkins approval step; just reusing WIT
The text was updated successfully, but these errors were encountered:
we'd need a
workItemPlannerApprove()
function we could use in pipelines - along with maybe a configuration option on thefabric8-pipelines ConfigMap
to know if we should use planner or stick with jenkins approvals on a per project basis.Then the
workItemPlannerApprove()
step would create a new WIT issue for the current BuildConfig namespace + name + space; with the build number (Build.name) and wait for it to be approved using however many +1s as required using RBAC and whatnot; then when the issue is approved/closed theworkItemPlannerApprove()
would continue. So like the default jenkins approval step; just reusing WITThe text was updated successfully, but these errors were encountered: