Conversation
|
Hi @AshwinHIBM. Thanks for your PR. I'm waiting for a ppc64le-cloud member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
/ok-to-test |
6c2c9b3 to
02afba6
Compare
|
@Rajalakshmi-Girish has some good comments/requests so I'll approve if she does. Thanks Raji! |
02afba6 to
af3b2ad
Compare
0e8af61 to
23a11d9
Compare
23a11d9 to
fb05c55
Compare
b4056e0 to
114c053
Compare
|
@Rajalakshmi-Girish lets review this PR |
I shall review this in a day. |
Rajalakshmi-Girish
left a comment
There was a problem hiding this comment.
@AshwinHIBM Let us schedule a call tomorrow. Please help me understand better.
|
|
||
| echo "* Start prow-info-docker *" | ||
| chmod ug+x $PWD/upstream-master-ci/prow-info-docker.sh | ||
| $PWD/upstream-master-ci/prow-info-docker.sh |
There was a problem hiding this comment.
@AshwinHIBM You mentioned periodic-config-docker is to Check the configuration of the kernel for suitability to run Docker., where as line here https://github.com/ppc64le-cloud/docker-ce-build/blob/main/upstream-master-ci/prow-info-docker.sh#L14 seems to display a text Prow Job to run CI tests on the Docker packages, Seems some discrepancy.
There was a problem hiding this comment.
I see DATE being directed to /home/prow/go/src/github.com/ppc64le-cloud/docker-ce-build/env/date.list at https://github.com/ppc64le-cloud/docker-ce-build/blob/main/upstream-master-ci/prow-info-docker.sh#L12
But there doesn't seem to be a file date.list in https://github.com/ppc64le-cloud/docker-ce-build/tree/main/env!
@AshwinHIBM Can we connect to understand better?
There was a problem hiding this comment.
@AshwinHIBM You mentioned
periodic-config-dockeris toCheck the configuration of the kernel for suitability to run Docker., where as line here https://github.com/ppc64le-cloud/docker-ce-build/blob/main/upstream-master-ci/prow-info-docker.sh#L14 seems to display a textProw Job to run CI tests on the Docker packages, Seems some discrepancy.
The statement "Prow Job to run CI tests...." is just a generic statement used in all the jobs, but agreed, it can be more specific.
There was a problem hiding this comment.
@AshwinHIBM You mentioned periodic-config-docker is to Check the configuration of the kernel for suitability to run Docker., where as line here https://github.com/ppc64le-cloud/docker-ce-build/blob/main/upstream-master-ci/prow-info-docker.sh#L14 seems to display a text Prow Job to run CI tests on the Docker packages, Seems some discrepancy.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: AshwinHIBM The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Do all jobs postsubmit-unit-test-docker, postsubmit-integration-test-docker, postsubmit-integration-test-docker require dind image?
Also, here are my comments for your scripts at https://github.com/ppc64le-cloud/docker-ce-build/tree/main/upstream-master-ci - just sharing my thoughts!
- Why the mention of
adding a git commitat https://github.com/ppc64le-cloud/docker-ce-build/blob/main/setup-pj-trigger.sh#L20? I see only date info being added to folder under https://github.com/ppc64le-cloud/docker-ce-build/tree/prow-job-tracking/job - Why the intermediate https://github.com/ppc64le-cloud/docker-ce-build/blob/main/setup-pj-trigger.sh? Why not directly call https://github.com/ppc64le-cloud/docker-ce-build/blob/main/trigger-prow-job-from-git.sh from https://github.com/ppc64le-cloud/docker-ce-build/blob/main/upstream-master-ci/prow-info-docker.sh
- How is moby dynamic here? https://github.com/ppc64le-cloud/docker-ce-build/blob/main/upstream-master-ci/build-dev-image.sh#L1 Where is it cloned?
- Why two files
prow-unit-test-docker.shunit-tests.sh? Can't the common part from files of first kind be clubbed at one place?
| #Set this to your dev branch for testing | ||
| WORK_BRANCH=main | ||
| git fetch https://github.com/${REPO_OWNER}/${REPO_NAME} ${WORK_BRANCH} | ||
| git checkout ${WORK_BRANCH} |
There was a problem hiding this comment.
@AshwinHIBM Will just git checkout main be not enough in place of above three commands in all jobs?
There was a problem hiding this comment.
Changing https://github.com/ppc64le-cloud/test-infra/pull/517/files#diff-7cc77aecddebbf7c3478065e05b998c98df879793b4afa288afb1781bd4c34e8R2 to AshwinHIBM/docker-ce-build automatically sets REPO_OWNER to AshwinHIBM and REPO_NAME to docker-ce-build which lets me test changes to the CI scripts which are in my fork before pushing to main. Having the WORK_BRANCH parameter on L37 prevents writing it twice on the next 2 lines. git fetch is the only line when the repository is fetched from the internet (as we're not using git clone here). This is the style we use for the existing jobs too. If there's a better style to provide the above functionality, I can change to it.
|
|
||
| echo "* Start prow-info-docker *" | ||
| chmod ug+x $PWD/upstream-master-ci/prow-info-docker.sh | ||
| $PWD/upstream-master-ci/prow-info-docker.sh |
There was a problem hiding this comment.
What Kernel settings are checked by periodic-config-docker job? is it required to check everyday?
Can we not verify it withe current underlying build cluster and take it for granted?
There was a problem hiding this comment.
It runs https://github.com/moby/moby/blob/master/contrib/check-config.sh
checks cgroups, apparmor, etc. Are you suggesting we remove it from CI and only run it when something changes with the underlying cluster like the OS version? I'm fine with that idea (we probably don't need to run it daily) but is there a way to know something changed with the cluster? Or instead changing the frequency to once a week/month?
| - error | ||
| channel: prow-job-notifications | ||
| report_template: 'Job {{.Spec.Job}} of type {{.Spec.Type}} ended with state {{.Status.State}}. <!subteam^S02N6DWBX0F> <{{.Status.URL}}|View logs>' | ||
|
|
There was a problem hiding this comment.
As discussed, shall we first try switching for scripts in https://github.com/ppc64le-cloud/test-infra/blob/master/config/jobs/ppc64le-cloud/build-docker/postsubmit-build-docker.yaml
fcfd159 to
70c06ed
Compare
The purpose of each job: