rascal/features/run.feature at 1af7406921ba725babd54615b0652d761678161b · makandra/rascal · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
Feature: Run "run"

  Scenario: Run a command in the main container, without a TTY
    Given the following gitlab-ci config:
      """
      job:
        variables:
          foo: bar
        image: job-image:latest
      """
      And the docker image "job-image:latest" exists

    When I successfully run `rascal run job -- bundle exec rake`
    Then docker /container run --rm -a STDOUT -a STDERR -w \/repo -v .*:\/repo -v rascal-aruba-job-builds:\/builds -e foo=bar --network deadbeef job-image:latest bash -c bundle exec rake;/ should have been called
      And docker /--tty/ should not have been called


  Scenario: Start required services
    Given the following gitlab-ci config:
      """
      job:
        image: job-image:latest
        services:
          - name: service-1-image:latest
            alias: service-1
      """
      And the docker image "job-image:latest" exists
      And the docker image "service-1-image:latest" exists

    When I successfully run `rascal run job -- rake`
    Then docker /container create --name rascal-aruba-job_service-1/ should have been called


  Scenario: Wrap the command in before_shell and after_shell
    Given the following gitlab-ci config:
      """
      .rascal:
        before_shell:
          - bundle check
        after_shell:
          - echo bye
      job:
        image: job-image:latest
      """
      And the docker image "job-image:latest" exists

    When I successfully run `rascal run job -- rake`
    Then docker /container run .* bash -c bundle check;rake;__rascal_status=\$\?;echo bye;exit \$__rascal_status/ should have been called


  Scenario: Keep arguments containing spaces and shell metacharacters intact
    Given the following gitlab-ci config:
      """
      job:
        image: job-image:latest
      """
      And the docker image "job-image:latest" exists

    When I successfully run `rascal run job -- bundle exec ruby test/foo_test.rb -n '/a test name/'`
    Then docker /container run .* bash -c bundle exec ruby test\/foo_test.rb -n \/a\\ test\\ name\// should have been called


  Scenario: Exit with the status of the command
    Given the following gitlab-ci config:
      """
      job:
        image: job-image:latest
      """
      And the docker image "job-image:latest" exists
      And the container command will exit with 3

    When I run `rascal run job -- rake`
    Then the exit status should be 3


  Scenario: Exit with zero when the command succeeds
    Given the following gitlab-ci config:
      """
      job:
        image: job-image:latest
      """
      And the docker image "job-image:latest" exists

    When I run `rascal run job -- rake`
    Then the exit status should be 0


  Scenario: Complain about a missing command
    Given the following gitlab-ci config:
      """
      job:
        image: job-image:latest
      """
      And the docker image "job-image:latest" exists

    When I run `rascal run job`
    Then the exit status should not be 0
      And stderr should contain "Missing command"
      And docker /container run/ should not have been called


  Scenario: Complain about an unknown environment
    Given the following gitlab-ci config:
      """
      job:
        image: job-image:latest
      """

    When I run `rascal run nope -- rake`
    Then the exit status should not be 0
      And stderr should contain "Unknown environment nope. Available: job."
      And docker /container run/ should not have been called