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
Currently the build number option is parsed as an integer (parseInt(pluginOptions.buildNumber, 10)) but in Sauce this is a "string".
When setting up CI on branches, it is useful to complement the build with extra information so perhaps there's no real reason to enforce it as a number.
The text was updated successfully, but these errors were encountered:
nelsonsilva
changed the title
Build number should not be parsed and integer
Build number should not be parsed as integer
Jan 19, 2018
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!
Currently the build number option is parsed as an integer (
parseInt(pluginOptions.buildNumber, 10)
) but in Sauce this is a "string".When setting up CI on branches, it is useful to complement the build with extra information so perhaps there's no real reason to enforce it as a number.
The text was updated successfully, but these errors were encountered: