1
0

6 Commits

Author SHA1 Message Date
4fbc5ca781 ci: Publish to Gitea
Some checks reported errors
dustin/pythonctnr/pipeline/head Something is wrong with the build of this commit
registry.pyrocufflink.blue is going away.  All container images hosted
there are being moved to Gitea.
2022-12-21 11:12:47 -06:00
c748e19236 ci: Switch buildroot container image
Some checks failed
dustin/pythonctnr/pipeline/head There was a failure building this commit
registry.pyrocufflink.blue is going away and all container images hosted
there are moving to Gitea.
2022-12-21 10:07:57 -06:00
a67ed39366 ci: Schedule to run monthly
Some checks reported errors
dustin/pythonctnr/pipeline/head Something is wrong with the build of this commit
2022-10-31 12:10:08 -05:00
4f4fd0d6bf ci: Enable ccache for buildroot
I wanted to use a persistent volume for the workspace volume of this
Jenkins pipeline in order to speed up subsequent builds.  Unfortunately,
this feature does not really work well in Jenkins.  Since the agent is
removed when the build completes, and therefore the volume is not
mounted anywhere, Jenkins cannot delete workspaces for deleted jobs.
This means that when feature branches/pull requests are merged, their
workspaces remain on disk forever.

Using the *dynamicPVC* option deletes the entire volume when the job
finishes.  This avoids wasting space, but does not allow subsequent
builds to reuse the workspace.  As a compromise, we can use a persistent
volume for the compiler cache and share it between builds.  Using the
compiler cache is not as effective as keeping the whole build directory,
but it still saves some time.  Also, it works across branches, too.
2022-10-31 12:03:52 -05:00
5f0d0cade4 Begin Jenkins CI pipeline
All checks were successful
dustin/pythonctnr/pipeline/head This commit looks good
2022-08-07 12:12:31 -05:00
6ff519aecd Initial commit 2022-08-07 10:36:18 -05:00