Use devspace as validator rather then omero-build?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 19
- Forks
- 18
- Avg merge
- 1d 53m
- Merged PRs (30d)
- 1
Description
Currently omero-build is the primary repository for checking the build status of downstream PRs, leading it to have a more complicated travis script, see https://github.com/ome/omero-build/blob/master/travis.sh
Adding in Bio-Formats to that script would further complicate matters. Perhaps this repository is a more natural location for that. However, to do so, it will be necessary to either spin up a devspace and check its status with a single script or run parts of this repository with less overhead.
- Auto-register for JDK without needing to enter
ci/ext/oraclecredentials - Generate snoopy token to not need to pass a
SOURCElocation
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading the linked omero-build/travis.sh script to understand how downstream PR build status is checked. Then review the two unchecked requirements about JDK registration and the snoopy token, and define which validation approach this repository should own before implementing it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100