I did some more digging on the issue and it looks like problem is in the getParametersFromWorkUnit() method. On Freestyle jobs, the conditional that checks unit.context.actions gets populated with values, but for Pipeline jobs it does not.

The WorkUnit object that is passed to getParametersFromWorkUnit() for a normal job looks like this:

hudson.model.queue.WorkUnit@53acb86e[work=Working]

, where "Working" is the name of the job. For Pipeline jobs, it looks like

hudson.model.queue.WorkUnit@496091d7[work=part of Throttle-this #11]

, where "Throttle-this" is the name of the job and "#11" is the build number.

To try and summarize:

Freestyle jobs where the plugin works:

- WorkUnit object: hudson.model.queue.WorkUnit@53acb86e[work=Working]
- WorkUnit.context: hudson.model.queue.WorkUnitContext@14401e37
- WorkUnit.context.actions: [hudson.model.ParametersAction@7e92e075, hudson.model.CauseAction@1d3d3d46]

Pipeline jobs where the plugin does not work:

- WorkUnit object: hudson.model.queue.WorkUnit@496091d7[work=part of Throttle-this #11]
- WorkUnit.context: hudson.model.queue.WorkUnitContext@47a7768b
- WorkUnit.context.actions: []

TCB plugin is not integrated with Pipeline, so it is a New Feature.

Closing as a duplicate of JENKINS-31801

Are you sure, it is duplicate: when I looked at JENKINS-31801, it seems to be about supporting throttle feature within the pipeline. Whereas if you look at the screenshot attached to this issue, it is about using TCB and pipeline like any other normal job.

And this specific issue is that the feature in TCB plugin "to throttle based on job parameters" for pipeline jobs does not work whereas it works for normal jobs.

hemanglavana I am sure. TCB plugin is not integrated with Pipeline, which is explicitly mentioned in https://github.com/jenkinsci/pipeline-plugin/blob/master/COMPATIBILITY.md . It means that any TCB plugin logic may work incorrectly with Pipeline.

thx for clarifying

Questioning why this request was closed. I have the same comment as hemanglavana, this issue seems to be asking about throttling pipelines based on parameter values. I do not see anything in the throttle concurrent build pipeline documentation related to parameter throttling. Am I looking in the wrong place?

https://github.com/jenkinsci/throttle-concurrent-builds-plugin#throttling-in-jenkins-pipeline

oleg_nenashev, Could you please look at this one? Now, this should be a bug and not Feature. 

any update on this? I saw it was linked to the workUnitContext issue

+1, any update on this ? we've used this plugin in the past but once we moved to pipelines its not working anymore, can't limit by parameters. 

We are having the same issue.
1. Uncheck "Do not allow concurrent builds"
2. Check "Throttle concurrent builds"
     -> Check "Prevent multiple jobs with identical parameters from running concurrently"

Below is Pipeline as code for the above steps:

// disableConcurrentBuilds(), --> Note concurrency is enabled since this line is commented out.
[$class: 'ThrottleJobProperty', categories: [], limitOneJobWithMatchingParams: true, maxConcurrentPerNode: 0, maxConcurrentTotal: 0, paramsToUseForLimit: '', throttleEnabled: true, throttleOption: 'project']

Having the same issues not being able to throttle pipeline jobs based on parameters, has this received any attention/help/updates? This is causing a lot of pain on our internal CI. Running Jenkins jenkins-2.222.1 with latest TCB.

Fixed in jenkinsci/throttle-concurrent-builds-plugin#117.

Released in 2.2.

I have a similar issue where Jenkins is NOT preventing a second build from running, despite it sharing a parameter value with the already running first build.
It says here the issue was fixed in v2.2, however I've tried with all versions starting from v2.2 all the way to v2.6, and all failed. 
Considering no one else has complained since the v2.2 release, does anyone have an idea as to what could be wrong in my setup that would cause the issue still to occur?
Thanks you all.

smits
We have been using this simple patch instead of the fix for this issue for quite a while. Feel free to try it.