Apache pre-release is used to bump version up together with #10416

Could someone run CI for the tests? Thank you in advance. I will merge back from main and bump up version in manifests after initial review from anyone.

/test

@ishleenk17 Thanks for running tests. I have one question. Do tests fail, when i did not include the new version/pre-release in the maifests.yml. According to doc, on pre-releases this should not be necessary as multiple PR'S can result in the same version.

Do I need to populate pre-releases (see Apache integration) in the manifests.yml?

@ishleenk17 I added the manifest versions. Can you please run CI again?

PS: I might have tagged the wrong people as you have the same avatar @aliabbas-elastic

/test

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

Unfortunately I have no access to Sonarqube and cannot review the failed objective on code coverage.

Please run CI again

/test

@aliabbas-elastic @andrewkroh @efd6 Is the CI failing test some kind of bug in the CI or what is wrong with the integration? As I have no idea what the problem is to be honest.

There is an issue with starting a service required for the system test.

Error: error running package system tests: could not complete test run: could not setup service: service is unhealthy: container (ID: ****) exited with code 127

I've tried running this locally and it works. The container does take a while to start up, so maybe in CI it is just taking a little too long? @elastic/sec-linux-platform do you have any ideas what might be going on here?

/test

I have asked the the ecosystem team on Slack about the failure here. Specifically,

• is the failure caused by a resource constraint problem associated with auditd running a separate Elastic Agent container,
• and why isn't the log file from the container include in the buildkite artifacts list.

I think we can bypass the CI failure if needed, but we'll give that team a little time to investigate. I also saw another auditd_manager PR that is failing (might be the same cause).

/test

💚 Build Succeeded

• Buildkite Build
• Commit: d0755db

History

• 💔 Build #14532 failed be88dc5
• 💔 Build #14102 failed 024f888
• 💔 Build #14078 failed 024f888
• 💔 Build #14070 failed 024f888
• 💔 Build #14057 failed 024f888

cc @Alphayeeeet

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
93.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

Package 1password - 1.30.0 containing this change is available at https://epr.elastic.co/search?package=1password

Package activemq - 1.6.0 containing this change is available at https://epr.elastic.co/search?package=activemq

Package akamai - 2.25.0 containing this change is available at https://epr.elastic.co/search?package=akamai

Package amazon_security_lake - 1.4.0 containing this change is available at https://epr.elastic.co/search?package=amazon_security_lake

Package apache - 1.24.0 containing this change is available at https://epr.elastic.co/search?package=apache

Package apache_tomcat - 1.8.0 containing this change is available at https://epr.elastic.co/search?package=apache_tomcat

Package arista_ngfw - 1.2.0 containing this change is available at https://epr.elastic.co/search?package=arista_ngfw

Package atlassian_bitbucket - 2.2.0 containing this change is available at https://epr.elastic.co/search?package=atlassian_bitbucket

Package atlassian_confluence - 1.26.0 containing this change is available at https://epr.elastic.co/search?package=atlassian_confluence

Package atlassian_jira - 1.27.0 containing this change is available at https://epr.elastic.co/search?package=atlassian_jira

Package auditd - 3.20.0 containing this change is available at https://epr.elastic.co/search?package=auditd

Package auditd_manager - 1.17.0 containing this change is available at https://epr.elastic.co/search?package=auditd_manager

Package auth0 - 1.18.0 containing this change is available at https://epr.elastic.co/search?package=auth0