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

chore: run reaper daily at 1:30 am#2512

Merged
mdelapenya merged 1 commit intoelastic:mainfrom
mdelapenya:run-aws-reaper-daily
May 10, 2022
Merged

chore: run reaper daily at 1:30 am#2512
mdelapenya merged 1 commit intoelastic:mainfrom
mdelapenya:run-aws-reaper-daily

Conversation

@mdelapenya
Copy link
Copy Markdown
Contributor

What does this PR do?

It runs the AWS reaper daily, at 1:30 am, right before the nightly schedules.

Why is it important?

We want to reduce the cloud costs, removing the AWS instances once a day instead of once a week.

Checklist

  • 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 run the Unit tests (make unit-test), and they are passing locally
  • I have run the End-2-End tests for the suite I'm working on, and they are passing locally
  • I have noticed new Go dependencies (run make notice in the proper directory)

Related issues

@mdelapenya mdelapenya added the backport-skip Skip notification from the automated backport with mergify label May 10, 2022
@mdelapenya mdelapenya self-assigned this May 10, 2022
@mdelapenya mdelapenya requested a review from a team May 10, 2022 16:16
@elasticmachine
Copy link
Copy Markdown
Contributor

💚 Build Succeeded

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-05-10T16:16:58.002+0000

  • Duration: 69 min 39 sec

Test stats 🧪

Test Results
Failed 0
Passed 307
Skipped 0
Total 307

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

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

  • /test : Re-trigger the build.

@mdelapenya mdelapenya merged commit 252e92b into elastic:main May 10, 2022
@mdelapenya
Copy link
Copy Markdown
Contributor Author

mdelapenya commented May 11, 2022

@v1v @amannocci I had to manually run the pipeline for the changes to be applied. Is there a way to persist the configuration in Jenkins, maybe at the JJBB level?

@v1v
Copy link
Copy Markdown
Member

v1v commented May 11, 2022

Is there a way to persist the configuration in Jenkins, maybe at the JJBB level?

First build will apply the changes, you can apply them also in the JJBB if needed. For instance, the daily-pipeline contains the timer trigger configuration also in the jjbb ->

triggers:
- timed: 'H H(2-3) * * 1-5'

mdelapenya added a commit to mdelapenya/e2e-testing that referenced this pull request May 11, 2022
* main:
  bump stack version 8.3.0-53513548 (elastic#2513)
  chore: run reaper daily at 1:30 am (elastic#2512)
mdelapenya added a commit to mdelapenya/e2e-testing that referenced this pull request May 22, 2022
* main:
  bump stack version 8.3.0-8ee1196f (elastic#2519)
  ci: daily pipeline to use main branch (elastic#2516)
  bump stack version 8.3.0-53513548 (elastic#2513)
  chore: run reaper daily at 1:30 am (elastic#2512)
  avoid aliases if no major.minor format (elastic#2501)
  bump stack version 8.3.0-d380914f (elastic#2505)
  chore: refactor cucumber tags (elastic#2496)
  chore: skip system-integration scenarios for Beats (elastic#2482)
  bump stack version 8.3.0-5c1ff35f (elastic#2494)
  chore: reduce AWS instances size (elastic#2477)
  chore: wait for the stack while provisioning (elastic#2486)
  bump stack version 8.3.0-6ba9f710 (elastic#2484)
@mdelapenya mdelapenya deleted the run-aws-reaper-daily branch July 13, 2022 09:27
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.

3 participants