mozilla-releng / mozilla-releng/scriptworker-scripts
\*scripts should log their version on start.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 38
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 14
Description
and/or revision.
We don't currently bump versions, and we may not have the git repo around to find the revision. Any solution here likely needs to work for both the docker-based scripts, and the mac-based scripts.
We may want to have a convention of creating a flatfile in a known location, with the scriptworker version and script revision, after creating the dockerfile and/or puppetizing the mac. Then it's a matter of reading this motd (message of the task, mott?) at the beginning if that file exists, possibly in a simple scriptworker_client function.
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 reviewing how the docker-based and mac-based scripts are created, then trace the proposed scriptworker_client entry point and the version or revision information available after Dockerfile or Puppet setup. Done means both script types log their version and/or revision on startup, including when the Git repository is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100