ci: add smoke testing job definition

[kruskall]

Companion PR to #310

Add job definition

[ghost]

💚 Build Succeeded

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-10-11T13:27:32.479+0000

• Duration: 8 min 54 sec

Test stats 🧪

Test	Results
Failed	0
Passed	164
Skipped	2
Total	166

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

There are some questions regarding when this particular job should run, see #310 (comment)

Those answers might imply some changes in this PR.

At the moment, the current changes will imply:

• Run always for every push in any PR or main.

If you can clarify when this job should run we can configure it accordingly.

OTOH, I normally like to keep support for PRs, and disable the automation for triggering the build for those PRs if needed. Hence, it's possible to run the pipeline for any PR manually (using the Jenkins UI, or even a GitHub comment), that's handy when testing changes related to the pipeline itself.

[kruskall]

OTOH, I normally like to keep support for PRs, and disable the automation for triggering the build for those PRs if needed. Hence, it's possible to run the pipeline for any PR manually (using the Jenkins UI, or even a GitHub comment), that's handy when testing changes related to the pipeline itself.

Agree, I think it's okay to only run it on main.