gitlab

98 readers

8 users here now

Discussion surrounding the Gitlab product (both CE and EE.)

founded 1 year ago

MODERATORS

[email protected]

Introducing CI/CD Steps, a programming language for DevSecOps automation (about.gitlab.com)

submitted 3 months ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Support for GitHub actions

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 3 months ago (1 children)

I skimmed it and I am not grokking how it is different than their current automation.

[–] [email protected] 1 points 3 months ago

Current implementations would be shell(sh/pwsh/...) command run defined in yaml.

The proposed implementation will allow you to break down your pipeline into composable steps and reuse github actions within the same build job. Without this, you will have to use DIND to run these steps.

# Example job using action
my-job:
  run:
    - name: greet_user
      step: gitlab.com/gitlab-org/ci-cd/runner-tools/echo-step@v1
      inputs:
        echo: hello $[[ GITLAB_USER_LOGIN ]]
    - name: greet_user_again
      action: mikefarah/yq@master
      inputs:
        cmd: echo ["${{ steps.greet_user.outputs.echo }} again!"] | yq .[0]

[–] [email protected] -1 points 3 months ago

In fact, one of the quotes from a recent customer survey states: “GitLab needs to embrace a post-YAML world for CI.”

So, over the past two years, our pipeline authoring team, led by Product Manager Dov Hershkovitch, has been working extensively on improving the pipeline authoring experience.

Then in the tutorial

Create a step.yml file.

So much for being post-YAML...

It sounds like they want to reinvent Dagger but are at the YAML phase.

Anti Commercial-AI license