Why are triggers disabled by default when I clone a project?
I can imagine that if you link a separate repository, that it should be disabled. But at this stage I was just cloning with a global repository. Anyway, I think that if there is only 1 repository linked to a configuration, the trigger should only watch that (and be enabled).
Hi Geert,
We decided to disable triggers when cloning after finding that some were being triggered immediately. Generally when you make a clone you would want to change some setting first before the triggers run. I will however schedule a task to revisit this - maybe it’s better to set the cloned configuration to be disabled by default instead?
Yes, 100 % agree. Just disable the whole thing so I can enable it when I am ready. We have extremely well defined templates where we only have to update a few variables and we have a new project set up (in the future (v2/v3) we hope for base templates where only changes will be stored per configuration). Anyway, we only need to change the variables, then we can enable it, that would be great.
Note this is low priority, just want to give you ideas to make the product even better (it’s already near perfection to me).
Thanks!
+1 … we also just copy the trunk configuration for specific versions. this is a really good pattern and we always have the same traps with those triggers
We’ve now implemented a change to disable the configuration instead of the triggers on cloning. This will be in the next release version.