If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 14/Jul/11 11:23 PM
Updated: 14/Jul/11 11:23 PM
|
|
Component/s: |
None
|
Affects Version/s: |
3.1.52
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
I use the Triggered build hyperlink that you provide in the step workflow view for those trigger steps that are "Wait for Finish" = true, very useful. I understand that it is difficult for you to provide this hyperlink for "Wait for Finish" = false trigger steps since you can't wait for the triggered build to start to ask it for its build id. However, I would still like to see this hyperlink if at all possible. My previous post concerning my new build workflow using my custom piece of code to manage my build graph uses "Wait for Finish" = false so that the queue worker thread setting is honored. Is there something you can do, like perhaps have the triggered build record the id of the build and step that triggered it and then once a build id of it is available, send that information back to the triggering build so that it can add the hyperlink?
|
Description
|
I use the Triggered build hyperlink that you provide in the step workflow view for those trigger steps that are "Wait for Finish" = true, very useful. I understand that it is difficult for you to provide this hyperlink for "Wait for Finish" = false trigger steps since you can't wait for the triggered build to start to ask it for its build id. However, I would still like to see this hyperlink if at all possible. My previous post concerning my new build workflow using my custom piece of code to manage my build graph uses "Wait for Finish" = false so that the queue worker thread setting is honored. Is there something you can do, like perhaps have the triggered build record the id of the build and step that triggered it and then once a build id of it is available, send that information back to the triggering build so that it can add the hyperlink? |
Show » |
There are no comments yet on this issue.
|
|