Skip to end of metadata
Go to start of metadata

Plugin Information

No information for the plugin 'openconnect-plugin' is available. It may have been removed from distribution.

Use VPN connectivity as part of your build and deployment process.

Plugin Requirements

  • Jenkins must be installed on Linux
  • OpenConnect must be installed
  • Jenkins user process must be part of sudoers (outlined below)

Linux Configuration Steps

  • sudo apt-get install openconnect
  • add the following lines to the bottom of /etc/sudoers (ubuntu configuration)

jenkins ALL=NOPASSWD:/usr/sbin/openconnect*
jenkins ALL=NOPASSWD:/bin/kill*

#Note: The above configuration assumes Jenkins master is running under the "jenkins" user

Known Limitations

  • Jenkins Master support only
  • Multiple VPN connectivity is not possible due to existing limitations with VPN protocol

Use Cases

1) Deploying to a network automatically or manually as part of your deployment process

You can't automate against remote networks secured by a third party! For example, let's say you have a customer that depends on you to push out maintenance releases to the applications you've developed. This plugin will
allow you to automatically connect to their VPN and deploy the application (see my other plugin, WebSphere Deployer Plugin)

2) Deploying to a network automatically or manually as part of your build process

You want to execute a build against a remote network (possibly remote maven build).

Things I'd like to accomplish (indirectly)

  • Checkout code from a remote network, build, test, and deploy it on the remote network
  • Automate stress testing against a remote network
  • Automate penetration testing against a remote work
  • No labels