Include s3-tests in ceph repo#65724
Conversation
a4b814c to
955e678
Compare
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
955e678 to
ed48507
Compare
Signed-off-by: Adam C. Emerson <aemerson@redhat.com>
ed48507 to
ae1eeac
Compare
|
fyi @ivancich |
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
| overrides: | ||
| s3tests: | ||
| force-branch: ceph-master | ||
| # force-branch: main |
There was a problem hiding this comment.
with this change, will teuthology take, by default, the test code from "main" or the test code from the branch being tested (as with the other tests)?
There was a problem hiding this comment.
It was part of testing, I'm having problems getting the SHA we're supposed to be testing down to the backend. I'm going to do a deep dive into teuthology to figure out exactly how the design works.
There was a problem hiding this comment.
ok. i think that the end goal would be to remove this file, and just take the test from the branch of the PR?
There was a problem hiding this comment.
Yes. This was just debugging/trying to figure out what's going on.
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
|
This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution! |
A Proof of Concept to try having s3-tests run from within the repo
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job DefinitionYou must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.