 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Nguyen Duc Long [05/Feb/26 04:08 AM]
I can track all builds trigger by user @deverloper.
You might consider adding a "Trigger By" filter to https://wiki.pmease.com/display/QB15/Manage+Build+Subscriptions
As I mentioned earlier, I need to track a specific build ID.
Developer: : I just applied a change and built it at https://xxx.xx/build/12345. Wait for it to finish and check the output. I am in the role of Tester: ok...I will check once every 5 minutes. This is exactly what I would like to understand from you: under what circumstances, or for which types of builds, would you like to watch them, and which builds would you prefer not to watch? In my view, when a build has just started, we do not yet know whether it will succeed or fail.
If you could provide certain rules to determine which types of builds require attention, we may potentially incorporate such rules into the existing notification mechanisms. Otherwise, randomly watching a build does not seem very reasonable. The solutions you shared all aim to monitor all builds of a configuration under specific conditions.
What I'm referring to is tracking a specific build under any given condition. Please see below docs:
1. https://wiki.pmease.com/display/QB15/Build+Notifications 2. https://wiki.pmease.com/display/QB15/Sending+Notifications+to+Microsoft+Teams 3. https://wiki.pmease.com/display/QB15/Sending+Notifications+to+Slack 4. https://wiki.pmease.com/display/QB15/Customize+Notification+Templates 5. https://wiki.pmease.com/display/QB15/Manage+Build+Subscriptions It seems I don't know how to use these features, please provide detailed instructions.
Automatically receive emails when build 12345 is complete (or fail, cancel) . QuickBuild supports the following notification mechanisms:
1. Build results can be sent to channels such as Slack, Microsoft Teams, and others via webhooks. 2. Users can subscribe to the build results of the configurations they care about and receive notifications via email or the Tray Monitor. From my perspective, these mechanisms already address the scenario you described. Is there anything I might be missing? "I am a build output tester. I do not have the authority to build or modify configurations."
dev: I just applied a change and built it at https://xxx.xx/build/12345. Wait for it to finish and check the output. tester: ok...I will check once every 5 minutes. I just don't want the tester to have to manually check if the build process is complete. @Nguyen,
We're investigation this issue now. We need more context on this issue. We have already had several channels to send build notifications. You can use webhook to send notifications to Slack or MS Teams, you can subscribe configuration notifications via email, Tray Monitor, etc. So I'm curious why you still need watch a running build? How you pick the builds you want to watch? You will watch some and ignore others? We plan to add this next major release which will be available early next year.
| |||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Able to watch a running build 