titan/soteria
3
0
Fork 0
Code Issues 87 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

[hermes] soteria #818: git_repository_not_found #42

New Issue
Open
opened 2026-09-24 07:30:56 +00:00 by hermes-automation · 0 comments
hermes-automation commented 2026-09-24 07:30:56 +00:00
Member
Copy Link

Hermes auto-triage classified incident soteria/818 as git_repository_not_found (confidence 0.95); first failed gate: initial SCM checkout (fetching the Jenkinsfile from origin) — the build never reached a named pipeline stage.

Why a human is needed

This build never got past checking out its own source: Jenkins' first git fetch against https://scm.bstein.dev/titan/soteria.git came back with an HTTP 404 and 'repository not found', and after a retry it failed the exact same way, so the build was marked FAILURE in under a tenth of a second with no stage, step, or test ever running. That points to the repository no longer existing at that exact path in Gitea (renamed, moved, or deleted) rather than anything wrong in soteria's code or tests. Confirming which of those it is, and either restoring the repository's location or updating the job's remote URL, needs someone with access to Gitea and the Jenkins job configuration, which is why this needs a human rather than being resolved from this evidence alone.

Ariadne did not authorize automated remediation: human_required.

Facts

  • jenkins — Build soteria #818 ended in FAILURE after 0.084 seconds, and no pipeline stage was ever recorded as reached (first_failed_stage is null). (jenkins.result, jenkins.duration_seconds, jenkins.first_failed_stage)
  • jenkins — The only recorded activity is Jenkins' initial git fetch used to read the Jenkinsfile from origin; that fetch exited with status 128 and stderr 'remote: 404 page not found' / "fatal: repository 'https://scm.bstein.dev/titan/soteria.git/' not found". (jenkins.console_failures[0] (line 19) and jenkins.console_tail)
  • jenkins — Jenkins retried the checkout and hit the identical fetch failure again before giving up ('Maximum checkout retry attempts reached, aborting') and marking the build FAILURE. (jenkins.console_tail)
  • jenkins — No structured test results were published for this build. (jenkins.failed_tests)
  • opensearch — OpenSearch could not be queried for correlated logs in this incident window; the request failed with 'Connection refused'. (log_evidence.error)

Evidence

The earliest failure region of the build console:

	at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310)
	at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277)
	at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136)
	at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:168)
	at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70)
	at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:317)
	at hudson.model.ResourceController.execute(ResourceController.java:101)
	at hudson.model.Executor.run(Executor.java:460)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://scm.bstein.dev/titan/soteria.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: remote: 404 page not found
fatal: repository 'https://scm.bstein.dev/titan/soteria.git/' not found

	at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchComma
... (truncated; the full log is in the linked build)

Inferences

  • The Gitea server is returning an HTTP 404 for the exact URL the job is configured to fetch (https://scm.bstein.dev/titan/soteria.git), not a network-level or server error. That normally means no repository currently exists at that path in Gitea — e.g. it was renamed, moved to a different namespac...
  • Because the failure happened while Jenkins was still trying to load the Jenkinsfile itself, none of soteria's own pipeline stages, build steps, or tests ever ran. There is nothing wrong in the application code or test suite for this build — the pipeline never reached the point of exercising either.
  • Fixing this means checking Gitea directly for whether titan/soteria still exists at that path (including recent rename/move history), then either restoring the repository at that location or repointing the job's SCM configuration at wherever it now lives. Simply re-running build #818 unchanged wi...

Links

  • Failed build: https://ci.bstein.dev/job/soteria/818/
  • Full evidence bundle and audit trail live in Ariadne at /api/admin/audit/events, event types hermes_autotriage_incident and hermes_autotriage_diagnosis.

Filed automatically by Ariadne from a Hermes Agent diagnosis (run run_3e704b14dbca4ce9850bfe5937708c59). Hermes has no write access to this repository; no files or infrastructure were changed.

Hermes auto-triage classified incident `soteria/818` as **git_repository_not_found** (confidence 0.95); first failed gate: `initial SCM checkout (fetching the Jenkinsfile from origin) — the build never reached a named pipeline stage`. ## Why a human is needed This build never got past checking out its own source: Jenkins' first git fetch against https://scm.bstein.dev/titan/soteria.git came back with an HTTP 404 and 'repository not found', and after a retry it failed the exact same way, so the build was marked FAILURE in under a tenth of a second with no stage, step, or test ever running. That points to the repository no longer existing at that exact path in Gitea (renamed, moved, or deleted) rather than anything wrong in soteria's code or tests. Confirming which of those it is, and either restoring the repository's location or updating the job's remote URL, needs someone with access to Gitea and the Jenkins job configuration, which is why this needs a human rather than being resolved from this evidence alone. Ariadne did not authorize automated remediation: `human_required`. ## Facts - **jenkins** — Build soteria #818 ended in FAILURE after 0.084 seconds, and no pipeline stage was ever recorded as reached (first_failed_stage is null). (`jenkins.result, jenkins.duration_seconds, jenkins.first_failed_stage`) - **jenkins** — The only recorded activity is Jenkins' initial git fetch used to read the Jenkinsfile from origin; that fetch exited with status 128 and stderr 'remote: 404 page not found' / "fatal: repository 'https://scm.bstein.dev/titan/soteria.git/' not found". (`jenkins.console_failures[0] (line 19) and jenkins.console_tail`) - **jenkins** — Jenkins retried the checkout and hit the identical fetch failure again before giving up ('Maximum checkout retry attempts reached, aborting') and marking the build FAILURE. (`jenkins.console_tail`) - **jenkins** — No structured test results were published for this build. (`jenkins.failed_tests`) - **opensearch** — OpenSearch could not be queried for correlated logs in this incident window; the request failed with 'Connection refused'. (`log_evidence.error`) ## Evidence The earliest failure region of the build console: ``` at PluginClassLoader for git//hudson.plugins.git.GitSCM._checkout(GitSCM.java:1310) at PluginClassLoader for git//hudson.plugins.git.GitSCM.checkout(GitSCM.java:1277) at PluginClassLoader for workflow-scm-step//org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:168) at PluginClassLoader for workflow-cps//org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:70) at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:317) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:460) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --force --progress -- https://scm.bstein.dev/titan/soteria.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: 404 page not found fatal: repository 'https://scm.bstein.dev/titan/soteria.git/' not found at PluginClassLoader for git-client//org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchComma ... (truncated; the full log is in the linked build) ``` ## Inferences - The Gitea server is returning an HTTP 404 for the exact URL the job is configured to fetch (https://scm.bstein.dev/titan/soteria.git), not a network-level or server error. That normally means no repository currently exists at that path in Gitea — e.g. it was renamed, moved to a different namespac... - Because the failure happened while Jenkins was still trying to load the Jenkinsfile itself, none of soteria's own pipeline stages, build steps, or tests ever ran. There is nothing wrong in the application code or test suite for this build — the pipeline never reached the point of exercising either. - Fixing this means checking Gitea directly for whether titan/soteria still exists at that path (including recent rename/move history), then either restoring the repository at that location or repointing the job's SCM configuration at wherever it now lives. Simply re-running build #818 unchanged wi... ## Links - Failed build: https://ci.bstein.dev/job/soteria/818/ - Full evidence bundle and audit trail live in Ariadne at `/api/admin/audit/events`, event types `hermes_autotriage_incident` and `hermes_autotriage_diagnosis`. Filed automatically by Ariadne from a Hermes Agent diagnosis (run [run_3e704b14dbca4ce9850bfe5937708c59](https://triage.bstein.dev/chat?resume=run_3e704b14dbca4ce9850bfe5937708c59)). Hermes has no write access to this repository; no files or infrastructure were changed. <!-- hermes-triage job=soteria classification=git_repository_not_found incident=soteria/818 -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
atlas-reconciler bstein hermes-automation
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: titan/soteria#42
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?