This request supersedes:
request 1189838
(Show diff)
Overview
Request 1190292 accepted
new package woodpecker: server, agent and CLI for the Woodpecker CI system
- Created by ojkastl_buildservice
- In state accepted
-
Package maintainer:
ojkastl_buildservice
- Supersedes 1189838
Loading...
Request History
ojkastl_buildservice created request
new package woodpecker: server, agent and CLI for the Woodpecker CI system
pluskalm accepted request
Also includes the system-user-woodpecker subpackages (required by both server and agent) as pointed out by @pluskalm in SR#1189837
Only caveat: The subpackage for the system users has the same version as the main package.
You could set Version per sub-package
I tried that, but it messed up later uses of %{version}. I thought this should be possible, but found nothing in the docs on short glance...
I have seen some case where it was done - I vaguely recall that there was some extra trick to make it work - lets see if I can find it
Actually one example is texlive - where different subpackages have diffferent versions
Ouch, that is a big one.
From what I understood there are only two places where %{version} is actually used. My guess is that those are not used due to the if or the subpackage version that was defined last is used there.
I cannot get the woodpecker package to use the actual woddpecker version 2.7.0 for the go ldflags, if the subpackage for the system user has a
Version:defined.define some helper variable with real version (i.e real_version), then use it for go ldflags instead of Version
also having increasing versions of subpackage which contains user is not a problem I would spent much time solving - I would actually not consider it problem at all
There is a vagrant-libvirt setup to play around with WoodpeckerCI. It is using the packages from my branch-project for devel:tools:scm, i.e. the package being submitted in this SR. https://github.com/johanneskastl/woodpecker_vagrant_libvirt_ansible