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
Is it out of scope to add a button to trigger pipelines from the UI (similar to jenkins/Circle/Gitlab)? I know you can re-trigger pipelines using /retest using chatops, but sometimes, chatops can get a bit chatty (too many comments may distract reviewers).
I can take a look at adding this feature, if that's fine.
The text was updated successfully, but these errors were encountered:
Hi,
yes in my opinion it's out of the scope of this project, because it's not read-only anymore once you start adding such actions.
I agree that chatops can be chatty, but as a benefit every action is logged ;-)
yes in my opinion it's out of the scope of this project, because it's not read-only anymore once you start adding such actions.
When I see read-only, I think that the UI should not have the ability to change pipeline/task definitions (similar to jenkins replay or configure pipeline) or any jx related files inside the .lighthouse directory , but the ability to re-run a failed pipeline or task or step would be incredible useful to the end users imho.
chiming here a bit late but i agree with @ankitm123 suggestion. having a retry button would significantly increase productivity and developer experience of Jenkins X as a whole.
Is it out of scope to add a button to trigger pipelines from the UI (similar to jenkins/Circle/Gitlab)? I know you can re-trigger pipelines using
/retest
using chatops, but sometimes, chatops can get a bit chatty (too many comments may distract reviewers).I can take a look at adding this feature, if that's fine.
The text was updated successfully, but these errors were encountered: