Merge remote-tracking branch 'upstream/master' into transaction_ignor…

…e_urls

* upstream/master:
  [CI] compare with the calculated SHA commit (elastic#336)
  add link to PHP documentation
  Link to create-agent-issues.sh in spec process

.ci/Jenkinsfile

@@ -81,7 +81,6 @@ pipeline {
             ]
             env.GHERKIN_SPECS_UPDATED = isGitRegionMatch(
               from: "${env.GIT_PREVIOUS_SUCCESSFUL_COMMIT}",
-              to: "${env.GIT_COMMIT}",
               patterns: regexps)
 
             // regexp for JSON specs
@@ -90,7 +89,6 @@ pipeline {
             ]
             env.JSON_SPECS_UPDATED = isGitRegionMatch(
               from: "${env.GIT_PREVIOUS_SUCCESSFUL_COMMIT}",
-              to: "${env.GIT_COMMIT}",
               patterns: regexps)
           }
         }

README.md

@@ -12,7 +12,7 @@
 | Java Agent                | [apm-agent-java][]    | [📘 elastic.co][apm-agent-java-docs]    | [📂 contrib][apm-agent-java-contrib]
 | JavaScript RUM Agent      | [apm-agent-rum-js][]  | [📘 elastic.co][apm-agent-js-base-docs] | [📂 contrib][apm-agent-rum-js-contrib]
 | Node.js Agent             | [apm-agent-nodejs][]  | [📘 elastic.co][apm-agent-nodejs-docs]  | [📂 contrib][apm-agent-nodejs-contrib]
-| PHP Agent                 | [apm-agent-php][]     | elastic.co - TBD                        | [📂 contrib][apm-agent-php-contrib]
+| PHP Agent                 | [apm-agent-php][]     | [📘 elastic.co][apm-agent-php-docs]     | [📂 contrib][apm-agent-php-contrib]
 | Python Agent              | [apm-agent-python][]  | [📘 elastic.co][apm-agent-python-docs]  | [📂 contrib][apm-agent-python-contrib]
 | Ruby Agent                | [apm-agent-ruby][]    | [📘 elastic.co][apm-agent-ruby-docs]    | [📂 contrib][apm-agent-ruby-contrib]
 | .NET Agent                | [apm-agent-dotnet][]  | [📘 elastic.co][apm-agent-dotnet-docs]  | [📂 contrib][apm-agent-dotnet-contrib]

specs/agents/process-spec.md

@@ -49,6 +49,7 @@ Every change that affects more than one agent should be initiated via a PR again
   They make sure the issues are assigned to a stack release milestone,
   based on the milestone of the agent table.
   The table should be amended to include the link to all the implementation issues.
+  The [`create-agent-issues.sh`](../../scripts/create-agent-issues.sh) script is your friend here.
   This makes it easier to see the current implementation state for each agent and makes it easy to verify that there's an issue for each agent.
   Agent teams can still change the milestone if priorities shift.
   However, they should let their team lead know.