Building Block triggering a pipeline
complete
Jelle den Burger
As a platform engineer, I want meshStack Building Blocks to trigger my automation pipeline through git, rather than having to do this with a Terraform workaround. This allows to me to quickly and easily integrate existing CI/CD Pipelines doing orchestration that I have already built before
R
Rebecca
complete
We are now providing the functionality in meshStack. You can setup a GitHub platform and configure the pipeline integration. Afterwards you can create building block definitions of type "pipeline automation". Enjoy!
Jelle den Burger
planned
We are currently focusing more on the status reporting part for pipelines integrated with meshStack.
In the mean time we recommend a workaround such as creating a file via Terraform and using our Terraform Building Blocks. https://registry.terraform.io/providers/integrations/github/latest/docs/resources/repository_file
Felix
This canny item is about creating files in a git repo.
If you are using GitLab and want to trigger a pipeline directly: https://meshcloud.canny.io/feature-requests/p/trigger-gitlab-job-via-api-as-building-block
R
Rebecca
in progress
R
Rebecca
Merged in a post:
When creating a new project, allow meshStack to provision a tenant using existing customer pipelines that manage tenants.
S
Shamil Radzhabov
The customer already uses CI/CD pipelines, like Git, or platforms to provision cloud tenants. It would be beneficial to trigger a remote pipeline or platform via API during the project creation process and integrate the resulting provisioning as a tenant in meshStack.
Workaround:
Presently, it's possible to set up this use case using a terraform building block. However, this solution is not optimal.
R
Rebecca
There’s no way to do that at the moment, but the good news is that we have already started working on that functionality, and it will be available this summer.