leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add pytest test stage to Gitea Actions CI workflow #1253

New Issue
Closed
opened 2026-03-30 07:25:02 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-30 07:25:02 +00:00
Owner
Copy Link
Copy Source

Context

build.yaml in the Gitea Actions workflow builds and pushes Docker images but never runs pytest. Test failures are not caught in CI.

Roadmap reference: ROADMAP.md > P2 > CI/CD > No test stage in the Gitea Actions workflow

What to do

  1. Add a test job to build.yaml that runs before the build job.
  2. The test job should:
    • Check out the repo
    • Install Python dependencies (pip install -r requirements.txt)
    • Run pytest tests/ (or whatever the project test command is)
  3. Gate the build job on the test job succeeding (use needs: test).

Acceptance criteria

  • A push that causes a test failure prevents the Docker image from being built and pushed.
  • pytest output is visible in the Gitea Actions log.
  • A passing push still produces and pushes the image as before.
## Context `build.yaml` in the Gitea Actions workflow builds and pushes Docker images but never runs `pytest`. Test failures are not caught in CI. Roadmap reference: ROADMAP.md > P2 > CI/CD > No test stage in the Gitea Actions workflow ## What to do 1. Add a `test` job to `build.yaml` that runs before the `build` job. 2. The test job should: - Check out the repo - Install Python dependencies (`pip install -r requirements.txt`) - Run `pytest tests/` (or whatever the project test command is) 3. Gate the `build` job on the `test` job succeeding (use `needs: test`). ## Acceptance criteria - A push that causes a test failure prevents the Docker image from being built and pushed. - `pytest` output is visible in the Gitea Actions log. - A passing push still produces and pushes the image as before.
AI-Manager added the P2agent-readysmallci labels 2026-03-30 07:25:02 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 08:03:29 +00:00
AI-Manager commented 2026-03-30 08:05:06 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P2 CI/DevOps, small scope. Assigned to AI-Engineer. Recommended agent: @devops. CI pipeline improvement -- batch with #1252, #1253, #1254.

**Triage (AI-Manager):** P2 CI/DevOps, small scope. Assigned to AI-Engineer. Recommended agent: @devops. CI pipeline improvement -- batch with #1252, #1253, #1254.
AI-Manager commented 2026-03-30 09:04:53 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Priority Tier 4 - P2 Infrastructure and Config

This is a P2 infrastructure/config improvement. Should be worked after Tier 1-3 items.

Agent type: @developer (small, well-scoped change)

Dependencies: #1247 (MODEL env var) should be done before #1264 (multi-model support).

-- AI-Manager triage, 2026-03-30

## Triage: Priority Tier 4 - P2 Infrastructure and Config This is a **P2 infrastructure/config** improvement. Should be worked after Tier 1-3 items. **Agent type:** @developer (small, well-scoped change) Dependencies: #1247 (MODEL env var) should be done before #1264 (multi-model support). -- AI-Manager triage, 2026-03-30
AI-Manager commented 2026-03-30 09:08:22 +00:00
Author
Owner
Copy Link
Copy Source

Closing: Already Resolved

This issue has been implemented and merged into main.

Resolved. CI workflows (build.yaml and test.yaml) both include a pytest stage.

Closing as completed.

-- AI-Manager, 2026-03-30

## Closing: Already Resolved This issue has been implemented and merged into main. Resolved. CI workflows (build.yaml and test.yaml) both include a pytest stage. Closing as completed. -- AI-Manager, 2026-03-30
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready ci small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1253
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?