Skip to main content

27 posts tagged with "2023"

View All Tags

· One min read

Week 27 (July 4th – July 10th)​

  • Packit now correctly reloads upstream specfile after running pre-sync action. (packit#2006)

Week 28 (July 11th – July 17th)​

  • Packit now includes instructions on how to checkout the dist-git PR locally when syncing the release. (packit-service#2116)
  • We have fixed a bug in processing options of %prep macros in our specfile library. For instance, when a quoted string appeared inside an expression expansion, it could lead to improper parsing, rendering the spec file invalid after accessing the options. (specfile#253)
  • packit.dev has a new format! As the content has expanded a lot in the recent year, we decided to switch to using Docosaurus: now all the documentation is in one place and this format also enables additional features for our blog posts. (packit.dev#694)

Weeks 29–30 (July 18th – July 31st)​

  • With plenty of team members on vacation, we didn't manage to implement any significant new features during these two weeks.

· 2 min read

Week 22 (May 30th – June 5th)​

  • Packit will now filter the pull requests based on the target branch if the branch is specified in the particular job configuration. (packit-service#2074)
  • Packit now supports manual_trigger in the configuration that allows you to make jobs run only when explicitly triggered by a comment. (packit-service#2069)

Week 23 (June 6th – June 12th)​

  • Our dashboard now shows projects in a table instead of the cards. (dashboard#267)

  • /packit test command has two new options:

    With --identifier option, Testing Farm will trigger only jobs with that identifier. (packit-service#2079)

    Also, it is now possible to specify labels for a job and trigger tests based on labels using a --labels option of the /packit test command. (packit#1988, packit-service#2088)

  • If the vm_image_build job doesn't have Copr project/owner configured, Copr project used for the latest Copr build of the pull request will be now used. (packit-service#2080)

  • Fixed filters in files_to_sync not being applied properly. (packit#1977)

  • The issue that could've caused inconsistencies when tests from a PR were supposed to be merged during the test runs on the Testing Farm has been fixed. (packit-service#2090)

Week 24 (June 13th – June 19th)​

Week 25 (June 21st – June 27th)​

  • If you are interested about the manual triggering deployed two weeks ago, David Kornel and Jakub Stejskal published a blog post about this on fedoramagazine.org.
  • Copr builds configured as a monorepo job will now be built in one Copr project together. The bug with overwriting the statuses for monorepo jobs has been fixed as well. (packit-service#2097)

Week 26 (June 27th – July 3rd)​

  • The bug which prevented errors on Testing Farm request submission from being correctly propagated to the user was fixed. (packit-service#2103)
  • pull_from_upstream jobs can now be retriggered with a comment /packit pull-from-upstream in a dist-git pull request. (packit-service#2087)

· 2 min read

Week 18 (May 4th - May 9th)​

We have experienced issues with automatic Bodhi updates that we are investigating. In case you miss a Bodhi update, you can retrigger the job via /packit create-update comment in a dist-git pull request. Besides that, during this short week (another Czech Republic public holiday) we didn't manage to implement any significant new features.

Week 19 (May 9th – May 15th)​

  • Packit now doesn't react to its own comments on Pagure and GitLab (on GitHub, this was already implemented). (packit-service#2048)

Week 20 (May 16th – May 22nd)​

  • We have implemented a denylisting mechanism allowing us to denylist namespaces/projects to prevent misuse of our service. (packit-service#2046)
  • Packit will now additionally require for each test job requiring build a build job definition to be present in the Packit configuration file. (packit-service#2012)
  • Packit now checks whether the configured architecture for the test target is supported by Testing Farm and in case it's not supported, Packit doesn't submit these test requests. (packit-service#2053)

Week 21 (May 23rd – May 29th)​

  • Unsuccessful Image Builder requests now provide error details so you can fix the Image configuration. (packit#1981)
  • Copr projects created by Packit will not follow the Fedora branching from now. This decision has been made to lower the load on Copr from the temporary Copr projects created, mainly, for the PR builds. If you are releasing your packages to the Copr, please use the new setting follow_fedora_branching. Already existing projects are not affected by this change and it is also not enforced with the custom Copr repositories. (packit#1970)
  • Additional artifact(s) passed as artifacts in the tf_extra_params dictionary will be now combined with the artifact passed by Packit instead of rewriting it. (packit-service#2056)
  • Specfile library now handles multiple %changelog sections. (specfile#230)

· 2 min read

Weeks 14–15 (April 3rd – April 17th)​

  • packit source-git related commands can skip dist-git repos, where the git trailer is not found, when looking for the right dist-git dir where to work. (packit#1938)
  • Tmt tests can now be run with fmf root outside of git root (packit#1936)
  • Commits created by Packit no longer contain the "Signed-off-by" tag. (packit#1934)
  • Packit's source_git functionality installs/loads the _packitpatch script in a more reliable manner that doesn't rely on deprecated setuptools functionality. (packit#1926)
  • Packit now supports monorepo configuration in CLI (packit#1864)
  • Packit should now correctly catch the logs if any of the user actions fail during propose_downstream. (packit#1939)
  • Packit now resets Release field in dist-git spec file to 1 when the version in upstream spec file is not up-to-date with the release that triggered propose_downstream. (packit#1940)

Week 16 (April 18th – April 24th)​

  • Packit now complies with PEP 621 and stores project metadata in pyproject.toml. (packit#1913)
  • Packit now properly respects upstream_ref for tags that start with "a", "b", "c", "e", "n", "r", "s". (packit#1943)
  • Packit Service now supports multi package configuration (a.k.a. monorepo configuration). (packit-service#1982)

Week 17-18 (April 25th – May 3rd)​

  • Detection of %autorelease usage in dist-git spec file during propose-downstream and pull-from-upstream has been improved and Packit will always preserve it. (packit#1949)
  • We have fixed an issue that prevented you from building in Copr and Koji on release in the GitLab upstream. (packit-service#2027)
  • TMT tests can now be run with FMF root outside of git root. (packit-service#2007)
  • When reacting to branch pushes, Packit now correctly checks whether the branch name matches the configuration for the test jobs with configured commit trigger. (packit-service#2015)
  • The propose-downstream job triggered by an issue comment now correctly loads the configuration from the upstream repository. (packit-service#2021)
  • Packit is newly on Mastodon. Or, more specifically, on Fosstodon. Follow @packit@fosstodon.org and be one of the first to know about all the news!

· One min read

Week 10 (March 7th – March 13th)​

  • Parsing the spec file by RPM is now performed only if really necessary, greatly improving performance in certain scenarios. (specfile#212)

Week 11 (March 14th – March 20th)​

  • Packit now uses the get_current_version action defined by the user to retrieve version before updating the specfile %setup macro (if any). (packit#1886)

Week 12 (March 21st – March 27th)​

  • 'upstream_tag_template' is now also used when looking for the latest version tag in Git. This allows upstream repositories to mix different tag-patterns in the same repository, but consider only one to tell the latest version. (packit#1891)

Week 13 (March 28th – April 3rd)​

  • Packit now preserves %autorelease during propose_downstream and pull_from_upstream. (packit#1904)
  • Since in GitLab, it is not possible to overwrite the pending statuses, Packit now provides more generic descriptions and URLs when setting the first pending status. (packit-service#1975)

· 3 min read

Weeks 5–6 (February 1st – February 13th)​

  • You can now use --srpm option with the packit build locally CLI command. (packit#1810)
  • You will newly see news about Packit as a footer of the GitHub check runs summary. (packit-service#1881)
  • Packit now groups related builds and test runs (e.g. triggered by the same event, just different chroots) together. In the future, this will allow better presentation of the overall pipelines (e.g. in the dashboard). We now also create database entries before sending requests to external service (e.g. Testing Farm), therefore failures will be more visible in the dashboard. (packit-service#1787)

Week 7 (February 14th – February 20th)​

  • Packit now provides PACKIT_PROJECT_VERSION environment variable when running changelog-entry action. (packit#1853)
  • Packit CLI now requires bodhi in version 7.0.0 at minimum. (packit#1844)
  • You can now specify branches for a job triggered by a commit with a regex. (packit-service#1909)

Week 8 (February 21st – February 27th)​

  • packit validate-config CLI command now provides details about errors when it cannot parse the config file. (packit#1861)
  • --update-release/--no-update-release CLI flag now affects only Release, not Version. (packit#1857)
  • Packit does fewer API calls when searching for the package configuration file in remote repositories. (packit#1846)
  • Commit statuses/check names will now contain the name of the branch or release for the build and test jobs with commit or release trigger. This will prevent the collision of the names. (packit-service#1920)

Week 9 (February 28th – March 6th)​

  • Aliases logic was updated to account for the upcoming Fedora release (Bodhi now marks such release as frozen). From now on, Fedora 38 updates will be created even when the release is frozen. (packit#1863)
  • packit validate-config now correctly checks glob-patterns in 'files_to_sync' (packit#1865) and provides details about errors when it cannot parse a config file. (packit#1861)
  • Pull-from-upstream jobs are now displayed on our dashboard 🥳 https://dashboard.packit.dev/jobs/pull-from-upstreams (packit-service#1951, packit-service#1939)
  • Packit will no longer automatically request access to the forks on GitLab. This will prevent us from spamming one-time contributors with requesting the access, whereas the regular contributors can add Packit following the instructions from the comments on the MRs, so they can receive the results of Packit pipeline right from the commit statuses. (packit-service#1946)
  • Packit will retry tasks that are interrupted by a worker shutdown. This should improve throughput and reduce cases where there is no outcome, i.e. "builds should have been done but nothing happened". (packit-service#1935)
  • OGR now understands a few community-hosted GitLab instances that could not be determined automatically from the hostname. Thanks to that, you don't need to hardcode these instances to be mapped correctly. (ogr#775)

Thank you, @SpyTec for so many wonderful changes in our dasbhoard.

· 3 min read

Week 0 🌄 (December 20th 2022 – January 2nd 2023)​

  • ogr now raises GitForgeInternalError rather than PagureAPIException when getting 50x response from the Pagure API. This should increase usability as those tasks will be retried. (ogr#762)
  • Packit now puts the correct release number into the changelog when the Release tag is reset during propose-downstream. (packit#1816))

Week 1 (January 3rd – January 9th)​

  • SRPMs for projects that installed the GitHub App before September 6th and don't have srpm_build_deps defined are now built in Copr as well. (packit-service#1822)
  • We have fixed a bug in dashboard that linked null as a Copr build for Testing Farm runs that do not require any Copr build. (dashboard#200)
  • All classes including Specfile itself can now be copied using the standard copy() and deepcopy() functions from copy module. (specfile#176)

Week 2 (January 10th – January 16th)​

Week 3 + 4 (January 17th – January 30th)​

  • Users can now re-trigger bodhi_update and koji_build jobs by /packit create-update and /packit koji-update comments in an issue opened by Packit in the configured issue_repository if anything went wrong during these jobs. (packit-service#1796)
  • All Copr projects created by Packit now default to enable_net=False: our documentation stated this, but it wasn't the case. This is now corrected. (packit#1825)
  • You can now specify update_release: false in the configuration to tell Packit not to change the Version and Release in the spec file. It works the same as --no-update-release (renamed from now deprecated --no-bump) in the CLI. (packit#1827)
  • Packit now supports setting module_hotfixes for Copr projects. (packit#1829)
  • Packit now also allows passing in free-form parameters to Testing Farm in order to support all of its options immediately once they are added. The parameters can be passed through the tf_extra_params config option. The free-form dictionary must follow the structure of Testing Farm POST requests. See our documentation and examples for more information. (packit-service#1853)
  • Fixed a bug in section parsing that caused sections to be ignored when there were macro definitions spread across the spec file and not cumulated at the top. (specfile#191)
  • Also fixed the infinite loop that occurred when section options were followed by whitespace. (specfile#197)