Manuel de la Peña

I tried to use `` elements instead, and jenkins populated the UI with two messages: one for the failure and one for the first skipped step

I ended up creating different directories per test suite: https://github.com/elastic/e2e-testing/tree/master/e2e/_suites - _suites - suite1 - main_test.go - suite2 - main_test.go

> @v1v One question I think is worth asking might be if we can get a high-level view of dependencies across **all** the observability repos. Perhap Do you think that...

Still seeing this. Playing with the default settings.yml file: Pushing this file: ```yaml labels: - name: "type/bug" color: '#CC0000' description: An issue with the system 🐛. - name: "type/feature" #...

Unfortunately, I'm not able to make it work with this `settings.yml` file, and the branch protection only works if and only if it's alone in the file. I've tried with...

> @mdelapenya > > what happens if you delete just the following lines? > > enable_automated_security_fixes: false enable_vulnerability_alerts: false Unfortunately nothing. See: https://github.com/tc-experiments/.github/blob/main/.github/settings.yml The branch protection is not created

Mmm, interestingly, I had an issue with the teams: there were teams that did not existed, and until creating them, the configuration failed. History (bottom-first): - https://github.com/tc-experiments/.github/commit/52ba68fb7d505360b0137bfd89bf68a5f6bf6d49 worked ✅ -...

... and will support the paralellisation of the test in Jenkins, as @kuisathaverat mentioned! In this sense, we are here ready to help in the definition of the test suites/categories!...

Then I think the team needs to provide the scaffolding code for skipping the test using python's test runner. Otherwise they won't appear as skipped

Seeing this behaviour here: https://github.com/testcontainers/testcontainers-go/runs/1384925491?check_suite_focus=true _Currently reading https://github.com/golang/go/issues/34610_