Browse code

always allow rebuilding images regardless of which files changed

We still have to manually start image building jobs, and there is
no disadvantage to allowing rebuilding arbitrary images.

Joseph Weston authored on 09/09/2019 14:09:57
Showing 1 changed files
... ...
@@ -30,9 +30,6 @@ variables:
30 30
 
31 31
 build-env:ubuntu:
32 32
   <<: *build-env
33
-  only:
34
-    changes:
35
-      - docker/Dockerfile.ubuntu
36 33
   script:
37 34
     - /kaniko/executor
38 35
       --context $CI_PROJECT_DIR/docker
... ...
@@ -41,9 +38,6 @@ build-env:ubuntu:
41 38
 
42 39
 build-env:debian:
43 40
   <<: *build-env
44
-  only:
45
-    changes:
46
-      - docker/Dockerfile.debian
47 41
   script:
48 42
     - /kaniko/executor
49 43
       --context $CI_PROJECT_DIR/docker
... ...
@@ -52,10 +46,6 @@ build-env:debian:
52 46
 
53 47
 build-env:conda:
54 48
   <<: *build-env
55
-  only:
56
-    changes:
57
-      - docker/Dockerfile.conda
58
-      - docker/*.yml
59 49
   script:
60 50
     - /kaniko/executor
61 51
       --context $CI_PROJECT_DIR/docker
... ...
@@ -64,10 +54,6 @@ build-env:conda:
64 54
 
65 55
 build-env:default:
66 56
   <<: *build-env
67
-  only:
68
-    changes:
69
-      - docker/Dockerfile.conda
70
-      - docker/*.yml
71 57
   script:
72 58
     - /kaniko/executor
73 59
       --context $CI_PROJECT_DIR/docker