You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/config.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,16 @@ functionality to suit your project's specific needs.
46
46
If you repeatedly specify the same value for an option while running a
47
47
task, you can configure CumulusCI to use that value as a default value.
48
48
49
+
For example: Let's configure the update_dependencies task to force resolution strategies in sandbox orgs. The task's `force_resolution_strategy` option controls whether to force the use of specified resolution strategies even in persistent orgs:
50
+
51
+
```yaml
52
+
update_dependencies:
53
+
options:
54
+
force_resolution_strategy: True
55
+
```
56
+
57
+
When True, this allows beta and 2GP resolvers to be used in sandbox orgs, while still enforcing safety checks in production orgs. When False (default), safety checks are enforced in all persistent orgs.
58
+
49
59
For example: Let's enforce a 90% code coverage requirement for Apex
50
60
code in your project. The `run_tests` task, which executes all Apex
51
61
tests in a target org, can enforce code coverage at a given percentage
0 commit comments