Resources
Configure resources, manage connections, and define dependencies. Keep your infrastructure organized and accessible to AI agents and team members.
Resources are external services connected to a JuhJuh project: code repositories, container registries, issue trackers, CI pipelines, and messaging channels. They supply the connections that power executions, deployments, and notifications. Each resource belongs to a project and is consumed by VMs and deployment pipelines.
Navigate to resources¶
- Open your organization
- Go to Projects in the sidebar
- Select a project
- Click the Resources tab
Resource types¶
| Type | What it connects |
|---|---|
| Code Repository | Git repositories (Bitbucket, GitHub, GitLab) |
| Container Registry | Container image registries for deployments |
| Jira / Linear / GitHub Issues / GitLab Issues | Issue trackers for ticket sync |
| Bitbucket Pipelines / GitHub Actions / GitLab CI | CI/CD pipelines |
| Slack / Discord / Teams / WhatsApp / Email | Messaging and notifications |
| Confluence / Notion | Documentation platforms |
| Kubernetes / Compute | Infrastructure targets |
| Webhook | Custom integrations |
Create a resource¶
- Navigate to your project's Resources tab
- Click New Resource
- Select the resource type
- Provide a name and configure the connection details (API tokens, URLs, credentials)
- Click Save
JuhJuh validates the connection immediately. A green status badge confirms the resource is live.
View resource details¶
Click any resource in the list to open its detail page. The detail view shows:
- Connection status and last verification time
- Configuration summary (sensitive values are masked)
- Tags and metadata
- Sync history (for issue trackers and repositories)
Test connections¶
- Click Test on any individual resource to verify its connection
- Click Test All to validate every resource in the project at once
Failed tests show the error reason in the status badge. Check your credentials or network access if a test fails.
Sync repository knowledge¶
For code repositories, JuhJuh can analyze the repository structure and extract knowledge that improves execution quality.
- Open a code repository resource
- Click Sync Knowledge
- JuhJuh scans the codebase for file structure, dependencies, patterns, and conventions
Knowledge sync status is tracked per resource and updates automatically.
Delete a resource¶
- Open the resource detail page
- Click Delete
- Confirm the deletion
Deleting a resource does not affect VMs or deployments already using it. Future deployments will need a replacement.
Key concepts¶
Primary resource. Each resource type can have one primary per project. The primary is used by default when JuhJuh needs that type. For example, the primary code repository is what agents clone for executions.
Tags. Auto-generated and user-defined labels (e.g., backend, frontend, payments) that help organize and filter resources across projects.
Configuration. Connection details stored securely. Sensitive values (tokens, passwords, API keys) are encrypted at rest and masked in the UI. You never see the raw value after saving.
Related¶
- Infrastructure Overview: how resources fit into the broader infrastructure model
- VMs: the compute instances that consume your resources
- Deployments: push container images using registry resources
- Projects: resources are scoped to a project
- Integrations: connect external platforms to your organization
- Slack: configure Slack as a messaging resource for notifications and commands