Migrate Jenkinsfile to GH Actions Workflow

[reakaleek]

Summary

Migrate Jenkinsfile to GH Actions Workflow

Details

Add docker layer caching to avoid docker pull rate limit.

Tasks

• Migrate Jenkinsfile
• Delete Jenkins Job config
• Delete Jenkins Job
• Update sheet

Depends On:

• Add docker-layer-caching action facade apm-pipeline-library#1979
• Fix docker-layer-caching action apm-pipeline-library#1982

[apmmachine]

❕ Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

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-12-20T15:27:28.245+0000

• Duration: 12 min 15 sec

Test stats 🧪

Test	Results
Failed	0
Passed	144
Skipped	0
Total	144

Steps errors

Expand to view the steps failures

Checks if running on a Unix-like node

• Took 0 min 0 sec . View more details here

🤖 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!)

[amannocci]

LGTM

[reakaleek]

FYI

I had to change the command gem update --system in the Dockerfile (b115db9).
The solution was taken from rubygems/rubygems#2534 (comment). Otherwise, all the tests with docker images <=ruby:2.5 would fail while trying to update with the error:

ERROR:  Error installing rubygems-update:
	There are no versions of rubygems-update (= 3.4.1) compatible with your Ruby & RubyGems
	rubygems-update requires Ruby version >= 2.6.0. The current ruby version is 2.5.9.229.
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory @ dir_chdir - /vendor/ruby_2.5/gems/rubygems-update-3.0.3
Updating rubygems-update
The command '/bin/sh -c gem update --system &&       gem install bundler:$BUNDLER_VERSION' returned a non-zero code: 1
Service 'specs' failed to build : Build failed
Error: Process completed with exit code 1.

P.S. This error is unrelated to the migration and started appearing during development. It was working just fine in earlier commits.