[docs] Add contributor agreement prereq to dev docs

[mdavis332]

What does this PR do?

CI builds fail if the elastic contributor agreement isn't on file for a github user. However, I didn't see that info anywhere prior to trying to submit my first integration so my initial CI build failed due to it.

This PR adds that language to the dev docs about building a new integration, specifically in the Open a PR section.

Related issues

• See [ti_cif3] Add New TI integration for the Collective Intelligence Framework v3 #3839 for a PR that failed due to no contributor agreement on file at time PR was submitted.

[cla-checker-service]

💚 CLA has been signed

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-08-16T08:16:14.734+0000

• Duration: 110 min 38 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5154
Skipped	9
Total	5163

Steps errors

Expand to view the steps failures

Test integration: containerd

• Took 1 min 51 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: docker

• Took 1 min 26 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Test integration: fireeye

• Took 2 min 58 sec . View more details here
• Description: eval "$(../../build/elastic-package stack shellinit)" ../../build/elastic-package test -v --report-format xUnit --report-output file --test-coverage

Delete kind cluster

• Took 0 min 13 sec . View more details here
• Description: kind delete cluster

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[mdavis332]

i signed the contributor agreement a few days ago shortly after my CI check for #3839 failed. just a heads up for any elastic team member looking at this, perhaps there's some manual work needed once the agreement is submitted before it registers with the CI pipeline? i.e., I would have expected the CLA check to not fail today since I signed it several days ago.

[jsoriano]

Hey @mdavis332, looking to the information about you in the CLA checker, it looks like you signed the CLA with a different email address than the one used in this commit. You need to sign the CLA with the same email address that you use in your commits.

You can find here the raw patch for the commit of this PR, where your email appears: https://github.com/elastic/integrations/commit/73fcc63fe3c9a7ef5f233833368df7d7ab6f7a78.patch

Could you try to modify your commit to use the same email address you used to sign the CLA? Or sign the CLA with the email you are using in your commits?

[mdavis332]

Hi @jsoriano, thank you for the help pointing that out! Git still routinely confounds me and I (mistakenly) intuited that the cla-checker-service would use the github username supplied in the contributor agreement rather than the user.email in the git config.

As my git-foo is such that it would take me longer to figure out how to fix that commit, I just re-signed the agreement with the email addr set in that config. Will that work?

[jsoriano]

Will that work?

CLA checker seems happy now, so it seems it worked :) thanks!

[jsoriano]

/test

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (282/282)	💚
Files	97.143% (510/525)	👍 0.022
Classes	97.143% (510/525)	👍 0.022
Methods	89.175% (4910/5506)	👎 -0.883
Lines	90.919% (92580/101827)	👎 -0.908
Conditionals	100.0% (0/0)	💚

[jsoriano]

/test