All of lore.kernel.org
 help / color / mirror / Atom feed
From: gmane@reliableembeddedsystems.com
To: Joshua Lock <joshua.g.lock@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: Y-AB automatic updates?
Date: Tue, 11 Oct 2016 18:38:45 +0300	[thread overview]
Message-ID: <d55fea8b61e453f1ad6bf5d2ea96ae75@reliableembeddedsystems.com> (raw)
In-Reply-To: <1476196748.2912.36.camel@linux.intel.com>

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


      reply	other threads:[~2016-10-11 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11  8:42 Y-AB automatic updates? gmane
2016-10-11 14:39 ` Joshua Lock
2016-10-11 15:38   ` gmane [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d55fea8b61e453f1ad6bf5d2ea96ae75@reliableembeddedsystems.com \
    --to=gmane@reliableembeddedsystems.com \
    --cc=joshua.g.lock@linux.intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.