Unfortunately TTM itself doesn't quite fit here due to the reasons outlined
in the code and the additional checks are not a good fit for adding it into
the go pipeline description, so write yet another OBS publishing bot!
For the initial test runs this is not triggered by timer runs yet.
We want to start transitioning to a git based development workflow. For the
first iteration, we would allow maintainers to opt-in by changing their package
in the devel project to use scmsync from src.opensuse.org/pool/${pkg_name} and
submit changes via pull requests on gitea. These pull requests will get
submitted directly by the scm-staging-bot to Factory from its home project as
submit requests.
Currently, such a submission would get auto-declined from the factory-auto
bot. With this commit, factory-auto will no longer decline such a submission
provided that the above conditions have been met.
Co-authored-by: Dirk Mueller <dmueller@suse.com>
Splitting an empty string with ' ' results in list(""), which the code does
not handle properly. Instead use just split() which returns an empty list()
insted.
Now we have some packages in the distro which fail installcheck
semi-intentionally: libstdc++6-gccX (with X < system GCC) conflicts with rpm
indirectly. While this can be ignored in stagings already, this caused an issue
once it's in the distro: The installcheck failure contains the release number
and so it gets rebuilt all the time in the hope to make it installable again.
This script is used eg. for the /snapshot-changes/opensuse/Tumbleweed
route and was using the WSGIScriptAlias apache command.
With the switch to nginx we need this more modern approach.
Do not run it in packages that do not ship systemd services and properly
call it with the service name as parameter for the packages that do ship services.
Do not run it in packages that do not ship systemd services and properly
call it with the service name as parameter for the packages that do ship services.
