Let plugins developers run their plugins tests continuously in Travis CI #4280

Closed
mattab opened this Issue Nov 7, 2013 · 5 comments

3 participants

@mattab
Piwik Open Source Analytics member

Follow up of #1673 Allow plugins to bundle unit/integration tests

Now that plugins can bundle their own tests, we could make it easy for plugin developers to run their tests on travis CI to ensure that their plugins will not break when they commit new changes to their github repository.

  • Add travis.yml template pre-generated in our tool ./console plugin:generate
@tsteur
Piwik Open Source Analytics member

In 71aac2f: refs #4280 created a travis.yml that allows plugin developers to run their tests on travis

@tsteur
Piwik Open Source Analytics member

We might need another console command in the future to update an existing .travis.yml file. Imagine plugin is generated and .travis.yml exists in plugin. The .travis.yml will never be updated again in case we make changes to the original .travis.yml file located in ExamplePlugin. We can think about this problem when needed.

@mattab
Piwik Open Source Analytics member

Excellent new feature!

@anonymous-piwik-user

Replying to tsteur:

We might need another console command in the future to update an existing .travis.yml file. Imagine plugin is generated and .travis.yml exists in plugin. The .travis.yml will never be updated again in case we make changes to the original .travis.yml file located in ExamplePlugin. We can think about this problem when needed.

How was this issue handled?

@tsteur
Piwik Open Source Analytics member

I will think about a solution once needed. Do you have any suggestions?

@mattab mattab added this to the 2.0.3 - Piwik 2.0.3 milestone Jul 8, 2014
@tsteur tsteur was assigned by mattab Jul 8, 2014
@sabl0r sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
@tsteur tsteur refs #4280 created a travis.yml that allows plugin developers to run …
…their tests on travis
71aac2f
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment