wyBuild does show what you version you last built (the version number next to the "Upload updates" button on the upload screen).
You're right, though -- we should probably indicate somewhere what version you last successfully *uploaded*.
We build updates for a number of our products from one machine using wyBuild and have enjoyed the simplicity of your product.
One thing I've been running into, which I couldn't find an article that specifically addresses this, was the need to have a log file to identify what the last action(s) were for a specific build/upload of a product. Many times I'm having to start a build or an upload and then get pulled away on another project. When I get back I often may not remember the last job I requested from wyBuild and when. I do realize that I can test the download of a build after I uploaded it, but that is a lengthy process to find the answer when a log file could answer my question. In some cases (generally for our staging server) I will recompile new media for the same version to be retested.
If this is something that you do not have currently, I'm really looking for simple log entries that state the following (I suspect the logs would be split up into their perspective product locations): 1. When the job was started2. What it was (Build or Upload)3. What build files were involved
Thank you again for your time.
Jim
wyBuild does show what you version you last built (the version number next to the "Upload updates" button on the upload screen).
You're right, though -- we should probably indicate somewhere what version you last successfully *uploaded*.
Thank you for the feedback Wyatt (Sorry for the delay).
I can see the last version uploaded in the "Upload the Updates" section, and it's not so bad when I'm uploading to our production server. However, our staging server may receive numerous builds for the same version which makes it challenging. I don't increment the version number because we roll our environments back at the end of each test. I try to keep the version tabs the same between our production and our staging so I know exactly what I'm going to deploy.
Jim