smokeTestRelease.py should confirm the git revision is "recognized" [LUCENE-7022]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Spinoff from #8078, but this issue aims to catch release bits built on unpushed changes in the smoke tester, by having it verify that the revision the bits were built from (stored in the JAR's META-INF) is in fact pushed to the public Apache git repository (git-wip-us.apache.org/repos/asf/lucene-solr.git).
This seems very important, since a git newbie like myself could easily mess something up and somehow push a release containing local (not pushed) commits that I then lose when deleting my local clone.
---
Migrated from [LUCENE-7022](https://issues.apache.org/jira/browse/LUCENE-7022) by Michael McCandless (@mikemccand)
Contributor guide
Research direction
Start by locating smokeTestRelease.py and the code that reads the revision from the JAR's META-INF. Trace how the smoke tester accesses the public Apache Git repository, then define completion as rejecting release bits whose recorded revision is not present there, while accepting recognized revisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, java, python
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100