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 "E4/Git"
(New page: == Git in e4 == We have a place in e4 for git repositories. === Current Repos === * git://git.eclipse.org/gitroot/e4/org.eclipse.e4.deeplink.git * git://git.eclipse.org/gitroot/e4/org.e...) |
(→Submitting for a build) |
||
| Line 21: | Line 21: | ||
We have 2 scripts used for submitting for the build. One to update the map files, and one to generate the submission report for our mailing list e4-dev@eclipse.org | We have 2 scripts used for submitting for the build. One to update the map files, and one to generate the submission report for our mailing list e4-dev@eclipse.org | ||
| − | [http://dev.eclipse.org/viewcvs/index.cgi/e4/releng/org.eclipse.e4.builder/scripts/git-map.sh?view=co git-map.sh] is used to update the map files. | + | [http://dev.eclipse.org/viewcvs/index.cgi/e4/releng/org.eclipse.e4.builder/scripts/git-map.sh?view=co&content-type=text/plain git-map.sh] is used to update the map files. |
| − | [http://dev.eclipse.org/viewcvs/index.cgi/e4/releng/org.eclipse.e4.builder/scripts/git-submission.sh?view=co git-submission.sh] is used to generate a build submission report. | + | [http://dev.eclipse.org/viewcvs/index.cgi/e4/releng/org.eclipse.e4.builder/scripts/git-submission.sh?view=co&content-type=text/plain git-submission.sh] is used to generate a build submission report. |
''Note:'' We have a policy that all commits have the associated bug number. Usually our format is: | ''Note:'' We have a policy that all commits have the associated bug number. Usually our format is: | ||
Revision as of 10:48, 22 October 2010
Git in e4
We have a place in e4 for git repositories.
Current Repos
- git://git.eclipse.org/gitroot/e4/org.eclipse.e4.deeplink.git
- git://git.eclipse.org/gitroot/e4/org.eclipse.e4.utils.git
- git://git.eclipse.org/gitroot/e4/org.eclipse.e4.installer.git
A repo then follows our standard subdir convention:
- bundles
- features
- examples
- tests
We build our git repos still using map files, checked into CVS in the /cvsroot/eclipse e4/releng module.
Submitting for a build
We have 2 scripts used for submitting for the build. One to update the map files, and one to generate the submission report for our mailing list e4-dev@eclipse.org
git-map.sh is used to update the map files.
git-submission.sh is used to generate a build submission report.
Note: We have a policy that all commits have the associated bug number. Usually our format is:
Bug <number> - <bug title>
and then any specific comments after. It's important that we only list 1 bug # per line. A line with "bug #" or "Bug "# without the title is also acceptable.
When ready to submit deeplinking for the build, you have to submit 2 repos, org.eclipse.e4.deeplink and org.eclipse.e4.utils. For each repo:
- cd into the repo (make sure it's up to date, you're on the master branch, etc)
- tag the repo: git tag v20101022-1030 # we use vDATE-TIME as our tag
- make sure you push the tag back to the public repo
- $ /bin/bash git-map.sh v20101022-1030 /opt/pwebster/workspaces/e4/releng/org.eclipse.e4.deeplink.releng/maps/deeplink.map bundles
- you'll have to execute the script for each subdiretory: bundles, examples, features, tests
Repeat the steps for the second repo.
Then when done you can generate your build submission report for the e4-dev list:
$ /bin/bash git-submission.sh >report.txt