| commit | 6f17e0d53260208085347fa2493b66ac486b6362 | [log] [tgz] |
|---|---|---|
| author | Jan-Philipp Steghöfer <ec@splashstudio.com> | Mon Apr 29 11:47:49 2019 +0200 |
| committer | Jan-Philipp Steghöfer <ec@splashstudio.com> | Mon Apr 29 19:38:29 2019 +0200 |
| tree | bb5fa2f385060ad9d0da3933c6e266cc7e3cb0b9 | |
| parent | a50903c1a4eddbf8428c1a2a2b0b1f03c217d4da [diff] |
[WIP] Updates to streamline release process
Capra is a configurable and extendable traceability management tool. It is created in the context of an ITEA funded project called AMALTHEA4Public whose main aim is to develop a platform that will improve the development of embedded multicore and many core systems.
Capra uses the Eclipse Modelling Framework (EMF) as its base technology and stores the traceability model as an EMF model. The traceability metamodel is not fixed and can be defined by the user. It relies on the Eclipse Extension mechanism and provides an extension point for artifacts types to be supported. To add a new type of artifact, one simply needs to add an extension to this extension point and implement the provided interfaces.
Before downloading and using Capra, download Eclipse Modelling Environment and make sure you have the listed dependencies installed.
If compilation errors occur during the first build, check if any of the dependencies above are missing. Cleaning all binaries also often helps resolve issues.
In order to use the Eclipse development infrastructure and to contribute to Capra (and other Eclipse projects), it is necessary to create an Eclipse account. With this account, you will be able to log in to the different services (such as Bugzilla, the Eclipse Wiki, or Hudson) and push code changes to Gerrit.
After you have created the account, you need to sign the Eclipse Committer Agreement (ECA). Depending on whether you work on your own time or for a company, different conditions apply. Please familiarise yourself with the legal issues, ask your employer for help if required, and then sign the ECA here.
Instead of using the Git repository listed above, use the Gerrit repository. You can copy the SSH or HTTPS links from the Capra Gerrit page. This will allow you to push your changes to Gerrit where the project committers can review them before adding them to the codebase.
develop branch. All development should be based on this branch, following the GitFlow approach. Your local changes should go into your own branch. We suggest to use the format <username>/feature/<feature-name>. Instead of feature, other identifiers such as fix can be used.We keep track of the features for Capra in our Bugzilla. If you plan to contribute your own features, please open a bug in the correct component there. The bug summary should contain the “[feature]” keyword so we know that this is not indeed a bug report. Please provide a short summary and a description of what you are doing. Use the comments of the bug to describe your progress. Other members of the community might engage you for discussions, so please take their opinions into account and react to their suggestions and feedback.
Capra uses Maven/Tycho. To check if your changes work, run maven in the root folder:
mvn clean verify
This will create binaries for Capra and run all tests. Code should only be committed if all tests passed!
To run Capra from within Eclipse, see the instructions above.
Please make sure that all points in the following checklist are fullfilled before committing your work to a Capra repository:
Organisation of imports and code formatting can be automated by selecting them as save actions for the Java editor in the Eclipse preferences.
It is important to maintain the correct copyright messages, indicating the contributors of each file and that it is covered by the EPL. You can use automation to insert a correct copyright header.
Install the Eclipse Releng Tools. They contain the copyright tool. Use the following copyright header:
Copyright (c) ${date} Chalmers | University of Gothenburg, rt-labs and others.
All rights reserved. This program and the accompanying materials
are made available under the terms of the Eclipse Public License v1.0
which accompanies this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html
Contributors:
Chalmers | University of Gothenburg and rt-labs - initial API and implementation and/or initial documentation
The Contributors entry can be replaced with the appropriate names. Use “Fix copyrights” from the context menu to add the copyrights to all relevant files in a project or folder.
If all pre-requisites listed above are fulfilled, the code can be pushed to Gerrit. Please note that Gerrit combines several commits into one change that will show up using the commit message of the last commit. Make sure that this commit message actually describes the changes you are pushing. Optionally, you can squash all commits into one before pushing to Gerrit.
These are the steps to push a change to Gerrit:
mvn clean verifygit push ssh://<username>@git.eclipse.org:29418/capra/org.eclipse.capra.git HEAD:refs/for/develop Please note that it is important to use the HEAD:refs/for/develop addition which indicates that the push is to Gerrit (refs/for/) and which branch the changes should be merged to (develop).The Sign-off needs to be in the footer of the commit message, i.e., separated from the commit message by a new line and in the same block.
Once your change has been pushed to Gerrit, one of the committers in the project will review the change and Hudson will try to build your code. You will be notified about the progress by email, using the email address you used in the Signed-off-by message. If your change is accepted, it will be merged into one of the branches in the main Git repository. If there are comments or Hudson fails to build the code, you need to make the necessary changes, amend your commit, and push again.
git commit --amendChange-Id and sign-off both need to be in the footer.
More information about contributing code via Gerrit and how to use the Eclipse Git repositories can be found here: