| << Back to previous view |
|
[QB-2740] Manual trigger disabled builds dont work off schedules
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 6.1.9 |
| Fix Version/s: | 6.1.19, 6.1.20 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Sivakumar Kailasam | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
We have certain builds where we don't want users to trigger builds manually, instead have the configs trigger a build if repo has changed. Between combinations of cron vs periodic schedules and repo changes inclusion vs if a variable is true, we figured out that these combinations don't work if the disabled option is set to no. The help text below that field says "If checked, the configuration will not able to be triggered manually." So we assumed that having this set to yes and setting a scheduled conditional build would let us achieve what we wanted. But only on setting it to no does this behavior work. This needs to be fixed. Or correct us if we were wrong.
|
| Comments |
| Comment by Robin Shen [ 15/Jun/16 12:44 AM ] |
| Will be fixed in next patch release. |
| Comment by AlSt [ 07/Jul/16 05:44 AM ] |
|
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? |
| Comment by AlSt [ 07/Jul/16 05:51 AM ] |
|
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. |
| Comment by 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. |