bluey

joined 1 year ago
[–] [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]
 

Support for GitHub actions

 

now with zero-downtime garbage collection.

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

try setting a lower mtu ?

[–] [email protected] 7 points 4 months ago* (last edited 4 months ago) (2 children)
[–] [email protected] 3 points 4 months ago

Yes, thanks to AshiLinux

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

has AOT vibes

[–] [email protected] 1 points 6 months ago* (last edited 6 months ago)

These have veen banned here for the same reason https://www.safeworkaustralia.gov.au/esban

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

been on it for a while. dnf upgrade was missed out :(

[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

I would prefer pulumi as this would allow me to spin up the entire infra and manage k8s from it.

do note, js/ts typically are tier 1 language for aws cdk and pulumi.

 

works like a charm

 

Crafting pipeline configurations with YAML can be intricate and challenging because YAML isn't a programming language, Developers may find themselves reinventing the wheel each time they try to create new configurations because they don't have visibility into existing configurations and work that others may have already done, resulting in inefficiency.

GitLab 16.7 introduces the CI/CD Catalog (Beta), with the goal of enhancing developer efficiency

 
2
GitLab outage (status.gitlab.com)
 

[Investigating] Our investigation into the root cause of the issue is still underway. Once availability has been restored, full details regarding the incident will be posted in the incident issue here: gitlab.com/gitlab-com/gl-infra/production/-/issues/15997

view more: next ›