Actions

You can probably find yourself in a situation where some part of the packit workflow needs to be tweaked for your package.

Packit supports actions, which can be used to change the default implementation of some steps in the workflow. Packit is able to execute multiple commands for a single action. Each action accepts a list of commands. By default, the commands are executed using python's subprocess module without shell. If you need a shell (e.g. you want to utilize an environment variable, subprocesses, pipelines, expansion or any shell syntax in your command), just wrap your command in a bash process:

bash -c "my fancy $command | grep success"

It's important to quote the content of the -c option so shell interprets it correctly as a single option input.

All actions are also executed inside Packit Service. The service creates a new sandbox environment where the command is run.

Actions have a default behaviour which you can override, hooks don't have any - hooks are a way for you to perform operations following a certain packit event, e.g. cloning an upstream repo.

caution

Like other keys, the actions can be defined on the top, package or job level. Be aware that when overriding, the whole action mapping is replaced instead of merging.

If you want to reduce duplications, you can use the following YAML syntax to do this:

actions: &common_actions
  action_1:
    - echo hello

packages:
  package_1:
    actions:
      <<: *common_actions
      action_2:
        - echo world

Currently, these are the actions you can use:

Command matrix

Syncing the release

These apply to propose-downstream command/job and pull-from-upstream job.

	name	working directory	when run	description
[hook]	`post-upstream-clone`	upstream git repo	after cloning the upstream repo (main) and dist-git repo (target branch) and before gpg keys verification and version compatibility check
[hook]	`pre-sync`	upstream git repo	after cloning the upstream repo (main) and dist-git repo (target branch) and after gpg keys verification and version compatibility check
	`prepare-files`	upstream git repo	after cloning, checking out of both upstream and dist-git repos	replace patching and archive generation
	`create-patches`	upstream git repo	after sync of upstream files to the downstream	replace patching
[hook]	`post-modifications`	upstream git repo	after all modifications to the spec file and downloading remote sources and before uploading to lookaside cache
	`get-current-version`	upstream git repo	when the current version needs to be found	expect version as a stdout parameter
	`changelog-entry`	upstream git repo	when adding a new changelog entry to the specfile	stdout is used as a changelog entry
	`commit-message`	upstream git repo	after running pre-sync hook and checking out the tags/branches	used to override default commit message

Creating SRPM

These apply to the srpm command and building in COPR.

	name	working directory	when run	description
[hook]	`post-upstream-clone`	upstream git repo	after cloning of the upstream repo (main) and before other operations
	`get-current-version`	upstream git repo	when the current version needs to be found	expect version as a stdout
	`create-archive`	upstream git repo	when the archive needs to be created	replace the code for creating an archive
	`create-patches`	upstream git repo	after sync of upstream files to the downstream	replace patching
	`fix-spec-file`	upstream git repo	after creation of a tarball	this action changes spec file to use the new tarball
[hook]	`post-modifications`	upstream git repo	after all modifications to the spec file and before running rpmbuild command
	`changelog-entry`	upstream git repo	when adding a new changelog entry to the specfile	stdout is used as a changelog entry

Actions details

All actions are executed in a locked-down OpenShift pod. Your commands are invoked with arbitrary UIDs from a high range. Some tools may experience problems with these UIDs, such as tar. You can observe an error like this:

tar: value 1021440000 out of uid_t range 0..2097151
tar: Exiting with failure status due to previous errors

For tar, it's recommended to use the pax format (tar -H pax).

If you run into similar issues with other tools, please consult documentation or maintainers of the project.

`create-archive`

It is expected to return a relative path within the repository to the generated archive. If there are more steps, then one of them has to return the archive name. The best practice is to do it from the last step and print it: bash -c 'echo path/to/archive-$VERSION.tar.gz'.

If you can, please place the generated archive in the same directory as your spec file.

If your project uses multiple archives, you should handle manipulation of your spec file yourself in the fix-spec-file action. You also have to put all the archives (spec file sources) in the same directory as your spec file. Packit expects that project only have a single archive set as Source0 — it does not have a mechanism to manipulate more sources right now.

`fix-spec-file`

By default, this action updates the spec file so it's possible to have a proper reference of the archive in the %prep section and unpack it during the build properly. The action tries to perform 3 operations on a spec file:

It replaces Source configured by spec_source_id (default Source0) with a local path to the generated archive.
It changes the first %setup (or %autosetup) macro in %prep and adds -n so the generated tarball can be unpacked (it tries to extract the directory name directly from the archive or uses the configured archive_root_dir_template).
It updates Version and Release in the spec file.

If you provide your own implementation, none of the above happens.

For example a package may define multiple Sources. In such a case, the default implementation of fix-spec-file won't be able to update %prep correctly. You can instead use the sed program to set the new Sources correctly, e.g.

actions:
  fix-spec-file:
  # define one of the Source variables correctly
  - sed -i my_specfile_path -e "s/https.*only-vendor.tar.xz/my_correct_tarball_path/"
  # fill in Release as if packit would have done it
  - bash -c "sed -i -r \"s/Release:(\s*)\S+/Release:\1${PACKIT_RPMSPEC_RELEASE}%{?dist}/\" my_specfile_path"

`commit-message`

Our internal API differentiates between the commit title and description, so we have an additional requirement on separating the commit title by an empty line. You can, of course, provide just the commit title.

Debugging

For your own debugging purposes we allow arbitrary output before outputting the actual commit message. In such case, your commit message needs to be separated by the following separator (on a separate line):

---%<--- snip ---%<--- here ---%<---

tip

This separator is exposed as an environment variable PACKIT_DEBUG_DIVIDER.

Examples

Example of correct output

debug output
---%<--- snip ---%<--- here ---%<---
Rebase to new upstream release 0.42.69

- Resolves rhbz#124

This output can be produced by the following config:

actions:
  commit-message:
    - echo 'debug output'
    - bash -c 'echo ${PACKIT_DEBUG_DIVIDER}'
    - bash -c 'echo -e "Rebase to new upstream release ${PACKIT_PROJECT_VERSION}\n"'
    - bash -c '[ -z "$PACKIT_RESOLVED_BUGS" ] || echo ${PACKIT_RESOLVED_BUGS} | tr " " "\n" | sed "s/^/- Resolves /"'

Example of incorrect output

---%<--- snip ---%<--- here ---%<---

missing the commit title

Environment variables set by packit

Additionally, packit sets several environment variables for the actions:

PACKIT_UPSTREAM_PACKAGE_NAME — set to the upstream_package_name value, if any
PACKIT_DOWNSTREAM_PACKAGE_NAME — set to the downstream_package_name value, if any
PACKIT_CONFIG_PACKAGE_NAME — set to the package name key for the packages dictionary in a monorepo project, falls back to the downstream_package_name or, if not set, to upstream_package_name

There are also action-specific environment variables, which you can see below.

`fix-spec-file`

PACKIT_PROJECT_VERSION — current version of the project (coming from git describe)
PACKIT_PROJECT_COMMIT — commit hash of the top commit
PACKIT_PROJECT_ARCHIVE — expected name of the archive
PACKIT_RPMSPEC_RELEASE — value for spec file's %release field which packit would set

`create-archive`

PACKIT_PROJECT_VERSION — current version of the project (coming from git describe)
PACKIT_PROJECT_NAME_VERSION — current name and version of the project (coming from git describe)

`changelog-entry`

PACKIT_PROJECT_VERSION — version to be set in the specfile, set when relevant (e.g. when syncing upstream release downstream)
PACKIT_PROJECT_UPSTREAM_TAG - upstream tag corresponding to the version to be set in the specfile
PACKIT_RESOLVED_BUGS - bugs resolved by the release separated by space, set when syncing upstream release downstream, e.g. rhbz#123 rhbz#124
PACKIT_PROJECT_PREVIOUS_VERSION - version from the specfile that is about to be changed

`commit-message`

PACKIT_PROJECT_VERSION — version to be set in the specfile
PACKIT_UPSTREAM_TAG — git tag of the upstream release
PACKIT_UPSTREAM_COMMIT — commit SHA of the upstream release
PACKIT_DEBUG_DIVIDER — divider that can be used to separate debug output from the actual commit message to be used
PACKIT_RESOLVED_BUGS - bugs resolved by the release separated by space, e.g. rhbz#123 rhbz#124

Release-synchronization actions

Related to the propose-downstream and pull-from-upstream jobs.

PACKIT_UPSTREAM_REPO — absolute path to cloned upstream git repo (main branch)
PACKIT_DOWNSTREAM_REPO — absolute path to cloned downstream git repo (target branch)
PACKIT_PROJECT_VERSION - version that is being proposed
PACKIT_PWD - absolute path to the directory where the actions are run; for git upstreams this is the same as PACKIT_UPSTREAM_REPO

List of actions that provide these environment variables:

post-upstream-clone
pre-sync
prepare-files
create-patches
post-modifications
commit-message

If you want to see the content of those variables, you can print using echo in the specific action:

actions:
  fix-spec-file:
  - bash -c "echo PACKIT_PROJECT_VERSION=${PACKIT_PROJECT_VERSION}"

and then make sure to run packit with the --debug option:

$ packit --debug srpm
...
2021-09-15 09:01:36.821 commands.py       DEBUG  Command: bash -c echo PACKIT_PROJECT_VERSION=${PACKIT_PROJECT_VERSION}
2021-09-15 09:01:36.826 logging.py        INFO   PACKIT_PROJECT_VERSION=0.14.0

Actions can be defined like this in your .packit.yaml:

specfile_path: package.spec
files_to_sync:
  - packit.yaml
  - package.spec
upstream_package_name: package
downstream_package_name: package
dist_git_url: https://src.fedoraproject.org/rpms/package.git
actions:
  prepare-files: "make prepare"
  create-archive:
  - "make archive"
  - bash -c "ls -1 ./package-*.tar.gz"
  changelog-entry:
  - bash -c 'echo "- New release ${PACKIT_PROJECT_VERSION}"'

Please note that %changelog expects dashes in a changelog entry, but the dash would be interpreted by echo as an option so we need to quote it.

Be aware, that commands do not share the working directory. So, if you want to change the working directory of a command or multiple commands, don't run cd as a separate command as shown in the following example. This won't work as expected:

actions:
  post-upstream-clone:
    - cd /tmp
    - touch test_file

Instead, spawn a shell and change the directory as the first command:

actions:
  post-upstream-clone:
    - bash -c "cd ${PACKIT_DOWNSTREAM_REPO}; touch new_file_for_dist_git.tmp"

Actions

Command matrix​

Syncing the release​

Creating SRPM​

Actions details​

create-archive​

fix-spec-file​

commit-message​

Debugging​

Examples​

Environment variables set by packit​

fix-spec-file​

create-archive​

changelog-entry​

commit-message​

Release-synchronization actions​

Command matrix

Syncing the release

Creating SRPM

Actions details

`create-archive`

`fix-spec-file`

`commit-message`

Debugging

Examples

Environment variables set by packit

`fix-spec-file`

`create-archive`

`changelog-entry`

`commit-message`

Release-synchronization actions