fedora-infra / rpmautospec

Clone

#193 3rd party tracking: Fedora CI
Opened 3 years ago by churchyard. Modified 3 years ago

Open
Close issue as:
Fixed Invalid Duplicate Insufficient Data

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

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

The Zuulpart is fixed. The Jenkins thing is not.

Log in to comment on this ticket.

Metadata
None

3rd party

None
None
None
None
Powered by Pagure 5.14.1
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.