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

Checkout matching openshift-ansible branch #434

Closed
wants to merge 1 commit into from

Conversation

jhadvig
Copy link
Contributor

@jhadvig jhadvig commented Jul 14, 2017

@@ -23,6 +23,10 @@ extensions:
script: |-
tito_tmp_dir="tito"
mkdir -p "${tito_tmp_dir}"
if [[ ${ORIGIN_TARGET_BRANCH} == release-1.* ]]
then
git checkout -b ${ORIGIN_TARGET_BRANCH} origin/${ORIGIN_TARGET_BRANCH}
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't there a bunch of logic for translating branch names? Where Origin has release-1.x or release-3.x and OpenShift Ansible has enterprise-x?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I dont think so, cause when you check the origin repo branches you can see what branches are there, in this case only release-1.x and stage-1.x ... and those reflect to the o-a branches... enterprise-1.x branches are only present in OCP

Copy link
Contributor

Choose a reason for hiding this comment

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

oh, maybe scott moved them

Copy link
Contributor

Choose a reason for hiding this comment

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

Definitely used to be enterprise-x

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I was surprised as well, cause I remember they have been there

@stevekuznetsov
Copy link
Contributor

I would rather see if we can fix the oct sync openshift-ansible step generated by sjb at the start of the job

@jhadvig
Copy link
Contributor Author

jhadvig commented Jul 17, 2017

Yeah I kinda understand why you want to fix it in the generated step but this is a pretty specific use-case in which we checkout the branch of o-a repository based on the branch against which the PR is sent. Not sure if this wouldn't be better in the step itself with a proper comment

@stevekuznetsov thoughts ?

@stevekuznetsov
Copy link
Contributor

Any reason why we don't always want to check out the matching branch if it exists? Seems like this would be applicable to stage, too (but not rebase-1.7)

@jhadvig
Copy link
Contributor Author

jhadvig commented Jul 24, 2017

Closing in favor of #434

@jhadvig jhadvig closed this Jul 24, 2017
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.

2 participants