Uses of Package
org.jenkinsci.plugins.ParameterizedRemoteTrigger
Package
Description
-
ClassDescriptionDeprecated.Deprecated.since 2.3.0-SNAPSHOT - use
Auth2
instead.This object wraps aRun
,FilePath
, andTaskListener
- the typical objects passed from one method to the other in a Jenkins Builder/BuildStep implementation.
The reason for wrapping is simplicity.This object wraps aRun
,FilePath
,TaskListener
andPrintStream
- the typical objects passed from one method to the other in a Jenkins Builder/BuildStep implementation.
The reason for wrapping is simplicity on the one hand.Http response containing header, body (JSON format) and response code.Holds everything regarding the remote server we wish to connect to, including validations and what not. -
ClassDescriptionThis object wraps a
Run
,FilePath
,TaskListener
andPrintStream
- the typical objects passed from one method to the other in a Jenkins Builder/BuildStep implementation.
The reason for wrapping is simplicity on the one hand. -
ClassDescriptionThis object wraps a
Run
,FilePath
,TaskListener
andPrintStream
- the typical objects passed from one method to the other in a Jenkins Builder/BuildStep implementation.
The reason for wrapping is simplicity on the one hand. -
ClassDescriptionHolds everything regarding the remote server we wish to connect to, including validations and what not.
-
ClassDescriptionThis object wraps a
Run
,FilePath
,TaskListener
andPrintStream
- the typical objects passed from one method to the other in a Jenkins Builder/BuildStep implementation.
The reason for wrapping is simplicity on the one hand. -
ClassDescriptionThis object wraps a
Run
,FilePath
, andTaskListener
- the typical objects passed from one method to the other in a Jenkins Builder/BuildStep implementation.
The reason for wrapping is simplicity.This object wraps aRun
,FilePath
,TaskListener
andPrintStream
- the typical objects passed from one method to the other in a Jenkins Builder/BuildStep implementation.
The reason for wrapping is simplicity on the one hand.Http response containing header, body (JSON format) and response code.If the remote Jenkins server uses the "Prevent Cross Site Request Forgery exploits" security option, a CSRF protection token must be sent in the header of the request to trigger the remote job.Holds everything regarding the remote server we wish to connect to, including validations and what not.
Auth2
instead.