Hi James, On 07/03/2012, at 2:54 PM, James Cicenia wrote:
> Early this morning I got the job to build and it duly put all the > frameworks,both wonder and webobjects in its Jenkins directory. And this is > where I lose all sense of what I am supposed to do. I'm not sure that you actually got the project to build given the following: > I have a project that works perfectly on my dev machine via Eclipse/Wolips. > This project is not under source control because my client still hasn't setup > git on teamforge for me. > I wrote them with urgency to get me git. I think this might be the problem. If your project is not under source control, I'm not sure how Jenkins is going to (a) know when it needs to build it (though conceivably you could just trigger it manually), or (b) retrieve it to do the build (though conceivably you could... point the job's build file at your development source code). > What do I do with Jenkins? Yeah, good question. Let's step back. Conventionally you would have Jenkins running continuously in the background waiting for some trigger (like a commit to a repository), at which point it updates its own working copy of your code, pulls in or updates any dependencies you've declared it needs, and then builds your projects, leaving some artefacts somewhere you've specified. As I mentioned earlier, it really should be at arm's length from development. Not having your work under source control is going to be fairly limiting, and I doubt Dave Avendasora's wiki instructions or associated scripts allow for this. (I haven't looked at them closely—we have our own scripts that pre-date that work.) > This all works. I'm not sure that it does. :-) Are you telling me that you've got Foo-Application.tar.gz and Foo-WebServerResources.tar.gz build products being created, you're deploying them in the usual way, and it works? Because short of that, it's not working. > But now what? What triggers Jenkins? As above, the conventional trigger would be a commit to a source control repository (whether via a post-commit hook, or Jenkins polling the repo). Or you could click on the "Build Now" icon. > How does it know anything about eclipse? It doesn't. They're not connected. Continuous integration should be proceeding in parallel to development. > Can I set up a job to not use a SCM temporarily? Potentially, though I've never done this. My advice would be to put Jenkins on hold until you can get your project into source control, and then proceed using Jenkins in the conventional way. -- Paul. http://logicsquad.net/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
