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

Introduce the concept of parent builds #15

Merged
merged 9 commits into from
Feb 6, 2015
Merged

Conversation

zackgalbreath
Copy link
Contributor

This changes the way that subprojects are handled.

Before this commit, the number of build errors, test failures, etc.
was accumulated across related subproject builds every time index.php
was rendered.

Now this math is only done once at the time of submission. This
simplifies the logic in index.php, allowing it to render more quickly
while using less memory. Going forward, it should also allow us to
introduce new subproject features, such as viewing all build errors
across packages for a particular build.

This changes the way that subprojects are handled.

Before this commit, the number of build errors, test failures, etc.
was accumulated across related subproject builds every time index.php
was rendered.

Now this math is only done once at the time of submission.  This
simplifies the logic in index.php, allowing it to render more quickly
while using less memory.  Going forward, it should also allow us to
introduce new subproject features, such as viewing all build errors
across packages for a particular build.
parentid is enough info to find the builds, date is unnecessary.
Instead of discarding a build from an unrecognized subproject,
we now add it to the project automatically.
If a parent build has no actual coverage of its own, CDash should
link to its children's coverage instead.
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.

1 participant