From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [COMMITTED] htdocs: add bse href, add robots.txt and testruns link
Date: Sun, 3 Jul 2022 01:07:05 +0200 [thread overview]
Message-ID: <20220702230704.115051-1-mark@klomp.org> (raw)
Add base href to make local hacking easier.
Add robots.txt to keep crawlers out.
Add bunsen testruns link and icon explanation.
---
htdocs/index.html.pre | 11 ++++++++++-
htdocs/robots.txt | 3 +++
2 files changed, 13 insertions(+), 1 deletion(-)
create mode 100644 htdocs/robots.txt
diff --git a/htdocs/index.html.pre b/htdocs/index.html.pre
index f0502b5..dcb377a 100644
--- a/htdocs/index.html.pre
+++ b/htdocs/index.html.pre
@@ -6,6 +6,7 @@
<meta name="description" content="Sourceware GNU Toolchain buildbot">
<meta name="keywords" content="sourceware gnu toolchain buildbot">
<link href="default.css" rel="stylesheet" type="text/css">
+ <base href="https://builder.sourceware.org/">
<title>GNU Toolchain sourceware buildbot</title>
</head>
<body>
@@ -21,7 +22,15 @@
<h2>buildbot</h2>
<p>
- The <a href="/buildbot/">buildbot</a> (<em>note:</em> uses javascript and websockets).
+ The <a rel="nofollow" href="/buildbot/">buildbot</a>
+ (<em>note:</em> uses javascript and websockets).
+ </p>
+ <p>
+ The <a rel="nofollow" href="/testruns/">
+ <img width="16" height="16" src="/testruns/favicon.ico"/>
+ bunsen testrun logs</a>
+ (click the <img width="16" height="16" src="/testruns/favicon.ico"/>
+ below for per project or builder logs).
</p>
<p>
The builder git config files:
diff --git a/htdocs/robots.txt b/htdocs/robots.txt
new file mode 100644
index 0000000..0c75670
--- /dev/null
+++ b/htdocs/robots.txt
@@ -0,0 +1,3 @@
+User-agent: *
+Disallow: /buildbot/
+Disallow: /testruns/
--
2.30.2
reply other threads:[~2022-07-02 23:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220702230704.115051-1-mark@klomp.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).