Skip to content
This repository has been archived by the owner on Sep 20, 2021. It is now read-only.

Provide telemetry reports #62

Open
5 tasks done
vonglasow opened this issue May 9, 2016 · 13 comments
Open
5 tasks done

Provide telemetry reports #62

vonglasow opened this issue May 9, 2016 · 13 comments

Comments

@vonglasow
Copy link
Member

vonglasow commented May 9, 2016

Add telemetry reports https://github.com/atoum/telemetry

  • Use reports extension -> Wait for telemetry standalone extension
  • Run reports extension to provide records
  • Define the best way for the project name. => We will use Hoa\Central
  • Use telemetry extension instead of reports extension
  • Wait for publishing telemetry-extension in packagist
@vonglasow
Copy link
Member Author

Hello,

Telemetry need a project name and it's now configured into the .atoum.php file or used the name in composer.json file but on the project where the report is set. So when we run any test the only project name used is the one defined into the config file which is test. And we need a way to give this name into the telemetry report.

Second point, this reporting use internet connection to send this report and we should run tests without internet connexion. So this report should be enabled or disabled.

  1. How can we set the project name for telemetry?
  2. How can we add an option to allowed or not this report?

@Hywan Hywan self-assigned this May 17, 2016
@Hywan
Copy link
Member

Hywan commented May 17, 2016

About the project name, we can simply use Hoa or hoa/central. However, hoa/test is fine to me. This is the library that we test. Is it necessary to have the exact name of the library? What is the gain?

About the Internet connection, I assume this is the role of the atoum extension to avoid errors if the report cannot be sent.

However, I see another problem. The report extension is excellent but it loads too much libraries. This is why it does not land yet in hoa/test. Do you think it would be hard to develop our own reporter or just use the telemetry part, extract from the report extension?

@Hywan
Copy link
Member

Hywan commented May 17, 2016

cc @jubianchi

@jubianchi
Copy link
Member

we could split the reports-ext and make the telemetry part standalone

@Hywan
Copy link
Member

Hywan commented May 19, 2016

@jubianchi Can we help?

@jubianchi
Copy link
Member

I'll make it available as a standalone ext before the PHPTour. Thanks for asking ;)

@vonglasow vonglasow changed the title Provide telemetry reports WIP: Provide telemetry reports May 23, 2016
@vonglasow
Copy link
Member Author

@jubianchi Hello, have you any update regarding the standalone ext ? Do you need help ?

@vonglasow
Copy link
Member Author

ping @jubianchi Hello, do you need some help to separate telemetry reporting extension ?

@Hywan
Copy link
Member

Hywan commented Sep 28, 2017

@vonglasow @jubianchi ping?

@vonglasow
Copy link
Member Author

@Hywan we need to see with @jubianchi to publish the extension, one workaround will be to fork it and publish it on our "namespace".

What do you think ?

@Hywan
Copy link
Member

Hywan commented Sep 29, 2017

I pinged @jubianchi yesterday, let's see if it happens :-).

@vonglasow
Copy link
Member Author

Telemetry extension published

@vonglasow vonglasow changed the title WIP: Provide telemetry reports Provide telemetry reports Oct 2, 2017
@jubianchi
Copy link
Member

jubianchi commented Oct 2, 2017

@vonglasow I just released the 1.0.0 ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

3 participants