redhat-exd-rebuilds/freshmaker

Freshmaker is a service that automatically rebuilds content.

freshmaker's Issues

remove references to lightblue

There are a couple of references to Lightblue, but Pyxis is replacing Lightblue. Can we drop all the Lightblue references and code?

remove references to PDC

There are a couple of references to PDC, but PDC is unmaintained. Can we drop all the PDC references and code?

How to deploy freshmaker for MBS on fedora28

@qixiang
Hi Qixiang:

I need to deploy freshmaker for MBS on fedora28.
The version of freshmaker on my fedora28 is freshmaker-0.0.4-5.fc28.noarch.(through dnf install -y freshmaker)
I have the following doubts about the deploying of freshmaker for MBS on fedora28.

1. Can I deploy freshmaker on a independent server(neither MBS server nor distgit server )?
2. Is “/etc/freshmaker/config.py” the only file I need to modify according to my envrionment(GIT_BASE_URL, MBS_BASE_URL,,,)?
3. I am not really understand the meaning and function of PDC_URL in config.py. Do I need my own PDC？
4. The docs about freshmaker is not for freshmaker-0.0.4. Would you please give me some information that can help me to modify config.py and deploy freshmaker for MBS on fedora28?

fix quay image build

The quay badge says the container has failed to build.

Has freshmaker been retired from Fedora?

@qixiang
Hi Qixiang:
I can not find the higher fedora release than fedora30 for freshmaker in fedora koji.
And I find that freshmaker has been retired from Fedora in fedora dist-git.
The newest tag of Freshmaker in github is v0.1.2 which was released on 21 May 2018, but the code is still updated in github.
So, I want to know:
1, How can I install freshmake on fedora31 or higer fedora release?
2, Has freshmaker been retired from Fedora? If yes, what service or software is uesd to replace freshmaker?

use Koji NVR parsing methods

contrib/freshmaker-cli has some methods that are similar to code Koji also has:

parse_nvr()
split_nvr_epoch()

See koji.parse_NVR() in koji/__init__.py

Since we're already importing Koji, we could delete these methods from Freshmaker.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency aiohttp to v3.9.4 [SECURITY]
• Update dependency jinja2 to v3.1.3 [SECURITY]
• Update dependency idna to v3.7 [SECURITY]
• Update dependency cryptography to v42 [SECURITY]
• Update Auto merged updates (alembic, beautifulsoup4, flask-login, flask-migrate, frozenlist, gql, graphql-core, greenlet, mako, markupsafe, multidict, psutil, pyparsing)
• Update all dependencies (JamesIves/github-pages-deploy-action, actions/checkout, actions/setup-python, attrs, certifi, dogpile-cache, flask, flask-sqlalchemy, itsdangerous, kobo, koji, odcs, prometheus-client, pyasn1, pyasn1-modules, pycairo, pycparser, pygments, pygobject, pyopenssl, python-dateutil, pytz, pyzmq, registry.fedoraproject.org/fedora, requests-gssapi, semver, sqlalchemy, stevedore, twisted, types-python-dateutil, typing-extensions, ubuntu, urllib3, werkzeug, zope-interface)
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

dockerfile

Dockerfile

• registry.fedoraproject.org/fedora 39-x86_64

github-actions

.github/workflows/docs.yml

• actions/checkout v4
• fedora-python/tox-github-action v38.0
• JamesIves/github-pages-deploy-action 4.1.0
• ubuntu 22.04

.github/workflows/tests.yml

• actions/checkout v2
• actions/setup-python v2
• ubuntu 20.04

pip_requirements

requirements.txt

• aiohttp ==3.9.1
• aiosignal ==1.3.1
• alembic ==1.13.0
• arrow ==1.3.0
• attrs ==23.1.0
• automat ==22.10.0
• backoff ==2.2.1
• beautifulsoup4 ==4.12.2
• certifi ==2023.11.17
• cffi ==1.16.0
• charset-normalizer ==3.3.2
• click ==8.1.7
• constantly ==23.10.4
• cryptography ==41.0.7
• decorator ==5.1.1
• defusedxml ==0.7.1
• dogpile-cache ==1.2.2
• fedmsg ==1.1.7
• flask ==2.2.5
• flask-login ==0.6.2
• flask-migrate ==4.0.5
• flask-sqlalchemy ==2.5.1
• frozenlist ==1.4.0
• gql ==3.5.0b8
• graphql-core ==3.3.0a3
• greenlet ==3.0.2
• gssapi ==1.8.3
• httplib2 ==0.22.0
• hyperlink ==21.0.0
• idna ==3.6
• incremental ==22.10.0
• itsdangerous ==2.1.2
• jinja2 ==3.1.2
• jsonformatter ==0.3.2
• kitchen ==1.2.6
• kobo ==0.35.0
• koji ==1.33.1
• krb5 ==0.5.1
• lockfile ==0.12.2
• mako ==1.3.0
• markupsafe ==2.1.3
• mock ==5.1.0
• moksha-common ==1.2.5
• moksha-hub ==1.5.17
• multidict ==6.0.4
• munch ==4.0.0
• mypy-extensions ==1.0.0
• odcs ==0.7.0
• openidc-client ==0.6.0
• pbr ==6.0.0
• prometheus-client ==0.19.0
• psutil ==5.9.6
• pyasn1 ==0.5.1
• pyasn1-modules ==0.3.0
• pycairo ==1.25.1
• pycparser ==2.21
• pygments ==2.17.2
• pygobject ==3.46.0
• pyldap ==3.0.0.post1
• pyopenssl ==23.3.0
• pyparsing ==3.1.1
• pyspnego ==0.10.2
• python-dateutil ==2.8.2
• python-fedora ==1.1.1
• python-json-logger ==2.0.7
• python-ldap ==3.4.4
• pytz ==2023.3.post1
• pyyaml ==6.0.1
• pyzmq ==25.1.2
• requests ==2.31.0
• requests-gssapi ==1.2.3
• requests-kerberos ==0.14.0
• requests-toolbelt ==1.0.0
• rpm ==0.1.0
• semver ==2.13.0
• six ==1.16.0
• soupsieve ==2.5
• sqlalchemy ==1.4.50
• stevedore ==5.1.0
• tabulate ==0.9.0
• twisted ==23.10.0
• txws ==0.9.1
• txzmq ==1.0.0
• types-python-dateutil ==2.8.19.14
• typing-extensions ==4.9.0
• urllib3 ==2.1.0
• werkzeug ==2.3.8
• yarl ==1.9.4
• zope-interface ==6.1

test-requirements.txt

what is a Freshmaker "build_id"?

The API v1 documentation does not tell users what build_id is.

For containers, it looks like build_id is actually the Koji buildContainer task ID, not a Koji build ID. This is an important gotcha.

freshmaker/handlers/koji/rebuild_images_on_parent_image_build.py has a hint about this:

# build_id is actually task id in build system, find out the actual build first

The problem is that freshmaker/models.py has this comment for build_id:

# Id of corresponding real build in external build system. Currently, it
# could be ID of a build in MBS or Koji, maybe others in the future.
# build_id may be NULL, which means this build has not been built in
# external build system.

The line build_id may be NULL, which means this build has not been built in external build system. is ambiguous.

Do we populate build_id when the Koji buildContainer task fails?

• If so, let's update this comment to reflect this.
• If not, let's update this comment from built to built successfully.

And let's update docs/api_v1.rst to describe how build_id relates to a Koji buildContainer task ID

(Longer term, it would be great to use the name "task_id" or "koji_task_id" throughout the codebase instead of re-using the name "build_id" to have two different meanings).

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• Update Auto merged updates (aiohttp, alembic, beautifulsoup4, flask-login, flask-migrate, frozenlist, gql, graphql-core, greenlet, jinja2, mako, markupsafe, multidict, psutil, pyparsing)
• Update all dependencies (JamesIves/github-pages-deploy-action, actions/checkout, actions/setup-python, attrs, certifi, cryptography, dogpile-cache, fedora-python/tox-github-action, flask, flask-sqlalchemy, idna, itsdangerous, kobo, koji, odcs, prometheus-client, pyasn1, pyasn1-modules, pycairo, pycparser, pygments, pygobject, pyopenssl, pyspnego, python-dateutil, pytz, pyzmq, registry.fedoraproject.org/fedora, requests, requests-gssapi, requests-kerberos, semver, sqlalchemy, stevedore, twisted, types-python-dateutil, typing-extensions, ubuntu, urllib3, werkzeug, zope-interface)

Detected dependencies

dockerfile

Dockerfile

• registry.fedoraproject.org/fedora 39-x86_64

github-actions

.github/workflows/docs.yml

• actions/checkout v4
• fedora-python/tox-github-action v38.0
• JamesIves/github-pages-deploy-action 4.1.0
• ubuntu 22.04

.github/workflows/tests.yml

• actions/checkout v2
• actions/setup-python v2
• ubuntu 20.04

pip_requirements

requirements.txt

• aiohttp ==3.9.1
• aiosignal ==1.3.1
• alembic ==1.13.0
• arrow ==1.3.0
• attrs ==23.1.0
• automat ==22.10.0
• backoff ==2.2.1
• beautifulsoup4 ==4.12.2
• certifi ==2023.11.17
• cffi ==1.16.0
• charset-normalizer ==3.3.2
• click ==8.1.7
• constantly ==23.10.4
• cryptography ==41.0.7
• decorator ==5.1.1
• defusedxml ==0.7.1
• dogpile-cache ==1.2.2
• fedmsg ==1.1.7
• flask ==2.2.5
• flask-login ==0.6.2
• flask-migrate ==4.0.5
• flask-sqlalchemy ==2.5.1
• frozenlist ==1.4.0
• gql ==3.5.0b8
• graphql-core ==3.3.0a3
• greenlet ==3.0.2
• gssapi ==1.8.3
• httplib2 ==0.22.0
• hyperlink ==21.0.0
• idna ==3.6
• incremental ==22.10.0
• itsdangerous ==2.1.2
• jinja2 ==3.1.2
• jsonformatter ==0.3.2
• kitchen ==1.2.6
• kobo ==0.35.0
• koji ==1.33.1
• krb5 ==0.5.1
• lockfile ==0.12.2
• mako ==1.3.0
• markupsafe ==2.1.3
• mock ==5.1.0
• moksha-common ==1.2.5
• moksha-hub ==1.5.17
• multidict ==6.0.4
• munch ==4.0.0
• mypy-extensions ==1.0.0
• odcs ==0.7.0
• openidc-client ==0.6.0
• pbr ==6.0.0
• prometheus-client ==0.19.0
• psutil ==5.9.6
• pyasn1 ==0.5.1
• pyasn1-modules ==0.3.0
• pycairo ==1.25.1
• pycparser ==2.21
• pygments ==2.17.2
• pygobject ==3.46.0
• pyldap ==3.0.0.post1
• pyopenssl ==23.3.0
• pyparsing ==3.1.1
• pyspnego ==0.10.2
• python-dateutil ==2.8.2
• python-fedora ==1.1.1
• python-json-logger ==2.0.7
• python-ldap ==3.4.4
• pytz ==2023.3.post1
• pyyaml ==6.0.1
• pyzmq ==25.1.2
• requests ==2.31.0
• requests-gssapi ==1.2.3
• requests-kerberos ==0.14.0
• requests-toolbelt ==1.0.0
• rpm ==0.1.0
• semver ==2.13.0
• six ==1.16.0
• soupsieve ==2.5
• sqlalchemy ==1.4.50
• stevedore ==5.1.0
• tabulate ==0.9.0
• twisted ==23.10.0
• txws ==0.9.1
• txzmq ==1.0.0
• types-python-dateutil ==2.8.19.14
• typing-extensions ==4.9.0
• urllib3 ==2.1.0
• werkzeug ==2.3.8
• yarl ==1.9.4
• zope-interface ==6.1

test-requirements.txt