OCPBUGS-5537: USHIFT-601 rebase: entrypoint and create_pr.py

[pmtk]

Because steps in "steps registry" are shared between branches I'd like to move rebase's commands.sh contents into microshift repository so that changes to the job are contained to specific branch.
Otherwise, when introducing rebase.py (wrapper for rebase.sh with extra goodies, will obsolete create_pr.py) will need either introducing into 4.12 branch (and I'd like to run in on main first, as a testing area) or special login in step's commands.sh.

[openshift-ci]

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

USHIFT-601: rebase: entrypoint and create_pr.py changes for 4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pmtk]

/bugzilla refresh

[openshift-ci]

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-5538 USHIFT-601: rebase: entrypoint and create_pr.py changes for 4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pmtk]

/jira refresh

[openshift-ci-robot]

@pmtk: No Jira bug is referenced in the title of this pull request.
To reference a bug, add 'OCPBUGS-XXX:' to the title of this pull request and request another bug refresh with /jira refresh.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-5538: USHIFT-601 rebase: entrypoint and create_pr.py changes for 4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@pmtk: This pull request references Jira Issue OCPBUGS-5538, which is invalid:

• expected the bug to target the "4.12.0" version, but no target version was set
• expected Jira Issue OCPBUGS-5538 to depend on a bug targeting a version in 4.13.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Because steps in "steps registry" are shared between branches I'd like to move rebase's commands.sh contents into microshift repository so that changes to the job are contained to specific branch.
Otherwise, when introducing rebase.py (wrapper for rebase.sh with extra goodies, will obsolete create_pr.py) will need either introducing into 4.12 branch (and I'd like to run in on main first, as a testing area) or special login in step's commands.sh.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pmtk]

/jira refresh

[openshift-ci-robot]

@pmtk: This pull request references Jira Issue OCPBUGS-5538, which is invalid:

• expected the bug to target the "4.12.0" version, but it targets "4.12" instead
• expected dependent Jira Issue OCPBUGS-5537 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead
• expected dependent Jira Issue OCPBUGS-5537 to target a version in 4.13.0, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@pmtk: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-5538: USHIFT-601 rebase: entrypoint and create_pr.py changes for 4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@pmtk: This pull request references Jira Issue OCPBUGS-5538, which is invalid:

• expected the bug to target the "4.12.0" version, but it targets "4.12" instead
• expected dependent Jira Issue OCPBUGS-5537 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is New instead
• expected dependent Jira Issue OCPBUGS-5537 to target a version in 4.13.0, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Because steps in "steps registry" are shared between branches I'd like to move rebase's commands.sh contents into microshift repository so that changes to the job are contained to specific branch.
Otherwise, when introducing rebase.py (wrapper for rebase.sh with extra goodies, will obsolete create_pr.py) will need either introducing into 4.12 branch (and I'd like to run in on main first, as a testing area) or special login in step's commands.sh.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@pmtk: This pull request references Jira Issue OCPBUGS-5537, which is invalid:

• expected the bug to target the "4.13.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Because steps in "steps registry" are shared between branches I'd like to move rebase's commands.sh contents into microshift repository so that changes to the job are contained to specific branch.
Otherwise, when introducing rebase.py (wrapper for rebase.sh with extra goodies, will obsolete create_pr.py) will need either introducing into 4.12 branch (and I'd like to run in on main first, as a testing area) or special login in step's commands.sh.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pmtk]

/jira refresh

[openshift-ci-robot]

@pmtk: This pull request references Jira Issue OCPBUGS-5537, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.0) matches configured target version for branch (4.13.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jogeo

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ggiguash]

/lgtm

[pmtk]

/cherry-pick release-4.12

[openshift-cherrypick-robot]

@pmtk: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ggiguash]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ggiguash,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@pmtk: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@pmtk: All pull requests linked via external trackers have merged:

• openshift/microshift#1242

Jira Issue OCPBUGS-5537 has been moved to the MODIFIED state.

In response to this:

Because steps in "steps registry" are shared between branches I'd like to move rebase's commands.sh contents into microshift repository so that changes to the job are contained to specific branch.
Otherwise, when introducing rebase.py (wrapper for rebase.sh with extra goodies, will obsolete create_pr.py) will need either introducing into 4.12 branch (and I'd like to run in on main first, as a testing area) or special login in step's commands.sh.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-cherrypick-robot]

@pmtk: new pull request created: #1245

In response to this:

/cherry-pick release-4.12

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.