Skip to content
Snippets Groups Projects
Select Git revision
  • cam/add-to-e2e-test
  • main default protected
  • ajwalker/oci
  • jburnett/file-reader
  • jburnett/debug
  • cam/inline-language-steps
  • cam/remove-executable-delegation
  • jburnett/add-action-e2e-test
  • cam/reuse-cache-for-build-and-test
  • cam/encapsulate-stepsctx-in-steps
  • jburnett-run-up-squashed
  • jburnett-run-up
  • cam/simplify-step-result-builder
  • jburnett/run-up
  • add-dependency-scanning
  • avonbertoldi/service-action-test
  • jburnett/changelog
  • jburnett/proto-structure
  • jburnett/combine-step-and-definition-2
  • use-domain-step-result
  • v0.5.0
  • v0.4.0
  • v0.3.0
  • v0.2.1
  • v0.2.0
  • v0.1.0
26 results

step-runner

  • Clone with SSH
  • Clone with HTTPS
    • Joe Burnett's avatar
    Merge branch 'jburnett/dynamic-step-refs' into 'main'
    Joe Burnett authored 
    Allow expressions in step reference URLs

Closes #50

See merge request !115
    06b82133
    History
    Joe Burnett's avatar 06b82133
    History
    Name Last commit Last update
    cmd
    pkg
    proto
    schema/v1
    .gitignore
    .gitlab-ci.yml
    .tool-versions
    CONTRIBUTING.md
    Dockerfile
    HOWTO.md
    LICENSE
    Makefile
    README.md
    go.mod
    go.sum
    main.go
    README.md

    Step Runner

    Step Runner is an RFC implementation for GitLab Steps, a CI/CD feature to define and use reusable components within a single job execution context. See HOWTO.md for usage.

    Project status

    Step Runner is currently an experimental feature. It can be tested in GitLab CI/CD jobs but should not be used for production workloads yet.

    Contributing

    Contributions are welcome, see CONTRIBUTING.md for more details.

    Project License

    You can view this projects license in LICENSE.

    Release

    During the experimental phase all changes to main are automatically built as a Docker image and tagged in the container repository as v0. So any workflows referencing the image always use the latest version of the code, and behavior could change at any time. See HOWTO.md for an example of how to test the Step Runner in a job by using the container image.