Concourse CI resource which install msi package in a remote window box.

Written in python as part of my concourse learning exercises.

Similary structured as other concourse resource concourse-smb-share wich was intentionaly written in javascript as node.js project. Now i can compare.

Yes it's serious question. Why involve more than 10 years old windows deployment technologies in pretty modern devops continuous integration pipeline?

Firstly, it is possible and secondly, at least for me, they are some kind of deep diving courses in CI world.

And why not a Jenkins? Its plugins support everything in the world. It's personal, I don't like java projects at all, ups ...

First of all, i pipeline define resource type:

- name: win-deploy
  type: docker-image
  source:
    repository: vavere/concourse-win-deploy

Second configure resource:

- name: win-server
  type: win-deploy
  source:
    host: bigone
    user: ((admin_name))
    pass: ((admin_pass))

And as posibly last step in pipeline jobs deploy your product:

- put: win-server
  params:
    file: result/product.msi

Sorry, I'm still learning python.

The MIT License (MIT)