|
|
| (20 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | ==Common Software Repository Reports== | + | = This page has been moved to https://github.com/eclipse-cbi/p2repo-analyzers/blob/main/README.md = |
| | | | |
| − | 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.
| + | [[Category:CBI| ]] |
| − | | + | |
| − | 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 [https://hudson.eclipse.org/simrel/ main page] that links to the [https://hudson.eclipse.org/simrel/job/simrel.mars.runaggregator.CLEAN_BUILD/lastSuccessfulBuild/artifact/aggregation/final/buildInfo/reporeports/index.html 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 [http://download.eclipse.org/staging/neon/buildInfo/reporeports/ 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
| + | |
| − | | + | |
| − | <code><nowiki>ssh://<userid>@git.eclipse.org/gitroot/simrel/org.eclipse.simrel.tests.git</nowiki></code>
| + | |
| − | | + | |
| − | or for Gerrit access:
| + | |
| − | | + | |
| − | <code><nowiki>ssh://<userid>@git.eclipse.org:29418/simrel/org.eclipse.simrel.tests</nowiki></code>
| + | |
| − | | + | |
| − | Or, for casual browsing, see {{Git|simrel|org.eclipse.simrel.tests.git}}.
| + | |
| − | | + | |
| − | The reports can be [[SimRel/Simultaneous_Release_Reports_Running_Locally| ran locally]] or adopted for your own builds.
| + | |
| − | | + | |
| − | Put another way, 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 but 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, long term, maybe even the common repository. Similarly, most, now, are oriented towards being a simple "ant task".
| + | |
| − | It might be possible, with moderate effort, to convert most to "unit tests" for more finely tuned testing and error reporting,
| + | |
| − | if there was ever an advantage to that.
| + | |
| − | | + | |
| − | Plus, more recently, Dennis Huebner has contributed the framework to run as JUnit tests, but that still needs to be documented. (See {{bug|487409}})
| + | |
| − | | + | |
| − | | + | |
| − | [[Category:CBI| ]] [[Category:Oxygen| ]] [[Category:Neon| ]] [[Category:Mars| ]] [[Category:Luna| ]] | + | |
