DevOps on Time Friend

Continuous Integration - Code Quality Scanning

Sun, 15 Dec 2019 23:15:00 +0000

To facilitate managing company code quality, integrating code quality scanning with continuous integration is an important step. Currently the company is relatively young, but in just one year, we’ve had close to 300 frontend projects.

With so many frontend projects, how we ensure code quality becomes a very important matter.

With too many code projects, code review is necessary. But manual code review cannot guarantee efficiency. Due to differences in individual levels and familiarity with company standards, we cannot guarantee consistent standards across all projects. Some potential bugs may also be missed.

Continuous Integration - Using GitLab CI for Frontend Project Continuous Integration

Fri, 20 Sep 2019 23:15:00 +0000

There are many continuous integration platforms on the market. Today I’ll introduce GitLab’s CI.

Starting from GitLab 8.0, GitLab CI has been integrated into GitLab.

Usage is very simple. As long as we create a .gitlab-ci.yml file in the project root directory and add a Runner, we directly integrate GitLab CI.

Integration method is very simple and convenient. Currently we put a .gitlab-ci.yml file in the front-end scaffold, and every subsequent front-end project can directly integrate GitLab CI according to standards.

A Bug Caused by .gitattributes File from Two Years Ago

Thu, 24 Jan 2019 19:33:33 +0000

Cause

On a whim, I opened a frontend project I wrote two years ago to start code review. I wrote this project alone for two years, roughly over a hundred thousand lines of code.

Found that Git in this project recognized all code files as binary files. This problem had troubled me for a long time, but I couldn’t find the cause. This led to my code having no diff history.

Git Case-Insensitive Causing Annoying Problem

Wed, 09 Jan 2019 19:33:33 +0000

Because a colleague changed a folder name from lowercase to uppercase, I couldn’t directly push, rebase and other operations locally. Very annoying~

error: The following untracked working tree files would be overwritten by checkout:
 xxx.js
Please move or remove them before you can switch branches.
Aborting

Solution

Set to case-sensitive (must restore configuration after problem is solved)

git config core.ignorecase false

Although setting case-sensitive will always affect code in other branches, so it’s not recommended to use this configuration permanently. After the problem is solved, it should be changed back.

Automated Deployment of Hugo, Hexo Blog with Travis CI

Tue, 20 Nov 2018 16:14:25 +0000

What is Travis CI?

Travis CI is an online hosted CI service. Using Travis for continuous integration doesn’t require setting up your own server. Most importantly, it’s free for open source projects. If company uses gitlab, it also provides corresponding continuous integration services. Won’t elaborate here.

Travis CI Configuration File

Travis requires project root directory must have a .travis.yml file.

When your repository has commits, travis will automatically execute the behaviors you configured below.

Git Delete All Commit History Solution

Tue, 30 Oct 2018 19:33:33 +0000

If your previous project committed some sensitive data, or you want to clear previous commit history, here’s the solution.

# 1. Check out a new branch
git checkout --orphan latest_branch

# 2. Stage all files
git add -A

# 3. Commit the staged files
git commit -am "commit message"


# 4. Delete the original branch
git branch -D master

# 5. Rename the current branch
git branch -m master

# 6. Push your history to the remote repository
git push -f origin master

Git Push Stuck Solution

Mon, 09 Apr 2018 19:33:33 +0000

The blog’s daily English is directly scraped from Shanbay English. To avoid directly requesting proxy interfaces (which would be relatively slow). So my program generates corresponding data files every day, and the frontend directly gets them via ajax. Blog content is also automatically published every day, achieving the effect of updating famous quotes and sentences daily. Haven’t checked for a long time, found many git commits weren’t pushed. After manually pushing, found there were over 800 modifications not pushed.

Git Series - About the Add Command

Sun, 10 Sep 2017 19:33:33 +0000

Basic Usage

Usually add <path> to the index library through the form git add <path>,

<path> can be a file or a directory:

git add <path>

If there are many changes, you can use the following command to add all changed files at once:

 git add -A .

Add all modifications to the staging area, including new files and edited files, excluding deleted files:

$ git add .

Means add all content:

Automated Deployment Frontend Code - Using grunt-ftp-deploy

Sun, 14 Jun 2015 23:36:00 +0000

Every time after modifying code, need to deploy to remote server, my operation steps are:

Modify code –> grunt build –> Open FileZilla –> Login ftp server –> Find local folder –> Find remote server target folder –> Select all local files –> Upload

Because deploying code, at some times will be particularly frequent. Every time need to repeat the above eight operations. Want to do something, change this.

Today our protagonist: grunt-ftp-deploy

Annoying AngularJS Annotations - Using grunt-ng-annotate

Fri, 12 Jun 2015 23:15:00 +0000

Angular added dependency injection

When writing code, roughly written as follows

 app.controller('tempController', function($scope, $http, $state, $timeout) {

 ...

 })

But such code, after compression will cause a problem. Function parameters: $scope, $http, $state, $timeout will become: a,b,c,d

Causing this function cannot find services to inject, because each parameter’s naming is strictly required.

As follows:

 app.controller('tempController', function(a,b,c,d) {

 ...

 })

To solve this problem, angular supports the following writing: