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

🌱 Add global ci #1405

Merged
merged 2 commits into from
Nov 27, 2023
Merged

🌱 Add global ci #1405

merged 2 commits into from
Nov 27, 2023

Conversation

fabianvf
Copy link
Contributor

Global CI Integration for Component Builds

This PR integrates a GitHub Action workflow to build and upload the component images, preparing them for the global CI system.

By integrating the global CI, we aim to streamline and standardize our CI process across all components, ensuring a more efficient and unified CI/CD pipeline.

@codecov
Copy link

codecov bot commented Sep 27, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (82a704c) 39.41% compared to head (80544f6) 39.41%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1405   +/-   ##
=======================================
  Coverage   39.41%   39.41%           
=======================================
  Files         146      146           
  Lines        4775     4775           
  Branches     1138     1138           
=======================================
  Hits         1882     1882           
  Misses       2879     2879           
  Partials       14       14           
Flag Coverage Δ
client 39.41% <ø> (ø)
server ∅ <ø> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines +74 to +78
test-integration:
needs: build-and-upload-for-global-ci
uses: konveyor/ci/.github/workflows/global-ci.yml@main
with:
component_name: tackle2-ui
Copy link
Member

Choose a reason for hiding this comment

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

Does it make sense to run the both api integration and ui tests as part of UI CI?

The UI tests make sense, but the api tests seem unnecessary.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@sjd78 reasonable since these shouldn't affect the API at all. We should have e2e ui tests running soon. Will update the PR when that's up

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@sjd78 it will now only run the UI tests

Signed-off-by: Fabian von Feilitzsch <fabian@fabianism.us>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants