max multiple executions does not seem to be a mapped option for a job

[codydiehl]

When you go to a job's Edit UI

there is an option named:

Multiple Executions? No / Yes
Limit Multiple Executions?: n

It appears that multiple executions is mapped to a value named:
allow_concurrent_executions = true
This option is equivalent to the Yaml definition export of multipleExecutions: true

however I am struggling to find an equivalent to Limit Multiple Executions?

Which maps to this within the yaml definition if you export the job:
maxMultipleExecutions: '10'

Would it be feasible to include this missing functionality when feasible please?

[fdevans]

Thanks for the feature request! You're right - we support allow_concurrent_executions (which maps to multipleExecutions in the API), but we don't currently support limiting the number of concurrent executions via maxMultipleExecutions.

This is a valid feature that should be added. We'll investigate and implement this for an upcoming release.

If you have access to a sample job export (JSON or YAML) that includes the maxMultipleExecutions field, it would be helpful to make sure we solve for your use case - feel free to share it here (sanitized if needed).

[codydiehl]

Sure thing.
Thanks!

Here is an example job definition in yaml, if you still require it.

- defaultTab: output
  description: Ansible Ping target hosts + become to validate SeDebugPriviledge Security Policy
  executionEnabled: true
  group: ansible
  loglevel: INFO
  maxMultipleExecutions: '5'
  multipleExecutions: true
  name: ansible-ping
  nodeFilterEditable: true
  nodefilters:
    dispatch:
      excludePrecedence: true
      keepgoing: true
      rankOrder: ascending
      successOnEmptyNodeFilter: false
      threadcount: '50'
    filter: ''
  nodesSelectedByDefault: false
  plugins:
    ExecutionLifecycle: {}
  scheduleEnabled: true
  sequence:
    commands:
    - configuration:
        ansible-become: 'false'
        ansible-encrypt-extra-vars: 'false'
        ansible-extra-param: -T 360
        ansible-playbook-inline: |
          - name: Ping
            hosts: all
            become: true
            tasks:
              - ping:
                when: ansible_os_family != "Windows"
              - win_ping:
                when: ansible_os_family == "Windows"
              - debug:
                  msg: |
                    fqdn: "{{ ansible_fqdn | lower }}"
                    user: "{{ ansible_user | lower }}"
        ansible-ssh-passphrase-option: option.password
        ansible-ssh-use-agent: 'false'
      description: Ping target hosts
      nodeStep: true
      type: com.batix.rundeck.plugins.AnsiblePlaybookInlineWorkflowNodeStep
    keepgoing: true
    strategy: parallel

[fdevans]

Good news - this has been added and will be included in the 1.2.0 release!

You can now use max_concurrent_executions to limit how many times a job can run at once:

resource "rundeck_job" "ansible_ping" {
  name                        = "ansible-ping"
  project_name                = "my-project"
  allow_concurrent_executions = true
  max_concurrent_executions   = 5
  
  command {
    shell_command = "ansible all -m ping"
  }
}

This matches the maxMultipleExecutions: '5' setting from your YAML example. When the limit is reached, additional execution requests will be queued.

See PR #233 for implementation details.