James Ennis authored Jul 27, 2018 and Javier Jardón committed Jul 27, 2018

  This patch also removes displaying the projects that live within
  the buildstream-examples repository, as we wish to deprecate this
  repo and migrate the two examples.
  - #438 and #439

  In addition to this, both examples do not 'build' in their current
  state.

Refer readers to our tutorial before referring them to existing bst projects

See merge request !578

The separator is useful in source files other than _project.py

This is part of a later plan to implement mirroring without forcing
everyone to update their sources. We use the expected calls to
Source.translate_url() when running Source.configure() to extract the
aliases from the URL. Multiple aliases must be extracted because
sources exist that may fetch from multiple aliases (for example, git
submodules)

Later, we want to substitute another URI where the alias normally reads
from the project - We accomplish this by re-instantiating the Source
with the alias overrides passed as an argument to the constructor.

**KLUDGE WARNING**: This involves making the source store its "meta"
object so that it's possible to create a copy of the source inside the
fetch queue, instead of back when the pipeline was being loaded.

This adds the SourceFetcher class, which is intended for sources that
fetch from multiple URLs (e.g. the git source and its submodules)

Fix when fetching

In user config (buildstream.conf), it is set with the "default-mirror"
field.

On the command-line, it is set with "--default-mirror"

This fixes:
* Bzr repositories pulling from the branch they were created with.
* Bzr's _ensure_mirror() not actually checking that it successfully
  mirrored the ref.

When implementing fetching from mirrors, I encountered some problems
with the git source:

1. The mirror URL was using translate_url()'s output, so if a different
   alias was used, then fetching from the mirror would go to a different
   directory, and be inaccessible.
2. After fixing that, fetching was unable to pull from a URL other than
   the one used at repository creation, meaning it wouldn't actually
   pull from the mirror.

This is helpful if you want to test what happens when you have one repo
that has diverged from another. By copying the repo you're sure they
start with shared history.

This is especially useful when mirroring.

Resolve "Support for downloading sources from mirrors"

Closes #328

See merge request !404

Qinusty authored Jul 23, 2018 and Qinusty committed Jul 27, 2018

This address issue #491.

When attempting to run buildstream with a configuration specifying
a cache quota larger than your available disk space, buildstream
will alert the user and exit.

Note:
This takes into consideration your current cache usage and
therefore restricts the overall size of your artifact cache folder.

Cache quota is now restricted to available disk space

See merge request !563

Resolve "Some log lines appear to be duplicates"

Closes #507

See merge request !573

Since we have now backported this to `bst-1.2`, the APIs have
been introduced in 1.2 and not 1.4

These features will be released in 1.1.5 since they have been
backported, lets reflect this in the NEWS file in master.

Also this adds the backported `remote` plugin to the NEWS

Use os.rename() to rename the cloned temporary repository into
place in the source cache, and issue a STATUS message when discarding
a duplicate clone, in the case where the same repository is cloned
twice in parallel.

The problem with using shutil.move() is that it will create the source
directory in a subdirectory of the destination when the destination
exists, so it's behavior depends on whether the destination exists.

This shutil.move() behavior has so far hidden the race condition
where a duplicate repo is created in a subdirectory, as you need
to have three concurrent downloads of the same repo in order to
trigger the error.

This fixes issue #503

git.py: Handle concurrent download completions properly

Closes #503

See merge request !583

Phil Dawson authored Jul 10, 2018 and Phil Dawson committed Jul 30, 2018

This is part of the work towards #437.

Phil Dawson authored Jul 11, 2018 and Phil Dawson committed Jul 30, 2018

This is part of the work towards #437.

Phil Dawson authored Jul 17, 2018 and Phil Dawson committed Jul 30, 2018

This is part of the work towards #437.

Phil Dawson authored Jul 19, 2018 and Phil Dawson committed Jul 30, 2018

This is part of the work towards issue #437.

This commit is part of the work required to resolve issue #436