-
Notifications
You must be signed in to change notification settings - Fork 743
Move products to a dedicated folder #7018
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Changes identified: Show detailsOthers: Recommended tests to execute: |
|
This change makes sense to me and it does make it easier to view the relevant covered products. Let's wait for more folks from the community to give feedback on this. I'd also like to get some time to change the OCP4 CI tests to reflect this new structure before merging this, so we don't have a long breakage. |
|
@matejak thanks for the PR, I've been advocating for a change like this to clean up the structure of the project. I think this will make things easier to digest at first glance, and hopefully easier to follow for new contributors. I also agree with @JAORMX that we should get more feedback from the community members to see if this is the appropriate way to clean up the structure, or perhaps there are other ideas. |
|
I completely agree to take this one slow. I think that we can leave it open at least until the end of May to accumulate feedback, and if the proposal is still alive, then I will resolve confilcts and we can then consider merging this. |
Do you want to add this to the discussions? |
I don't know, and I am leaning towards that it isn't needed - the discussion itself can take place here, and I have announced the intention on the mailing list, which is a traditional communication channel. However, if there is no feedback next week, I think that we can announce in the GH discussion. |
This automatically clones the content repo, from which we get the test info. This is done by detecting if the ROOT_DIR env variable is empty: if it's empty, we clone it and set the env variable appropriately. This also takes into account the `products` dir that's being proposed [1], so the OCP4 e2e tests will not be affected by this change. [1] ComplianceAsCode/content#7018 Signed-off-by: Juan Antonio Osorio Robles <jaosorior@redhat.com>
a8e30e0 to
cc5a0cc
Compare
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
cc5a0cc to
6f3b163
Compare
|
I think that as no objections came, it is time to prepare for start seriously considering merging this PR. |
6f3b163 to
690ec52
Compare
|
/retest |
1 similar comment
|
/retest |
690ec52 to
35f7c6f
Compare
|
@matejak: One suggestion by @richardmaciel-canonical was that if you used |
I think that I have used |
35f7c6f to
00779d9
Compare
|
/retest |
|
/test e2e-aws-ocp4-e8 |
|
Note for reviewers - the git diff (not Github diff) is very clean except files that had to be modified because they contained relative paths (s.a. XSLT transforms). |
00779d9 to
271161e
Compare
|
I'm getting this warning when running If I create the symlinks for these two folder in the root directory then the warning disappears. Do you know what could that be? Do you see the same on your side? It looks like it's a valid issue: https://github.com/ComplianceAsCode/content/runs/2792925585?check_suite_focus=true#step:4:110 Update1: I'm suspecting that has something to do with these lines: https://github.com/ComplianceAsCode/content/blob/master/cmake/SSGCommon.cmake#L1405-L1408 Update2: Prepending |
271161e to
b013182
Compare
|
/retest |
b013182 to
822cced
Compare
|
LGTM. The commits were accidentally pushed directly to master. No need to reopen nor revert. The changes in master look fine. So no need to take any extra action. |
|
@matejak: The following tests failed, say
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/test-infra repository. I understand the commands that are listed here. |
This automatically clones the content repo, from which we get the test info. This is done by detecting if the ROOT_DIR env variable is empty: if it's empty, we clone it and set the env variable appropriately. This also takes into account the `products` dir that's being proposed [1], so the OCP4 e2e tests will not be affected by this change. [1] ComplianceAsCode/content#7018 Signed-off-by: Juan Antonio Osorio Robles <jaosorior@redhat.com>
This PR aims to make the project directory tree more structured.
As it just moves directories, the backward compatibility of patches can be achieved by creating symlinks from the root directory:
for prod in products/*; do ln -s "$prod" $(basename "$prod"); done