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

Move pre-release test jobs to ci.centos #15701

Closed
rhopp opened this issue Jan 15, 2020 · 4 comments
Closed

Move pre-release test jobs to ci.centos #15701

rhopp opened this issue Jan 15, 2020 · 4 comments
Assignees
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current status/in-progress This issue has been taken by an engineer and is under active development.
Milestone

Comments

@rhopp
Copy link
Contributor

rhopp commented Jan 15, 2020

Is your task related to a problem? Please describe.

On codenvy.ci we were triggering these jobs manually.
We need to find a way how to perform pre-release testing on ci.centos.org (as manual trigger is not an option there) and move the jobs there.

List of jobs:
https://ci.codenvycorp.com/view/qa-rc/

@rhopp rhopp added kind/task Internal things, technical debt, and to-do tasks to be performed. team/che-qe labels Jan 15, 2020
@rhopp rhopp added this to the Backlog - QE milestone Jan 15, 2020
@rhopp rhopp added the severity/P1 Has a major impact to usage or development of the system. label Jan 15, 2020
@artaleks9 artaleks9 self-assigned this Jan 22, 2020
@artaleks9 artaleks9 added the status/in-progress This issue has been taken by an engineer and is under active development. label Jan 22, 2020
@rhopp rhopp modified the milestones: Backlog - QE, 7.9.0 Jan 29, 2020
@rhopp
Copy link
Contributor Author

rhopp commented Jan 29, 2020

We've discussed the possible approach with Vitalli today and this is the suggested outcome:

Testing of RC artifacts

  • Vitalli (or whoever is doing the release of Che) will ping QE, that rc images (quay.io/eclipse/che-server:rc-7.9.0, quay.io/eclipse/che-keycloak:rc-7.9.0, ...(images built from che repo)) are ready.
    • che-theia, registries etc. are already released (a.k.a. quay.io/che-plugin-registry:7.9.0, ...)
  • QA engineer will merge the release branch to our rc-testing branch (cico-rc-test).
    • This will trigger the testing jobs on ci.centos which:
      • Extract the current version from pom.xml (mvn help:evaluate -Dexpression=project.version -q -DforceStdout).
      • Do all necessary changes for correct deployment using chectl (customresource.yaml, ...)
      • Installs che & runs the tests against it.

@artaleks9
Copy link
Contributor

artaleks9 commented Jan 30, 2020

Moving releases jobs:
(Java selenium on ci.codenvycorp)

  • Move Multiuser stable - in progress
  • Setup jobs to be triggered by push to some "qe" branch - in progress
  • Move Multiuser all - not started
  • Move Hot update - not started

On crw jenkins

  • Happy Path - not started
  • Devfiles tests - not started
  • OCP OAuth - not started

@artaleks9
Copy link
Contributor

artaleks9 commented Feb 14, 2020

Moving releases jobs:
(Java selenium on ci.codenvycorp):


  • che-integration-tests-ocp-rc - Not Started (this task has a low priority and will be done later).
  • che-multiuser-ocp-recreate-strategy-test-rc => Now this functionality is switched off, so the job is always failure. See more details: Update helm chart to use RollingUpdate strategy #15915. So the job will be updated or renamed.

@rhopp
Copy link
Contributor Author

rhopp commented Feb 20, 2020

Done by this: #16039

@rhopp rhopp closed this as completed Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current status/in-progress This issue has been taken by an engineer and is under active development.
Projects
None yet
Development

No branches or pull requests

4 participants