ci(jenkins): support windows build

[v1v]

Highlights

• Support testing in windows for the Node.js version 12.
• appveyor is not supported anymore.

Iterations

• Support docker in Windows. got some issues when using linux docker containers. no matching manifest for windows/amd64 in the manifest list entries

Tasks

• Validate it works with versions: 10 and 12
• Validate it works with the same list of versions stated in: .ci/.jenkins_nodejs.yml
• Revert a37263c
• process.title does not match the value in the CI windows workers #1418 should be fixed
• Required to install ES, and other services as it was initially configured with.
• If possible, let's bump a Linux worker with all the required docker containers and configure the Windows CI Worker with those env variables to be able to use those services out of the box. Then it might simplify dramatically the Windows environment...

Follow-ups

• Transform windows test output to JUnit trends within the CI Pipeline. Let's work on this in a second iteration
• When merged then it's required to disable the GH check for continuous-integration/appveyor/pr
• Support testing in windows for all the Node.js versions defined in .ci/.jenkins_nodejs.yml
  • the toplevel linux agent is the one with all the services up and running, so can it be used with concurrent test executions?
• Generate docker images in the internal docker registry to just consume them.
• Docker orchestration with docker-compose.

Deprecated

Docker for windows is not required

See c21dc48

• Docker images for:
  • cassandra.
  • elasticsearch.
  • mongodb.
  • mssql.
  • mysql.
  • postgres.
  • redis.

[Qard]

Nice! Looking forward to seeing this land. :)

Also, we can probably drop AppVeyor in this PR too. What do you think, @watson?

[watson]

Good idea @Qard - let's just remove AppVeyor in the PR as well 👍

[Qard]

LGTM other than minor comment about version pinning.

[watson]

Does this need to be backported to the 2.x branch as well, or does it just need to be in master to also run Windows tests for PRs to and when new commits land in the 2.x branch`?

[Qard]

I would try to backport it, if we can. Getting appveyor fully out of the pipeline in all actively maintained branches would be ideal.

[mdelapenya]

LGTM 👍

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
126da47, 86210cc

Please, read and sign the above mentioned agreement if you want to contribute to this project

[watson]

🎉 All looks good 👍 Just have a small question that's probably very easy to answer

[watson]

Great work!!

[watson]

The two CI failures can safely be ignored IMO as long as you squash-and-merge and give the resulting squashed commit a valid commit message. If you prefer to verify this beforehand, you can squash locally and force push up to your feature branch of course.