diff options
| author | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2022-11-26 05:47:53 +0300 |
|---|---|---|
| committer | Robin Haberkorn <robin.haberkorn@googlemail.com> | 2022-11-27 19:25:09 +0300 |
| commit | 9c789e80407cdfe3f5f7d2feb8e77bdeb130b78a (patch) | |
| tree | 278423fe5965e727895ccd1d5bd38239088e4386 /README | |
| parent | 85599c7e929237c61fb4b7857935475a6e57c8ec (diff) | |
| download | sciteco-9c789e80407cdfe3f5f7d2feb8e77bdeb130b78a.tar.gz | |
Nightly Builds are uploaded as a Github release now instead of artefacts
* replace actions/upload-artifact with pyTooling/Actions/releaser
* The release URL will never change:
https://github.com/rhaberkorn/sciteco/releases/tag/nightly
* On the downside there is now a "nightly" tag in the repo that will
be updated to HEAD whenever a nightly build runs - but other than that it does no harm.
* Compared with artifacts, the new method has several advantages:
* No more nightly.link Github App required
* We can add arbitrary files into releases and no longer have to ZIP everything.
So you can now download the Debian packages separately, the Mac OS "package" is a tar.gz
(instead of zipped tar).
For the Windows packages not much changes, though.
* Files get updated in the "Nightly Builds" release even when individual jobs in the
nightly.yml workflow fail.
With artefacts, the entire workflow must be successful.
* Releases are not deleted after 90 days as opposed to artefacts.
So when my workflow breaks next time, there will still be files to download
for a long time.
* As a downside, the file names in the release have to be uniform and must not contain
versions, commit hashes and dates so that uploads replace old files instead of adding
new ones.
Some manual cleanup could still be necessary after large packaging changes.
This could be worked around, by uploading everything first as artefacts and updating the
release in a separate job, but is not worth the trouble IMHO.
* Another disadvantage is that there will be no old nightly builds to download
(although these were not easily downloadable for end users before).
Diffstat (limited to 'README')
| -rw-r--r-- | README | 9 |
1 files changed, 5 insertions, 4 deletions
@@ -1,4 +1,5 @@ -[](https://github.com/rhaberkorn/sciteco/actions/workflows/ci.yml) [](https://github.com/rhaberkorn/sciteco/actions/workflows/nightly.yml) +[](https://github.com/rhaberkorn/sciteco/actions/workflows/ci.yml) +[](https://github.com/rhaberkorn/sciteco/releases/tag/nightly) Overview ======== @@ -115,11 +116,11 @@ There are prebuilt binary packages and source bundles for your convenience: * The official [SciTECO homepage](http://sciteco.sf.net/) is a live demo. These releases may be quite outdated, so you may also try out the -[nightly builds](https://nightly.link/rhaberkorn/sciteco/workflows/nightly/master) - -they represent the repository's HEAD commit but may well be instable. +[nightly builds](https://github.com/rhaberkorn/sciteco/releases/tag/nightly) - +they represent the repository's HEAD commit but may well be unstable. Both ncurses and Gtk+ packages are provided both for Ubuntu and Windows. For [Mac OS X](https://github.com/rhaberkorn/sciteco/wiki/Mac-OS-Support), -we currently only provide ncurses builds. +we currently only provide *experimental* ncurses builds. If everything fails, you can try building from source. See [`INSTALL`](INSTALL) for more details. |