9 posts tagged with "October"

Week 44 (October 29th – November 4th)​

• Packit now supports and defaults to fast_forward_merge_into syntax via --dist-git-branches-mapping in dist-git init. (packit#2456)

Week 43 (October 22nd – October 28th)​

• We have added support for retriggering jobs that are configured for commit and release trigger. Retriggering can be done via commit comments on the relevant commit, using the usual comments, such as /packit build or /packit test, but the branch or tag need to be specified like this (without the arguments, we will default to commit trigger for the default branch of the repository):

  /packit build --commit <branch-name>
  

  or

  /packit build --release <tag-name>
  

  (packit-service#2589)

• There is a new method for getting a single commit comment, supporting also retrieval and adding reactions in GitHub. (ogr#865)

• We have improved the feedback for the Open Scan Hub job. You can now see if the scan is in a pending, running, canceled, failed, or successful state. A failed or canceled scan is shown as neutral and does not cause your pull request validation to fail. (packit-service#2543)

Week 42 (October 15th – October 21st)​

• Manual test trigger command (/packit test) now accepts --env option(s) to override environment variables passed to Testing Farm. (packit-service#2583)

Week 41 (October 8th – October 14th)​

• We have fixed an issue that was introduced during the unification of the interface for passing resolved Bugzillas / Jira tickets to the sync-release or bodhi_update jobs. (packit#2442)

Week 40 (October 1st – October 7th)​

• packit validate-config now checks for the existence of the downstream package. (packit#2436)
• Packit now allows building VM images via CLI without any Copr repository specified. (packit#2434)
• We have unified interface of passing resolved bugs (e.g., Bugzillas as of now) to Packit CLI and via comments. Both CLI and comments now use --resolve-bug switch (comments accept comma-separated list of bugs, CLI accepts the switch multiple times (also -b)). (packit#2428 and packit-service#2560)
• packit init now adds working directories that are used in packit prepare-sources into the .gitignore file in the same directory where Packit config resides. (packit#2431)
• Before triggering the non-scratch Koji builds, we now check whether there is not already a build in progress or completed for the same NVR. (packit-service#2559)
• We have improved the error reporting for failed downstream jobs. (packit-service#2544)
• We have fixed an issue that caused inconsistencies with the expected behaviour stated by the documentation when adding duplicitous reactions to GitLab comments. (ogr#861)

Week 44 (October 31st – November 6th)​

• Dist tag (%{?dist}) is now enforced when updating release during SRPM creation. (packit#2106)

Week 43 (October 24th – October 30th)​

• Packit no longer downloads sources excluded using spec file conditions. (packit#2132)

Week 41 (October 10th – October 16th)​

• (breaking) Packit no longer accepts packit.json or .packit.json as a configuration file name. (packit#2123)
• We have implemented several improvements in syncing the release downstream:
  • Packit now updates ACL of its own dist-git forks to allow users and groups with commit rights to the original dist-git repo to push directly to a fork. (packit#2112)
  • Packit now also properly cleans up the branch after syncing the release which should prevent unwanted files (e.g. tarballs) being committed to dist-git. (packit#2125)
  • We have adjusted the way how Packit includes the resolved bugzillas in the commit messages created when syncing the release downstream so that the resolved bugzillas are included in changelog when using %autochangelog. (packit#2126)
• Packit now reacts to retriggering comments for downstream jobs by commenting on the same issue/PR and providing information about the jobs. (packit-service#2222)
• We have fixed an issue that prevented you from running the jobs on the GitLab.com due to failing resolution of the upstream/downstream relationship for the cloned project. (packit#2120)
• Packit now triggers the build for the /packit test comment command if the last build was not successful. (packit-service#2228)

And special thanks to @SpyTec for multiple wonderful dashboard improvements!

Week 40 (October 3rd – October 9th)​

• We have fixed an issue that you could encounter when running the Packit from the CLI that caused misinterpretation of the repository to be an upstream repo instead of a downstream. (packit#2117)
• Packit now also detects resolved bugs in the default update notes (created from changelog diff) and assigns these when submitting the Bodhi updates. (packit#2111)
• We have fixed an issue that prevented automated allowlisting in the Packit Service. (packit#2113)
• Packit now exports PACKIT_UPSTREAM_PACKAGE_NAME, PACKIT_DOWNSTREAM_PACKAGE_NAME and PACKIT_CONFIG_PACKAGE_NAME also in the changelog_entry action. (packit#2103)
• Packit now posts a comment with a link to the Packit dashboard to the pull requests created in Fedora dist-git when syncing the release. (packit-service#2215)