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'm using the conditional build step with Stash Notify. If the conditional build step prevents the Stash notification then in Stash I get "build in progress" indefinitely.
Regardless of the conditional build step Stash gets notified at the beginning of a build that it's in progress.
Maybe have the plugin not do the initial notification if conditional build step is being used? Or have an option to not use the initial notification all together?
The text was updated successfully, but these errors were encountered:
This is an issue for me as well. My deployment job can run from an upstream build job - and in that case I have the GIT_COMMIT ID. But it can also run manually - pulling down a user-specified version from our maven repo. In this case - I do not have a GIT_COMMIT ID. I'd really love to use the Conditional Build step to determine if I have a GIT_COMMIT ID - and if so - notify Stash. As the OP indicates this does not seem to work because of the "build in progress" notification, which can not be wrapped in a conditional build step. Hoping for an easy fix, like an opt-out of the "build in progress" notification, or recognize that it is part of a conditional build step - and check if the step is enabled before notifying.
I'm using the conditional build step with Stash Notify. If the conditional build step prevents the Stash notification then in Stash I get "build in progress" indefinitely.
Regardless of the conditional build step Stash gets notified at the beginning of a build that it's in progress.
Maybe have the plugin not do the initial notification if conditional build step is being used? Or have an option to not use the initial notification all together?
The text was updated successfully, but these errors were encountered: