Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CBI/p2repoAnalyzers/Repo Reports"
m (Made a little more current.) |
(Updated to have accurate repo, and other small edits) |
||
| Line 9: | Line 9: | ||
For now, the tests and scripts are in Git repo. To load into workspace, and appropriate URL would be similar to | For now, the tests and scripts are in Git repo. To load into workspace, and appropriate URL would be similar to | ||
| + | <code><nowiki>ssh://<userid>@git.eclipse.org:29418/cbi/org.eclipse.cbi.p2repo.analyzers</nowiki></code> | ||
| − | + | Or, for casual browsing, see {{Git|cbi|org.eclipse.cbi.p2repo.analyzers.git}}. | |
| − | or for | + | The reports can be [[CBI/p2repoAnalyzers/Repo_Reports_Running_Locally| ran locally]] or adopted for your own builds. |
| − | + | In fact, the ultimate goal is that the reports for the simultaneous release common repository are simply a final sanity check and that all projects can perform these tests themselves, early in development cycle. But ... until then, the reports will be ran against, at least, the common staging repositories. Most of the tests can be used, with some copy/paste/hacking directly from an IDEs workbench, against a local repository on your file system. Start small. :) | |
| − | + | If/when others have fixes, abstractions, or new tests, please open a bug in the cross-project component, so these tests and reports can be improved over time by community effort. | |
| − | + | The code and scripts, as of right now, are oriented towards simply "producing reports". But if you browse the code, you'll see some commented-out code in places that can cause "failed" flags to be set, which would be appropriate for some projects ... and, eventually, even the Simultaneous Release repository. Running the reports are, as of right now, are oriented towards being a simple "ant task". But more recently Dennis Huebner has contributed the framework to run as JUnit tests, but that still needs to be documented. (See {{bug|487409}}) and there is a bug open to convert to Maven tasks (see {{bug|487468}}). | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | The code and scripts, as of right now, are oriented towards simply "producing reports". But if you browse the code, | + | |
| − | you'll see some commented-out code in places that can cause "failed" flags to be set, which would be appropriate for some | + | |
| − | projects ... and, | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
[[Category:CBI| ]] [[Category:Oxygen| ]] [[Category:Neon| ]] [[Category:Mars| ]] [[Category:Luna| ]] | [[Category:CBI| ]] [[Category:Oxygen| ]] [[Category:Neon| ]] [[Category:Mars| ]] [[Category:Luna| ]] | ||
Revision as of 14:27, 16 October 2016
Common Software Repository Reports
This page roughly describes collection of automated checks and reports to run against p2 repositories or directories of jars. Eventually it will become more of a "how to" and FAQ oriented page.
The reports are ran against the latest successful CLEAN BUILD on Hudson, so can always be viewed there. There is even a link on the Hudson build instance main page that links to the latest report. The report is also copied, along with the repository, so it ends up on staging area too, so can be also be viewed under staging repo.
While many projects have their own, similar tests (which have one way or another provided the starting point for all these tests) it is worth some effort effort to collect some common tests in a common place to encourage reuse and improvements.
For now, the tests and scripts are in Git repo. To load into workspace, and appropriate URL would be similar to
ssh://<userid>@git.eclipse.org:29418/cbi/org.eclipse.cbi.p2repo.analyzers
Or, for casual browsing, see org.eclipse.cbi.p2repo.analyzers.git (browse, stats, fork on OrionHub) .
The reports can be ran locally or adopted for your own builds.
In fact, the ultimate goal is that the reports for the simultaneous release common repository are simply a final sanity check and that all projects can perform these tests themselves, early in development cycle. But ... until then, the reports will be ran against, at least, the common staging repositories. Most of the tests can be used, with some copy/paste/hacking directly from an IDEs workbench, against a local repository on your file system. Start small. :)
If/when others have fixes, abstractions, or new tests, please open a bug in the cross-project component, so these tests and reports can be improved over time by community effort.
The code and scripts, as of right now, are oriented towards simply "producing reports". But if you browse the code, you'll see some commented-out code in places that can cause "failed" flags to be set, which would be appropriate for some projects ... and, eventually, even the Simultaneous Release repository. Running the reports are, as of right now, are oriented towards being a simple "ant task". But more recently Dennis Huebner has contributed the framework to run as JUnit tests, but that still needs to be documented. (See bug 487409) and there is a bug open to convert to Maven tasks (see bug 487468).