Hithomelabs/ci-runner-test
11
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[ISSUE-67] CI Runner Test Repo & Validation Workflow #1

Closed
Dave wants to merge 0 commits from ISSUE-67 into test
pull from: ISSUE-67
merge into: Hithomelabs:test
Conversation 0 Commits - Files Changed -
Dave commented 2026-07-04 18:18:44 +00:00
Member
Copy Link

Summary

Create the CI Runner Test repository with a minimal Gradle/Java project and validation workflow.

What's Included

  • Minimal Gradle/Java project: build.gradle, settings.gradle.kts, App.java, AppTest.java, committed Gradle wrapper (gradlew, gradlew.bat, gradle/wrapper/)
  • Validation workflow: .gitea/workflows/test-ci-runner.yml with workflow_dispatch trigger
    • Uses container: 192.168.0.100:8928/hithomelabs/ci-runner:latest
    • Includes actions/setup-java@v4 for JDK 17 (Temurin) — required because image is JRE-only
    • Verifies tools: Java, Docker, Git, Node.js
    • Runs ./gradlew build
    • Tests Docker CLI with host socket mount
  • README.md: Documents purpose and how to trigger
  • .gitignore: Standard Gradle ignores

Notes

  • Repo created as Dave/ci-runner-test (not Hithomelabs/ci-runner-test) due to token scope limitations — needs transfer to org
  • workflow_dispatch-only trigger — never triggers on push
  • Prerequisite: Verify /var/run/docker.sock is bind-mounted on the runner before triggering

Issues

## Summary Create the CI Runner Test repository with a minimal Gradle/Java project and validation workflow. ## What's Included - **Minimal Gradle/Java project**: `build.gradle`, `settings.gradle.kts`, `App.java`, `AppTest.java`, committed Gradle wrapper (`gradlew`, `gradlew.bat`, `gradle/wrapper/`) - **Validation workflow**: `.gitea/workflows/test-ci-runner.yml` with `workflow_dispatch` trigger - Uses `container: 192.168.0.100:8928/hithomelabs/ci-runner:latest` - Includes `actions/setup-java@v4` for JDK 17 (Temurin) — required because image is JRE-only - Verifies tools: Java, Docker, Git, Node.js - Runs `./gradlew build` - Tests Docker CLI with host socket mount - **README.md**: Documents purpose and how to trigger - **.gitignore**: Standard Gradle ignores ## Notes - Repo created as `Dave/ci-runner-test` (not `Hithomelabs/ci-runner-test`) due to token scope limitations — needs transfer to org - `workflow_dispatch`-only trigger — never triggers on push - **Prerequisite**: Verify `/var/run/docker.sock` is bind-mounted on the runner before triggering ## Issues - Hithomelabs/HomeLabDocker#67
Dave closed this pull request 2026-07-04 18:18:54 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
architect:complete

Architect phase completed

  
complexity:high

High complexity

  
complexity:low

Low complexity

  
complexity:medium

Medium complexity

  
cross-repo

Cross-repository item

  
cross-repo-dev

Cross-repository development

  
dev:in-progress

Development in progress

  
effort:l

Large effort (2-4 weeks)

  
effort:m

Medium effort (1-2 weeks)

  
effort:s

Small effort (2-5 days)

  
effort:xl

Extra large effort (4+ weeks)

  
effort:xs

Extra small effort (1-2 days)

  
epic
analytics
Data analytics of platform data and logs analysis.

  
epic
development
Developing new features, services. front and and back end as well as batch jobs

  
epic
devops
Epic related to CI/CD pipeline, runners, setup and workflow triggers

  
epic
infra
Epic related to infrastructure tasks, configuring hard drives, network equipment, firewalls, anything involving getting hands dirty.

  
epic
observability
Observability stack, uptime, service discovery, network, firewall, processes, resource consumption etc.

  
epic
platform
Related to authentication, authorization, keys, passwords, configs. Updates and upgrades related to platform.

  
epic
product
Issues discussing products and features come over here.

  
lead:complete

Lead/Code review phase completed

  
needs-decision

Requires user decision/selection

  
pipeline-complete

Pipeline completed successfully

  
pipeline-error

Pipeline failed with error

  
pipeline-running

Pipeline is currently running

  
priority
later
To be done but can wait. Generally areas that don't want immediate attention and warrant pre-planning, analysis and/or design

  
priority
next
Not a burning issue but needs to be worked on next. Generally should not be blocked by any issue other than priority::now

  
priority
now
Immediate priority, critical for PROD go-live

  
start-pipeline

Trigger the SDLC pipeline to start

  
status
acceptance
Testing results are good and issue looks good to deploy. It is a pre-deployment sign-off of test results

  
status
blocked
Need to solve another issue before this issue can be picked. The issue is blocked till the blocking issue isn't resolved

  
status
done
Issue deployment successful.

  
status
in progress
Issue has been picked up and someone is working on it.

  
status
in review
The issue has been work on but, a review has been requested, generally good to transition to this if all PRs raised require review or are reviewed.

  
status
in testing
Code review complete and issue is in testing in lower environment. P.S. This means unit tests have already been written.

  
status
ready
Issue does not have any blocker and is ready to be picked.

  
status
refine
Something working already well in PROD but a change that makes life a little more easier, like skip into in netflix. Issues that signify added convenience.

  
status
triage
Issue is requested but not scoped. Need to be added to systematically review and categorize

  
subtask

Subtask issue

  
type
analysis
An issue to perform analysis, exploring deign and implementation decisions/ considerations.

  
type
bug
A bug, needs to be fixed, raised out of an incident.

  
type
hygiene
Features remain the same, makes the platform, faster, better and less-error prone. Makes developer/ system-admin life easier

  
type
mantainence
Primarily version upgrades

  
type
story
Something new, a new feature !

  
user-story

PM-created user story

No Label
architect:complete
complexity:high
complexity:low
complexity:medium
cross-repo
cross-repo-dev
dev:in-progress
effort:l
effort:m
effort:s
effort:xl
effort:xs
epic
analytics
epic
development
epic
devops
epic
infra
epic
observability
epic
platform
epic
product
lead:complete
needs-decision
pipeline-complete
pipeline-error
pipeline-running
priority
later
priority
next
priority
now
start-pipeline
status
acceptance
status
blocked
status
done
status
in progress
status
in review
status
in testing
status
ready
status
refine
status
triage
subtask
type
analysis
type
bug
type
hygiene
type
mantainence
type
story
user-story
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Hithomelabs/ci-runner-test#1
No description provided.
Delete Branch "ISSUE-67"

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?