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

upgrade to 2.1 don't pull latest changes for stf #128

Closed
vdelendik opened this issue Apr 29, 2022 · 2 comments
Closed

upgrade to 2.1 don't pull latest changes for stf #128

vdelendik opened this issue Apr 29, 2022 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@vdelendik
Copy link
Contributor

vdelendik commented Apr 29, 2022

as we clone single branch we can't switch into the new one and pull changes...
as result old sources are deployed from 2.0 release.
let's investigate what might be done to automate this process.

@vdelendik vdelendik added the bug Something isn't working label Apr 29, 2022
@vdelendik vdelendik added this to the 2.2.1 milestone Apr 29, 2022
@vdelendik vdelendik modified the milestones: 2.2.1, 2.3 Apr 29, 2022
@vdelendik vdelendik modified the milestones: 2.3, 2.4 Aug 19, 2022
@vdelendik
Copy link
Contributor Author

fixed by cloning stf with all branches and checkouting to the released version (2.4 as of today).
during the verification we have to inspect that upgrade steps have rm -rf stf step. As result for new upgrades we can easily pull latest changes from released branch

@dhreben
Copy link

dhreben commented Dec 30, 2022

Verified.

Steps:

  1. rm -rf stf
  2. ./zebrunner sh setup
  3. Confirm rebuild STF components

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants