[oe] [RFC][meta-oe][PATCH] jenkins: add 1.547
Martin Jansa
martin.jansa at gmail.com
Sun Jan 19 13:43:27 UTC 2014
On Sat, Jan 18, 2014 at 12:04:04PM +0100, Koen Kooi wrote:
> The package split is based on the debian packages which have -common/-server and -slave.
>
> Signed-off-by: Koen Kooi <koen at dominion.thruhere.net>
> ---
>
> This introduces a dependency on meta-java, which is of course a big no-no for meta-oe :( That leaves me with a few questions:
>
> 1) What's the best place for the jenkins recipe?
That's really hard question, I can only think that meta-java or
completly new layer would fit.
> 2) Do we have a virtual/runtime thing to express a dependency on /usr/bin/java without dragging in meta-java?
I think this isn't enough, because it would still show error that
virtual/java-foo isn't provided in included layers.
You can make it PACKAGECONFIG (sort of like RP did with python for
opkg-utils) which means that without PACKAGECONFIG change it won't build
at all.
> 3) Any ideas for the contents and deps of the jenkins-slave package?
Just something like jenkins user and runtime dependency on java and leave
slave setup on jenkins master?
> .../jenkins/jenkins/jenkins-server.service | 11 +++++++
> meta-oe/recipes-devtools/jenkins/jenkins_1.547.bb | 36 ++++++++++++++++++++++
> 2 files changed, 47 insertions(+)
> create mode 100644 meta-oe/recipes-devtools/jenkins/jenkins/jenkins-server.service
> create mode 100644 meta-oe/recipes-devtools/jenkins/jenkins_1.547.bb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20140119/ccf350a2/attachment-0002.sig>
More information about the Openembedded-devel
mailing list