How about crafting a special jenkins_build.xml that calls the relevant tasks from build.xml? jenkins_build.xml would have its own jenkins.properties file.
This way, we wont have the hassle of checking in stuff that would affect users who dont care about jenkins. On Thu, Jan 24, 2013 at 8:59 PM, Justin Mclean <jus...@classsoftware.com>wrote: > Hi, > > > I'm not sure I understood that, but could you add the option in > > build.properties? > There is no local build.properties file that we can easily edit on the > Jenkins box (as we have no access) and we wouldn't want to put it in SVN as > it would then effect all builds. Initially Jenkins start with a clean slate > and checks out everything from SVN. > > > Then if we think we need to remove that option to fix it, we don't have > to learn jenkins, we can just edit the build.properties? > Don't think so see above. I could have the build script generate a > build.properties file but that seem a little silly. > > > On a related note, is there a way to ask Jenkins to simply 'try again'? > Yes but it would fail again, if the files are not there it will fail each > time until we change to build options to download the files. > > > Back in the day, we had a file called kick-build.txt in the root that > we'd modify > > and check in to do that. > Any checkin will trigger a build and run of the check in texts (once per > hour max). You can also manually run builds. > > Justin
