Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
ffbs-gluon
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
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
darkbit
ffbs-gluon
Commits
95c04cd8
Unverified
Commit
95c04cd8
authored
8 years ago
by
Ruben Barkow
Committed by
Matthias Schiffer
8 years ago
Browse files
Options
Downloads
Patches
Plain Diff
docs: improve autoupdater explanation
parent
c9563cde
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/features/autoupdater.rst
+14
-11
14 additions, 11 deletions
docs/features/autoupdater.rst
with
14 additions
and
11 deletions
docs/features/autoupdater.rst
+
14
−
11
View file @
95c04cd8
...
...
@@ -11,14 +11,19 @@ during development), but it can be enabled by setting the variable GLUON_BRANCH
to override the default branch set in the set in the site configuration.
A manifest file for the updater can be generated with `make manifest`. A signing script (using
ecdsautils) can by found in the `contrib` directory. When creating the manifest,
``GLUON_PRIORITY`` can
be set
on the command line
,
or i
t can be taken from the
``site.mk``.
``
ecdsautils
``
) can by found in the `contrib` directory. When creating the manifest,
the
``PRIORITY`` value may be defined by setting ``GLUON_PRIORITY``
on the command line or i
n
``site.mk``.
The priority defines the maximum number of days that may pass between releasing an update and installation
of the images. The update probability will start at 0 after the release time mentioned in the manifest
and then slowly rise to 1 up to the point when the number of days given by the priority has passed.
``GLUON_PRIORITY`` defines the maximum number of days that may pass between releasing an update and installation
of the images. The update probability will start at 0 after the release time declared in the manifest file
by the variable DATE and then slowly rise up to 1 when ``GLUON_PRIORITY`` days have passed. The autoupdater checks
for updates hourly (at a random minute of the hour), but usually only updates during its run between
4am and 5am, except when the whole ``GLUON_PRIORITY`` days and another 24 hours have passed.
The priority may be an integer or a decimal fraction.
``GLUON_PRIORITY`` may be an integer or a decimal fraction.
Automated nightly builds
------------------------
A fully automated nightly build could use the following commands:
...
...
@@ -71,11 +76,9 @@ These commands can be used on a node:
# Force update check, even when the updater is disabled
autoupdater -f
::
# If fallback is true the updater will perform an update only if
#
the timespan given by the priority
and another 24h have passed
# If fallback is true the updater will perform an update only if
the timespan
#
PRIORITY days (as defined in the manifest)
and another 24h have passed
autoupdater --fallback
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