Skip to content

Enable Docker CI#517

Open
AshwinHIBM wants to merge 2 commits intoppc64le-cloud:masterfrom
AshwinHIBM:enable-docker-ci
Open

Enable Docker CI#517
AshwinHIBM wants to merge 2 commits intoppc64le-cloud:masterfrom
AshwinHIBM:enable-docker-ci

Conversation

@AshwinHIBM
Copy link
Contributor

@AshwinHIBM AshwinHIBM commented Dec 10, 2024

The purpose of each job:

  1. periodic-config-docker: Check the configuration of the kernel for suitability to run Docker.
  2. periodic-build-dev-image-docker: Build a minimal Docker development image.
  3. postsubmit-unit-test-docker: Run unit tests against https://github.com/moby/moby
  4. postsubmit-integration-test-docker: Run integration tests against https://github.com/moby/moby
  5. postsubmit-integration-cli-docker: Run the end-to-end test suite from https://github.com/docker/cli

@ppc64le-cloud-bot ppc64le-cloud-bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 10, 2024
@ppc64le-cloud-bot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@ppc64le-cloud-bot ppc64le-cloud-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 10, 2024
@Rajalakshmi-Girish
Copy link
Collaborator

/ok-to-test

@Rajalakshmi-Girish Rajalakshmi-Girish added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Dec 11, 2024
@ppc64le-cloud-bot ppc64le-cloud-bot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Dec 16, 2024
@clnperez
Copy link

clnperez commented Jan 3, 2025

@Rajalakshmi-Girish has some good comments/requests so I'll approve if she does. Thanks Raji!

@AshwinHIBM AshwinHIBM force-pushed the enable-docker-ci branch 4 times, most recently from 0e8af61 to 23a11d9 Compare January 28, 2025 17:45
@AshwinHIBM AshwinHIBM marked this pull request as draft February 4, 2025 10:36
@ppc64le-cloud-bot ppc64le-cloud-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 4, 2025
@AshwinHIBM AshwinHIBM force-pushed the enable-docker-ci branch 2 times, most recently from b4056e0 to 114c053 Compare February 5, 2025 13:19
@AshwinHIBM AshwinHIBM marked this pull request as ready for review March 24, 2025 12:32
@ppc64le-cloud-bot ppc64le-cloud-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 24, 2025
@mkumatag
Copy link
Contributor

@Rajalakshmi-Girish lets review this PR

@Rajalakshmi-Girish
Copy link
Collaborator

@Rajalakshmi-Girish lets review this PR

I shall review this in a day.

Copy link
Collaborator

@Rajalakshmi-Girish Rajalakshmi-Girish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

ppc64le-cloud/docker-ce-build#271

@ppc64le-cloud-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AshwinHIBM
Once this PR has been reviewed and has the lgtm label, please assign rajalakshmi-girish for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Collaborator

@Rajalakshmi-Girish Rajalakshmi-Girish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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!

#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}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AshwinHIBM Will just git checkout main be not enough in place of above three commands in all jobs?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Contributor Author

@AshwinHIBM AshwinHIBM Apr 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>'

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AshwinHIBM
Copy link
Contributor Author

Squashing 7dece64 and 114c053.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants