Do you use Subversion as SCM ?
if yes, svn:externals are a very convenient way of specifying
dependencies among projects and have jenkins schedule builds according
to those dependencies
In the /lib of each project, you don't copy "physically" the jars of
yours that it depends on but you make an svn:externals link to them
where they are stored in svn.
Then, each time the low-level lib is changed, Jenkins detects it via
the externals, re-import the new version in its workspace and starts
buidling.
By doing, so you don't have duplicate definitions in Jenkins versus
SVN: everything is in 1 single place: the externals of svn
regards
didier
C is pretty platform dependent, so just because you store libs in scm doesn't mean you are hitting all your targets.
I would probably recommend using ivy. Ivy will give you the ability to use transitive dependency management over your c libs. You can contextualize by platform. This will give you flexibility to build cleanly for different platforms or even just different versions of libraries or whatever.
You can keep the libs out of your vcs.
You don't even need to build with it. You can just use it to handle your dependencies, but i recommend not.
Leo
(none)
On Tue, Dec 13, 2011 at 11:08 AM, Kamal Ahmed <kamal22...@yahoo.com> wrote:
> [Winstone 2011/12/13 11:02:59] - Untrapped Error in Servlet
> javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException:
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.443.jar!/jenkins/model/Jenkins/configure.jelly:58:84:
> <st:include> No page found 'config.jelly' for class
> org.jenkinsci.plugins.slave_setup.SetupConfig
Disable the slave setup plugin, restart. Then look for an existing
JIRA that captures this problem, or open a new one.
-Jesse
--
There are 10 types of people in this world, those
that can read binary and those that can not.
From: Jesse Farinacci <jie...@gmail.com>
To: jenkins...@googlegroups.com
Sent: Tuesday, December 13, 2011 11:13 AM
Subject: Re: Cannot access "Manage Jenkins" 1.443