Skip to content

Conversation

blakerouse
Copy link
Contributor

What does this PR do?

Changes the agentless-app-release.yaml to build with USE_PACKAGE_VERSION and publish to serverless when a commit is merged into main.

Why is it important?

To keep serverless up-to-date with latest elastic-agent builds.

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • 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
  • [ ] I have added an integration test or an E2E test

@blakerouse
Copy link
Contributor Author

This was successful with publishing to serverless here: https://buildkite.com/elastic/agentless-serverless-release/builds/18

@blakerouse blakerouse marked this pull request as ready for review August 26, 2025 23:44
@blakerouse blakerouse requested a review from a team as a code owner August 26, 2025 23:44
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

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

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @blakerouse

Copy link
Member

@v1v v1v left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@blakerouse blakerouse merged commit 4dcd045 into main Sep 2, 2025
20 checks passed
@blakerouse blakerouse deleted the main-to-serverless branch September 2, 2025 18:12
kaanyalti pushed a commit to kaanyalti/elastic-agent that referenced this pull request Sep 4, 2025
… main (elastic#9583)

* Update job to build and push.

* Fix artifacts.

* Add to core pipeline for main branch.

---------

Co-authored-by: Francisco Ramon <[email protected]>
intxgo pushed a commit to intxgo/elastic-agent that referenced this pull request Sep 24, 2025
… main (elastic#9583)

* Update job to build and push.

* Fix artifacts.

* Add to core pipeline for main branch.

---------

Co-authored-by: Francisco Ramon <[email protected]>
nkvoll added a commit that referenced this pull request Sep 24, 2025
nkvoll added a commit that referenced this pull request Sep 24, 2025
v1v added a commit that referenced this pull request Sep 26, 2025
* upstream: (505 commits)
  Update journald tests now that Filebeat supports watching folders (#10131)
  [deploy/kubernetes]: add info about hostPID for Universal Profiling (#10173)
  Fall back to process runtime if otel runtime is unsupported (#10087)
  Conditionall check for ms_tls13kdf build tag (#10160)
  [docs][edot] add entry for profiles (#10163)
  edot/docs: add support for profiles (#10146)
  Add Logstash exporter (#10137)
  Add back publish to serverless. (#10159)
  Improve Integration test documentation (#10155)
  Fix multiarch service image push from main to serverless (#10129)
  Forward migrate action to endpoint (#9801)
  Comment out check for ms_tls13kdf tag for FIPS-capable binaries (#10148)
  [otel] add receivers: apache, iis, mysql, postgresql, sqlserver v0.135.0 (#9344)
  Add k8sevents receiver in kube-stack (#10086)
  feat: emit system resource metrics for EDOT subprocess (#10003)
  [AutoOps] Configure OTel Exporter to Send Maximum-sized Batches (#10126)
  keep enrollment token when replacing data with signed (#10115)
  Revert "Publish `elastic-agent-service` container directly to serverless from main (#9583)" (#10127)
  Add agent_policy_id and policy_revision_idx to checkin requests (#9931)
  remove resource/k8s processor and use k8sattributes processor for service attributes (#10108)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants