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
I really appreciate this plugin—it fits our workflow perfectly.
However, I've noticed a few areas that could greatly enhance its usability.
It's fantastic that we can set the GitHub PR status, but there's an issue when builds are triggered manually: the lack of a GitHubPRCause causes this post-build step to fail, marking the entire job as failed.
Although builds can be triggered via the plugin's Github branches page, this method isn't very practical for builds that require parameters (I haven't found a way to trigger a build with parameters from there). This becomes problematic when needing to initiate a job from a specific branch with non-default parameters.
Currently, the only solution I see is to maintain a separate Jenkins project for manual triggers, with the github-integration-plugin disabled.
It would be great to have the ability to trigger builds with parameters directly through the plugin! Alternatively, having the ability to silently handle errors during manual triggers would also be beneficial.
The text was updated successfully, but these errors were encountered:
Also - it happens even when build triggered by plugin, but for Branch (not PR). It seems we need a separate pipeline for these branch triggers, where no post-action set?
Hello!
I really appreciate this plugin—it fits our workflow perfectly.
However, I've noticed a few areas that could greatly enhance its usability.
It's fantastic that we can set the GitHub PR status, but there's an issue when builds are triggered manually: the lack of a GitHubPRCause causes this post-build step to fail, marking the entire job as failed.
Although builds can be triggered via the plugin's Github branches page, this method isn't very practical for builds that require parameters (I haven't found a way to trigger a build with parameters from there). This becomes problematic when needing to initiate a job from a specific branch with non-default parameters.
Currently, the only solution I see is to maintain a separate Jenkins project for manual triggers, with the github-integration-plugin disabled.
It would be great to have the ability to trigger builds with parameters directly through the plugin! Alternatively, having the ability to silently handle errors during manual triggers would also be beneficial.
The text was updated successfully, but these errors were encountered: