Skip to content

Conversation

BourgoisMickael
Copy link
Contributor

@BourgoisMickael BourgoisMickael commented Apr 4, 2025

@bert-e
Copy link
Contributor

bert-e commented Apr 4, 2025

Hello bourgoismickael,

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.

@bert-e
Copy link
Contributor

bert-e commented Apr 4, 2025

Incorrect fix version

The Fix Version/s in issue CLDSRV-635 contains:

  • 7.10.54

  • 7.70.65

  • 8.8.47

  • 9.0.10

  • 9.1.0

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 7.10.54

  • 7.70.65

  • 8.8.46

  • 9.0.9

  • 9.1.0

Please check the Fix Version/s of CLDSRV-635, or the target
branch of this pull request.

@BourgoisMickael
Copy link
Contributor Author

ping

@scality scality deleted a comment from bert-e Apr 4, 2025
@bert-e
Copy link
Contributor

bert-e commented Apr 4, 2025

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@BourgoisMickael BourgoisMickael changed the title CLDSRV-635: Bump arsenal for kmip logs CLDSRV-635: Bump arsenal for kmip logs (backport) Apr 4, 2025
Copy link
Contributor

@jonathan-gramain jonathan-gramain left a comment

Choose a reason for hiding this comment

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

Is this a temporary branch for testing until we bump arsenal 7.10.x? Otherwise I would expect a real version bump, not a reference to a branch

@BourgoisMickael
Copy link
Contributor Author

Is this a temporary branch for testing until we bump arsenal 7.10.x? Otherwise I would expect a real version bump, not a reference to a branch

Yes I'm merging arsenal and bumping arsenal then I update this commit to point to the new arsenal version

@BourgoisMickael BourgoisMickael force-pushed the improvement/CLDSRV-635-kmip-logs branch from 0522620 to ca0d3fe Compare April 8, 2025 10:02
@BourgoisMickael
Copy link
Contributor Author

/create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Apr 8, 2025

Conflict

A conflict has been raised during the creation of
integration branch w/7.70/improvement/CLDSRV-635-kmip-logs with contents from improvement/CLDSRV-635-kmip-logs
and development/7.70.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/7.70/improvement/CLDSRV-635-kmip-logs origin/development/7.70
 $ git merge origin/improvement/CLDSRV-635-kmip-logs
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/7.70/improvement/CLDSRV-635-kmip-logs

The following options are set: create_integration_branches

@BourgoisMickael
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Apr 8, 2025

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/7.4

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Apr 8, 2025

Build failed

The build for commit did not succeed in branch w/9.1/improvement/CLDSRV-635-kmip-logs

The following options are set: approve, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Apr 8, 2025

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

  • ✔️ development/7.10

  • ✔️ development/7.70

  • ✔️ development/8.8

  • ✔️ development/9.0

  • ✔️ development/9.1

The following branches have NOT changed:

  • development/7.4

Please check the status of the associated issue CLDSRV-635.

Goodbye bourgoismickael.

The following options are set: approve, create_integration_branches

@bert-e bert-e merged commit ca0d3fe into development/7.10 Apr 8, 2025
10 checks passed
@bert-e bert-e deleted the improvement/CLDSRV-635-kmip-logs branch April 8, 2025 10:41
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.

5 participants