Skip to content
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

build(main): add ci for latest #3512

Closed
wants to merge 1 commit into from

Conversation

cuisongliu
Copy link
Collaborator

@cuisongliu cuisongliu commented Jul 16, 2023

πŸ€– Generated by Copilot at d008fcf

Summary

πŸššπŸ’¬πŸ› οΈ

This pull request updates several GitHub workflows for building, pushing, and renewing the cluster images for sealos. It also fixes the issue title format for the gh-rebot action and renames the cloud.yml workflow to ci-patch-image.yml.

We'll build and push the cluster images, latest and tag
We'll sync them with the issues, and the gh-rebot flag
We'll heave away and haul away with buildx and output
We'll patch the sealos images and make the cloud module stout

Walkthrough

  • Rename the workflow file from cloud.yml to ci-patch-image.yml to reflect its purpose (link)
  • Add the cloud module to the matrix of modules that are built and pushed by the controllers workflow, to include the cloud controller in the cluster images (link, link)
  • Remove the raw value of dev from the matrix of tags that are checked by the controllers and frontend workflows, to avoid building images with the dev tag, which is not used anymore (link, link)
  • Modify the output variables of the prepare steps in the controllers and frontend workflows, to include the cluster image name with the tag name and the latest cluster image name with the latest tag (link, link)
  • Modify the sed command that replaces the old docker image name with the new docker image name in the manifests, to use the latest tag instead of the dev tag for the old docker image name, in the controllers and frontend workflows (link, link)
  • Modify the cluster image building and manifesting steps in the controllers, frontend, and services workflows, to build and manifest both the cluster image with the tag name and the cluster image with the latest tag, for each platform and module (link, link, link)
  • Modify the renew issue and sync images steps in the controllers, frontend, services, and release workflows, to use the Chinese brackets for the issue title, for consistency with other issues in the repository (link, link, link, link, link, link, link, link)
  • Add new steps to the renew issue and sync images steps in the controllers, frontend, and services workflows, to renew the issue and sync the images for the cluster image with the latest tag, using the same action but with a different comment body and version (link, link, link)

Signed-off-by: cuisongliu <cuisongliu@qq.com>
@codecov
Copy link

codecov bot commented Jul 16, 2023

Codecov Report

❗ No coverage uploaded for pull request base (release-v4.3@aaafe9a). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@               Coverage Diff               @@
##             release-v4.3    #3512   +/-   ##
===============================================
  Coverage                ?   72.97%           
===============================================
  Files                   ?        8           
  Lines                   ?      618           
  Branches                ?        0           
===============================================
  Hits                    ?      451           
  Misses                  ?      132           
  Partials                ?       35           

β˜” View full report in Codecov by Sentry.
πŸ“’ Do you have feedback about the report comment? Let us know in this issue.

@cuisongliu cuisongliu closed this Jul 16, 2023
@cuisongliu cuisongliu deleted the tag_ci_v4.3 branch July 16, 2023 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants