-
Notifications
You must be signed in to change notification settings - Fork 172
Modify jenkins steps to adjust 4.0 change #98
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
Conversation
When get server version of 4.0 above cluster, the returned result is "Server Version: version.Info{Major:"1", Minor:"12+".....}", so I add one step "Given /^I have a jenkins server with above 40 cluster$/ do" . |
We should rather update Environment#get_version method work using the 4.x call instead of the old one. Then use existing step wrt the login step,what is the need of this new step? |
Master branch is only for 4.0 cluster version. Can we update existing step instead? |
@akostadinov since this pr [1], the version for 4.0 is kubernetes version now, could we use client version instead ? |
For the login step,need add a step to choose the auth type since there are two auth type(kubeadmin and other one auth type) at least. |
I need to check how we can do things. Maybe we can use |
@akostadinov |
Both 3.1 and 3.2 version get 403 forbidden when access version/openshift url. |
We have a cmd 3.1 4.0 |
I think that btw from bugzilla I see that probably there is a way to get api server version somehow. But still no info how. Do you know this? |
Alex, you are right, |
I'm trying to reach directly to the developer to see what he meant by getting api server version. |
0eceb71
to
6dadbfa
Compare
@@ -102,11 +103,16 @@ | |||
# non-SSO login. | |||
# Installation step also installs based on this. | |||
Given /^I log in to jenkins$/ do | |||
if env.version_ge("3.4", user: user) && user.password? | |||
if env.version_ge("3.4", user: user) && env.version_le("3.11", user: user) && user.password? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in this branch we should only support 4.x, conditions for older cluster verisions better be gone. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
v3 branch is for 3.x? Could the cvp tool choose the branch, since default branch is master in runner-v3 job
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure what CVP is. In any case, master branch not suitable to run stuff on 3.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CVP is [container verification pipeline tool][https://docs.engineering.redhat.com/pages/viewpage.action?spaceKey=CVP&title=Container+Verification+Pipeline+E2E+Documentation#ContainerVerificationPipelineE2EDocumentation-ProductTests) which anli is taking development.
I will remove the conditions for older cluster verisions later.
@akostadinov Removed the conditions for older cluster verisions, and test case passed. |
/lgtm Thank you! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akostadinov, xiuwang 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:
Approvers can indicate their approval by writing |
jenkins log
@openshift/devexp-qe please help review