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.

Sign up for GitHub

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

Jump to bottom

Test and Release/Build environment should match #3023

Closed
2 tasks
kadel opened this issue Apr 27, 2020 · 3 comments · Fixed by #3204
Closed
2 tasks

Test and Release/Build environment should match #3023

kadel opened this issue Apr 27, 2020 · 3 comments · Fixed by #3204
Assignees
@mohammedzee1000
Labels
area/release-eng Issues or PRs related to the Release Engineering area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
Sprint 184

Comments

@kadel
Copy link
Member

kadel commented Apr 27, 2020 •
edited
Loading

It is important that the test environment and release/build environment match.
For example, the same Go version should be used everywhere.

Acceptance criteria:

  • use the same go versions everywhere (1.12)
  • document how to change go version (all places where it needs to be updated)

/area release-eng
/area testing
/kind bug
/priority high

/cc @amitkrout @mohammedzee1000
@openshift-ci-robot openshift-ci-robot added area/release-eng Issues or PRs related to the Release Engineering area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). labels Apr 27, 2020
@mohammedzee1000
Copy link
Contributor

It seems like a pretty straightforward but important problem.
/assign

@mohammedzee1000 mohammedzee1000 mentioned this issue May 19, 2020
Merged
@mohammedzee1000 mohammedzee1000 added this to For consideration in Sprint 184 via automation May 19, 2020
@mohammedzee1000 mohammedzee1000 moved this from For consideration to In progress in Sprint 184 May 19, 2020
@mohammedzee1000 mohammedzee1000 moved this from In progress to For review in Sprint 184 May 19, 2020
@dharmit
Copy link
Member

dharmit commented May 19, 2020

And on developer system I'm using 1.14.2. 😆

@mohammedzee1000
Copy link
Contributor

I guess that is ok as CI will detect any issues that you try to pass off :P

Sprint 184 automation moved this from For review to Done May 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mohammedzee1000 mohammedzee1000

Labels
area/release-eng Issues or PRs related to the Release Engineering area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
No open projects
Sprint 184
  
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Setting golang version uniformly accross repo and updating docs mohammedzee1000/odo
4 participants
@kadel @dharmit @mohammedzee1000 @openshift-ci-robot