build(jenkins): update sdk

[garymathews]

No description provided.

[build]

	Warnings
⚠️	guid is inconsistent across platforms. It is f0d8fd44-86d2-4730-b67d-bd454577aeee in android/manifest and fee93b77-8eb3-418c-8f04-013664c4af83 in ios/manifest
⚠️	SDK version declared in Jenkinsfile (9.0.0.v20200207060625) does not match iOS' titanium.xcconfig value (9.0.0.v20200205142057)

	Messages
📖	💾 Here are the artifacts produced: ti.map-android-5.0.1.zip ti.map-iphone-3.3.0.zip
📖	✅ All tests are passing Nice one! All 44 tests are passing.
📖	🎉 - congrats on your new release

Dependencies with modified semantic versioning:

• @commitlint/cli - from ^8.2.0 to ^8.3.5
• @commitlint/config-conventional - from ^8.2.0 to ^8.3.4
• @seadub/danger-plugin-junit - from ^0.1.1 to ^0.1.2
• @seadub/danger-plugin-titanium-module - from 0.0.4 to 0.0.7
• danger - from ^7.1.0 to ^9.2.10
• eslint - from ^5.10.0 to ^6.8.0
• eslint-config-axway - from ^4.1.1 to ^4.5.0
• eslint-plugin-jasmine - from ^2.10.1 to ^4.1.0
• husky - from ^3.0.8 to ^4.2.1
• lint-staged - from ^9.4.1 to ^10.0.7
• titanium-docgen - from ^0.2.0 to ^4.2.0

Generated by 🚫 dangerJS against 396a9b2

[jquick-axway]

@sgtcoolguy, the Jenkins build always fails with this PR. The log states that the Android emulator fails to startup. Happens every time we kick off a build. Perhaps that's a lie and something else is wrong?

[sgtcoolguy]

I'm seeing the same when I try to run the android test locally. I'll have to take a deeper look

[sgtcoolguy]

OK, I think it's unrelated to this PR and is a new issue cropping up. I suspect that the android adb binary changed in some slight way that is throwing off our emulator code to not pick up when the emulator is booted after starting it ourselves. If I have an emulator pre-booted before running, that works, but if I don't, it show stew same error as here where it thinks it's never booted fully (though it is). cc @cb1kenobi

[sgtcoolguy]

Here's the PR for the android emulator fix: tidev/node-titanium-sdk#140

[jquick-axway]

@sgtcoolguy, thanks for digging into this. I know we can disable snapshot support for each avd. We can do this via the emulator's GUI or via the INI file. Perhaps we should do this until you and Chris Barber come to terms on what the final CLI change should be? We can also launch the emulator with the --no-snapshot command line argument to disable it too.

[sgtcoolguy]

I assume you did this manually, because the package-lock.json wasn't also updated. You'll need to update that files as well.

Next time, use npm --no-git-tag-version version patch and it'll update both.