Closed
Bug 1147811
Opened 10 years ago
Closed 8 years ago
Use of Travis and coveralls bagdes to improve developers trust on the project
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: carocad, Unassigned)
Details
Attachments
(2 files)
|
819 bytes,
patch
|
Details | Diff | Splinter Review | |
|
943 bytes,
patch
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150306140254
Steps to reproduce:
- Go to https://github.com/mozilla/build-mozharness
- The readme states the possibility to test the changes in Travis and use Coveralls
- Test the project in both Travis and Coveralls
Actual results:
Both services provided useful information about the build status and code coverage after a push to the github repository, nevertheless the information that they provide is lost as my tests were done on a fork of the original code
Expected results:
The project could have indicators of the current build status and of its code coverage.
In my opinion this can improve third-party trust on the software which can lead to more contributions as people will like a more stable software that they can work with.
The result of this patch can be seen on: https://github.com/carocad/build-mozharness
Comment 3•8 years ago
|
||
Mozhareness has been moved to the gecko tree.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•