Y-AB automatic updates?

Y-AB automatic updates?

[gmane]

Hi,

With a latest and greatest Yocto Autobuilder I noticed stuff like this 
when I restart it:

---
...
  Updating PRSERV
remote: Counting objects: 20, done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 20 (delta 17), reused 0 (delta 0)
Unpacking objects: 100% (20/20), done.
 From git://git.openembedded.org/bitbake
    35927a9..d9713ed  master     -> origin/master
    35927a9..d9713ed  1.32       -> origin/1.32
  + 21defce...09dd499 master-next -> origin/master-next  (forced update)
Updating 35927a9..d9713ed
Fast-forward
  bin/bitbake         |  2 +-
  lib/bb/__init__.py  |  2 +-
  lib/bb/ui/depexp.py | 24 ++++++++++++++++++++++++
  3 files changed, 26 insertions(+), 2 deletions(-)

---

This pumps e.g. the bitbake version:

Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Tue Oct 11 08:46:35 2016 +0100

     bitbake: Update version to 1.32.0

---

Is this really intentionally and what's the purpose?

Say you have a build server for your production software and PRSERV is 
being (randomly) updated.
Due to a bug before or after the update the build output might be 
different.
So you can't reproduce your images any more.

Some people (including myself) really would like to have reproduce able 
builds.

Is there a "non hacky" way to turn these updates off?

Regards,

Robert

Re: Y-AB automatic updates?

[Joshua Lock]

On Tue, 2016-10-11 at 11:42 +0300, gmane@reliableembeddedsystems.com
wrote:
> Hi,
> 
> With a latest and greatest Yocto Autobuilder I noticed stuff like
> this 
> when I restart it:
> 
> ---
> ...
>   Updating PRSERV
> remote: Counting objects: 20, done.
> remote: Compressing objects: 100% (20/20), done.
> remote: Total 20 (delta 17), reused 0 (delta 0)
> Unpacking objects: 100% (20/20), done.
>  From git://git.openembedded.org/bitbake
>     35927a9..d9713ed  master     -> origin/master
>     35927a9..d9713ed  1.32       -> origin/1.32
>   + 21defce...09dd499 master-next -> origin/master-next  (forced
> update)
> Updating 35927a9..d9713ed
> Fast-forward
>   bin/bitbake         |  2 +-
>   lib/bb/__init__.py  |  2 +-
>   lib/bb/ui/depexp.py | 24 ++++++++++++++++++++++++
>   3 files changed, 26 insertions(+), 2 deletions(-)
> 
> ---
> 
> This pumps e.g. the bitbake version:
> 
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date:   Tue Oct 11 08:46:35 2016 +0100
> 
>      bitbake: Update version to 1.32.0
> 
> ---
> 
> Is this really intentionally and what's the purpose?

The bitbake repository is fetched by the ab-prserv script, the purpose
of which is to run a PRServer for the autobuilder.

The ab-prserv script, and the code which calls it in yocto-start-
autobuilder, won't start the script if PRSERV_HOST and PRSERV_PORT
aren't set.

If you point PRSERV_HOST and PRSERV_PORT at a non-localhost PRServer
the git repo won't be fetched/updated.

Regards,

Joshua

Re: Y-AB automatic updates?

[gmane]

Hi,

On 2016-10-11 17:39, Joshua Lock wrote:
> aren't set.
> 
> If you point PRSERV_HOST and PRSERV_PORT at a non-localhost PRServer
> the git repo won't be fetched/updated.
> 

I use the Y-AB for nightly builds and to populate DL_DIR and friends. 
It's also not unusual to use this machine as the "master" PRSERV. What 
you are saying is that if I do so through the ab-prserv script (which I 
would like to use) it will automatically update PRServer and suggest as 
a work around to move my PRServer to another machine?

I would like to use Y-AB and run the PRServer on it as well - ideally by 
using the script. So I guess I'll need to hack the ab-prserv script.

How can you do QA with the Y-AB in it's "default mode" where it 
potentially updates the PRServer whenever you restart it? And you need 
to restart it e.g. to add/modify configuration files.
I also can't see any indication which version of the PRServer is being 
used in the build logs.

> Regards,
> 
> Joshua

Regards,

Robert