[Release] Update test environments for 8.1.2

[elasticmachine]

Update test environment versions to the correct Elastic Stack version.

Merge only after the release of 8.1.1.

[botelastic]

This pull request doesn't have a Team:<team> label.

[ruflin]

@klacabane @matschaffer This looks off. Likely it should be 8.0.1 or similar? Same below.

[matschaffer]

Seems a little weird, yeah. Not sure what opens these PRs. Guessing something @elastic/observablt-robots manages?

[v1v]

We don't manage this, the scripts are stored in ingest-dev, the snippet for the specific makefile goal in charge of this, can be seen below:

PATCHNUM ?= $(shell echo $(CURRENT_RELEASE) | cut -f3 -d.)
LATEST_RELEASE ?= $(MAJOR).$(MINOR).$(shell expr $(PATCHNUM) - 1)

## @help:update-previous-minor-filebeat:Update the references on with the previous minor release for the filebeat previous minor testing stage
.PHONY: update-previous-minor-filebeat
update-previous-minor-filebeat:
ifeq ($(MAJOR),6)
	echo '6.<minor> branch does not need to add any backport policy.'
else
	cd beats; \
		$(SED) -E -e "s#(image: docker\.elastic\.co/.*):[0-9]+\.[0-9]+\.[0-9]+#\1:$(LATEST_RELEASE)#g" testing/environments/prev-minor.yml
endif

and CURRENT_RELEASE=8.1.1 as stated in the branch automation

On the other hand, this particular automation was requested by @adriansr in #28274 in case it's required further details.

In a nutshell, I think rc1 was added back in the days in #30027, I don't know what's the version that should be added in this particular case :/

[ruflin]

It seems the script is fine it is just not able to deal with -rc1 etc. As having rc1 etc. is kind of unique and an edge case, I suggest we clean it up manually.

[ruflin]

@matschaffer For the ping, I assumed this is because of stack monitoring that we test prev minor but it seems more generic, so we need to handle this from the Agent team.

[elasticmachine]

💚 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-03-22T14:57:55.790+0000

• Duration: 132 min 3 sec

Test stats 🧪

Test	Results
Failed	0
Passed	25667
Skipped	2192
Total	27859

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

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

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b update_testing_env_next_8.1.2 upstream/update_testing_env_next_8.1.2
git merge upstream/8.1
git push upstream update_testing_env_next_8.1.2

[ruflin]

I pushed a manual cleanup to the PR.

[ruflin]

Hm, this should actually be 8.0.* I guess?

[cmacknz]

/test

[cmacknz]

The build succeeded but the status still shows as pending in the PR, https://beats-ci.elastic.co/job/Beats/job/beats/job/PR-30855/4/

I'm going to merge this.