Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
PrivateStorageio
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
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
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
PrivateStorage
PrivateStorageio
Graph
13e843f0a10f7520ab3ffa43fad38a2b20e0b939
Select Git revision
Branches
20
118-borg-backup-not-running-as-it-should
125.dont-set-static-datasource-uids
125.silence-broken-backup-alerts
133.give-access-to-prod-infra
149.fix-bootloader
157.authorize-new-hro-key
162.flexible-grafana-module
163.jp-to-ben-for-prod
164.grafana-alert-rules
190-our-regular-updates-fill-up-the-servers-boot-partitions
207.payment-server-exception-reporting
287.publish-tahoe-error-rate
300.monitor-payment-server
352.cachix
42.update-nixpkgs
445.update-zkapauthorizer
62.openssl-111k
67.rationalize-morph-names.2
87.qemu-local-grid
87.test-local-grid
20 results
You can move around the graph by using the arrow keys.
Begin with the selected commit
Created with Raphaël 2.2.0
22
Mar
17
15
12
8
23
Feb
16
15
14
Jan
12
23
Sep
22
21
16
15
14
4
1
Jul
25
Jun
23
22
19
17
11
10
9
8
5
4
3
1
30
May
29
5
29
Apr
8
7
20
Mar
26
Feb
2
Dec
26
Nov
20
19
8
7
6
5
4
1
31
Oct
30
29
28
26
25
24
23
21
18
16
11
4
27
Sep
26
25
24
23
20
16
9
6
5
4
29
Aug
28
12
7
6
14
Jun
13
nope - that's ultimate only
Attempt to trick GitLab into parsing and displaying the report
okay fix this not-arbitrary byte string
try this expose_as thing
Repeat Yourself
emit json instead of text
Hack our logic into the script instead
Just cannot use exit_codes, it is too new a feature
less wrong way to propagate errors maybe
Allow the vulnix pipeline to fail but propagate the code
Just ignore vulnix errors entirely?
Avoid confusing morph and vulnix errors
See how this more specific config fares
Try to allow the failure through GitLab
Merge remote-tracking branch 'origin/develop' into 81.vulnerability-scan
Merge branch '61.default-token-count-config' into 'develop'
Update ZKAPAuthorizer
Merge remote-tracking branch 'whetstone/master'
Merge branch 'gitlab-ci-6' into 'master'
Merge branch 'fix-bootloader-splash-329' into 'master'
Increase boot loader timeout to 10s
try not to fail because vulnix finds vulnerabilities
Allow secrets to be missing
try to catch and report morph error
get a bit more visibility
might not need any cleanup
Say the magic words to make everything okay
Try to run vulnix scans
Merge branch 'gitlab-ci-5' into 'master'
Make branch names reflect discussion result
Merge branch 'gitlab-ci-4' into 'master'
GitLab CI: Add deployment hooks
GitLab config: Quote all the {str|th}ings!
Remove CircleCI config
Add GitLab CI config
Note the new location of this project
Merge branch 'docs-styling'
docs: remove phone-home github button, add static text instead
Merge pull request #58 from PrivateStorageio/monitoring-plan
Add graphviz and text to explain dashboard order
Loading