Skip to content

flagon-io/g1t

public

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

Deploy

A push says where its time went: receiving it, the rules, the secret scan and the git store's answer each have their own Server-Timing step#120

How this runs on g1t · 27 notes
  • check: `actions/checkout` checks out from g1t.
  • plan: `actions/checkout` checks out from g1t.
  • plan: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
  • migrate: `actions/checkout` checks out from g1t.
  • migrate: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
  • core: `actions/checkout` checks out from g1t.
  • core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • core: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • core: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
  • edge: `actions/checkout` checks out from g1t.
  • edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • edge: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • edge: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
  • front: `actions/checkout` checks out from g1t.
  • front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • front: `actions/cache`: g1t keeps the cache per repository: up to 2 GiB an entry and 10 GiB a repository, until it goes 7 days unused, and at most 28 days.
  • front: `environment`: the job gets the values its secrets and variables give this environment once the environment's protection rules (required reviewers, a wait timer, which branches may deploy) let it through. Unless it says `deployment: false`, the run records a deployment to it.
  • smoke: `actions/checkout` checks out from g1t.

Triggered via push

syntaqxb46bfb0main

Status

Succeeded

Total duration

4m 29s

Artifacts

—

deploy.yml· on: push
Plansummary

Deploy plan for b46bfb0

unitstageactionlivewhy
eventscorea991613nothing it is built from changed
identitycorea991613nothing it is built from changed
reposcoredeploya9916132 changed files (services/repos/src/git_http.rs)
workcorea991613nothing it is built from changed
searchcorea991613nothing it is built from changed
projectscorebee5a81nothing it is built from changed
chatcorea991613nothing it is built from changed
docs-servicecorea991613nothing it is built from changed
notifycorea991613nothing it is built from changed
agentscorea991613nothing it is built from changed
billingcorea991613nothing it is built from changed
integrationscorea991613nothing it is built from changed
webhookscorea991613nothing it is built from changed
actionscorea991613nothing it is built from changed
packagescorea991613nothing it is built from changed
securitycorea991613nothing it is built from changed
deploymentscorea991613nothing it is built from changed
runnercorea991613nothing it is built from changed
contextcorea991613nothing it is built from changed
ogcorea991613nothing it is built from changed
apiedgea991613nothing it is built from changed
modelscorea991613nothing it is built from changed
pagesedge4bc4681nothing it is built from changed
statusedgea991613nothing it is built from changed
webfrontbee5a81nothing it is built from changed
sudofronta991613nothing it is built from changed
docsfrontdeploya9916131 changed file (apps/docs/src/content/docs/guides/git.md)
core (rust)summary

sccache

Compile requests                     35
Compile requests executed            28
Cache hits                            6
Cache hits (Rust)                     6
Cache misses                         22
Cache misses (Rust)                  22
Cache hits rate                   21.43 %
Cache hits rate (Rust)            21.43 %
Cache timeouts                        0
Cache read errors                     0
Forced recaches                       0
Cache write errors                    0
Cache errors                          0
Compilations                         22
Compilation failures                  0
Non-cacheable compilations            0
Non-cacheable calls                   7
Non-compilation calls                 0
Unsupported compiler calls            0
Average cache write               1.251 s
Average compiler                  0.230 s
Average cache read hit            0.437 s
Failed distributed compilations       0

Non-cacheable reasons:
missing input                         3
-                                     2
crate-type                            2

Cache location                  ghac, name: sccache-v0.18.0, prefix: /sccache/
Base directories                (none)
Version (client)                0.18.0