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

Change output to outputformat as param changed in drctl #2154

Draft
wants to merge 12 commits into
base: development/2.6
Choose a base branch
from

Conversation

KillianG
Copy link
Collaborator

DRCTL status now fails if it, actually fails

Issue: ZENKO-4903

DRCTL status now fails if it, actually fails

Issue: ZENKO-4903
@bert-e
Copy link
Contributor

bert-e commented Sep 24, 2024

Hello killiang,

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 Sep 24, 2024

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.

@KillianG
Copy link
Collaborator Author

/create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Sep 24, 2024

Integration data created

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

The following branches will NOT be impacted:

  • development/2.5

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: create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Sep 24, 2024

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

tmate-server-port: ${{ secrets.TMATE_SERVER_PORT }}
tmate-server-rsa-fingerprint: ${{ secrets.TMATE_SERVER_RSA_FINGERPRINT }}
tmate-server-ed25519-fingerprint: ${{ secrets.TMATE_SERVER_ED25519_FINGERPRINT }}
timeout-minutes: 30
Copy link
Contributor

Choose a reason for hiding this comment

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

should not be commited!

@KillianG KillianG marked this pull request as draft September 25, 2024 08:47
@francoisferrand
Copy link
Contributor

/after_pull_request=2155

@bert-e
Copy link
Contributor

bert-e commented Sep 26, 2024

Waiting for other pull request(s)

The current pull request is locked by the after_pull_request option.

In order for me to merge this pull request, run the following actions first:

➡️ Merge the OPEN pull request:

Alternatively, delete all the after_pull_request comments from this pull request.

The following options are set: after_pull_request, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Sep 27, 2024

Conflict

A conflict has been raised during the update of
integration branch w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time with contents from w/2.9/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time
and development/2.10.

Please resolve the conflict on the integration branch (w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time).

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time
 $ git pull  # or "git reset --hard origin/w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time"
 $ git merge origin/development/2.10
 $ # <intense conflict resolution>
 $ git commit
 $ git merge origin/w/2.9/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time

The following options are set: after_pull_request, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Sep 27, 2024

Incorrect fix version

The Fix Version/s in issue ZENKO-4903 contains:

  • 2.10.0

  • 2.6.68

  • 2.7.64

  • 2.8.44

  • 2.9.21

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

  • 2.10.1

  • 2.6.68

  • 2.7.64

  • 2.8.44

  • 2.9.21

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

The following options are set: after_pull_request, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Sep 27, 2024

Conflict

A conflict has been raised during the update of
integration branch w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time with contents from w/2.9/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time
and development/2.10.

Please resolve the conflict on the integration branch (w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time).

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time
 $ git pull  # or "git reset --hard origin/w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time"
 $ git merge origin/development/2.10
 $ # <intense conflict resolution>
 $ git commit
 $ git merge origin/w/2.9/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/2.10/bugfix/ZENKO-4903-fix-drctl-status-taking-too-much-time

The following options are set: after_pull_request, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Sep 27, 2024

Incorrect fix version

The Fix Version/s in issue ZENKO-4903 contains:

  • 2.10.0

  • 2.6.68

  • 2.7.64

  • 2.8.44

  • 2.9.21

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

  • 2.10.1

  • 2.6.68

  • 2.7.64

  • 2.8.44

  • 2.9.21

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

The following options are set: after_pull_request, create_integration_branches

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.

3 participants