|
|
|
[
Permlink
| « Hide
]
Robin Shen [09/Jul/16 12:23 AM]
Controlling this with group permission should be the way to go. Will revert this for backward compatibility in next patch release.
Another thing that came just to my mind is:
Scheduled build might be needed to rerun some time e.g. when there was an unexpected environmental problem (network issues etc). So disabling it would prevent everyone from starting a build. Why not use group permissions without "RUN_BUILD" for certain configuration subtrees? So administrators can still rerun a build and "normal" users can't. Also the description of Configuration>General Setting>Schedule states "Please note that if the configuration is disabled, the schedule will not take effect (but is able to be inherited by child configurations)." This will definitely break a lot of configurations. Sorry, but this affects a lot of other stuff.
Following scenario: We have a structure like root>tests root>tests>junit root>tests>integration and we want to schedule them all at the same time (and be able to set this time on root>tests), but the config root>tests (with "disabled"="yes") should never run. The child configurations should run of course so we activate them with "disabled"="no". Everything is the same in the configurations, so we use inheritance. The only thing that's different is one variable defining the build target (and the disabled=no). How do we achieve something like that after we update to 6.1.19? |