The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Nemo/Development
(→Setting up a webhook to github) |
|||
| Line 3: | Line 3: | ||
== Setting up a webhook to github == | == Setting up a webhook to github == | ||
| − | Open the git tree you have. Go to Settings->Service Hooks->WebHook URLs and enter https://webhook.merproject.org/webhook/ | + | Open the git tree you have. Go to '''Settings->Service Hooks->WebHook URLs''' and enter https://webhook.merproject.org/webhook/ to the URL field. Click "Update Settings" and "Test Hook". After clicking "Test Hook" the webhooks admin interface will show to the admins that you have active git tree. Contact Sage or w00t at #nemomobile IRC channel and they can help you to setup the rest of the process. When this is done everytime you tag on the selected branch the webhook will automatically launch the service and the new sources will be build. |
| − | + | ||
| − | After | + | |
== With tar_git service == | == With tar_git service == | ||
Revision as of 14:24, 5 April 2013
Contents |
Automated Packaging from git
Setting up a webhook to github
Open the git tree you have. Go to Settings->Service Hooks->WebHook URLs and enter https://webhook.merproject.org/webhook/ to the URL field. Click "Update Settings" and "Test Hook". After clicking "Test Hook" the webhooks admin interface will show to the admins that you have active git tree. Contact Sage or w00t at #nemomobile IRC channel and they can help you to setup the rest of the process. When this is done everytime you tag on the selected branch the webhook will automatically launch the service and the new sources will be build.
With tar_git service
With tar_git service packaging information is carried on the same branch in rpm/ subdirectory. This directory can contain any files which all are exported to packaging in OBS. If more than one .spec, .yaml or .changes is present the one that matches to the "Package" in webhooks will be taken. This allows one to create multiple packages with same source and different .spec file.
Changelogs are automatically generated from git commit messages, when ever git commit contains line that starts with "[sample text] Longer sample text." that is added automatically to the next changelog entry when version is tagged. If .changes file is located in the rpm/ subdirectory it is used as a base of the changelog generation and automated changelogs are appended to that.
TODO
FAQ
Q: I removed a tag remotely and pushed it again, but this didn't trigger the webhook at github? A: Retag locally and then push again.
With git_pkg service
TODO
Other stuff
This section is a bit of a guide about how to perform unified development on the software that we (in Nemo) write and maintain.
- Nemo/Development/Releasing - for releasing software we maintain
