metalk8s icon indicating copy to clipboard operation
metalk8s copied to clipboard

Improvement/node 16 in ci

Open JBWatenbergScality opened this issue 3 years ago • 2 comments

Component:

Context:

Summary:

Acceptance criteria:


Closes: #ISSUE_NUMBER

JBWatenbergScality avatar Apr 11 '22 13:04 JBWatenbergScality

Hello jbwatenbergscality,

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.

Status report is not available.

bert-e avatar Apr 11 '22 13:04 bert-e

Waiting for approval

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

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

  • @chengyanjin

  • @lucieleonard

  • @jbwatenbergscality

  • @alexandre-allard-scality

  • @gdemonet

  • @teddyandrieux

  • @nicolast

  • @thomasdanan

bert-e avatar Apr 11 '22 13:04 bert-e

Branches have diverged

This pull request's source branch improvement/node-16-in-ci has diverged from development/123.0 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the following solutions:

  • Merge origin/development/123.0 into improvement/node-16-in-ci
  • Rebase improvement/node-16-in-ci onto origin/development/123.0

Note: If you choose to rebase, you may have to ask me to rebuild integration branches using the reset command.

bert-e avatar Aug 24 '22 15:08 bert-e

Integration data created

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

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

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

bert-e avatar Aug 24 '22 16:08 bert-e

Waiting for approval

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

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

  • @lucieleonard

  • @jbwatenbergscality

  • @chengyanjin

  • @thomasdanan

  • @gdemonet

  • @teddyandrieux

bert-e avatar Aug 24 '22 16:08 bert-e

/approve

JBWatenbergScality avatar Aug 29 '22 12:08 JBWatenbergScality

Waiting for approval

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

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

  • @lucieleonard

  • @jbwatenbergscality

  • @chengyanjin

  • @thomasdanan

  • @gdemonet

  • @teddyandrieux

The following options are set: approve

bert-e avatar Aug 29 '22 12:08 bert-e

Build failed

The build for commit did not succeed in branch improvement/node-16-in-ci.

The following options are set: approve

bert-e avatar Aug 29 '22 13:08 bert-e

In the queue

The changeset has received all authorizations and has been added to the relevant queue(s). The queue(s) will be merged in the target development branch(es) as soon as builds have passed.

The changeset will be merged in:

  • :heavy_check_mark: development/124.0

The following branches will NOT be impacted:

  • development/123.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

There is no action required on your side. You will be notified here once the changeset has been merged. In the unlikely event that the changeset fails permanently on the queue, a member of the admin team will contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a member of the admin team now.

The following options are set: approve

bert-e avatar Aug 29 '22 17:08 bert-e

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

  • :heavy_check_mark: development/124.0

The following branches have NOT changed:

  • development/123.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue NODE-16.

Goodbye jbwatenbergscality.

bert-e avatar Aug 29 '22 17:08 bert-e