Laravel deployment using GitLab's pipelines
In my previous article, I explained the basics of Docker images and introduced a simple GitLab pipeline that runs our test suite and checks our code style. In this article, we will set up a more complex pipeline that ends up deploying our applications using Laravel Deployer 🚀. Full code on GitHub â¡Pipeline specifications Before diving into some code, let's take a minute to decide what we want our
Go tools and GitLab: How to do continuous integration like a boss
Go tools and GitLab: How to do continuous integration like a boss How the team at Pantomath makes their lives easier with GitLab CI. At Pantomath, we use GitLab for all our development work. The purpose of this paper is not to present GitLab and all its features, but to introduce how we use these tools to ease our lives. So what is it all about? To automate everything that is related to your devel
Introducing GitLab Container Registry
Introducing GitLab Container Registry Built on open source software, GitLab Container Registry isn't just a standalone registry; it's completely integrated with GitLab. Yesterday we released GitLab 8.8, super powering GitLab's built-in continuous integration. With it, you can build a pipeline in GitLab, visualizing your builds, tests, deploys and any other stage of the life cycle of your software.
Autoscale GitLab CI runners and save 90% on EC2 costs – Substrakt Health
Code quality is always a top priority for us. We want to know that our code works every time and when it stops working we want to know immediately. We use GitLab CI to run our tests every time we push new code and before every deployment. GitLab CI lets us split this work across multiple servers and scale up and down capacity as required to keep costs down for us. This tutorial will show you how t
Catch bugs systematically: how to build a GitLab CI testing pipeline in 4 steps
By Joyz Your first app is a hit the day it’s launched. But one week later, you realize that it has no retention. You discover that this is because whenever a user clicks the “send†button, their comments get posted twice. The bug was so minor, but it killed your momentum. But that’s okay. For your second app, you and your partner check more carefully. You both click, click, click your app all day
Gitlab CI を使ã£ã¦ã¿ã‚‹ãƒ¡ãƒ¢ - ngyukiã®æ—¥è¨˜
Jenkins ã‹ã‚‰ã®ç§»è¡Œã®ãŸã‚ã«ä»Šæ›´ã ã‘ã©ä½¿ã£ã¦ã¿ãŸãƒ¡ãƒ¢ã€‚ ãªãŠã€ã†ã¡ã® Gitlab ã¯ã‚½ãƒ¼ã‚¹ã‹ã‚‰å…¥ã‚Œã¦ã„ã¦ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚‚ MySQL ã§ã™ã€‚ãŸã¾ã«ã—ã‹ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚¢ãƒƒãƒ—ã—ã¦ã„ãªã„ã®ã§ã¡ã‚‡ã£ã¨å¤ã„ã§ã™(8.17.2)。 å‚考 https://docs.gitlab.com/ee/ci/ å…¬å¼ã®ãƒ‰ã‚ュメント https://docs.gitlab.com/ee/ci/yaml/README.html .gitlab-ci.yml ã®ãƒªãƒ•ã‚¡ãƒ¬ãƒ³ã‚¹ https://docs.gitlab.com/ee/ci/runners/README.html Runner ã®ãƒ‰ã‚ュメント https://docs.gitlab.com/runner/ å…¬å¼ã® Runner ã®å®Ÿè£…ã®ãƒ‰ã‚ュメント https://gitlab.com/gitlab-org/gitlab-ci-multi-runner ↑ã®ãƒª
ã€Review Apps】GitLab CI を使ã£ã¦ã€è‡ªå‹•ãƒ‡ãƒ—ãƒã‚¤ãƒ»è‡ªå‹•ãƒ¬ãƒ“ュー環境作æˆã‚’実ç¾ã™ã‚‹ | ãƒã‚·ãƒ£ãƒã‚°ã€‚
ã“ã‚“ã«ã¡ã¯ã€tanakaã§ã™ã€‚ゴールデンウィークä¸ã¯ã€ãƒ€ãƒ©ãƒ€ãƒ©ã¨éŽã”ã•ãªã„ãŸã‚ã«ã‚³ãƒ¯ãƒ¼ã‚ングスペースã®å‹‰å¼·ä¼šã¨ã‹ã«å‚åŠ ã—ã¦ã¾ã—ãŸã€‚ å‚åŠ ã—ãŸæ—¥ä»¥å¤–ã¯ãƒ€ãƒ©ãƒ€ãƒ©ã¨éŽã”ã—ã¦ã„ã¾ã—ãŸâ€¦ã€‚ 今日ã¯GitLab CI 㧠Review Apps を使ã£ã¦ã€gitリモートリãƒã‚¸ãƒˆãƒªã¸ã®åæ˜ ã¨åŒæ™‚ã«è‡ªå‹•ãƒ‡ãƒ—ãƒã‚¤ã—ãŸã‚Šã€ãƒ–ランãƒã‹ã‚‰ãƒ¬ãƒ“ュー環境を構築ã™ã‚‹æ–¹æ³•ã‚’紹介ã—ã¾ã™ã€‚ é¢å€’ãªä½œæ¥ã¯è‡ªå‹•åŒ–ã—ã¦ã€ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°ãªã©ã®ä½œæ¥ã«é›†ä¸ã§ãるよã†ã«ã—ãŸã„ã§ã™ã。 å‰æ é™çš„ブãƒã‚°ã‚¸ã‚§ãƒãƒ¬ãƒ¼ã‚¿ Hexo を使ã£ã¦ã‚³ãƒ³ãƒ†ãƒ³ãƒ„を生æˆã—ã¾ã™ 生æˆã—ãŸã‚³ãƒ³ãƒ†ãƒ³ãƒ„ã‚’ rsync ã§å…¬é–‹ã‚µã‚¤ãƒˆã‚„レビュー環境ã«ã‚³ãƒ”ーã—ã¾ã™ master ブランãƒã¸ã®æ›´æ–°ã¯è‡ªå‹•çš„ã«å…¬é–‹ã‚µã‚¤ãƒˆã«ã‚¢ãƒƒãƒ—ã•ã‚Œã¾ã™ã€‚ブランãƒã®æ›´æ–°ã¯ãƒ¬ãƒ“ュー環境ã«ã‚¢ãƒƒãƒ—ã•ã‚Œã¾ã™ã€‚(ブランãƒã”ã¨ã«ãƒ¬ãƒ“ュー環境ãŒä½œæˆã•ã‚Œã¾ã™) ブランãƒãŒ master ã«ãƒžãƒ¼ã‚¸ã•ã‚ŒãŸã‚Šã€å‰Šé™¤ã•ã‚Œ
Gitlab CIを使ã£ã¦Sphinxã®ãƒ‰ã‚ュメントを自動ã§PDFã«ãƒ“ルドã™ã‚‹ - once upon a time,
gitlab.comã¯è‡ªå‰ã§Docker image登録ã§ããŸã‚Šã€CIæŒã£ã¦ã„ãŸã‚Šã¨ä¾¿åˆ©ã§ã™ã。ã—ã‹ã‚‚ã€privateレãƒã‚¸ãƒˆãƒªã‚‚ãŠé‡‘ã‹ã‹ã‚‰ãªã„ã¨ã„ã†å¤ªã£è…¹ã€‚ 技術書典2ã«å‘ã‘ãŸãƒ¬ãƒã‚¸ãƒˆãƒªã¯gitlab.comã§ç®¡ç†ã—ã¦ã„ã¾ã™ã€‚ 今回ã¯å…±è‘—者ã«Python使ã„ãŒå¤šã„ãŸã‚Sphinxを使ã£ã¦æ›¸ã„ã¦ã„ã‚‹ã‚“ã§ã™ãŒã€Sphinxã¯common markã§ã‚‚書ã‘ã‚‹ã®ã§markdownã§ã‚‚æ–‡ç« ã‚’æ›¸ãã“ã¨ãŒå‡ºæ¥ã¾ã™ã€‚ å‰å›žã®è¨˜äº‹ã§ã¯ã€æ•°å¼å…¥ã‚Šã®markdownã‹ã‚‰PDFを生æˆã™ã‚‹Docker imageを作りã¾ã—ãŸãŒã€ãれを使ã†ã¨ç°¡å˜ã«Gitlab-CIã§PDFãŒç”Ÿæˆã§ãã¾ã™ã€‚ chezou.hatenablog.com ã‚„ã‚Šæ–¹ã¯ç°¡å˜ã€ã‚ãªãŸã®Sphinxã®ãƒ—ãƒã‚¸ã‚§ã‚¯ãƒˆã«ã€ä»¥ä¸‹ã®ã‚ˆã†ãª.gitlab-ci.ymlを書ãã ã‘。もã¡ã‚ã‚“ã€å¿…è¦ã«å¿œã˜ã¦pathsã¯å¤‰æ›´ã—ã¦ãã ã•ã„。 image: chezou
GitLabã§ãƒ‰ã‚ュメントã®ãƒ“ルドã¨ãƒ›ã‚¹ãƒ†ã‚£ãƒ³ã‚° - Blank File
完全ã«æ€ã„ã¤ãã§ã€GitLabã§ãƒ‰ã‚ュメントをgit管ç†ã—ã¦CIã§ãƒ“ルドã—ã¦GitLab Pagesã§è¡¨ç¤ºã™ã‚‹ã€ã¨ã„ã†ã®ã‚’ã‚„ã£ã¦ã¿ã¾ã—ãŸã€‚ GitLabã¯GitHubã¿ãŸã„ãªã‚µãƒ¼ãƒ“スã§ã™ã€‚ （ã¨ã„ã†ã‹GitHubクãƒãƒ¼ãƒ³ã§ã€ä»¥å‰ã¯ã‚ã¾ã‚Šã«ã‚‚ä¼¼éŽãŽã¦ãŸãŸã‚ã«ãªã‚“ã‹è‰²ã€…ã‚ã£ãŸã‚‰ã—ã„ã€ã¨ã„ã†ã‚¦ãƒ¯ã‚µã‚’ã©ã“ã‹ã§ç›®ã«ã—ãŸã‚ˆã†ãªãƒ»ãƒ»ãƒ»ï¼Ÿï¼‰ （ãã®ã›ã„ã‹ã‚ã‹ã‚Šã¾ã›ã‚“ãŒã€ãƒ—ルリクエストã¯Merge Requestã¨ã„ã†åå‰ã®ã‚ˆã†ã§ã™ã・・・） GitHubã§ã‚‚ä¼¼ãŸã‚ˆã†ãªã“ã¨ã¯ã§ãã¾ã™ãŒã€ Travis CI（ãªã©ã®CIサービス）を使ã£ã¦gh-pagesブランãƒã«ãƒ—ッシュã™ã‚‹ Read the Docsを使ã£ã¦ãã£ã¡ã§ãƒ“ルド＆表示 ãªã©ã„ãšã‚Œã«ã—ã‚別サービスã¨ã®é€£æºãŒå¿…è¦ã«ãªã£ã¦ã—ã¾ã„ã¾ã™ã€‚ ãƒãƒ¼ã‚«ãƒ«ã§htmlを作ã£ã¦è‡ªåˆ†ã§pushã™ã‚‹ã“ã¨ã‚‚ã§ãã¾ã™ãŒã€ãã‚Œã¯ä½•ã‹å°‘ã—è² ã‘ãŸæ°—ãŒã™ã‚‹ã®ã§å´ä¸‹ã§ã™ã€‚ GitLab
Building a new GitLab Docs site with Nanoc, GitLab CI, and GitLab Pages
Building a new GitLab Docs site with Nanoc, GitLab CI, and GitLab Pages How we built the new GitLab Docs portal from the ground up We recently rebuilt docs.gitlab.com from scratch. Where previously the site was generated with a simple Ruby script, we now use a proper static site generator. Check out the improvements we made, the structure we now use to deploy from specific directories in multiple
GitLab CI ã®å¸ƒæ•™ for iOS
8. セットアップ 1. Gitlab ã§CI を有効化 2. Macマシンã«MultiRunner をインストール 3. Runnerã®ç™»éŒ² Links Enable or disable GitLab CI Install on MacOS Setting up GitLab CI for iOS projects 9. ジョブã®ä½œæˆ リãƒã‚¸ãƒˆãƒªç›´ä¸‹ã«.gitlab-ci.ymlã‚’ç½®ã before_script: - echo "Start gitlab ci runner" - #Deploygateã®APIKeyãªã©ã¯ãƒžã‚·ãƒ³ä¸Šã«è¨å®š - . ~/.bashrc_runner - bundle install ios-master: stage: archive script: - #実行コマンド - bundle exec fastlane dg only: - #ブランãƒã‚’指定
GitLab CI x Docker ã®ã‚¹ã‚¹ãƒ¡
2016/11/1 Roppongi.rb ã§ã® LTã®è³‡æ–™ã§ã™ã€œ
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
gitlab-ci ã‚’ Google Compute Engine(GCE) ã§æœˆé¡100円以内ã§å›žã™ | tmnm.tech
ã“ã“ãŒã™ã”ã„よGitLab CI #gitlabjp
GitLab 10.1 ã« GitLab CI + GitLab Pages + Sphinx ã§ãƒ‰ã‚ュメントビルド環境を整ãˆã‚‹
7 ways to speed up your GitLab CI/CD times
移動ã—ã¾ã—㟠- SmartHR Tech Blog
GitLab CI + Review Apps ã§ç°¡æ˜“レビュー環境
https://bryce.fisher-fleig.org/faster-ci-debugging-with-gitlabci/
GitLab, Consumer Driven Contracts, Helm and Kubernetes
{{#tags}}- {{label}}
{{/tags}}