Task states not being synced
Issue #22
resolved
Hi Julius,
It appears that the tasks states are not maintained when replicating templates.
I have your latest plugin, running on Bamboo 5.14.4.1 right now. The log appears to be clean, and it looks like everything but the tasks states is being replicated. Can you help me try and debug this?
Comments (21)
-
repo owner
-
repo owner
- changed status to wontfix
-
reporter
Hi Julius,
That option would be very much appreciated. I thought the 'attempt to maintain task states' checkbox would have dealt with this, but it doesn't work any more (or maybe it never did?)
For my use case, I'd like that checkbox to be in the template's misc configuration along with the 'Requires server pause' checkbox.
-
repo owner
So the template to dictate this is a master that will override anything.
Can be done.
Julius
-
repo owner
- marked as enhancement
-
repo owner
- changed status to open
-
reporter
Julius, before you totally launch yourself into this, I just would like to clarify:
Shouldn't this setting do what I need it to do? 'Attempt to maintain task states' I do have it checked, but it's not working.
-
repo owner
it should wipe the states make them as in template
-
reporter
Ok, then this is the bug I'm actually reporting - it stopped syncing the states. I don't know exactly when it stopped, though I recently upgraded from Bamboo 5.12 to 5.14.4.1. I will re-check to make sure I wasn't just seeing things or running the wrong template.
-
repo owner
i will review also the code to see if the new merge engine is not breaking this
-
reporter
Thank you. I can confirm that this feature is broken. The plans which use a specific template are not correctly syncing the task states, even though they are told to do so. This will also cause trouble for the Dynamic Task Switcher.
-
repo owner
I have tested on my instance and everything works fine, mine is 5.14.3.1.
Can you try one thing, tick the option, save, untick it then save again.
Julius
-
repo owner
I have added one hotfix to print the settings it receives internally regarding state replication:
You can try with that and see if the merge state is false
Julius
-
repo owner
I tested again the features up to version 5.15.0.1, and cannot find anything wrong.
Question for you are, you templating the tasks ? The task state is maintained during task replication, so there is a logical dependency between the 2.
Julius
-
reporter
Hi Julius, sorry for the slowness - dealing with fires daily.
I have the following options checked:
- Template Tasks Definition
- Attempt to maintain task states
- Merge Job Misc Configuration
These are checked on my template, and in the actual build plan.
I'll try to run your hotfix plugin ASAP.
-
repo owner
on template you dont need to check anything other then ... is a template
on the child plan remove the attempt to maintain task states.
make sure your tasks have unique descriptions
Julius
-
reporter
Hi Julius, this is what I see in the logs:
WARN [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-9] [LoggingServlet] Found a plan ( GENERICS-CSSHARP-BIO ) that has a template PT-CSHARP-JRS PT-CSHARP WARN [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-9] [LoggingServlet] Tasks size: 9 merge model 1 merge states true merge tasks true merge trigger false merge requirements true WARN [AtlassianEvent::0-BAM::EVENTS:pool-1-thread-9] [LoggingServlet] Final Task List Size: 9
-
reporter
I finally figured out what you meant ... 'doh! You're ok to close this.
I finally understood that 'attempt to maintain task states' means attempt to maintain the states as set in the target build plan. So, not a bug or anything strange after all. Sorry for taking up all this time!
-
reporter
- changed status to resolved
Not a bug.
-
Account Deactivated
Maybe change maintain to preserve for better clarification?
-
repo owner
Good idea, will keep it in mind.
Thanks, Julius
- Log in to comment
Hi George,
unfortunately I have bad news for you, this is by design. What most people do, they have some fat template with scripts etc and for example 3 types of test result parsers. In the actual build they enable the task they need only.
So what we did until now was to maintain based on name the task state very carefully.
The only thing we can do is to add a new feature for you, a tick box that states, no matter what replicate the task states.
Julius