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

Travis system extraction part 1 #8379

Merged
merged 18 commits into from Jul 19, 2015
Merged

Travis system extraction part 1 #8379

merged 18 commits into from Jul 19, 2015

Conversation

diosmosis
Copy link
Member

Part 1 of #8373

Moves the travis scripts and files and the .travis.yml generator to a new repository so it is decoupled from Piwik. This way, changes in Piwik won't cause the travis files or generator to fail, and for older Piwiks the travis scripts can be patched to make the build work by creating version branches.

The way the system works now is as follows:

  • .travis.yml is generated using the code ./tests/travis/generator which does not depend on Piwik. This generated file must always work with supported Piwik versions, no matter which version generated it.
  • During travis execution, the autoupdate check for .travis.yml will be done before any other operation using the latest travis-scripts code. This means the latest version of .travis.yml will be used, which should work since we require it to work w/ all supported Piwik versions.
  • In plugin builds when checking out the Piwik branch to test against, we will afterwards force the master branch in travis-scripts to be used. If there is a branch in travis-scripts that matches the version of Piwik the build is testing against, however, that branch is used.
  • After this the build proceeds as normal.

diosmosis and others added 15 commits July 18, 2015 15:41
…itory. Decoupled from Piwik core so changes in Piwik won't affect how this runs. Original command forwards to new app to maintain BC and ease of use.
…vis, use the travis-scripts entry point so the generator will be completely decoupled from Piwik.
…exist (RecursiveDirectoryIterator throws if not).
@diosmosis diosmosis added the Pull Request WIP Indicates the current pull request is still work in progress and not ready yet for a review. label Jul 19, 2015
@diosmosis diosmosis self-assigned this Jul 19, 2015
@diosmosis diosmosis added this to the 2.14.2 milestone Jul 19, 2015
diosmosis added 3 commits July 18, 2015 18:29
…s possible the repo was cloned if the it doesn't exist in Piwik master.
…t branch so the travis-scripts repo is always pointing to the latest.
@diosmosis diosmosis added c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. and removed Pull Request WIP Indicates the current pull request is still work in progress and not ready yet for a review. labels Jul 19, 2015
diosmosis added a commit that referenced this pull request Jul 19, 2015
Travis system extraction part 1, moves the travis scripts and files and the .travis.yml generator to a new repository so it is decoupled from Piwik.
@diosmosis diosmosis merged commit 5dfa30b into master Jul 19, 2015
@diosmosis diosmosis deleted the travis_system_extraction branch July 19, 2015 04:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. c: Tests & QA For issues related to automated tests or making it easier to QA & test issues.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant