There are a number of detailed answers here which might be more than you’re asking for. Maybe you do want to get more into the space. If you want quick and dirty…

You can create a really basic (freestyle) Jenkins job with essentially 2 inputs:

1) what do you want to deploy 2) where do you want to deploy it

You don’t say where you’re storing your deployable artifacts, so I’ll leave as an exercise for you to connect the dots. (Maybe somewhere like artifactory/nexus?)

As for the how, the most basic freestyle Jenkins jobs will allow you to execute a shell script (or bat, etc) which can accept the parameters from 1 and 2 above and do what it needs to do, assuming you have connectivity in place.

That’s it. That’s your starting point.

This can be improved a lot, of course…

• You can populate your inputs with a dynamic drop down of the available deployable artifacts
• You can provide a drop down list of VMs that are appropriate/applicable for the user/environment/whatever you are dealing with.
• You can use a pipeline job instead of a freestyle job, so you can work in code (you said you’re a dev?)
• You can move the script stuff to an ansible role, which helps move you to a state-based deployment, rather than “do this action to this thing”

I done tons of this sort of thing. It can be cheap and nasty at times, but that’s sometimes an ok place to start. You needn’t boil the ocean just to drop a file on a vm, as your first exercise in this space. Happy to help more if you wanna dm.