diff options
-rw-r--r-- | doc/handbook/chapters/developer.texi | 28 |
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi index 3d9493cec..cf13fd816 100644 --- a/doc/handbook/chapters/developer.texi +++ b/doc/handbook/chapters/developer.texi | |||
@@ -689,6 +689,7 @@ Here you can find some rules to help you write code for GNUnet. | |||
689 | @menu | 689 | @menu |
690 | * Naming conventions:: | 690 | * Naming conventions:: |
691 | * Coding style:: | 691 | * Coding style:: |
692 | * Continuous integration:: | ||
692 | * Commit messages and developer branches:: | 693 | * Commit messages and developer branches:: |
693 | @end menu | 694 | @end menu |
694 | 695 | ||
@@ -1094,6 +1095,33 @@ fun (short i, | |||
1094 | 1095 | ||
1095 | @end itemize | 1096 | @end itemize |
1096 | 1097 | ||
1098 | @cindex Continuous integration | ||
1099 | @node Continuous integration | ||
1100 | @subsection Continuous integration | ||
1101 | |||
1102 | The continuous integration buildbot can be found at @uref{https://buildbot.gnunet.org}. | ||
1103 | Repositories need to be enabled by a buildbot admin in order to participate | ||
1104 | in the builds. | ||
1105 | |||
1106 | The buildbot can be configured to process scripts in your repository root under @code{.buildbot/}: | ||
1107 | |||
1108 | The files @code{build.sh}, @code{install.sh} and @code{test.sh} are executed | ||
1109 | in order if present. If you want a specific worker to behave differently, | ||
1110 | you can provide a worker specific script, e.g. @code{myworker_build.sh}. | ||
1111 | In this case, the generic step will not be executed. | ||
1112 | |||
1113 | For the @code{gnunet.git} repository, you may use "!tarball" or "!coverity" in | ||
1114 | your commit messages. | ||
1115 | "!tarball" will trigger a @code{make dist} of the gnunet source and verify that it | ||
1116 | can be compiled. The artifact will then be published to @uref{https://buildbot.gnunet.org/artifacts}. | ||
1117 | This is a good way to create a tarball for a release as it verifies the build | ||
1118 | on another machine. | ||
1119 | |||
1120 | The "!coverity" trigger will trigger a coverity build and submit the results | ||
1121 | for analysis to coverity: @uref{https://scan.coverity.com/}. | ||
1122 | Only developers with accounts for the GNUnet project on coverity.com are able to | ||
1123 | see the analysis results. | ||
1124 | |||
1097 | @cindex Commit messages and developer branches | 1125 | @cindex Commit messages and developer branches |
1098 | @node Commit messages and developer branches | 1126 | @node Commit messages and developer branches |
1099 | @subsection Commit messages and developer branches | 1127 | @subsection Commit messages and developer branches |