[gjs: 1/5] CI: Don't run linters on tags



commit fd3b996549f358e938fba5b8bff555ad3f1fc043
Author: Philip Chimento <philip chimento gmail com>
Date:   Mon Jun 18 16:43:22 2018 -0700

    CI: Don't run linters on tags
    
    At the point when we've pushed a tag, it's too late to go back and fix
    linter errors, so there's no point in holding up the rest of the build if
    there's something wrong with the code style.
    
    In addition, they compare against master, so when tagging a commit that
    isn't the head of master, as we did today, it appears as if the tag has
    "introduced" new linter failures.

 .gitlab-ci.yml | 3 +++
 1 file changed, 3 insertions(+)
---
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index a2539498..e0306d54 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -225,6 +225,7 @@ cppcheck:
     CODECHECK: "CPPCHECK"
   except:
     - schedules
+    - tags
 
 cpplint:
   <<: *build
@@ -235,6 +236,7 @@ cpplint:
     CODECHECK: "CPPLINT"
   except:
     - schedules
+    - tags
 
 eslint:
   <<: *build
@@ -245,6 +247,7 @@ eslint:
     CODECHECK: "ESLINT"
   except:
     - schedules
+    - tags
 
 #############################################
 #         Daily jobs / Frequent jobs        #


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]