Oleg Nenashev added a comment - 2018-08-13 17:02 Not sure what is this query about. Jobs are triggered via CLI or REST API, there should be nothing specific to Pipeline

Markus Baur added a comment - 2018-08-15 15:27 In order to run pipeline scripts from a remote point one could write a script like this: curl -X POST "https://jenkins.host/job/my_cool_job/build" triggering a job on the jenkins server. For some good reasons this does not work without autorization, so jenkins returns "Authentication required" which is expected. Some time ago it was possible to add an authenticationToken to a pipelineJob, so this would essentially become curl -X POST "https://jenkins.host/job/my_cool_job/build" --data "token=MySuperSecretToken" So everyone in our department could trigger the job by invoking a simple script. There is one job for every computer in our department doing some management and thus these jobs change frequently. Because of this we are using jobDSL to update and configure all of those jobs. Since the token (and with it scm and concurrentBuild) are deprecated for pipelineJobs now, our infrastructure falls apart. So it would be nice if you could redirect us to the appropriate migration paths or reintroduce these features.