|
|
@@ -40,8 +40,8 @@ with a random selection of packages. With the large commit activity on
|
|
|
Buildroot, these autobuilders are a great help in detecting problems
|
|
|
very early after commit.
|
|
|
|
|
|
-All build results are available at http://autobuild.buildroot.org[],
|
|
|
-statistics are at http://autobuild.buildroot.org/stats.php[]. Every day,
|
|
|
+All build results are available at https://autobuild.buildroot.org[],
|
|
|
+statistics are at https://autobuild.buildroot.org/stats.php[]. Every day,
|
|
|
an overview of all failed packages is sent to the mailing list.
|
|
|
|
|
|
Detecting problems is great, but obviously these problems have to be
|
|
|
@@ -58,7 +58,7 @@ basically two things that can be done:
|
|
|
these steps:
|
|
|
. Check if you can reproduce the problem by building with the same
|
|
|
configuration. You can do this manually, or use the
|
|
|
- http://git.buildroot.org/buildroot-test/tree/utils/br-reproduce-build[br-reproduce-build]
|
|
|
+ https://git.buildroot.org/buildroot-test/tree/utils/br-reproduce-build[br-reproduce-build]
|
|
|
script that will automatically clone a Buildroot git repository,
|
|
|
checkout the correct revision, download and set the right
|
|
|
configuration, and start the build.
|
|
|
@@ -73,7 +73,7 @@ basically two things that can be done:
|
|
|
In the commit message of a patch fixing an autobuild failure, add a
|
|
|
reference to the build result directory, as follows:
|
|
|
----
|
|
|
-Fixes: http://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069
|
|
|
+Fixes: https://autobuild.buildroot.org/results/51000a9d4656afe9e0ea6f07b9f8ed374c2e4069
|
|
|
----
|
|
|
|
|
|
=== Reviewing and testing patches
|