OpenSystemsDevelopment / qpdf

Commit 894d1c650c5d0266f64da665a3e41334d9977fab

Authored by Jay Berkenbilt
1 parent 92635d12

Minor notes on GitHub Actions migration

Inline Side-by-side
Showing 2 changed files with 12 additions and 4 deletions
ChangeLog
  View file @894d1c6
  1 +2020-10-16 Jay Berkenbilt <ejb@ql.org>
  2 +
  3 + * Build using GitHub Actions. The intention is that this will
  4 + replace Azure Pipelines as the official CI for qpdf for the next
  5 + release.
  6 +
1 7 2020-04-29 Jay Berkenbilt <ejb@ql.org>
2 8  
3 9 * Bug fix: qpdf --check was writing errors and warnings reported
... ...
... ... @@ -29,7 +29,8 @@ Candidates for upcoming release
29 29 * #446: recognize edited QDF files
30 30 * #436: parsing of document with form xobject
31 31  
32   -* Try migrating to github actions
  32 +* Complete migratiion to GitHub Actions. Do a case-insensitive search
  33 + for azure to find documentation references.
33 34  
34 35 * Remember to check work `qpdf` project for private issues
35 36 * file with very slow page extraction
... ... @@ -207,7 +208,8 @@ Page splitting/merging
207 208 MSVC Wildcard Expansion
208 209 =======================
209 210  
210   -(This section is referenced in azure_pipelines.yml.)
  211 +(This section is referenced in azure_pipelines.yml and
  212 +.github/workflows/main.yml.)
211 213  
212 214 The qpdf executable built with msvc is linked with setargv.obj or
213 215 wsetargv.obj so that wildcard expansion works. It doesn't work exactly
... ... @@ -223,8 +225,8 @@ qpdf executable in Windows should be retested manually.
223 225 Unfortunately, there is no automated test for wildcard expansion with
224 226 MSVC because I can't figure out how to prevent qtest from expanding
225 227 the wildcards before passing them in, and explicitly running "cmd /c
226   -..." from qtest doesn't seem to work in Azure Pipelines, though I can
227   -make it work locally.
  228 +..." from qtest doesn't seem to work in Azure Pipelines (haven't
  229 +attempted in GitHub Actions), though I can make it work locally.
228 230  
229 231 Ideally, we should figure out a way to test this in CI by having a
230 232 test that fails if wildcard expansion is broken. In the absence of
... ...