assisted-service
assisted-service copied to clipboard
MGMT-9589: Distribute sdist package to PyPI in addition to wheel one
We currently build both the source distribution and wheel packages for the assisted-service Python client, but only the wheel package is uploaded to PyPI. This PR start uploading both packages to enhance compatibility and installation flexibility.
List all the issues related to this PR
- [ ] New Feature
- [x] Enhancement
- [ ] Bug fix
- [ ] Tests
- [ ] Documentation
- [ ] CI/CD
What environments does this code impact?
- [x] Automation (CI, tools, etc)
- [ ] Cloud
- [ ] Operator Managed Deployments
- [ ] None
How was this code tested?
- [ ] assisted-test-infra environment
- [ ] dev-scripts environment
- [ ] Reviewer's test appreciated
- [x] Waiting for CI to do a full test run
- [ ] Manual (Elaborate on how it was tested)
- [ ] No tests needed
Checklist
- [x] Title and description added to both, commit and PR.
- [x] Relevant issues have been associated (see CONTRIBUTING guide)
- [x] This change does not require a documentation update (docstring,
docs
, README, etc) - [ ] Does this change include unit-tests (note that code changes require unit-tests)
Reviewers Checklist
- Are the title and description (in both PR and commit) meaningful and clear?
- Is there a bug required (and linked) for this change?
- Should this PR be backported?
@danmanor: This pull request references MGMT-9589 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
Currently we build both source distribution package and wheel package of assisted-service python client, but upload only the wheel one. We want to upload both to pypi
List all the issues related to this PR
- [ ] New Feature
- [ ] Enhancement
- [ ] Bug fix
- [ ] Tests
- [ ] Documentation
- [ ] CI/CD
What environments does this code impact?
- [ ] Automation (CI, tools, etc)
- [ ] Cloud
- [ ] Operator Managed Deployments
- [x] None
How was this code tested?
- [ ] assisted-test-infra environment
- [ ] dev-scripts environment
- [ ] Reviewer's test appreciated
- [ ] Waiting for CI to do a full test run
- [ ] Manual (Elaborate on how it was tested)
- [x] No tests needed
Checklist
- [ ] Title and description added to both, commit and PR.
- [ ] Relevant issues have been associated (see CONTRIBUTING guide)
- [ ] This change does not require a documentation update (docstring,
docs
, README, etc)- [ ] Does this change include unit-tests (note that code changes require unit-tests)
Reviewers Checklist
- Are the title and description (in both PR and commit) meaningful and clear?
- Is there a bug required (and linked) for this change?
- Should this PR be backported?
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.
@danmanor: This pull request references MGMT-9589 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
Currently we build both source distribution package and wheel package of assisted-service python client, but upload only the wheel one. We want to upload both to pypi
List all the issues related to this PR
- [ ] New Feature
- [x] Enhancement
- [ ] Bug fix
- [ ] Tests
- [ ] Documentation
- [ ] CI/CD
What environments does this code impact?
- [x] Automation (CI, tools, etc)
- [ ] Cloud
- [ ] Operator Managed Deployments
- [ ] None
How was this code tested?
- [ ] assisted-test-infra environment
- [ ] dev-scripts environment
- [ ] Reviewer's test appreciated
- [x] Waiting for CI to do a full test run
- [ ] Manual (Elaborate on how it was tested)
- [ ] No tests needed
Checklist
- [ ] Title and description added to both, commit and PR.
- [ ] Relevant issues have been associated (see CONTRIBUTING guide)
- [ ] This change does not require a documentation update (docstring,
docs
, README, etc)- [ ] Does this change include unit-tests (note that code changes require unit-tests)
Reviewers Checklist
- Are the title and description (in both PR and commit) meaningful and clear?
- Is there a bug required (and linked) for this change?
- Should this PR be backported?
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.
@danmanor: This pull request references MGMT-9589 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
We currently build both the source distribution and wheel packages for the assisted-service Python client, but only the wheel package is uploaded to PyPI. This PR start uploading both packages to enhance compatibility and installation flexibility.
List all the issues related to this PR
- [ ] New Feature
- [x] Enhancement
- [ ] Bug fix
- [ ] Tests
- [ ] Documentation
- [ ] CI/CD
What environments does this code impact?
- [x] Automation (CI, tools, etc)
- [ ] Cloud
- [ ] Operator Managed Deployments
- [ ] None
How was this code tested?
- [ ] assisted-test-infra environment
- [ ] dev-scripts environment
- [ ] Reviewer's test appreciated
- [x] Waiting for CI to do a full test run
- [ ] Manual (Elaborate on how it was tested)
- [ ] No tests needed
Checklist
- [x] Title and description added to both, commit and PR.
- [x] Relevant issues have been associated (see CONTRIBUTING guide)
- [x] This change does not require a documentation update (docstring,
docs
, README, etc)- [ ] Does this change include unit-tests (note that code changes require unit-tests)
Reviewers Checklist
- Are the title and description (in both PR and commit) meaningful and clear?
- Is there a bug required (and linked) for this change?
- Should this PR be backported?
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.
/cc @adriengentil
/cc @paul-maidment
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 68.43%. Comparing base (
9a4ece9
) to head (6df2953
). Report is 21 commits behind head on master.
Additional details and impacted files
@@ Coverage Diff @@
## master #6294 +/- ##
==========================================
+ Coverage 68.29% 68.43% +0.14%
==========================================
Files 241 245 +4
Lines 35858 36060 +202
==========================================
+ Hits 24488 24679 +191
+ Misses 9211 9203 -8
- Partials 2159 2178 +19
/RETEST
/retest
I think we had an issue with artifacts different than whl
I'll try to find the ticket
I think we had an issue with artifacts different than
whl
I'll try to find the ticket
The ticket is: https://issues.redhat.com/browse/MGMT-8446 The fix was on: https://github.com/openshift/assisted-service/pull/3019
@eliorerz so we need to remove the "v" prefix from its version
@eliorerz so we need to remove the "v" prefix from its version
Yes, but this prefix is auto generated using vcversioner
, that is why I created this ticket.
Just adding the extra artifact will cause the job to fail.
@eliorerz Thank you
/hold
/unhold
@eliorerz I changed it, let me know what you think
/retest
/retest
/retest
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danmanor, eliorerz
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [danmanor,eliorerz]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
/retest-required
Remaining retests: 0 against base HEAD ffa8b5c57785f9fd63d892fbee1510676af7d71a and 2 for PR HEAD 6df2953ddae73e6d0ac43f8ff93943bc3183bd74 in total
@danmanor: all tests passed!
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.
[ART PR BUILD NOTIFIER]
This PR has been included in build ose-agent-installer-api-server-container-v4.17.0-202405281343.p0.g66a3ef7.assembly.stream.el9 for distgit ose-agent-installer-api-server. All builds following this will include this PR.