September 2020

Week 36 (August 31th - September 4th) #

We store the submission time of SRPM builds now (packit-service#795 by Anchit).
Shreyas improved implementation of the build status reporting (packit-service#740).
Anchit enhanced the /koji-builds endpoint to be more consistent with /copr-builds endpoint (packit-service#791).

Stage now uses Tokman to get access tokens for GitHub, which should resolve race condition when running parallel jobs (Tokman by Hunor, ogr integration by Matej).
Franta has addressed problems with Testing-Farm cluster with custom response on PRs that links to more information (pinned info, packit-service#798).

The combination of the source-git patches with existing patches now works well (packit#963).
Service now mostly supports also GitLab as you can see here or here. A lot of small issues were fixed in the last week (packit-service#806, packit-service#812, packit-service#814, packit-service#815, packit-service#816 ).
Created Copr projects are now prefixed with the hostname for non-GitHub services and also support multipart namespaces (packit-service#819).
Laura fixed two testing-farm related issues (packit-service#808, packit-service#809). You can now use test job also on Pagure and GitLab thanks to that.

Packit-service can be configured to work with private namespaces. This is plumbing work which we need right now for CentOS Stream. We are not planning to enable this for GitHub - packit-service will still work only for public repositories, private ones are ignored. packit-service#831
If git tag contains more information than just version (e.g. pkg_name-v1.2.3), it is possible to use upstream_tag_template to extract version from the tag, which will be used in a subsequent task. doc packit#959
Added support for globbing pattern in upstream_ref. doc packit#960
Packit --remote is global option now and available for all commands. Because of this sync-from-downstream --remote was renamed to --remote-to-push. Remote can now be specified in the user’s config (via upstream_git_remote parameter). packit#977

Following bugs were fixed:

Packit-service is now explicitly checking if requested copr-build targets exist and if not, the user is informed about it. packit-service#835
We have improved the way how packit updates %setup line in a spec file - you are now able to set content of -n option via archive_root_dir_template config option, it defaults to {upstream-pkg-name}. doc packit#834
Packit is able to generate a patch file with format-patch without leading a/ and b/ in the patch diff. Required for patches in dist-git which are applied with -p0.
Contribution guidelines were updated, now we have one shared link.