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

Bump deps & release Zenko #2069

Merged
merged 6 commits into from
May 18, 2024
Merged

Bump deps & release Zenko #2069

merged 6 commits into from
May 18, 2024

Conversation

francoisferrand
Copy link
Contributor

@francoisferrand francoisferrand commented May 17, 2024

  • Bump cloudserver 8.8.24
  • Bump scuba 1.0.1
  • Bump s3utils 1.14.9
  • Bump zenko-operator 1.5.47
  • Release Zenko 2.6.55

Issue: ZENKO-4816

@bert-e
Copy link
Contributor

bert-e commented May 17, 2024

Hello francoisferrand,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@francoisferrand francoisferrand changed the base branch from development/2.8 to development/2.6 May 17, 2024 15:37
@scality scality deleted a comment from bert-e May 17, 2024
@scality scality deleted a comment from bert-e May 17, 2024
@francoisferrand
Copy link
Contributor Author

/approve

@scality scality deleted a comment from bert-e May 17, 2024
@bert-e
Copy link
Contributor

bert-e commented May 17, 2024

Build failed

The build for commit did not succeed in branch improvement/ZENKO-4816.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented May 17, 2024

Build failed

The build for commit did not succeed in branch w/2.7/improvement/ZENKO-4816.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented May 17, 2024

Build failed

The build for commit did not succeed in branch improvement/ZENKO-4816.

The following options are set: approve

@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@williamlardier
Copy link
Contributor

Having scality/s3utils#317 in this PR would be great cc @francoisferrand

And I fixed the deployment with a new commit: there is no metrics scraping in the CI (confirmed it works well in the platform)

@williamlardier
Copy link
Contributor

/force_reset

@bert-e
Copy link
Contributor

bert-e commented May 18, 2024

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: approve, wait

@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@scality scality deleted a comment from bert-e May 18, 2024
@bert-e
Copy link
Contributor

bert-e commented May 18, 2024

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.6

  • ✔️ development/2.7

  • ✔️ development/2.8

  • ✔️ development/2.9

The following branches have NOT changed:

  • development/2.5

Please check the status of the associated issue ZENKO-4816.

Goodbye francoisferrand.

The following options are set: approve

@bert-e bert-e merged commit e78d1c8 into development/2.6 May 18, 2024
14 checks passed
@bert-e bert-e deleted the improvement/ZENKO-4816 branch May 18, 2024 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants