For example when build status should be notified when pipeline comes from some other code than the repo.
Imagine a pipeline with multiple downstream sub-jobs. Those jobs may be triggered manually as an optional verification or simply too long for base job.
UTs good, static good additional tests ok time-consuming verification failed
\/ \/ \/
0) repo A build --> trigger 1 --> notify --> END
\
1) \ test repo pipeline --> a very long process or processes --> notify --> END
3) Another test repo pipeline with repo A revision as paramter --> notify -- END
But I think the fact that stashnotifier is active and download count is rather substantial talks by itself 
Hi, Matt, thanks for the request. Can you elaborate a bit more on your use case, and what you are trying to achieve with a separate build status notification?