<feed xmlns='http://www.w3.org/2005/Atom'>
<title>cgitext.git/tests, branch master</title>
<subtitle>cgitext – CGI for Git extension</subtitle>
<id>https://sayag.it/cgitext.git/atom/tests?h=master</id>
<link rel='self' href='https://sayag.it/cgitext.git/atom/tests?h=master'/>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/'/>
<updated>2026-08-15T15:17:12Z</updated>
<entry>
<title>diff: pick refs from web ui</title>
<updated>2026-08-15T15:17:12Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-08-15T15:17:12Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=61aa4378441859ed2851db01d5d1b01ed1aa2458'/>
<id>urn:sha1:61aa4378441859ed2851db01d5d1b01ed1aa2458</id>
<content type='text'>
Beforehand the choice between two refs in diff could not be changed from
web ui (only via url query), and by default it was current and previous
commit. Now it is doable with dropdown menus.
</content>
</entry>
<entry>
<title>tests: check that a misconfigured repo.path is reported</title>
<updated>2026-07-30T05:27:47Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-07-30T05:27:47Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=1614f25c38d5dd1817cf7651b2fc5e07503fc454'/>
<id>urn:sha1:1614f25c38d5dd1817cf7651b2fc5e07503fc454</id>
<content type='text'>
Check that a repo.path which does not exist or is not a repository is
reported, for the summary page, for an unknown page name and for the ci
page.

cgit used to hang on these requests rather than fail, so the helper puts a
deadline on each one: a regression should fail the test instead of wedging
the suite.

Signed-off-by: Saya Andy &lt;saya.andy@posteo.com&gt;
</content>
</entry>
<entry>
<title>ui-ci: let a ci-filter decide whether the tab is shown</title>
<updated>2026-07-30T05:27:31Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-07-30T05:27:31Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=7162aef3344a4f4f2d7edd2f214d805bd744c20c'/>
<id>urn:sha1:7162aef3344a4f4f2d7edd2f214d805bd744c20c</id>
<content type='text'>
cgit cannot know whether the ref being viewed actually has a pipeline, so
the "ci" tab is offered for every ref and only reveals a missing one once
followed. Probing the ci system from cgit is not an option: the tab is
part of the page header, so it would mean a blocking request for every
page of every repository, cgit links no http client, and job pages are
usually not readable anonymously.

Add a ci filter instead, which receives the ref, whether it is a branch or
a tag, and the expanded url, and answers with its exit status. This keeps
credentials, timeouts and caching in a script, where they belong;
filters/ci-jenkins.sh demonstrates all three against Jenkins' REST API.

The verdict is memoized, so the filter runs once per request rather than
once for the tab and again for the redirect, and it governs the page as
well as the tab, so a hidden tab cannot be reached by typing the url.

Signed-off-by: Saya Andy &lt;saya.andy@posteo.com&gt;
</content>
</entry>
<entry>
<title>ui-ci: add a "ci" tab which redirects to an external ci system</title>
<updated>2026-07-30T05:26:52Z</updated>
<author>
<name>Saya Andy</name>
<email>saya.andy@posteo.com</email>
</author>
<published>2026-07-30T05:26:52Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=b4b4f2325db71041f38902143b28bae94762b111'/>
<id>urn:sha1:b4b4f2325db71041f38902143b28bae94762b111</id>
<content type='text'>
Add a "ci" page which redirects to an external ci system for the ref
being viewed, along with a tab for it in the repository header.

The target is a url template, configurable globally or per repository,
with separate settings for branches and tags because pipelines for the
two commonly live at different locations: on a Jenkins multibranch
pipeline a branch is at job/&lt;name&gt;/job/&lt;ref&gt; while a tag is at
job/&lt;name&gt;/view/tags/job/&lt;ref&gt;. $ref, $repo and $slug are substituted,
$slug being the repository url with any ".git" suffix removed and slashes
replaced by dashes, which is the shape job names usually take.

An explicit repo.ci-url drops the branch and tag urls the repository
would otherwise inherit from the global settings, as it could never take
effect otherwise.

The expansion is written to the Location header verbatim rather than
through cgit_redirect(), which percent-encodes '?', '=' and '%' and would
corrupt any url carrying a query string. An expansion containing CR or LF
is refused so that it cannot smuggle in further headers.

Signed-off-by: Saya Andy &lt;saya.andy@posteo.com&gt;
</content>
</entry>
<entry>
<title>tests: t0107: support older and/or non-GNU tar</title>
<updated>2020-12-29T20:06:17Z</updated>
<author>
<name>Todd Zullinger</name>
<email>tmz@pobox.com</email>
</author>
<published>2020-12-29T19:18:01Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=bd6f5683f6cde4212364354b3139c1d521f40f39'/>
<id>urn:sha1:bd6f5683f6cde4212364354b3139c1d521f40f39</id>
<content type='text'>
The untar tests for various compression algorithms use shortcut options
from GNU tar to handle decompression.  These options may not be provided
by non-GNU tar nor even by slightly older GNU tar versions which ship on
many systems.

An example of the latter case is the --zstd option.  This was added in
GNU tar-1.32 (2019-02-23)¹.  This version of tar is not provided by
CentOS/RHEL, in particular.  In Debian, --zstd has been backported to
the tar-1.30 release.

Avoid the requirement on any specific implementations or versions of tar
by piping decompressed output to tar.  This is compatible with older GNU
tar releases as well as tar implementations from other vendors.  (It may
also be a slight benefit that this more closely matches what the
snapshot creation code does.)

¹ Technically, the --zstd option was first released in tar-1.31
  (2019-01-02), but this release was very short-lived and is no longer
  listed on the GNU Tar release page.

Signed-off-by: Todd Zullinger &lt;tmz@pobox.com&gt;
Signed-off-by: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;
</content>
</entry>
<entry>
<title>tests: try with commit-graph</title>
<updated>2020-10-21T22:04:10Z</updated>
<author>
<name>Christian Hesse</name>
<email>mail@eworm.de</email>
</author>
<published>2020-10-21T20:16:57Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=adcc4f822fe11836e5f942fc1ae0f00db4eb8d5f'/>
<id>urn:sha1:adcc4f822fe11836e5f942fc1ae0f00db4eb8d5f</id>
<content type='text'>
Git 2.24.0 enabled commit-graph by default and caused crashes without
necessary update. Let's test to work with commit-graph.

Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
<entry>
<title>tests: do not copy snapshots to /tmp/</title>
<updated>2020-10-21T22:03:01Z</updated>
<author>
<name>Christian Hesse</name>
<email>mail@eworm.de</email>
</author>
<published>2020-10-21T19:31:52Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=a1039ab17591cc531c877bc693088fd2e45c97ff'/>
<id>urn:sha1:a1039ab17591cc531c877bc693088fd2e45c97ff</id>
<content type='text'>
No idea why this was added... Possibly to inspect the snapshot manually?
Let's drop it.

Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
<entry>
<title>global: replace hard coded hash length</title>
<updated>2020-10-20T21:57:12Z</updated>
<author>
<name>Christian Hesse</name>
<email>mail@eworm.de</email>
</author>
<published>2020-10-20T21:46:09Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=a4de0e810b69710c3b32f6d253d80d16dec09f36'/>
<id>urn:sha1:a4de0e810b69710c3b32f6d253d80d16dec09f36</id>
<content type='text'>
With sha1 we had a guaranteed length of 40 hex chars. This changes now
that we have to support sha256 with 64 hex chars... Support both.

Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
<entry>
<title>global: replace references to 'sha1' with 'oid'</title>
<updated>2020-10-20T21:57:12Z</updated>
<author>
<name>Christian Hesse</name>
<email>mail@eworm.de</email>
</author>
<published>2020-10-20T21:32:45Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=779631c6dc23c15bbbf45a7c7ab9fffb619037b7'/>
<id>urn:sha1:779631c6dc23c15bbbf45a7c7ab9fffb619037b7</id>
<content type='text'>
For some time now sha1 is considered broken and upstream is working to
replace it with sha256. Replace all references to 'sha1' with 'oid',
just as upstream does.

Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
<entry>
<title>git: update to v2.29.0</title>
<updated>2020-10-19T18:27:28Z</updated>
<author>
<name>Christian Hesse</name>
<email>mail@eworm.de</email>
</author>
<published>2020-10-06T14:32:08Z</published>
<link rel='alternate' type='text/html' href='https://sayag.it/cgitext.git/commit/?id=629659d2cffbf059374fc53e6400ff0bebe1ddde'/>
<id>urn:sha1:629659d2cffbf059374fc53e6400ff0bebe1ddde</id>
<content type='text'>
Update to git version v2.29.0, this requires changes for these
upstream commits:

* dbbcd44fb47347a3fdbee88ea21805b7f4ac0b98
  strvec: rename files from argv-array to strvec

* 873cd28a8b17ff21908c78c7929a7615f8c94992
  argv-array: rename to strvec

* d70a9eb611a9d242c1d26847d223b8677609305b
  strvec: rename struct fields

* 6a67c759489e1025665adf78326e9e0d0981bab5
  test-lib-functions: restrict test_must_fail usage

Signed-off-by: Christian Hesse &lt;mail@eworm.de&gt;
</content>
</entry>
</feed>
