We were planning recursively adding files and folders by commandline for the future. We'll move it up to the wyBuild 2.6.10 release.
Scripting updates
Currently our builds are handled by a combination of VisualStudio builds, and .btm (4dos) scripts (and a few utility .exe's). Bottom line: start a script on our server, and everything is built for the next build of the software, and properly packaged for distribution as a CD source image (file structure on server, not an actual ISO).
wyBuild could only make sense for our organization if the process can be automated. Looking at your how-to / introduction to using wyBuild.exe from the command line, looks a combination of promising and problematic.
In particular, your new versions XML format looks like I would have to generate XML for each and every file in our distribution (which includes over 11,500 individual files, distributed across several hundred folders and subfolders). This obviously can be automated if I build a custom tool that recurses the folders in question and generates the XML for your consumption.
However... that seems horribly inefficient from my POV. In your GUI, you can just add folders, where it automatically scans all files and subfolders for the relevant files and folders to scan and compare to generate a patch from. Is there a similar set of functionality in the "new versions XML"?
<Files dir="basedir"> <File source="T:\Distributions\English\13.0\*" recurse=true /> </Files>
Or some-such?
Your software & methods seem pretty solid. I'm psyched about adding this to our product, but I definitely would appreciate the ability to not have to implement the entire <file=> 11,500 times (I'd have to write an xml generator tool for this, and then maintain it, etc., when I suspect you could add such a feature quite cheaply, which would benefit many folks, and have zero upkeep to it from our side).
So the question becomes: what's your development cycle like? Every 3mos, 6mos, a year, etc?
Thanks for the helpful answers to our questions (and for a great tool for the industry).
So the question becomes: what's your development cycle like? Every 3mos, 6mos, a year, etc?
We plan on releasing 2.6.10 by the end of next week (assuming no show-stopper bugs). This release will include the "recursively adding files by commandline" feature.
On average we make about 2 releases a month which include bug fixes and minor feature additions. We have a major release (e.g. 2.x -> 3.x) around every 2 to 3 years.
OK, we've added the ability to add a folder's complete contents via commandline. Use the new <Folder> element in the XML file. See the updated article on building updates from commanline.
Also, in wyBuild 2.6.10, the commandline builder has been separated from wyBuild.exe. Use the new "wybuild.cmd.exe".
Wyatt wrote:> OK, we've added the ability to add a folder's complete contents via commandline.> Use the new <Folder> element in the XML file. See the updated article> on building updates from commanline.> > Also, in wyBuild 2.6.10, the commandline builder has been separated from wyBuild.exe.> Use the new "wybuild.cmd.exe".
Is there a way to import reg changes into wybuild?
I have about 40 registry changes to make. It's rather troublesome to add them one by one through the interface.It would be great to either have an xml file of the project file to allow manual manipulation or import the reg file
That's a good idea. We'll add this to wyBuild 2.6.11 or 2.6.12.