Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add BUILDKITE_ANALYTICS_TOKEN in fips-e2e-test step #4544

Merged
merged 1 commit into from
Mar 5, 2025

Conversation

pchila
Copy link
Member

@pchila pchila commented Mar 5, 2025

What is the problem this PR solves?

Set BUILDKITE_ANALYTICS_TOKEN for FIPS E2E test step. Without this env var FIPS E2E step will break on CI
// Please do not just reference an issue. Explain WHAT the problem this PR solves here.

How does this PR solve the problem?

Include FIPS E2E test step to the list of steps for which BUILDKITE_ANALYTICS_TOKEN will be set in pre-command hook.
// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

How to test this PR locally

Design Checklist

  • [ ] I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
  • [ ] I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
  • [ ] I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files
  • [ ] I have added tests that prove my fix is effective or that my feature works
  • [ ] I have added an entry in ./changelog/fragments using the changelog tool

Related issues

@pchila pchila added the ci CI related tasks label Mar 5, 2025
@pchila pchila self-assigned this Mar 5, 2025
@pchila pchila requested a review from a team as a code owner March 5, 2025 08:58
Copy link
Contributor

mergify bot commented Mar 5, 2025

This pull request does not have a backport label. Could you fix it @pchila? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@pierrehilbert pierrehilbert added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Mar 5, 2025
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@pchila pchila merged commit 2c04d3d into elastic:main Mar 5, 2025
10 checks passed
@v1v v1v added backport-8.x Automated backport to the 8.x branch with mergify backport-9.0 Automated backport to the 9.0 branch labels Mar 5, 2025
mergify bot pushed a commit that referenced this pull request Mar 5, 2025
(cherry picked from commit 2c04d3d)

# Conflicts:
#	.buildkite/hooks/pre-command
mergify bot pushed a commit that referenced this pull request Mar 5, 2025
@v1v
Copy link
Member

v1v commented Mar 5, 2025

Let's backport it, even though it's only for main but based on my experience, anything regarding the CI should be backported for the sake of future backports and to reduce merge conflicts.

pchila added a commit that referenced this pull request Mar 5, 2025
(cherry picked from commit 2c04d3d)

Co-authored-by: Paolo Chilà <paolo.chila@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify backport-9.0 Automated backport to the 9.0 branch ci CI related tasks Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants