marceloavf / marceloavf/github-tools-vsts
Fix build log for CI
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 25
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Fix exceeding build log when runing on CI. (build.js)
```
2018-02-06T16:19:40.7275090Z [?25l - building githubReleasePublish process
2018-02-06T16:19:40.8327697Z [?25l[1000D[K[1A[1000D[K \ building githubReleasePublish process
2018-02-06T16:19:41.2363158Z [?25l[1000D[K[1A[1000D[K | building githubReleasePublish process
2018-02-06T16:19:42.2896616Z [?25l[1000D[K[1A[1000D[K / building githubReleasePublish process
2018-02-06T16:19:42.3717460Z [?25l[1000D[K[1A[1000D[K - building githubReleasePublish process
2018-02-06T16:19:42.4551553Z [?25l[1000D[K[1A[1000D[K \ building githubReleasePublish process
2018-02-06T16:19:42.5760848Z [?25l[1000D[K[1A[1000D[K | building githubReleasePublish process
2018-02-06T16:19:42.6848003Z [?25l[1000D[K[1A[1000D[K / building githubReleasePublish process
2018-02-06T16:19:42.7774394Z [?25l[1000D[K[1A[1000D[K - building githubReleasePublish process
2018-02-06T16:19:42.8659911Z [?25l[1000D[K[1A[1000D[K \ building githubReleasePublish process
2018-02-06T16:19:42.9648628Z [?25l[1000D[K[1A[1000D[K | building githubReleasePublish process
2018-02-06T16:19:43.0695843Z [?25l[1000D[K[1A[1000D[K / building githubReleasePublish process
2018-02-06T16:19:43.2207629Z [?25l[1000D[K[1A[1000D[K - building githubReleasePublish process
2018-02-06T16:19:43.3380712Z [?25l[1000D[K[1A[1000D[K \ building githubReleasePublish process
2018-02-06T16:19:43.4393661Z [?25l[1000D[K[1A[1000D[K | building githubReleasePublish process
2018-02-06T16:19:43.5447784Z [?25l[1000D[K[1A[1000D[K / building githubReleasePublish process
2018-02-06T16:19:43.6506653Z [?25l[1000D[K[1A[1000D[K - building githubReleasePublish process
2018-02-06T16:19:43.7661779Z [?25l[1000D[K[1A[1000D[K \ building githubReleasePublish process
2018-02-06T16:19:43.9148203Z [?25l[1000D[K[1A[1000D[K | building githubReleasePublish process
2018-02-06T16:19:44.0451574Z [?25l[1000D[K[1A[1000D[K / building githubReleasePublish process
2018-02-06T16:19:44.1536377Z [?25l[1000D[K[1A[1000D[K - building githubReleasePublish process
2018-02-06T16:19:57.7201864Z [?25l[1000D[K[1A[1000D[K \ building githubReleasePublish process
2018-02-06T16:19:57.8612351Z [?25l[1000D[K[1A[1000D[K | building githubReleasePublish process
2018-02-06T16:19:58.0091283Z [?25l[1000D[K[1A[1000D[K / building githubReleasePublish process
2018-02-06T16:19:58.0908484Z [?25l[1000D[K[1A[1000D[K - building githubReleasePublish process
2018-02-06T16:19:58.2395342Z [?25l[1000D[K[1A[1000D[K \ building githubReleasePublish process
2018-02-06T16:19:58.3203904Z [?25l[1000D[K[1A[1000D[K | building githubReleasePublish process
2018-02-06T16:19:58.4097680Z [?25l[1000D[K[1A[1000D[K √ building githubReleasePublish process
```
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 inspecting build.js and reproduce the CI build that emits the repeated progress lines shown in the issue. Trace how the build status is written to the log; the work is done when the CI log no longer contains a separate line for each progress update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100