Migrate Build to Jenkins
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
This project is still running a mostly manual build process and the parts that run in CI are still on CircleCI.
To be inline with the rest of the organization we need to migrate the tests + build process to Jenkins.
What ever parts can be automated as a part of the release should also be automated.
1. Update build to Jenkins
2. Include our [semantic-release](https://github.com/logdna/semantic-release-config-logdna) setup
3. automate npm publish
4. attach package artifacts to github release
5. Look into auto publishing to chocolatey. Homebrew is just pointed at our release artifacts. Debian would be a bit more involved
TODO:
- [ ] Get Chocolatey credentials added to Jenkins (cc @smusali)
- [ ] Look into automating a [PR for homebrew](https://github.com/Homebrew/homebrew-cask/commit/9fd03d674e278bac473a7d59f559ca7d130ffcbe)
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.
Research direction
Start by reviewing the existing CircleCI configuration and current release process. Map the Jenkins migration to the listed requirements: semantic-release, npm publishing, GitHub release artifacts, and Chocolatey/Homebrew automation. Done means the build and tests run in Jenkins and the agreed release steps are automated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100