Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus PapyGame"
(Created page with "= PapyGame = PapyGame is a gamification extension for Papyrus, i.e. modeling becomes a game, See more information on the [https://www.papygame.com/home/ PapyGame home page]....") |
|||
| Line 2: | Line 2: | ||
PapyGame is a gamification extension for Papyrus, i.e. modeling becomes a game, See more information on the [https://www.papygame.com/home/ PapyGame home page]. | PapyGame is a gamification extension for Papyrus, i.e. modeling becomes a game, See more information on the [https://www.papygame.com/home/ PapyGame home page]. | ||
| − | |||
| − | = Development guidelines = | + | == Development guidelines == |
PapyGame follows the same guidelines as the development of Papyrus itself. These are available in eh Papyrus developer guide. A subsection clarifies how to code contribute the developed code. | PapyGame follows the same guidelines as the development of Papyrus itself. These are available in eh Papyrus developer guide. A subsection clarifies how to code contribute the developed code. | ||
| − | + | * [https://wiki.eclipse.org/Papyrus/Papyrus_Developer_Guide Papyrus Developer Guide] and | |
| − | + | * [https://wiki.eclipse.org/Papyrus/Papyrus_Developer_Guide/How_To-_Code_Contributing How-to contribute code] | |
| − | The source code can be found in the [https://git.eclipse.org/c/papyrus/org.eclipse.papyrus-papygame.git/ | + | === Git === |
| + | |||
| + | The source code can be found in the [https://git.eclipse.org/c/papyrus/org.eclipse.papyrus-papygame.git/ PapyGame git], the linked website offers several options to clone it. | ||
| + | |||
| + | === Build === | ||
The build of the PapyGame plugins (not the Gamification engine) is done by the Eclipse CI infrastructure, see [https://ci.eclipse.org/papyrus/view/PapyGame/ PapyGame CI view]. There a several jobs. | The build of the PapyGame plugins (not the Gamification engine) is done by the Eclipse CI infrastructure, see [https://ci.eclipse.org/papyrus/view/PapyGame/ PapyGame CI view]. There a several jobs. | ||
| − | + | * A nightly build job that schedules a new build each day | |
| − | + | * A gerrit build job that is scheduled when changes are pushed to git, See [https://wiki.eclipse.org/Gerrit], a general mechanism to manage proposed patches. | |
| − | + | * A specific job [https://ci.eclipse.org/papyrus/job/PapyGame-Gerrit-Test/ PapyGame-Gerrit-Test] that produces an update-site and an installable RCP (an archived Eclipse installation having all extensions). This build gets triggered, when a developer uses test specific topic “Test”, for instance via | |
git push origin HEAD:refs/for/master/Test | git push origin HEAD:refs/for/master/Test | ||
It may be possible to add additional build jobs with additional topics. | It may be possible to add additional build jobs with additional topics. | ||
A Papyrus committer can verify the quality of the commited patch and eventually merge it into the git repository. It is possible to refine patches with subsequent amentmends (git --amend) and eventually out update-site or RCP by using the "Test" gerrit job. | A Papyrus committer can verify the quality of the commited patch and eventually merge it into the git repository. It is possible to refine patches with subsequent amentmends (git --amend) and eventually out update-site or RCP by using the "Test" gerrit job. | ||
Revision as of 04:27, 16 February 2023
PapyGame
PapyGame is a gamification extension for Papyrus, i.e. modeling becomes a game, See more information on the PapyGame home page.
Development guidelines
PapyGame follows the same guidelines as the development of Papyrus itself. These are available in eh Papyrus developer guide. A subsection clarifies how to code contribute the developed code.
Git
The source code can be found in the PapyGame git, the linked website offers several options to clone it.
Build
The build of the PapyGame plugins (not the Gamification engine) is done by the Eclipse CI infrastructure, see PapyGame CI view. There a several jobs.
- A nightly build job that schedules a new build each day
- A gerrit build job that is scheduled when changes are pushed to git, See [1], a general mechanism to manage proposed patches.
- A specific job PapyGame-Gerrit-Test that produces an update-site and an installable RCP (an archived Eclipse installation having all extensions). This build gets triggered, when a developer uses test specific topic “Test”, for instance via
git push origin HEAD:refs/for/master/Test
It may be possible to add additional build jobs with additional topics.
A Papyrus committer can verify the quality of the commited patch and eventually merge it into the git repository. It is possible to refine patches with subsequent amentmends (git --amend) and eventually out update-site or RCP by using the "Test" gerrit job.