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 want to separate the responsibilities of the manually trigger button on the job into two separate buttons:
a button that will force a check for all your resources that are inputs to your job
another button that will manually trigger a new build with the current versions of each resource
In order to achieve this, we will need to implement a new button that will force check all your resources that are inputs to your job. We assume it can use the GetBuildInputs and CheckResource API endpoints to achieve this. This check-all button should not block the user from starting a new build. That being said, having the check button not block on pipeline scheduling might cause some hiccups of the check-all button not being finished and the scheduler kicking off a new build with only a few of the new versions that the user expected to find.
cc @Lindsayauchin would you be able to create a design for this? Thanks a lot! 😄
We want to separate the responsibilities of the manually trigger button on the job into two separate buttons:
In order to achieve this, we will need to implement a new button that will force check all your resources that are inputs to your job. We assume it can use the GetBuildInputs and CheckResource API endpoints to achieve this. This check-all button should not block the user from starting a new build. That being said, having the check button not block on pipeline scheduling might cause some hiccups of the check-all button not being finished and the scheduler kicking off a new build with only a few of the new versions that the user expected to find.
cc @Lindsayauchin would you be able to create a design for this? Thanks a lot! 😄
Related to #2438
The text was updated successfully, but these errors were encountered: