rpms/grafana-pcp
7
0
Fork 0
Code Issues Pull Requests Releases Activity
Performance Co-Pilot Grafana Plugin
37 Commits 10 Branches 43 Tags 348 KiB
Shell 68.5%
Python 31.5%
a7f717f67e
Go to file
Fedora Release Engineering a7f717f67e Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild 
Signed-off-by: Fedora Release Engineering <releng@fedoraproject.org>
2022-07-21 12:57:21 +00:00
.fmf Initial set of gating tests for grafana-pcp on Fedora 2021-02-03 21:00:35 +01:00
.github/workflows update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00
plans Initial set of gating tests for grafana-pcp on Fedora 2021-02-03 21:00:35 +01:00
tests Fix of test case ownership 2021-02-03 21:05:11 +01:00
.gitignore update to upstream 3.2.0 2021-11-12 16:21:30 +01:00
0001-remove-unused-frontend-crypto.patch update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00
0002-Revert-all-rename-plugin-IDs-from-pcp-to-performance.patch update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00
build_frontend.sh update to upstream 3.2.0 2021-11-12 16:21:30 +01:00
create_bundles_in_container.sh update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00
gating.yaml Initial set of gating tests for grafana-pcp on Fedora 2021-02-03 21:00:35 +01:00
grafana-pcp.rpmlintrc update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00
grafana-pcp.spec Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild 2022-07-21 12:57:21 +00:00
list_bundled_nodejs_packages.py update to upstream 3.1.0 2021-06-25 18:05:09 +02:00
Makefile update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00
README.md update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00
sources update to upstream grafana-pcp 5.0.0 2022-07-07 18:59:33 +02:00

README.md

grafana-pcp

The grafana-pcp package

Setup instructions

  • clone the upstream sources: git clone https://github.com/performancecopilot/grafana-pcp && cd grafana-pcp
  • checkout the version of the specfile: git checkout <currentversion>
  • apply existing patches: git am ../0*.patch

Upgrade instructions

  • follow the Setup instructions above
  • rebase to the new version: git fetch && git rebase --onto <newversion> <oldversion>
    • rebasing remove-unused-frontend-crypto.patch: only apply the patch to package.json and run yarn install, then yarn.lock will get updated automatically
  • create new patches from the modified git commits: git format-patch -N --no-stat --no-signature <newversion> && mv *.patch ..
  • update Version, Release, %changelog and tarball NVRs in the specfile
  • create bundles and manifest: ./create_bundles_in_container.sh
  • update specfile with contents of the .manifest file
  • run local build: rpkg local
  • run rpmlint: rpmlint -r grafana-pcp.rpmlintrc /tmp/rpkg/grafana-pcp-*/grafana-pcp-*.src.rpm /tmp/rpkg/grafana-pcp-*/x86_64/grafana-pcp-*.x86_64.rpm
  • run a scratch build: fedpkg scratch-build --srpm
  • upload new source tarballs: fedpkg new-sources *.tar.gz *.tar.xz
  • commit new sources file

Patches

  • create the patch
  • declare and apply (%prep) the patch in the specfile
  • if the patch affects Go or Node.js dependencies, or the webpack
    • add the patch to PATCHES_PRE_VENDOR or PATCHES_PRE_WEBPACK in the Makefile
    • create new tarballs
    • update the specfile with new tarball name and contents of the .manifest file

General guidelines

  • aim to apply all patches in the specfile
  • avoid rebuilding the tarballs

Patches fall in several categories:

  • modify dependency versions
  • modify both sources and vendored dependencies (e.g. CVEs)
  • modify the Node.js source (i.e. affect the webpack)
  • some patches are conditional (e.g. FIPS)

Patches cannot be applied twice. It is not possible to unconditionally apply all patches in the Makefile, and great care must be taken to include the required patches at the correct stage of the build.

Reproducible Bundles

Run ./create_bundles_in_container.sh to generate a reproducible vendor and webpack bundle.