Manual deploy of the msbuild.zip plugin file into Jenkins

[Matthew Wright]

Due to firewall restrictions, I have to download plugin packages and upload them instead of using the update mechanism Jenkins provides.

How to do this for the msbuild.zip and mstest.zip deployment packages is the question as I haven't found anything on this after a lengthy search.

TIA.

MW

[Sami Tikka]

I believe Jenkins does not have any support for uploading msbuild/mstest into your Jenkins server. This is usually the case with build tools.

-- Sami

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Adam Westhusing]

Do you have direct access to the machine?  You should be able to put the plugins in the Jenkins/plugins directory and then install the plugin through the UI.  I believe if you already have it in the plugins directory, Jenkins will use the local copy.

[Matthew Wright]

Thanks for this guys,

The msbuild plugin (same for mstest) are packaged as zip files.  The manual upload through the Jenkins UI chokes on this type of file because it isn't a *.hpi file.  I had tried just copying the unzipped package directory to the plugins directory but, without a matching .jpi file for that plugin, Jenkins didn't recognize having to load it.

Last night I just used my personal system to load the plugins through the standard method of using the Available tab and checking the ones I wanted.  Somehow, that method is able to load those packages correctly.  Copying the directory and matching .jpi files onto my work system then worked fine.

MW