Skip to content
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.

[7.17](backport #2172) feat: support downloading project artifacts for the new bucket layout #2183

Closed
wants to merge 2 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 28, 2022

This is an automatic backport of pull request #2172 done by Mergify.
Cherry-pick of 044dedf has failed:

On branch mergify/bp/7.17/pr-2172
Your branch is up to date with 'origin/7.17'.

You are currently cherry-picking commit 044dedf4.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .ci/ansible/tasks/setup_test_script.yml
	modified:   .ci/bump-stack-version.sh
	modified:   .ci/scripts/functional-test.sh
	modified:   e2e/README.md
	modified:   e2e/_suites/fleet/README.md
	modified:   e2e/_suites/fleet/ingest_manager_test.go
	modified:   e2e/_suites/kubernetes-autodiscover/README.md
	modified:   internal/common/defaults.go
	modified:   internal/deploy/docker_test.go
	modified:   internal/deploy/elastic_package.go
	modified:   internal/versions_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .ci/Jenkinsfile
	both modified:   e2e/_suites/fleet/fleet.go
	both modified:   e2e/_suites/fleet/stand-alone.go
	both modified:   e2e/_suites/kubernetes-autodiscover/autodiscover_test.go
	added by them:   internal/buckets.go
	added by them:   internal/buckets_test.go
	both modified:   internal/deploy/docker.go
	both modified:   internal/installer/elasticagent_deb.go
	both modified:   internal/installer/elasticagent_docker.go
	both modified:   internal/installer/elasticagent_rpm.go
	both modified:   internal/installer/elasticagent_tar.go
	both modified:   internal/installer/elasticagent_tar_macos.go
	both modified:   internal/installer/elasticagent_zip.go
	both modified:   internal/versions.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

…#2172)

* feat: support for the new bucket structure

* feat: calculate bucket URLs using resolvers

* chore: support for legacy Beats

Old PRs needs to be tested and the binaries could not exist in the new layout

* chore: support looking up the bucket in up-to 3 locations

1. new project layout
2. new beats layout
3. legacy beats layout

* chore: simplify boolean logic

* fix: pass worker environment for versions to the VMs

* fix: predefine kibana version

* fix: remove extra char

* fix: remove extra char

* chore: log resolvers

* chore: use new project method when fetching artifacts

* fix: pass stack version to stack deployment

* fix: use artifact to check for ubi8 variant

* chore: improve logs in resolvers

* fix: apply variants to project resolver

Ubi8 is a valid variant for elastic-agent

* chore: use Stack version for the dependant beats

In the running-on-top-of-beats feature file, the code installs some Beats
and we do not want to use the given SHA, because elastic-agent now lives
in a separate repo, therefore they do not share commit SHAs

* fix: use fleet-ci bucket for elastic-agent and fleet-server

* chore: look up both CI buckets

* chore: make useCISnapshots configurable on downloads

* chore: background processes should not use CI snapshots

* feat: separate elastic-agent version from beats version

* chore: extract useCISnapshots to a function

* chore: use Github_Check_Repo to identify where the Git commit lives

* fix: k8s-autodiscover lives in both worlds

* fix: missing package

* fix: use snapshot version in k8s-autodiscover

(cherry picked from commit 044dedf)

# Conflicts:
#	.ci/Jenkinsfile
#	e2e/_suites/fleet/fleet.go
#	e2e/_suites/fleet/stand-alone.go
#	e2e/_suites/kubernetes-autodiscover/autodiscover_test.go
#	internal/buckets.go
#	internal/buckets_test.go
#	internal/deploy/docker.go
#	internal/installer/elasticagent_deb.go
#	internal/installer/elasticagent_docker.go
#	internal/installer/elasticagent_rpm.go
#	internal/installer/elasticagent_tar.go
#	internal/installer/elasticagent_tar_macos.go
#	internal/installer/elasticagent_zip.go
#	internal/versions.go
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Feb 28, 2022
@mdelapenya mdelapenya added backport-skip Skip notification from the automated backport with mergify and removed conflicts There is a conflict in the backported pull request labels Feb 28, 2022
@elasticmachine
Copy link
Contributor

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-02-28T18:14:15.337+0000

  • Duration: 8 min 41 sec

Steps errors 4

Expand to view the steps failures

Install dependencies
  • Took 0 min 10 sec . View more details here
  • Description: .ci/scripts/install-dependencies.sh
Install dependencies
  • Took 0 min 2 sec . View more details here
  • Description: .ci/scripts/install-dependencies.sh
Build and test
  • Took 0 min 7 sec . View more details here
  • Description: .ci/scripts/build-test.sh
Archive the artifacts
  • Took 0 min 0 sec . View more details here
  • Description: [2022-02-28T18:17:08.736Z] Archiving artifacts script returned exit code 2

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

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

  • /test : Re-trigger the build.

@mdelapenya mdelapenya mentioned this pull request Feb 28, 2022
8 tasks
@mdelapenya
Copy link
Contributor

Superseded by #2187

@mdelapenya mdelapenya closed this Feb 28, 2022
@mergify mergify bot deleted the mergify/bp/7.17/pr-2172 branch February 28, 2022 20:03
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport-skip Skip notification from the automated backport with mergify
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants