Even though JFrog continued Bintray normal operation until 31 Mar 2021, I'm
disabling Github Actions uploads now. Termux Bintray repository continues to
be available in read-only mode until the final shutdown by JFrog.
Will turn off the bintray mirroring for grimler.se once I confirm (as
well as I can) that this works as intended. Will upload a wiki page
with some information about how this is set up on the server in case
someone wants to make a similar setup.
Also use v2 for upload- and download-artifact.
Begin phasing out dl.bintray.com/termux/termux-packages-24.
Before Bintray will go read-only (28 Feb), we need to ensure that
its repo has consistent state and no/minimal amount of issues as
large amount of users will continue to use it until Bintray finally
go down.
I still leaving autobuild/autodeploy (packages.yml) to Bintray repo
to process all remaining updates or pull requests with for short time.
For now script will just check package updates each 6 hours and print
them to console. Nothing will be built/pushed.
Functionality will be extended gradually.
Warning: Cache service responded with 429 during upload chunk.
/home/runner/work/_actions/actions/cache/v2/dist/save/index.js:3305
throw new Error(`Cache upload failed because file read failed with ${error.message}`);
^
Error: Cache upload failed because file read failed with EBADF: bad file descriptor, read
at ReadStream.<anonymous> (/home/runner/work/_actions/actions/cache/v2/dist/save/index.js:3305:31)
at ReadStream.emit (events.js:210:5)
at internal/fs/streams.js:167:12
at FSReqCallback.wrapper [as oncomplete] (fs.js:470:5)
Github Actions do not allow to overwrite already stored cache for
specific key. This caching approach is suitable for projects, where
dependencies are being tracked within lock files or their alternatives,
for exapmle NPM, Ruby or Python. Termux-packages is not such repository
where we can easily retrieve cache by using old key and generate a new
one after building was finished.
%ci:no-build causes packages not being built, however it doesn't prevent
artifacts from being uploaded/downloaded. Due to unavailable *.deb files,
upload job fails during download of the artifacts archive.
Placeholder file should make a valid artifact archive to be available so
job will not fail anymore.
