Skip to content
GitLab
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
buildstream
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
6
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
BuildStream
buildstream
Commits
59b37f70
Commit
59b37f70
authored
6 years ago
by
James Ennis
Browse files
Options
Downloads
Patches
Plain Diff
using_config.rst: Update our instructions for how we declare caches in user config
parent
2838d080
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/source/using_config.rst
+52
-15
52 additions, 15 deletions
doc/source/using_config.rst
doc/source/using_configuring_artifact_server.rst
+2
-0
2 additions, 0 deletions
doc/source/using_configuring_artifact_server.rst
with
54 additions
and
15 deletions
doc/source/using_config.rst
+
52
−
15
View file @
59b37f70
...
...
@@ -32,38 +32,75 @@ the supported configurations on a project wide basis are listed here.
Artifact server
~~~~~~~~~~~~~~~
The project you build will often specify a :ref:`remote artifact cache
<artifacts>` already, but you may want to specify extra caches. There are two
ways to do this. You can add one or more global caches:
Although project's often specify a :ref:`remote artifact cache <artifacts>` in
their ``project.conf``, you may also want to specify extra caches.
**Example**
Assuming that your host/server is reachable on the internet as ``artifacts.com``
(for example), there are two ways to declare remote caches in your user
configuration:
1. Adding global caches:
.. code:: yaml
#
# Artifacts
#
artifacts:
url: https://artifacts.com/artifacts
# Add a cache to pull from
- url: https://artifacts.com/artifacts:11001
server-cert: server.crt
# Add a cache to push/pull to/from
- url: https://artifacts.com/artifacts:11002
server-cert: server.crt
client-cert: client.crt
client-key: client.key
push: true
# Add another cache to pull from
- url: https://anothercache.com/artifacts:8080
server-cert: another_server.crt
.. note::
Caches listed there will be considered lower priority than those specified
by the project configuration.
Caches declared here will be used by **all** BuildStream project's on the user's
machine and are considered a lower priority than those specified in the project
configuration.
You can also add project-specific caches:
**Example**
2. Specifying caches for a specific project within the user configuration:
.. code:: yaml
projects:
project-name:
artifacts:
- url: https://artifacts.com/artifacts1
- url: ssh://user@artifacts.com/artifacts2
# Add a cache to pull from
- url: https://artifacts.com/artifacts:11001
server-cert: server.crt
# Add a cache to push/pull to/from
- url: https://artifacts.com/artifacts:11002
server-cert: server.crt
client-cert: client.crt
client-key: client.key
push: true
# Add another cache to pull from
- url: https://ourprojectcache.com/artifacts:8080
server-cert: project_server.crt
.. note::
Caches listed here will be considered a higher priority than those specified
by the project. Furthermore, for a given list of URLs, earlier entries will
have higher priority.
Notice that the use of different ports for the same server distinguishes between
pull only access and push/pull access. For information regarding this and the
server/client certificates and keys, please see:
:ref:`Key pair for the server <server_authentication>`.
Caches listed here will be considered higher priority than those specified
by the project.
If you give a list of URLs, earlier entries in the list will have higher
priority than later ones.
Strict build plan
~~~~~~~~~~~~~~~~~
...
...
This diff is collapsed.
Click to expand it.
doc/source/using_configuring_artifact_server.rst
+
2
−
0
View file @
59b37f70
...
...
@@ -98,6 +98,8 @@ Command reference
:prog: bst-artifact-server
.. _server_authentication:
Key pair for the server
~~~~~~~~~~~~~~~~~~~~~~~
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment