semaphoreci/spc

Tooling for compiling and evaluating pipelines on Semaphore 2.0.

Semaphore Pipeline Compiler (SPC)

Tooling for compiling and evaluating pipelines on Semaphore 2.0.

Release Process

Releases are built by Sempahore for every git tag on Github. To initialize the release process:

1. go to the project root
2. Run make tag.patch (or make tag.minor, or make tag.major) to bump and push a new tag to Github
3. Semaphore will take over, and execute the .semaphore/release.yml.

On Sempahore, we use GoReleaser to create releases. Its configuration is stored in .goreleaser.yml.

spc's Issues

Feature request - ignore keys

Hi, is it possible to add some kind of syntax to allow semaphore to ignore specific keys in pipeline configuration
example and usecase
https://www.netways.de/en/blog/2019/11/21/gitlab-ci-yaml-write-less-with-anchors-extends-and-hidden-keys/
https://medium.com/@kinghuang/docker-compose-anchors-aliases-extensions-a1e4105d70bd

Currently if I try to use this pattern semaphore will throw this error

Unprocessable YAML file.
Error: [{"Schema does not allow additional properties.", "#/.defaults"}]

[Feature Request] Support value property in env_var for promotions

The current solution is to use the options with default_value, but that leads to awkward dx inside the actual semaphore CI (you see only one option in the option list when promoting)

It would be much cleaner to just support value so that the options field could hide and also free text is also supported.

promotions:
  - name: Upload to Saucelabs
    pipeline_file: saucelabs.yml
    auto_promote:
      when: "result = 'passed'"
    parameters:
      env_vars:
        # This works 
        - name: BUILD_TARGET
          required: true
          default_value: beta
          options:
            - beta
        # This breaks with the following error
        # Unprocessable YAML file.
        # Error: [{"Schema does not allow additional properties.", "#/promotions/env_vars/1/value"}]
        - name: PLATFORM
          value: android

[Feature Request] environment variable support in when conditions

when doesn't currently support environment variables. The current workaround is to add env var checks inside our own scripts.

if [ SOME_ENV_VAR = true ]; then run commands; else echo "skip commands"; fi

It would be very useful to have access to env variables in the when condition so that these scripts do not have to be more complicated.

...
blocks:
  - name: 'Distribute iOS build'
    skip: 
      when: $PLATFORM == 'android'
...

If other env notation is not usable, it could be at the same level as the change_in function:

...
blocks:
  - name: 'Distribute Android build'
    skip: 
      when: "env(PLATFORM) == 'ios'"
...