e2e

Name: e2e
Author: Azure

E2E scenarios run concurrently across branches and share predefined AKS clusters with unrelated tests.

by Azure(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from Azure/AgentBaker (.github/instructions/e2e.instructions.md). Copyright stays with the author.

E2E shared-environment rules

E2E scenarios run concurrently across branches and share predefined AKS clusters with unrelated tests.

E2E clusters also share infrastructure.

Give each scenario-created Kubernetes object a unique name.
Target each workload only to the scenario node.
Do not modify or delete shared Kubernetes objects, other nodes, system pools, predefined clusters, or shared Azure infrastructure.
Do not make cluster-wide changes in a scenario.
Keep shared-infrastructure changes additive and idempotent.
For shared-infrastructure changes, use new resource names to avoid collisions with concurrent branches.
If a cluster configuration change can conflict across branches, change the configured cluster name to create a separate AKS cluster.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/azure-agentbaker-e2e-instructions/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

azure-agentbaker-e2e-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "azure-agentbaker-e2e-instructions",
  "kind": "skill",
  "name": "e2e",
  "description": "E2E scenarios run concurrently across branches and share predefined AKS clusters with unrelated tests.",
  "publisher": "Azure",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "E2E scenarios run concurrently across branches and share predefined AKS clusters with unrelated tests."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/Azure/AgentBaker",
      "path": ".github/instructions/e2e.instructions.md",
      "ref": "0126ec30b126be56c4b9d02992f57ae1cfdd6875",
      "url": "https://github.com/Azure/AgentBaker/blob/0126ec30b126be56c4b9d02992f57ae1cfdd6875/.github/instructions/e2e.instructions.md",
      "key": "Azure/AgentBaker/.github/instructions/e2e.instructions.md"
    },
    "applies_to": "e2e/**"
  },
  "instructions": "# E2E shared-environment rules\n\nE2E scenarios run concurrently across branches and share predefined AKS clusters with unrelated tests.\n\nE2E clusters also share infrastructure.\n\n- Give each scenario-created Kubernetes object a unique name.\n- Target each workload only to the scenario node.\n- Do not modify or delete shared Kubernetes objects, other nodes, system pools, predefined clusters, or shared Azure infrastructure.\n- Do not make cluster-wide changes in a scenario.\n- Keep shared-infrastructure changes additive and idempotent.\n- For shared-infrastructure changes, use new resource names to avo",
  "cost": {
    "context_tokens": 193
  }
}

Fetch it by URL: GET /api/v1/registry/azure-agentbaker-e2e-instructions/manifest?version=1.0.0

About

E2E shared-environment rules

Use it

Manifest

Reviews