title: How to use Jenkins pipeline `options` correctly
body: <p>Snippet generator created a <code>properties</code> block for me. First run reported</p>
  
  <pre><code>WorkflowScript: 1: The properties section has been renamed as of version 0.8. Use options instead. @ line 1, column 1.
     pipeline {
  </code></pre>
  
  <p>Replacing <code>properties</code> to <code>options</code>results with the following error:</p>
  
  <pre><code>Errors encountered validating Jenkinsfile:
  WorkflowScript: 4: options can not be empty @ line 4, column 5.
     options([$class: 'ThrottleJobProperty',
  </code></pre>
  
  <p>Here is the full <code>jenkinsfile</code> for reference</p>
  
  <pre><code>pipeline {
      agent any
  
      options([[$class: 'ThrottleJobProperty',
              categories: ['xcodebuild'],
              limitOneJobWithMatchingParams: false,
              maxConcurrentPerNode: 0,
              maxConcurrentTotal: 0,
              paramsToUseForLimit: '',
              throttleEnabled: true,
              throttleOption: 'category']])
  
      stages {
          stage("Empty" {
              steps {
                  echo "Do nothing"
              }
          }
      }
  }
  </code></pre>