refstack

setup_env removes and reclones tempest

Bug #1643048 reported by Carl Baldwin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
refstack
Invalid
Wishlist
Unassigned

Bug Description

The tempest repo is pretty slow to clone. So, why does this code remove it [1] just to reclone it again? It would be a very nice improvement to just clean it out, fetch the latest and then checkout the correct ref.

[1] https://github.com/openstack/refstack-client/blob/333cdde3123ab7df5ec377c970ee1586cf67efeb/setup_env#L87-L96

Catherine Diep (cdiep)
Changed in refstack:
importance: Undecided → Wishlist
Revision history for this message
Sergey Slipushenko (sslypushenko) wrote :

I guess setup-env script can optionally reuse already existed tempest installation. But current default behavior is absolutely ok for me.

Revision history for this message
Martin Kopec (mkopec) wrote :

Launchpad is an old bug tracker, refstack and refstack-client use storyboard, they have been for some time. This bug is already tracked there: https://storyboard.openstack.org/#!/story/1643048
I'm gonna close this as Invalid just to close this issue here, on LP.

Changed in refstack:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.