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

Created unified system for running tests in travis for Piwik Core and any Piwik plugin. #5962

Merged
merged 6 commits into from Aug 11, 2014

Conversation

diosmosis
Copy link
Member

System includes a console command (generate:travis-yml) that generates a .travis.yml file for a plugin or core. The travis file will check in travis if it needs to be updated, and if so it will fail the build and tell the user. If a specific command line option is specified supplying a github user token, the .travis.yml file will be updated within travis automatically.

Notes:

  • comments and non-travis sections will be preserved
  • includes logic for plugins to test themselves against latest stable version instead of just on master
  • the system is primarily controlled by environment variables. developers can change/add variables in .travis.yml and the auto-updating will preserve the changes.

This build is for a build w/ an out of date .travis.yml: https://travis-ci.org/piwik/piwik/builds/32146361
This build is the build that occurred right after the auto-update commit: https://travis-ci.org/piwik/piwik/builds/32146459

I will use the command on plugins after merged w/ core.

diosmosis and others added 2 commits August 10, 2014 15:52
… any Piwik plugin. System includes a console command (generate:travis-yml) that generates a .travis.yml file for a plugin or core. The travis file will check in travis if it needs to be updated, and if so it will fail the build and tell the user. If a specific command line option is specified supplying a github user token, the .travis.yml file will be updated within travis automatically.

Notes:

  - comments and non-travis sections will be preserved
  - includes logic for plugins to test themselves against latest stable version instead of just on master
  - the system is primarily controlled by environment variables. developers can change/add variables in .travis.yml and the auto-updating will preserve the changes.
@diosmosis
Copy link
Member Author

@mattab Please review.

@@ -54,4 +54,25 @@ count=$(($count + 1))

echo -e "\n${RED}Timeout (${timeout} minutes) reached. Terminating \"$@\"${RESET}\n"
kill -9 $cmd_pid
}

travis_retry() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mattab
Copy link
Member

mattab commented Aug 10, 2014

So much automation it makes me cry with joy ;-) Looks good!

mattab pushed a commit that referenced this pull request Aug 11, 2014
Created unified system for running tests in travis for Piwik Core and any Piwik plugin.
@mattab mattab merged commit f69187c into master Aug 11, 2014
@diosmosis diosmosis deleted the travis_system branch August 11, 2014 08:30
diosmosis pushed a commit that referenced this pull request Aug 12, 2014
diosmosis pushed a commit that referenced this pull request Aug 12, 2014
diosmosis pushed a commit that referenced this pull request Aug 12, 2014
…d since this is done by special GenerateTravisYml command.
diosmosis pushed a commit that referenced this pull request Aug 12, 2014
…l (directory must be the plugin dir for plugin tests).
diosmosis pushed a commit that referenced this pull request Aug 12, 2014
diosmosis pushed a commit that referenced this pull request Aug 12, 2014
diosmosis pushed a commit that referenced this pull request Aug 13, 2014
…lugins using DEPENDENT_PLUGINS travis environment variable (set in .travis.yml file manually).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants