[Feature]: Implement an HTCondor CI Workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- docker, github-actions, python
- Domain
- ci-cd, infrastructure
Research direction
Start by inspecting the scaffold under stacks/htcondor/ and its stacks.yml entry, then review the healthcheck and shared-volume credential conventions. Implement the HTCondor workflow and verify that the relevant daemons start, a condor job is submitted and tracked, and its output files are evaluated; the bespoke workflow should be removed.
Written by the indexing model from the issue text.
Description
User Story
As a contributor for the HTCondor module,
I want to trigger the HTCondor CI pipelines,
So that my changes are properly tested and no regressions are injected into this package.
Feature Description
As part of the separation of the python modules that interact with different grid gateways/compute elements, it is important to have automated tests that can validate changes made to the HTCondor python module, ensuring that changes are functional and that no regressions are added.
Given that we still don't have in this repository a python module to interact with HTCondor, I would suggest to provide the following deliverables in this ticket:
- a GitHub workflow that runs an HTCondor docker container, with the relevant daemons (master, collector, negotiator, schedd and startd)
- submit a condor job to this HTCondor container, using condor binary commands.
- track the job submitted
- verify the output files of the job to ensure that it went well
Definition of Done
- The HTCondor CI pipeline is triggered
- Job submission works
- Evaluation of results/files is performed
- Harmonized onto the scaffold:
stacks/htcondor/layout,stacks.ymlentry, healthcheck,
creds in the shared volume, bespoke workflow removed
Alternatives Considered
No response
Related Issues
No response
Additional Context
No response
- Dominant language
- Python
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DIRACGrid/intercede
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in DIRACGrid/intercede
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1780 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·