Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

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

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

mattab opened this issue Nov 7, 2013 · 5 comments
Assignees
Labels
Milestone

Comments

@mattab
Copy link
Member

@mattab mattab commented Nov 7, 2013

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

This comment has been minimized.

Copy link
Member

@tsteur tsteur commented Dec 17, 2013

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

@tsteur

This comment has been minimized.

Copy link
Member

@tsteur tsteur commented Dec 17, 2013

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

This comment has been minimized.

Copy link
Member Author

@mattab mattab commented Dec 19, 2013

Excellent new feature!

@anonymous-piwik-user

This comment has been minimized.

Copy link

@anonymous-piwik-user anonymous-piwik-user commented Dec 20, 2013

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

This comment has been minimized.

Copy link
Member

@tsteur tsteur commented Dec 20, 2013

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

@mattab mattab added T: Task labels Jul 8, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.