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

refactor(ci): use data-platform workflows #286

Merged
merged 3 commits into from
Feb 3, 2025
Merged

Conversation

orfeas-k
Copy link
Contributor

@orfeas-k orfeas-k commented Feb 3, 2025

  • Refactor charmcraft.yaml files to enable the usage of charmcraft-cache and data-platform-workflows in general. See issue for details
  • Enable the usage of build_charm.yaml workflow, which allows independent and cached charm builds, making the CI more efficient and fast.
  • Refactor the tests and the integrate workflow to be able to use the charm artefacts generated by the build_charm.yaml workflow
  • Add promote.yaml workflow to replace the old release.yaml workflow_dispatch funcionality.
  • Remove publish.yaml workflow as the release process is handled by the recently refactor release.yaml.

Closes #277

Refactor charmcraft.yaml files to enable the usage of charmcraft-cache
and data-platform-workflows in general.

Close #271
…284)

* refactor(ci): use data-platform-workflows in on_pull/push workflows

* Enable the usage of `build_charm.yaml` workflow, which allows
  independent and cached charm builds, making the CI more efficient and
  fast.
* Refactor the tests and the integrate workflow to be able to use the
  charm artefacts generated by the `build_charm.yaml` workflow:
  - Refactor integrate.yaml to be ci.yaml, a workflow that now takes
    care for the whole pipeline from generating charm paths, to
    building, to testing, and then releasing. This change will replace
    on_pull_request.yaml.
  - on_push.yaml is now replaced entirely by release, which will run on
    pushes to main or track/* branches. This workflow is in charge of
    building -> testing -> releasing.
  - Refactor individual and repository level integration tests to be
    able to use charm artefacts besides building them.

Close #272
* Add promote.yaml workflow to replace the old release.yaml
  workflow_dispatch funcionality.
* Remove publish.yaml workflow as the release process is handled by the
  recently refactor release.yaml.

Fix #277
Copy link
Contributor

@NohaIhab NohaIhab left a comment

Choose a reason for hiding this comment

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

LGTM! Once you merge could you also send a PR to https://github.com/canonical/charmcraftcache-hub to point the branch to main? Thank you and good job!

@orfeas-k orfeas-k merged commit 7f01ab6 into main Feb 3, 2025
33 checks passed
@orfeas-k orfeas-k deleted the kf-6775-use-cached-builds branch February 3, 2025 14:09
carlcsaposs-canonical pushed a commit to canonical/charmcraftcache-hub that referenced this pull request Feb 3, 2025
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.

Use cached builds for release and publish workflow
2 participants