Skip to content

NimTechnology

Trình bày các công nghệ CLOUD một cách dễ hiểu.

  • Kubernetes & Container
    • Docker
    • Kubernetes
      • Ingress
      • Pod
    • Helm Chart
    • OAuth2 Proxy
    • Isito-EnvoyFilter
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Vault
    • Longhorn – Storage
    • VictoriaMetrics
    • MetalLB
    • Kong Gateway
  • CI/CD
    • ArgoCD
    • ArgoWorkflows
    • Argo Events
    • Spinnaker
    • Jenkins
    • Harbor
    • TeamCity
    • Git
      • Bitbucket
  • Coding
    • DevSecOps
    • Terraform
      • GCP – Google Cloud
      • AWS – Amazon Web Service
      • Azure Cloud
    • Golang
    • Laravel
    • Python
    • Jquery & JavaScript
    • Selenium
  • Log, Monitor & Tracing
    • DataDog
    • Prometheus
    • Grafana
    • ELK
      • Kibana
      • Logstash
  • BareMetal
    • NextCloud
  • Toggle search form

[Golang] Use -buildvcs=false to disable VCS stamping

Posted on June 18, 2024June 18, 2024 By nim No Comments on [Golang] Use -buildvcs=false to disable VCS stamping

Trong 1 lần mình build image trên bitbucket pipeline thì nó bị lỗi này:

INFO[0020] Args: [-c GOOS=linux go build -o app]        
INFO[0020] Running: [/bin/sh -c GOOS=linux go build -o app] 
error obtaining VCS status: exit status 128
	Use -buildvcs=false to disable VCS stamping.
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1

The -buildvcs=false flag in the go build command is used to disable VCS (Version Control System) stamping during the build process. This flag is particularly useful in environments where the Go compiler might face issues accessing the version control metadata, such as when building Docker images in isolated environments like CI/CD pipelines.

Contents

Toggle
  • Why Disable VCS Stamping with -buildvcs=false?
  • How to disable VCS Stamping

Why Disable VCS Stamping with -buildvcs=false?

  • Build Environments: In CI/CD pipelines, especially when building Docker images, the build environment may not have access to the VCS metadata, leading to errors.
  • Simpler Builds: Disabling VCS stamping can simplify the build process by avoiding the need for VCS metadata.
  • Performance: It can slightly improve build performance by skipping the collection of VCS information.

How to disable VCS Stamping

Adding the -buildvcs=false flag ensures that the build process does not fail due to missing VCS information.

refer to: https://www.reddit.com/r/golang/comments/x5e3ld/how_to_set_buildvcsfalse_as_default/

Bitbucket

Post navigation

Previous Post: [RabbitMQ] Queue announces “cluster is in minority”
Next Post: [Security] How to access S3 when you stay at any EC2!

More Related Articles

[Private NPM] Create The Private NPM Packages Bitbucket
[Kaniko/Bitbucket/ECR] Accomplish the workflow: CI by bitbucket pipeline, Kaniko build image and push image to ECR AWS - Amazon Web Service
[Bitbucket Pipeline] The deployment environment ‘xxx’ in your bitbucket-pipelines.yml file occurs multiple times in the pipeline. Please refer to our documentation for valid environments and their ordering. Bitbucket
[Bitbucket] You can run and make anything on Bitbucket Pipeline Bitbucket
[Bitbucket-pipelines] Lesson1: Creating Your First Pipeline Bitbucket
[Bitbucket] Git Clone/Pull/Push with Bitbucket through API Token. Bitbucket

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Tham Gia Group DevOps nhé!
Để Nim có nhiều động lực ra nhiều bài viết.
Để nhận được những thông báo mới nhất.

Recent Posts

  • [AWS/EKS] Cache Docker image to accelerate EKS container deployment. July 10, 2025
  • [Laravel] Laravel Helpful June 26, 2025
  • [VScode] Hướng dẫn điều chỉnh font cho terminal June 20, 2025
  • [WordPress] Hướng dấn gửi mail trên WordPress thông qua gmail. June 15, 2025
  • [Bitbucket] Git Clone/Pull/Push with Bitbucket through API Token. June 12, 2025

Archives

  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021

Categories

  • BareMetal
    • NextCloud
  • CI/CD
    • Argo Events
    • ArgoCD
    • ArgoWorkflows
    • Git
      • Bitbucket
    • Harbor
    • Jenkins
    • Spinnaker
    • TeamCity
  • Coding
    • DevSecOps
    • Golang
    • Jquery & JavaScript
    • Laravel
    • NextJS 14 & ReactJS & Type Script
    • Python
    • Selenium
    • Terraform
      • AWS – Amazon Web Service
      • Azure Cloud
      • GCP – Google Cloud
  • Kubernetes & Container
    • Apache Kafka
      • Kafka
      • Kafka Connect
      • Lenses
    • Docker
    • Helm Chart
    • Isito-EnvoyFilter
    • Kong Gateway
    • Kubernetes
      • Ingress
      • Pod
    • Longhorn – Storage
    • MetalLB
    • OAuth2 Proxy
    • Vault
    • VictoriaMetrics
  • Log, Monitor & Tracing
    • DataDog
    • ELK
      • Kibana
      • Logstash
    • Fluent
    • Grafana
    • Prometheus
  • Uncategorized
  • Admin

Copyright © 2025 NimTechnology.