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
When the repository has a branch policy on master but does NOT check the "Limit merge types" option, RenovateBot crashes with an unhandled null.
Enabling the option (but leaving all options selected - so effectively the same thing) fixes the crash.
e.g. checked like this screenshot is fine, but if I uncheck this, it crashes out.
The exception is thrown from node_modules\renovate\dist\platform\azure\azure-helper.js line 212 when it tries to do Object.keys(policyConfigurations) and policyConfigurations is null.
From the log:
ERROR: Repository has unknown error (repository=MyOrg/MyRepo)
"err": {
"message": "Cannot convert undefined or null to object",
"stack": "TypeError: Cannot convert undefined or null to object\n at Function.keys (<anonymous>)\n at Object.getMergeMethod (/home/vsts/.config/yarn/global/node_modules/renovate/dist/platform/azure/azure-helper.js:212:20)\n at process._tickCallback (internal/process/next_tick.js:68:7)"
}
The text was updated successfully, but these errors were encountered:
elwynelwyn
changed the title
Crash on Azure when "Limit merge types" option is unchecked
Crash on Azure when branch policy "Limit merge types" option is unchecked
Oct 23, 2019
This is a:
I'm using:
via this VSTS task:
https://marketplace.visualstudio.com/items?itemName=jyc.vsts-extensions-renovate-me
Please describe the issue:
When the repository has a branch policy on
master
but does NOT check the "Limit merge types" option, RenovateBot crashes with an unhandled null.Enabling the option (but leaving all options selected - so effectively the same thing) fixes the crash.
e.g. checked like this screenshot is fine, but if I uncheck this, it crashes out.
The exception is thrown from
node_modules\renovate\dist\platform\azure\azure-helper.js
line 212 when it tries to doObject.keys(policyConfigurations)
andpolicyConfigurations
is null.From the log:
The text was updated successfully, but these errors were encountered: