Details
-
Type:
Improvement
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: lsstsw
-
Labels:None
-
Team:Architecture
Description
One difficulty in developers using lsstsw is that we cannot force a rebuild. One of the great strengths of lsstsw for developers is being able to build the code in a set of repos on a particular tag; in this situation it is often more useful to the developers to have the code in the cloned repos rebuilt than have the code installed in the stack. But that can go terribly awry if one builds things in the wrong order, leaving a host of unbuilt git clones. For instance last night I did the following:
- rebuild a ticket
- rebuild master
at that point my git clones were at master, when I wanted them on the ticket, and there was nothing I could think to do about it except start with a fresh stack (which is a major headache due to all the packages missing from lsstsw). I am still digging out of the mess.
Of course forced rebuild is useful for other situations, as well, such as confirming that we can build the stack. Some packages have intermittent build errors and doing an occasional fresh build is often the only way to catch those.
Attachments
Issue Links
- mentioned in
-
Page Loading...
I believe that this feature request is still potentially valuable, but we've managed to live without it for several years, so it remains on the back burner.