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

Getting build feedback from CI is too slow -> let's make it faster #6412

Closed
2 of 4 tasks
mattab opened this issue Oct 10, 2014 · 2 comments
Closed
2 of 4 tasks

Getting build feedback from CI is too slow -> let's make it faster #6412

mattab opened this issue Oct 10, 2014 · 2 comments
Labels
answered For when a question was asked and we referred to forum or answered it. c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Oct 10, 2014

The goal of this issue is to discuss the best ways to ensure that when a developer pushes code to Piwik our CI service will run the builds and provide feedback very quickly, ideally under 20 minutes after pushing

Current challenges

Ideas

Please contribute ideas and suggestions so we can make CI feedback as fast as it should ie. within 10-20min!

@mattab mattab added this to the Short term milestone Oct 10, 2014
@mattab mattab added Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. labels Oct 10, 2014
@sgiehl
Copy link
Member

sgiehl commented Oct 10, 2014

Just a small note: I've already added fast_finish: true to travis.yml some time ago, so travis will mark a build as failure / error as soon as the first job failed/errored. But waiting for a success is a bit long, indeed.

@mattab
Copy link
Member Author

mattab commented Dec 1, 2014

The situation is better in terms of builds times, although the problem is still here. We can also now use the TestRunner plugin to run tests on EC2 which is useful for core devs. I'm moving to Mid term but QA speed will always be on our minds.

@mattab mattab modified the milestones: Mid term, Short term Dec 1, 2014
@mattab mattab removed the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label Dec 1, 2014
@mattab mattab closed this as completed Jan 5, 2015
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Jan 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it. c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants