ansible-collections/git-events
2
0
Fork 0
Code Issues 1 Pull Requests Actions Projects Releases Wiki Activity

Create #1

New Issue
Open
opened 2025-06-29 06:06:53 +00:00 by jon · 2 comments
jon commented 2025-06-29 06:06:53 +00:00
Owner
Copy Link

Develop an ansible rulebook that is container based so that it can be deployed globally for a Gitea instance to process Runner logs for Problem matchers.

📚 Details

Goal is to create a container base solution that is scalable and deployed for a Gitea instance. This solution will process CI jobs on receiving a webhook event.

Basic workflow for Problem matchers

  1. CI job runs
  2. System Webhook posts PR related CI jobs to rulebook
  3. Checks repo config
  4. Processes job log
  5. Optional Post PR review comments
  6. Optional Post results as comment Does Gitea have sticky comments like gitea

💡Unknowns / Outstanding Questions

  • How could the repo owner provide their config

🚧Tasks

▶️ Requirements

  • Only Accepts Authenticated connections
  • Uses a system level user as a bot account for posting and commenting
  • Needs to be configurable by repo owner
Develop an ansible rulebook that is container based so that it can be deployed globally for a Gitea instance to process Runner logs for Problem matchers. ## 📚 Details Goal is to create a container base solution that is scalable and deployed for a Gitea instance. This solution will process CI jobs on receiving a webhook event. ### Basic workflow for Problem matchers 1. CI job runs 2. System Webhook posts PR related CI jobs to rulebook 3. Checks repo config 4. Processes job log 5. _Optional_ Post PR review comments 6. _Optional_ Post results as comment _Does Gitea have sticky comments like gitea_ ### 💡Unknowns / Outstanding Questions - [ ] How could the repo owner provide their config ## 🚧Tasks - [ ] clusters/.profile#12 - [ ] migrate Created [Kustomize Manifests](https://github.com/nofusscomputing/kubernetes) - [x] Create [Rulebook](https://ansible.readthedocs.io/projects/rulebook/en/latest/rulebooks.html) - [ ] Write up playbook/runbook on usages. _(Deployment, secrets etc)_ ## ▶️ Requirements - [x] Only Accepts Authenticated connections - [ ] Uses a system level user as a bot account for posting and commenting - [ ] Needs to be configurable by repo owner
jon added the
Type
Epic
Priority
Low
4
Urgency
Medium
3
 labels 2025-06-29 06:06:53 +00:00
jon self-assigned this 2025-06-29 06:06:53 +00:00
jon added spent time 2 minutes 2025-06-29 06:08:28 +00:00
jon added a new dependency 2025-06-29 06:09:08 +00:00
actions/gitea-github-parser#1 - Create
jon added spent time 3 hours 2025-06-29 09:02:17 +00:00
jon added spent time 6 hours 40 minutes 2025-06-29 15:51:47 +00:00
jon referenced this issue from a commit 2025-06-29 22:56:38 +00:00
feat(rulebook): initial webhook
jon referenced this issue from a commit 2025-06-29 22:56:38 +00:00
feat(docker): initial
jon referenced this issue from a commit 2025-06-29 22:56:38 +00:00
docs: add readme
jon deleted spent time 2025-06-29 23:01:05 +00:00
- 6 hours 40 minutes
jon referenced this issue from a commit 2025-06-30 18:42:57 +00:00
chore: update galaxy meta files
jon referenced this issue from a commit 2025-06-30 18:42:57 +00:00
feat(docker): add alpine build
jon referenced this issue from a commit 2025-07-01 11:23:49 +00:00
chore(parser): code cleanup
jon added spent time 30 minutes 2025-07-01 15:03:12 +00:00
jon commented 2025-07-01 15:08:33 +00:00
Author
Owner
Copy Link

Setup push syncing to github repo of same name.

Setup push syncing to github repo of same name.
jon added a new dependency 2025-07-02 01:19:32 +00:00
fussfreehome/perseus#11 - Add CI/CD YAML linting to PERSEUS repo
jon commented 2025-07-07 14:45:14 +00:00
Author
Owner
Copy Link

3629b2ff21 fixed a bug

3629b2ff21a0573a046393cff5ca192cccf905d7 fixed a bug
jon added spent time 1 hour 30 minutes 2025-07-07 14:45:38 +00:00
jason removed a dependency 2025-07-17 23:53:58 +00:00
fussfreehome/perseus#11 - Add CI/CD YAML linting to PERSEUS repo
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Area/CI-CD
Documentation changes
Area/Documentation
Documentation changes
Area/Security
This is security issue
Area/Testing
Issue or pull request related to testing
Bug
Failure to Confirm
Bug exists due to not confirming/testing code
Bug
Regression
THe bug is a regression of a feature
Bug
To be Confirmed
This bug is not confirmed
Bug
Unable to Reproduce
A developer can not re-create/re-produce the bug
Compat/Breaking
Breaking change that won't be backward compatible
Impact
Critical
1
The impact is critical in that it is blocking or prevents usage.
Impact
High
2
The impact requires that changes be made for continuted usage.
Impact
Low
4
The impact requires the user approach from a different angle for continued usage.
Impact
Medium
3
The impact requires a workaround for continued usage.
Impact
Very Low
5
The impact has a slight effect on usage.
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Priority
Very High
1
The priority is critical
Priority
Very Low
5
The priority is very low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Type
Bug
Something is not working
Type
Epic
Epic User Story
Type
Feature
Feature / Module
Type
Incident
Something occured related to a service
Type
RFE
Request for Enhancement
Type
Task
A work item that must be done
Urgency
Low
4
Prioritize this amoungst your list of things to do.
Urgency
Major
1
Urgency is so high it should have been dealt with last week.
Urgency
Medium
3
Start as soon as possible.
Urgency
Very High
2
Urgency is high enough to warrant near immediate commencement.
Urgency
Very Low
5
Add this to your list of things to do.
No Label
Priority
Low
4
Type
Epic
Urgency
Medium
3
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason jon
No Assignees jon
1 Participants
Notifications
Total Time Spent: 5 hours 2 minutes
jon
5 hours 2 minutes
Due Date
No due date set.
Blocks
#1 Create
actions/gitea-github-parser
Depends on
You do not have permission to read 1 dependency
Reference: ansible-collections/git-events#1
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?