JamesWhat would be your thoughts on creating a Git repository just to store the *.wyp file in along with the binaries of previous versions?
Where to persist .wyp file?
JamesHello,
In the scenario of the application being build on the CI server, I have checked in a *.wyp file with the application. After the build is completed a 'newVersion.xml' file is generated that is passed to wybuild.cmd.exe to modify the *.wyp file.
The binaries for this release (/bu) are stored away in a share that will be kept for the life of the application, along with the incremental/catch-up update files.
The question is where do you recommend to persist these changes to the *.wyp file. I'm against the CI server checking these changes back into Git, as it is not really a change to the product, and it would trigger another build of the CI server (unless tagged with something appropriate). Another developer could revert this CI commit and we would have a broken chain of updates built by wyBuild, who is not aware of 1.1 existing whilst building 1.2.
Do you have any advise on this - should I just keep the *.wyp file in the same directory as I am keeping the previous version binaries. Although I don't like the approach personally.
JamesJamesTo follow up on this thread, I create a new repository to store the binaries and the updates in the following structure:
AppUpdates /App.wyp /addVersion.xml <- Generated with a Powershell script with Files and Actions. /Binaries /v1.0.1/** /v1.0.2/** etc /Updates /app.all.to.1.0.1.wyu /app.all.to.1.0.2.wyu /wyserver.wys
This seems to be working well, and I can now run all my scripts in TeamCity and have a new update created along with storing the binaries of all previous versions to ensure we can build new versions as we go along.
The application is not very large (11MB) and so storing many revisions in Git does not matter to much for me, on a major release change I could always purge old versions from the repository and the wyp.
I wouldn't worry so much about storing the update files themselves (*.wyu and *.wys), but yes, the wyp file and all the original binaries are important. You should retain and backup the binaries to your app, and storing the wyp in a git repository isn't a bad idea.