Piping unity Editor.log from C:\Windows\system32\config\systemprofile\AppData\Local\Unity\Editor\Editor.log WARN: Revision data for previous build unavailable unable to determine change log $ "C:\Program Files\TortoiseHg\hg.exe" log -rev. $ "C:\Program Files\TortoiseHg\hg.exe" update -rev defaultĨ9 files updated, 0 files merged, 0 files removed, 0 files unresolved Pruned down to 0 probably relinkable files Tip has 89 files, estimated total number of files: 133 Relinking C:\Bitnami\jenkins-1.568-0\apps\jenkins\jenkins_home\hgcache\F3BC0D0C62E81590DAC468D0CD39E7E3EEF2EA34\.hg/store to C:\Bitnami\jenkins-1.568-0\apps\jenkins\jenkins_home\jobs\Template Unity Project\workspace\.hg/store $ "C:\Program Files\TortoiseHg\hg.exe" -config extensions.relink= relink C:\Bitnami\jenkins-1.568-0\apps\jenkins\jenkins_home\hgcache\F3BC0D0C62E81590DAC468D0CD39E7E3EEF2EA34 $ "C:\Program Files\TortoiseHg\hg.exe" clone -noupdate C:\Bitnami\jenkins-1.568-0\apps\jenkins\jenkins_home\hgcache\F3BC0D0C62E81590DAC468D0CD39E7E3EEF2EA34 "C:\Bitnami\jenkins-1.568-0\apps\jenkins\jenkins_home\jobs\Template Unity Project\workspace" Here is the console output that I get: $ "C:\Program Files\TortoiseHg\hg.exe" clone -noupdate C:\repo\TemplateUnityProject.hg C:\Bitnami\jenkins-1.568-0\apps\jenkins\jenkins_home\hgcache\F3BC0D0C62E81590DAC468D0CD39E7E3EEF2EA34 Naturally for this purpose, I'm using the Unit圓dBuilder, Mercurial, and Redmine plugins in Jenkins. hgignore file, and a bunch of README.txt files so I can commit the folders into Mercurial. For testing purposes, I chose this fairly minimal project that has one scene, one build script, one. This solutions has an obvious drawback of discarding any artifacts from previous build, which might save time during the next build and cloning the entire repository from the source control each time instead of just a bunch of changes.įor us I figured we are not running these 'qa' builds too often and the codebase is not too big yet, so we've settled with this workaround for the time being.I'm currently trying to turn one of my Windows 7 machine into a continuous integration server that builds Unity 3D projects from several Mercurial repositories. Do not forget to mark this checkbox in job configuration: There is a plugin, which can make this a part of a build job: Workspace Cleanup Plugin. Simple (although not excatly most efficient) trick that works is wiping the workspace before build. Jenkins developers already know about this issue: Support tags instead of branches hg/hgtags tag points to the "old" revision, it thinks nothing has changed for that tag-branch. Jenkins uses a variation of hg incoming -r 'tag' to check for changes in repository.So in order to see moved tag you have to have this file in local repository. Tags in Mercurial are merely records in a version controlled file.Unfortunately, Mercurial's approach to tags and Jenkins' approach to checking for changes in repositories do not let the magic happen: We also have a bunch of jobs on Jenkins, which are supposed to get latest 'qa' revision, build and deploy the system to testing environment.Īnd one would think that since Mercurial's -r parameters work equally well with branches and tags, he is all set. For example, we use tag 'qa' to mark a version of the system, which we think is worth deploying into our testing environment and running exetended set of tests. We use Mercurial tags to designate revisions suitable for some practical purposes. If you like us use Mercurial for your source control and use Jenkins for continous integration and deployment, there is something you should know.
0 Comments
Leave a Reply. |