Closed ghost closed 1 year ago
I guess we need to disable CircleCI pipelines, to be able to merge this.
I guess we need to disable CircleCI pipelines, to be able to merge this.
Those checks are created automatically by CircleCI since this PR has no configuration. We can not disable circleci without merging this PR. (master still has circle-ci.yml and we need those pipelines to create releases until this pr is merged).
Will disable circleci integration after merging.
https://github.com/mattermost/mattermost-helm/pull/360#discussion_r940280062
@spirosoik Do check the proposal here: https://github.com/mattermost/mattermost-helm/pull/360#discussion_r940317891
I would strongly suggest rethinking using Makefiles binded with bash scripts committed to repos codebase, to build/release software. When using a tool such as Github Actions for CI
Summary
We will move CircleCI pipelines to Github Actions to fix race condition. Since we stop supporting CircleCI, we are migrating existing pipelines to Github Actions.
This PR contains migration of release pipelines.
Ticket Link
https://mattermost.atlassian.net/browse/CLD-3709
Failing CircleCI checks
Please ignore CircleCI checks, there is no circle pipeline configured in PR that causes builds to fail in CircleCI. That is because project is enabled in CircleCI.
After merging this PR to master we will disable builds at CircleCI.