fedora-infra / rpmautospec

#193 3rd party tracking: Fedora CI
Closed: Invalid by nphilipp. Opened by churchyard.

Closed: Invalid
Reopen Issue

Story Time

As a package maintainer,

I want the pull requests CI (Zuul and Jenkins) to understands the rpmautospec macros,
so I can still enjoy the benefits of CI when I opt in to rpmautospec.

Acceptance Criteria

  • A pull request to src.fp.o/rpms that opts in for the rpmautospec macros is successfully tested with the correct release value on Fedora CI (i.e. Jenkins)
  • A pull request to src.fp.o/rpms that opts in for the rpmautospec macros is successfully tested with the correct release value on Zuul CI
  • A pull request to src.fp.o/rpms that changes a package that already uses the rpmautospec macros is successfully tested with the correct release value on Fedora CI (i.e. Jenkins)
  • A pull request to src.fp.o/rpms that changes a package that already uses the rpmautospec macros is successfully tested with the correct release value on Zuul CI

Background

I suspect this depends on https://pagure.io/fedora-infra/rpmautospec/issue/191

I've also opened a testing PR at https://src.fedoraproject.org/rpms/python-rpm-generators/pull-request/42

Related Zuul issue: https://pagure.io/fedora-ci/general/issue/258

Metadata Update from @nphilipp:
- Issue tagged with: 3rd party

The Zuulpart is fixed. The Jenkins thing is not.

I’ll close this issue as the project has been moved to https://github.com/fedora-infra/rpmautospec some time ago. If this is still relevant, please open a ticket there.

Metadata Update from @nphilipp:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)
Metadata
None

3rd party

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.