Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Refactor CI/CD workflows

See original GitHub issue

Currently there is a lot of duplication of code between the “Test and Deploy” workflow deploying master to dev and the “Test and Deploy PR” workflow handling the ci deployments. This could be improved by using common actions as components. Also, we should decouple the release of a renku chart on tag from this tag being deployed to our CD deployment. This will give us more freedom in tagging form non-master branches.

The building blocks for this could be:

Run acceptance tests through helm (see https://github.com/SwissDataScienceCenter/renku/issues/1762)
Define a “Deploy RenkuLab” action (#1839)
Define “Deploy RenkuLab to CD” and “Deploy RenkuLab to CI” action which use the above (#1839 and #1867)
~Define “Test Renku” action~ Havinghelm test availble make the running of tests so easy that it doesn’t seem to justify a separate action for this anymore. The more complicated handling of test artefacts is being made available through an action (https://github.com/SwissDataScienceCenter/renku/pull/1874).
Define a “Publish Chart action”

Then we could have different workflows for PRs, pushes to master and tags which compose those actions in an appropriate way.

Issue Analytics

State:
Created 3 years ago
Reactions:1
Comments:8 (8 by maintainers)

Top GitHub Comments

4reactions

ableulercommented, Oct 30, 2020

Yeah, that would be neat. Then we would finally have the long-discussed scenario where we can run integration test on component PRs.

1reaction

Panaetiuscommented, Nov 25, 2020

We can use https://github.com/marketplace/actions/slash-command-dispatch#slash_command-context

I think we should allow specific git refs for individual components to be specified as arguments, as well as just values for the values.yaml, like /deploy renku-ui=abdfeg123457ad renku-gateway.image.tag=abcdefg12345 jupyterhub.proxy.token=badc0ffee0ddfood

Top Results From Across the Web

The complete CI/CD Setup (Part 6 - Pipeline refactoring)

In this series of blog posts I'll describe how to setup and deploy a complete CI/CD pipeline on Kubernetes.

Refactoring GitHub Actions Workflow for Azure Static Web Apps

Throughout this post, I'm going to refactor the existing Azure Static Web Apps CI/CD pipeline workflows, using the "reusable workflows" ...

Refactor a code responsible for creating a CI/CD pipeline

We should refactor pipeline creation service, since it accumulated a lot of ... Refactor a code responsible for creating a CI/CD pipeline.

How to set up an efficient development workflow with Git and ...

Discussing CI/CD, various Git flows, and how to combine them effectively, with an example from the Android world.

CI/CD Pipeline: All You Need to Know - Opsera

A typical CI/CD pipeline includes the following stages. These stages make up the development lifecycle and workflow from source code to production: Source: ......