I've been reading up on your conditional build options in wyBuild (Referring to article: http://wyday.com/wybuild/help/commandline.php) and wanted to see if there was a way to override the Upload server configuration via commandline or the xml file? I'm referring to the section titled "Upload the Updates" in the wyBuild GUI.
I'm looking to create a break in my current releases to cut over to a new location which will be confined within a licensed track. However, I don't want to keep reconfiguring the upload location if I need make a small change to the previous track and upload. If there is an override option I could script it so it's static for future changes.
wanted to see if there was a way to override the Upload server configuration via commandline or the xml file?
No, there's not.
I'm looking to create a break in my current releases to cut over to a new location which will be confined within a licensed track.
I don't really understand what you're doing. if you give me more information I might be able to help you.
We are implementing a new licensing server and our client applications will validate the license and direct wyUpdate to point to a new location to retrieve the wyserver.wys file. I need to transition our current solution to this new method which will be handled in the next release. However, the current solution is calling wyUpdate.exe without any commandline parameters to connect to a ftp server to download the media. I can't see uploading to the same location since that would allow anyone to simply run wyUpdate.exe directly and get the latest updates without hitting our license server first.
Right now, my solution has been to simply make 1 last upload in the current location and reconfigure the project to upload to a new location and compile using the -vs="<version number>" parameter to continue compiling here. My thought (And this isn't a big deal now) was have the option to redirect back to the earlier location without having to manually change the server location in the GUI (e.g. Scripted). This would be if there is a critical fix that we need to back fill.
I hope that this makes sense. I'm trying to keep this transition smooth while preventing a bypass solution for licensing is critical. This seemed to be the avenue for me to take since I can't upload the update and server files to separate locations (Unless I missed that option).
