SRC_URI and latest HEAD revision with git

DISCUSSION Steffen Sledz 4 participants 15 messages Jul 22, 2013 – Aug 1, 2013

Share & tools

Steffen Sledz

author

2013-07-22 06:21 UTC #0 lore raw

After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).

I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.

Cheers,
Steffen

Signature · 7 lines

DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058

Nicolas Dechesne

2013-07-22 09:02 UTC #1 lore raw

Quoted 7 lines · Steffen Sledz

After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.

you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.

e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distro/include/poky-floating-revisions.inc

Steffen Sledz

author

2013-07-22 09:46 UTC #2 lore raw

Quoted 8 lines · Nicolas Dechesne

Quoted 3 lines · On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]…
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g. http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distro/include/poky-floating-revisions.inc

Hmmmm? This doesn't seem the work.

Here's what i tried in my recipe:

------------> snip <------------
PR = "r3"

SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------

But i get package versions like

gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3

where SRCPB is always 0. :(

A bit more description and/or a complete example would be very helpful.

Regards,
Steffen

Signature · 7 lines

DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058

Paul Eggleton

2013-07-22 09:51 UTC #3 lore raw

Quoted 26 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:

Quoted 6 lines · Nicolas Dechesne
Quoted 4 lines · On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]…
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
Quoted 8 lines
Quoted 2 lines
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distr
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------

Quoted 7 lines

But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.

If you want these to increment now AIUI you need to be using the PR server:

https://wiki.yoctoproject.org/wiki/PR_Service

Cheers,
Paul

Signature · 2 lines

Paul Eggleton
Intel Open Source Technology Centre

Steffen Sledz

author

2013-07-22 10:30 UTC #4 lore raw

Quoted 31 lines · Paul Eggleton

Quoted 30 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 6 lines · Nicolas Dechesne
Quoted 4 lines · On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]…
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
Quoted 8 lines
Quoted 2 lines
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distr
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3

Quoted 7 lines

Quoted 3 lines
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:
https://wiki.yoctoproject.org/wiki/PR_Service

This seems to be the thing we need.

But the description is not very helpful from the view of a recipe maintainer. It describes mostly the server part.

* What do i have to write in my recipe?
* What modifications in bitbake.conf, local.conf, ... are necessary?

Regards,
Steffen

Signature · 7 lines

DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058

Paul Eggleton

2013-07-22 11:08 UTC #5 lore raw

Quoted 43 lines · On Monday 22 July 2013 12:30:53 Steffen Sledz wrote:

Quoted 42 lines · Paul Eggleton
Quoted 30 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 10 lines · Nicolas Dechesne
On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]
Quoted 6 lines · <mailto:[email protected]>> wrote:
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
Quoted 7 lines
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
r
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
Quoted 7 lines
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:

Quoted 8 lines

Quoted 1 line
https://wiki.yoctoproject.org/wiki/PR_Service
This seems to be the thing we need.
But the description is not very helpful from the view of a recipe maintainer. It describes mostly the server part.
* What do i have to write in my recipe?

Nothing special. If you used SRCPV in PV where you are using an SCM in SRC_URI, that should be enough. The integer at the start of SRCREV will be incremented automatically if the revision changes, and if it doesn't but other values within the recipe change then PR will automatically be incremented above the initial value set in the recipe.

Quoted 1 line

* What modifications in bitbake.conf, local.conf, ... are necessary?

I believe as described in the page I linked above you should only need to set PRSERV_HOST.

Cheers,
Paul

Signature · 2 lines

Paul Eggleton
Intel Open Source Technology Centre

Martin Jansa

2013-07-22 12:41 UTC #6 lore raw

Quoted 59 lines · Paul Eggleton

Quoted 43 lines · On Monday 22 July 2013 12:30:53 Steffen Sledz wrote:
Quoted 42 lines · Paul Eggleton
Quoted 30 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 10 lines · Nicolas Dechesne
On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]
Quoted 6 lines · <mailto:[email protected]>> wrote:
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
Quoted 7 lines
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
r
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
Quoted 7 lines
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:
Quoted 8 lines
Quoted 1 line
https://wiki.yoctoproject.org/wiki/PR_Service
This seems to be the thing we need.
But the description is not very helpful from the view of a recipe maintainer. It describes mostly the server part.
* What do i have to write in my recipe?
Nothing special. If you used SRCPV in PV where you are using an SCM in SRC_URI, that should be enough. The integer at the start of SRCREV will be incremented automatically if the revision changes, and if it doesn't but other values within the recipe change then PR will automatically be incremented above the initial value set in the recipe.

Quoted 4 lines

Quoted 1 line
* What modifications in bitbake.conf, local.conf, ... are necessary?
I believe as described in the page I linked above you should only need to set PRSERV_HOST.

If you need to support upgrade path from old LOCALCOUNT db in PERSISTENT_DIR then you also need to migrate last numbers to PRSERV db.

Signature · 1 line

Martin 'JaMa' Jansa     jabber: [email protected]

Steffen Sledz

author

2013-07-23 06:23 UTC #7 lore raw

In reply to Paul Eggleton

Quoted 59 lines · Paul Eggleton

Quoted 43 lines · On Monday 22 July 2013 12:30:53 Steffen Sledz wrote:
Quoted 42 lines · Paul Eggleton
Quoted 30 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 10 lines · Nicolas Dechesne
On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]
Quoted 6 lines · <mailto:[email protected]>> wrote:
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
Quoted 7 lines
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
r
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
Quoted 7 lines
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:
Quoted 8 lines
Quoted 1 line
https://wiki.yoctoproject.org/wiki/PR_Service
This seems to be the thing we need.
But the description is not very helpful from the view of a recipe maintainer. It describes mostly the server part.
* What do i have to write in my recipe?
Nothing special. If you used SRCPV in PV where you are using an SCM in SRC_URI, that should be enough. The integer at the start of SRCREV will be incremented automatically if the revision changes, and if it doesn't but other values within the recipe change then PR will automatically be incremented above the initial value set in the recipe.

Quoted 4 lines

Quoted 1 line
* What modifications in bitbake.conf, local.conf, ... are necessary?
I believe as described in the page I linked above you should only need to set PRSERV_HOST.

You're right. This works. ;-)

I've two points more:
* The Wiki-Page mentions the bitbake-prserv-tool. Where can this be found? It does not seem to be part of the bitbake repo.
* Does anyone have systemd configs or sysvinit scripts for handling the bitbake-prserv?

Cheers,
Steffen

Signature · 7 lines

DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058

Paul Eggleton

2013-07-23 08:20 UTC #8 lore raw

Quoted 23 lines · On Tuesday 23 July 2013 08:23:54 Steffen Sledz wrote:

Quoted 22 lines · Paul Eggleton
Quoted 4 lines · On Monday 22 July 2013 12:30:53 Steffen Sledz wrote:
Quoted 3 lines · Paul Eggleton
If you want these to increment now AIUI you need to be using the PR server:
Quoted 8 lines
Quoted 1 line
https://wiki.yoctoproject.org/wiki/PR_Service
This seems to be the thing we need.
But the description is not very helpful from the view of a recipe maintainer. It describes mostly the server part.
* What do i have to write in my recipe?
Nothing special. If you used SRCPV in PV where you are using an SCM in SRC_URI, that should be enough. The integer at the start of SRCREV will be incremented automatically if the revision changes, and if it doesn't but other values within the recipe change then PR will automatically be incremented above the initial value set in the recipe.
Quoted 1 line
* What modifications in bitbake.conf, local.conf, ... are necessary?

Quoted 7 lines

Quoted 2 lines
I believe as described in the page I linked above you should only need to set PRSERV_HOST.
You're right. This works. ;-)
I've two points more:
* The Wiki-Page mentions the bitbake-prserv-tool. Where can this be found?

Perhaps confusingly it's part of OE-Core. I haven't looked at it to see if there's anything OE-specific about it that meant it had to be there rather than supplied with bitbake.

Quoted 2 lines

* Does anyone have systemd configs or sysvinit scripts for handling the bitbake-prserv?

I don't, but perhaps others do.

Cheers,
Paul

Signature · 2 lines

Paul Eggleton
Intel Open Source Technology Centre

Steffen Sledz

author

2013-07-31 10:02 UTC #9 lore raw

Re: SRC_URI and latest HEAD revision with git (in oe-classic)

In reply to Paul Eggleton

Quoted 31 lines · Paul Eggleton

Quoted 30 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 6 lines · Nicolas Dechesne
Quoted 4 lines · On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]…
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
Quoted 8 lines
Quoted 2 lines
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distr
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3

Quoted 7 lines

Quoted 3 lines
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:
https://wiki.yoctoproject.org/wiki/PR_Service

And here comes my next really big problem. :(

We're sitting on an big, old but active project based on oe-classic and bitbake 1.12.0. Irksomely we're forced to switch from SVN to GIT for this project. So we need the AUTOREV/PRSERV stuff for this old environment too.

Has anyone tried to backport the feature to an older bitbake/oe-classic environment? Or can someone give some hints what's to do?

Steffen

Signature · 7 lines

DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058

Paul Eggleton

2013-07-31 12:50 UTC #10 lore raw

Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic)

Quoted 45 lines · On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote:

Quoted 35 lines · Paul Eggleton
Quoted 34 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 10 lines · Nicolas Dechesne
On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]
Quoted 6 lines · <mailto:[email protected]>> wrote:
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
Quoted 7 lines
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
r
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
Quoted 8 lines
Quoted 3 lines
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:
https://wiki.yoctoproject.org/wiki/PR_Service

Quoted 8 lines

And here comes my next really big problem. :(
We're sitting on an big, old but active project based on oe-classic and bitbake 1.12.0. Irksomely we're forced to switch from SVN to GIT for this project. So we need the AUTOREV/PRSERV stuff for this old environment too.
Has anyone tried to backport the feature to an older bitbake/oe-classic environment? Or can someone give some hints what's to do?

I'm not sure, but my gut feeling is you'd be better off trying to bring the project up to be based on OE-Core rather than trying to bring such functionality back to OE-Classic, particularly since for full functionality it requires signature-based tasks that are only supported with current versions of bitbake and require support from the metadata. You'd be trading some hopefully short-term pain for long-term gain if the project is going to continue for a reasonable amount of time.

Cheers,
Paul

Signature · 2 lines

Paul Eggleton
Intel Open Source Technology Centre

Steffen Sledz

author

2013-08-01 06:11 UTC #11 lore raw

Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic)

Quoted 55 lines · Paul Eggleton

Quoted 45 lines · On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote:
Quoted 35 lines · Paul Eggleton
Quoted 34 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 10 lines · Nicolas Dechesne
On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]
Quoted 6 lines · <mailto:[email protected]>> wrote:
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
Quoted 7 lines
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
r
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
Quoted 8 lines
Quoted 3 lines
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:
https://wiki.yoctoproject.org/wiki/PR_Service
Quoted 8 lines
And here comes my next really big problem. :(
We're sitting on an big, old but active project based on oe-classic and bitbake 1.12.0. Irksomely we're forced to switch from SVN to GIT for this project. So we need the AUTOREV/PRSERV stuff for this old environment too.
Has anyone tried to backport the feature to an older bitbake/oe-classic environment? Or can someone give some hints what's to do?

Quoted 7 lines

I'm not sure, but my gut feeling is you'd be better off trying to bring the project up to be based on OE-Core rather than trying to bring such functionality back to OE-Classic, particularly since for full functionality it requires signature-based tasks that are only supported with current versions of bitbake and require support from the metadata. You'd be trading some hopefully short-term pain for long-term gain if the project is going to continue for a reasonable amount of time.

I was afraid to get this answer. ;-)

Unfortunately we do not have the manpower to bring up this old project to oe-core. Our team is working hard on a follow-up project based on oe-core.

I read something about a solution using

BB_GIT_CLONE_FOR_SRCREV = "1"
BB_LOCALCOUNT_OVERRIDE = ""

which should be supported by the old oe-classic/bitbake-1.12.0. Could this be a solution for our problem? What drawbacks does it have?

Steffen

Signature · 7 lines

DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058

Martin Jansa

2013-08-01 10:35 UTC #12 lore raw

Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic)

Quoted 66 lines · Steffen Sledz

Quoted 55 lines · Paul Eggleton
Quoted 45 lines · On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote:
Quoted 35 lines · Paul Eggleton
Quoted 34 lines · On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
Quoted 10 lines · Nicolas Dechesne
On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <[email protected]
Quoted 6 lines · <mailto:[email protected]>> wrote:
After being OE abstinent for some months i'd like to ask what is the current suggested method for recipes building from the HEAD revision of a git repository (we need this for continuous integration).
I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final decision, documentation and a good example.>
Quoted 7 lines
you can use ${AUTOREV} for this purpose. You can look at poky-bleeding distro config for such an example.
e.g.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
r
o/include/poky-floating-revisions.inc
Hmmmm? This doesn't seem the work.
Here's what i tried in my recipe:
------------> snip <------------
PR = "r3"
SRCREV="${AUTOREV}"
PV = "gitr${SRCPV}"
------------> snip <------------
But i get package versions like
gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
Quoted 8 lines
Quoted 3 lines
where SRCPB is always 0. :(
A bit more description and/or a complete example would be very helpful.
If you want these to increment now AIUI you need to be using the PR server:
https://wiki.yoctoproject.org/wiki/PR_Service
Quoted 8 lines
And here comes my next really big problem. :(
We're sitting on an big, old but active project based on oe-classic and bitbake 1.12.0. Irksomely we're forced to switch from SVN to GIT for this project. So we need the AUTOREV/PRSERV stuff for this old environment too.
Has anyone tried to backport the feature to an older bitbake/oe-classic environment? Or can someone give some hints what's to do?
Quoted 7 lines
I'm not sure, but my gut feeling is you'd be better off trying to bring the project up to be based on OE-Core rather than trying to bring such functionality back to OE-Classic, particularly since for full functionality it requires signature-based tasks that are only supported with current versions of bitbake and require support from the metadata. You'd be trading some hopefully short-term pain for long-term gain if the project is going to continue for a reasonable amount of time.
I was afraid to get this answer. ;-)

Quoted 8 lines

Unfortunately we do not have the manpower to bring up this old project to oe-core. Our team is working hard on a follow-up project based on oe-core.
I read something about a solution using
BB_GIT_CLONE_FOR_SRCREV = "1"
BB_LOCALCOUNT_OVERRIDE = ""
which should be supported by the old oe-classic/bitbake-1.12.0. Could this be a solution for our problem? What drawbacks does it have?

BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone).

empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed).

Quoted 14 lines

Steffen

Signature · 11 lines

DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Signature · 1 line

Martin 'JaMa' Jansa     jabber: [email protected]

Steffen Sledz

author

2013-08-01 10:52 UTC #13 lore raw

Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 10 lines · Martin Jansa

Quoted 7 lines · Steffen Sledz
Quoted 1 line · Paul Eggleton
On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote:
... I read something about a solution using
BB_GIT_CLONE_FOR_SRCREV = "1" BB_LOCALCOUNT_OVERRIDE = ""
which should be supported by the old oe-classic/bitbake-1.12.0. Could this be a solution for our problem? What drawbacks does it have?
BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone).

Every git repo? Or every git repo used with AUTOREV only?

Quoted 1 line

empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed).

That should be OK for us.

- --
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle; Amtsgericht Berlin Charlottenburg; HRB 130120 B; Ust.-IDNr. DE273952058
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlH6PgUACgkQlSfCk8EgCzhRlgCgm/sRrRd945HXKRdsj8aL/+qa bagAnidiDoZO6PtViGA9zJfSRa+n4IcK
=rQan
-----END PGP SIGNATURE-----

Martin Jansa

2013-08-01 11:37 UTC #14 lore raw

Re: [oe] SRC_URI and latest HEAD revision with git (in oe-classic)

Quoted 9 lines · Steffen Sledz

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 5 lines · Martin Jansa
Quoted 4 lines · Steffen Sledz
Quoted 1 line · Paul Eggleton
On Wednesday 31 July 2013 12:02:42 Steffen Sledz wrote:
... I read something about a solution using

Quoted 7 lines

Quoted 5 lines
Quoted 3 lines
BB_GIT_CLONE_FOR_SRCREV = "1" BB_LOCALCOUNT_OVERRIDE = ""
which should be supported by the old oe-classic/bitbake-1.12.0. Could this be a solution for our problem? What drawbacks does it have?
BB_GIT_CLONE_FOR_SRCREV will need to clone every git repository included in metadata you're using (even if the recipe isn't built, because it needs to define AUTOREV for parsing and that needs local clone).
Every git repo? Or every git repo used with AUTOREV only?

Every git repo with SRCPV.

Quoted 20 lines

Quoted 1 line
empty BB_LOCALCOUNT_OVERRIDE should work correctly, but you need to synchronize bb_persist_data.sqlite3 between multiple builders (if you have multiple builders populating the same binary feed).
That should be OK for us.
- --
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:[email protected]
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle; Amtsgericht Berlin Charlottenburg; HRB 130120 B; Ust.-IDNr. DE273952058
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlH6PgUACgkQlSfCk8EgCzhRlgCgm/sRrRd945HXKRdsj8aL/+qa bagAnidiDoZO6PtViGA9zJfSRa+n4IcK
=rQan
-----END PGP SIGNATURE-----

Signature · 1 line

Martin 'JaMa' Jansa     jabber: [email protected]