User tests: Successful: Unsuccessful:
When running the build script, we put packages in two directories with semi-consistent names (but variable enough to make scripting mildly annoying, just look at the diff for this PR). IMO there's really no need for this, just shove them all in one package. For whomever is running releases they just need to read file names if they're doing anything special, for end users they never see this process anyway, and for the nightly build scripts as I move them (back) onto the Jenkins box it simplifies things just enough to slow my gray hair growth by about two hours.
Apply patch, run build script, check output (compiled packages) is in one directory.
Status | New | ⇒ | Pending |
Category | ⇒ | Repository |
I have tested this item
I have tested this item
Status | Pending | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-06-15 05:59:26 |
Closed_By | ⇒ | laoneo | |
Labels |
Added:
?
|
Tested with Ubuntu for Windows (or whatever they are calling it.
Packages built correctly before patch in sub-directories
Packages built correctly after patch in one directory
Both cases I got this error but I suspect thats me and not the script. Just posting it for completeness