set default port for firewall

Since port parameter seems to be missing from init.pp, use the same logic to determin it as in cli_helper.pp

add possibility to disable/uninstall plugins

- add possibility to disable/uninstall plugins.
- move $plugins_host outside of if block, as it looks identical for both cases.
- rename all occurrences of ${name}.hpi with ${plugin}

For uninstall/disable, there are 2 ifs added, each with 2 execs (one for jpi an one for hpi)

  if ($version == 'absent' or $version == 'uninstall') {
   test -f ${plugin_dir}/${plugin}  && rm -rf ${name} ${plugin} ${name}.jpi ${name}.jpi.pinned && touch ${name}.jpi.disabled
   test -f ${plugin_dir}/${name}.jpi -a ! -f ${plugin_dir}/${name}.jpi.disabled && touch ${plugin_dir}/${name}.jpi.disabled
} elsif ($version == 'disable' or $version == 'disabled') {
   test -f ${plugin_dir}/${name}.jpi -a ! -f ${plugin_dir}/${name}.jpi.disabled  && touch ${plugin_dir}/${name}.jpi.disabled
   test -f ${plugin_dir}/${plugin} -a ! -f ${plugin_dir}/${plugin}.disabled         && touch ${plugin_dir}/${plugin}.disabled
} else {
}

update firewall
Add support for "No Proxy Host" list

The Jenkins proxy configuration supports a whitelist of nodes that will
not use the the proxy when Jenkins (or some plugins) attempts to
communicate. As of right now, this setting will be cleared by Puppet
if any other aspect of the proxy configuration is managed.

This commit adds support for the "No Proxy Whitelist" by adding a new
parameter to the `jenkins` class. The new parameter, `no_proxy_list`,
will accept an array of hostname patterns to no longer use the proxy to
access. The `no_proxy_list` parameter is optional and will default to
`undef`.
Add tests for the `no_proxy_list` parameter

This commit adds tests to verify the behaviour of the `no_proxy_list`
parameter on the `::jenkins` class. The tests verify what happens when
the parameter is set and unset.
Improve how `::jenkins::proxy` accesses variables

Without this commit, the template referenced by the class
`::jenkins::proxy` was using the `lookupvar()` method in the ERB
tags to access variables from other class scopes. This method of
accessing the variables is at the mercy of changes to Puppet's internal
Ruby API. This method is also not very clear as to what is happening
without having to read through both the class and the template.

This commit changes the method of variable access to use a simple
variable assignment operation in the Puppet DSL to bring the values of
the required variables into the local scope. This is preferred as it
makes the template easier to read and keeps the template's operations
relative to the place from where it is called. In the Puppet code
itself, it is now more clear as to what data is used by the
`::jenkins::proxy` class and where that data is coming from.
Add documentation for `no_proxy_list` parameter
Merge pull request #202 from trlinkin/proxy_work

Proxy work
Fix typo in job/present.pp
Fix for #174 allows setting $jenkins::port

When used with strict variables turned on, firewall.pp expects
$jenkins::port to be set. Overriding in hiera will not correct as it's
still an undefined variable in code. This fix allows port to be set and
provides a default in params.pp
Merge pull request #204 from eshamow/fix_undefined_jenkins_port

Fix for #174 allows setting $jenkins::port
Merge pull request #203 from miles-/patch-1

Fix typo in job/present.pp
Merge pull request #191 from cristi1979/master

set default port for firewall
Refactor some code to get the configured Jenkins port with the jenkins_port function

Fixes #206
Merge pull request #207 from rtyler/issues/206-firewall-port-refactor

Introduce the jenkins_port function
Switch to using a metadata.json

Requires something newer than puppet 3.5.1 to build FWIW

Fixes #177
Update the changelog with the most recent two releases
It was called Nestor
Merge remote-tracking branch 'upstream/master'