[B! docker][CI] TokyoIncidentsã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

TokyoIncidents id:TokyoIncidents

dockerã¨CIã«é–¢ã™ã‚‹TokyoIncidentsã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (10)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

CI ç”¨ Docker ã‚¤ãƒ¡ãƒ¼ã‚¸ä½œæˆã«ãŠã‘ã‚‹ãƒ™ã‚¹ãƒˆãƒ—ãƒ©ã‚¯ãƒ†ã‚£ã‚¹
H2O ã® CI ã§ã¯é•·ã‚‰ãã€ç§˜ä¼ã®ã‚¿ãƒ¬çš„ãª .travis.yml ã‚’ä½¿ã„ç¶šã‘ã¦ããŸã®ã§ã™ãŒã€ãªã«ã¶ã‚“ä¾å˜é–¢ä¿‚ãŒå¤šã„ã‚‚ã®ã§ã€ã ã„ã¶ãƒ¡ãƒ³ãƒ†ãƒŠãƒ³ã‚¹ãŒè¾›ã„æ„Ÿã˜ã«ãªã£ã¦ãã¦ã„ã¾ã—ãŸã€‚ã¾ãŸã€CI ãƒ†ã‚¹ãƒˆã§ç™ºç”Ÿã—ãŸã‚¨ãƒ©ãƒ¼ã®èª¿æŸ»ã®åº¦ã«ã€æ™‚é–“ã®ã‹ã‹ã‚‹ CI ã‚’å›žã•ãªã‘ã‚Œã°ãªã‚‰ãªã„ã“ã¨ãŒã€é–‹ç™ºè€…ã®ã‚¹ãƒˆãƒ¬ã‚¹ã¨ãªã£ã¦ã„ã¾ã—ãŸã€‚ ãã“ã§ä¸€å¿µç™ºèµ·ã—ã¦ã€Docker ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’ä½¿ã£ãŸ CI ã«åˆ‡ã‚Šæ›¿ãˆã‚‹ã“ã¨ã«ã—ã¾ã—ãŸï¼ˆå®Ÿè¡Œç’°å¢ƒã¨ã—ã¦ã¯å¼•ãç¶šã Travis ã‚’ä½¿ã„ã¾ã™ï¼‰ã€‚ ãã®éš›ã«ã€è¦ä»¶ã¨ã—ã¦ä»¥ä¸‹ã®ã‚ˆã†ãªã“ã¨ã‚’è€ƒãˆã¾ã—ãŸã€‚ CIä»¥å¤–ã«ã€ã‚³ãƒŸãƒƒãƒˆå‰ã®ãƒ†ã‚¹ãƒˆã«ã‚‚ä½¿ãˆã‚‹ã‚ˆã†ãªã‚¤ãƒ¡ãƒ¼ã‚¸ã«ã™ã‚‹ã“ã¨ ã‚³ãƒžãƒ³ãƒ‰ä¸€ç™ºã§ãƒ“ãƒ«ãƒ‰ã¨ãƒ†ã‚¹ãƒˆãŒå‹•ä½œã™ã‚‹ã“ã¨ ç„¡é§„ãªå‡¦ç†ã‚’ã—ãªã„ã“ã¨ ãã®çµæžœã€ä»¥ä¸‹ã®ã‚ˆã†ãªå®Ÿè£…ã«ãªã‚Šã¾ã—ãŸã€‚ ãƒ†ã‚¹ãƒˆã«å¿…è¦ãªã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ç¾¤ã‚’ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ãŸã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’ Docker Hub ã«ã‚¢ãƒƒãƒ—ãƒãƒ¼ãƒ‰ã—ã¦ãŠã ãƒ†ã‚¹ãƒˆã«ã¯ã€1.
TokyoIncidents 2017/12/28
docker

ci
ãƒªãƒ³ã‚¯
How to build a CI/CD pipeline with Docker
The goal of every software team is to minimize the gap between conception, implementation, and deployment to maximize competitive advantage. Yet speed should not come at the expense of the application integrity or customer (user) experience. To help with this, many teams integrate a continuous integration/continuous deployment (CI/CD) pipeline into their development process. With CI/CD, you get sp
TokyoIncidents 2017/11/15
ci

docker
ãƒªãƒ³ã‚¯
CircleCI 2.0ã®workflowsã‚’åˆ©ç”¨ã—ã¦ã„ã„æ„Ÿã˜ã«docker-composeã‚’cacheã™ã‚‹ - Qiita
å‰ç½®ã CircleCIã®workflowã§ä¸Šæ‰‹ã„ã“ã¨docker-composeã®é‡ã„å‡¦ç†ã‚’ãªã‚“ã¨ã‹ã™ã‚‹ã®ã‚’ã‚„ã£ã¦ã¿ãŸã€‚ ä»Šå›žã¯docker-composeã®buildå‡¦ç†ãŒé‡ãã¦testä¸¦åˆ—åŒ–ã™ã‚‹ã¨ãã“ãŒãƒœãƒˆãƒ«ãƒãƒƒã‚¯ã«ãªã‚‹ã‚ˆã†ãªå ´åˆã‚’æƒ³å®šã—ã¦ã„ã‚‹ã€‚ buildè‡ªä½“ãŒé‡ããªã„å ´åˆã‚„ä¸¦åˆ—åŒ–ãŒä¸è¦ãªå ´åˆã¯ã€ã‚€ã—ã‚cacheç”Ÿæˆãƒ»å‘¼ã³å‡ºã—ã§é…ããªã‚‹ãƒ‘ã‚¿ãƒ¼ãƒ³ã‚‚ã‚ã‚‹ã€‚ Enabling Docker Layer Cachingãªã©å…¬å¼ã®dockerã‚ãƒ£ãƒƒã‚·ãƒ¥ã‚‚ã‚ã‚‹ãŒã€machineãƒ¢ãƒ¼ãƒ‰ã§ãªã„ã¨docker-composeãŒãƒ•ãƒ«ã«åˆ©ç”¨ã§ããªã„ï¼ˆvolumesãŒåˆ©ç”¨ã§ããªã„ï¼‰ã®ã§save_cache / restore_cacheã‚’ä½¿ã†ã‚„ã‚Šæ–¹ã‚’è‰²ã€…ã²ãã£ãŸã€‚ æ‰‹å§‹ã‚ã«dockerã‚’cacheã—ã¦ã¿ã‚‹ docker-composeã«é£›ã³ã¤ãå‰ã«ã€dockerå˜ä½“ã®pullã¨testã‚’workflowã§
TokyoIncidents 2017/08/07
ci

docker
ãƒªãƒ³ã‚¯
Androidã®CIã¯Dockerã§ãƒ“ãƒ«ãƒ‰ã™ã‚‹ã®ãŒæ¥½ - Qiita
è¿½è¨˜: å®Ÿéš›ã«é‹ç”¨ã™ã‚‹éš›ã¯ãƒ©ã‚¤ã‚»ãƒ³ã‚¹ã«ã”æ³¨æ„ãã ã•ã„: å…¬é–‹ç”¨Dockerã‚¤ãƒ¡ãƒ¼ã‚¸ã«Android SDKã‚’å«ã‚ã‚‹ã®ã¯ãƒ©ã‚¤ã‚»ãƒ³ã‚¹é•åã¨ã„ã†è©± - Islands in the byte stream ä¸‰è¡Œã¾ã¨ã‚ ç¤¾å†…ã®Jenkinsç’°å¢ƒ / Travis-CI / Circle-CI ãªã©ã€CIã‚µãƒ¼ãƒ“ã‚¹ã”ã¨ã«ãƒ“ãƒ«ãƒ‰è¨å®šã‚’èª¿ã¹ã‚‹ã®ã«ã†ã‚“ã–ã‚Šã—ãŸã®ã§Dockerizeã—ã¦ã¿ãŸ æ‰‹å…ƒã¨CIç’°å¢ƒãŒã¾ã£ãŸãåŒã˜ã«ãªã‚‹ã®ã§ä¸€åº¦å‹•ãã‚ˆã†ã«ãªã£ãŸã‚‰å®‰å®šã—ã¦å‹•ã‹ã›ã‚‹ã¯ãš ã¨ã‚Šã‚ãˆãšCircle-CIã§è©¦ã—ã¦å‹•ã„ãŸ å‰æ OSXã®å ´åˆã€boot2dockerã¨dockerã‚’homebrewã§å…¥ã‚Œã¾ã—ã‚‡ã†ã€‚boot2dockerã¯dockerã‚’å‹•ã‹ã™ãŸã‚ã®VMã¨Linuxã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’é©å½“ã«æ•´ãˆã¦ãã‚Œã‚‹ã‚„ã¤ã§ã™ã€‚ Dockerfile Dockerfile ã¯ã“ã‚“ãªæ„Ÿã˜ã€‚samtstern/android-sdk
TokyoIncidents 2015/03/09
Android

docker

ci
ãƒªãƒ³ã‚¯
Automating peco releases via Docker : D-7 <altijd in beweging>
ã€Œãªã‚“ã‹å¤–éƒ¨CIã‚µãƒ¼ãƒ“ã‚¹ã ã‚‹ã„ãªãƒ¼ã€ã€Œãƒªãƒªãƒ¼ã‚¹ã¨ã‹ã‚‚ã†ãƒãƒ¼ã‚«ãƒ«ã®ç’°å¢ƒã§ã‚„ã‚ŠãŸã„ãªãƒ¼ã€ã€Œãƒžã‚·ãƒ³å–ã£æ›¿ãˆã¦ã‚‚ã™ãç’°å¢ƒä½œã‚Œã‚‹ã‚ˆã†ã«ã—ãŸã„ãªãƒ¼ã€ãªã©ãªã©ã®æ¬²æ±‚ãŒã‚ã£ãŸã®ã¨ã€go1.4ãŒãƒªãƒªãƒ¼ã‚¹ã•ã‚ŒãŸã®ã‚‚ã‚ã£ã¦Dockerã§å…¨éƒ¨è‡ªå‹•åŒ–ã—ã¦ã¿ãŸã€‚ æˆ¦ç•¥ã¨ã—ã¦ã¯ Travis CIã¨ã‹ã®é€£æºã¯æ®‹ã™ã‘ã©ã€æ‰‹å…ƒã§ã„ã¤ã§ã‚‚åŒæ§˜ã®ãƒ†ã‚¹ãƒˆã‚’èµ°ã‚‰ã›ã‚‰ã‚Œã‚‹ã‚ˆã†ã«ã—ã¦ãŠããƒªãƒªãƒ¼ã‚¹ã¯æ‰‹å…ƒã§ãƒãƒ¼ã‚¸ãƒ§ãƒ³æŒ‡å®šã™ã‚Œã°åŸºæœ¬çš„ã«ä¸€ç™ºã§é€šã‚‹ã‚ˆã†ã«ã—ã¦ãŠãå®Ÿè£…ã¯å˜ç´”ã§ã€ubuntuãƒ™ãƒ¼ã‚¹ã®ã‚¤ãƒ¡ãƒ¼ã‚¸ã«å¿…è¦ãªgoã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã¨ãƒ„ãƒ¼ãƒ«é¡žï¼ˆgoxcã¨ghrï¼‰ã‚’å±•é–‹ã—ã¦ãŠã„ã¦ã€pecoã®ãƒ‡ã‚£ãƒ¬ã‚¯ãƒˆãƒªã¯å¾Œã‹ã‚‰docker run -vã§ãƒžã‚¦ãƒ³ãƒˆã§ãã‚‹ã‚ˆã†ã«ã—ã¦ãŠãã€‚ ä½¿ã†æ™‚ã¯å…ˆã«ã‚¤ãƒ¡ãƒ¼ã‚¸ã‚’ä½œæˆã—ã¦ãŠãï¼ˆã‚ãƒ£ãƒƒã‚·ãƒ¥ä½¿ã£ã¦ã‚‹ã‹ã‚‰å½“ç„¶ç´ æ—©ãèµ°ã‚Šã¾ã™ãï¼ï¼‰
TokyoIncidents 2014/12/16
docker

ci
ãƒªãƒ³ã‚¯
CircleCI
Run CI/CD workflows in Docker for reliable, deterministic testing. Automatically build and deploy your applications in any environment with best-in-class CI/CD.
TokyoIncidents 2014/08/21
ci

docker
ãƒªãƒ³ã‚¯
CIï¼ˆç¶™ç¶šçš„çµ±åˆï¼‰as a Serviceã®ã€ŒCircle CIã€ãŒDockerå¯¾å¿œã‚’é–‹å§‹
Githubã«ã‚³ãƒ¼ãƒ‰ã‚’ãƒ—ãƒƒã‚·ãƒ¥ã™ã‚‹ã¨è‡ªå‹•çš„ã«ã‚³ãƒ¼ãƒ‰ã‚’å–ã‚Šè¾¼ã‚“ã§ãƒ“ãƒ«ãƒ‰ãŒè¡Œã‚ã‚Œã€ãƒ†ã‚¹ãƒˆãŒèµ°ã‚‹ã€‚ã„ã‚ã‚†ã‚‹ã€ŒCIï¼šContinuous Integrationï¼ˆç¶™ç¶šçš„çµ±åˆï¼‰ã€ã‚’å®Ÿç¾ã™ã‚‹CI as a Servicesã‚’æä¾›ã™ã‚‹ã€ŒCircle CIã€ãŒã€Dockerå¯¾å¿œã«ã‚ˆã‚‹ç¶™ç¶šçš„ã‚¤ãƒ³ãƒ†ã‚°ãƒ¬ãƒ¼ã‚·ãƒ§ãƒ³ï¼ç¶™ç¶šçš„ãƒ‡ãƒªãƒãƒªã®é–‹å§‹ã‚’ç™ºè¡¨ã—ã¾ã—ãŸã€‚ Dockerãƒ•ã‚¡ã‚¤ãƒ«ã«ã‚ˆã£ã¦Circle CIã§è¡Œã†ãƒ“ãƒ«ãƒ‰ã¨ãƒ†ã‚¹ãƒˆç’°å¢ƒã‚’å®šç¾©ã§ãã‚‹ãŸã‚ã€é–‹ç™ºç’°å¢ƒã¨ãƒ†ã‚¹ãƒˆç’°å¢ƒã€ãƒ‡ãƒ—ãƒã‚¤å…ˆã®ç¨¼åƒç’°å¢ƒãªã©ã®é•ã„ã‚’äº‹å®Ÿä¸Šãªãã›ã‚‹ã“ã¨ãŒå¤§ããªåˆ©ç‚¹ã ã¨èª¬æ˜Žã•ã‚Œã¦ã„ã¾ã™ã€‚ You can now use all Docker functionality within our build environments. All of the usual Docker commands work as expected, so you can bu
TokyoIncidents 2014/08/12
ci

docker
ãƒªãƒ³ã‚¯
ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ç‰ˆDroneã§ã€è‡ªä½œã®Docker imageã‚’ä½¿ã£ã¦ãƒ“ãƒ«ãƒ‰ã‚’è¡Œã†æ–¹æ³• - Yosssi's blog
ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ç‰ˆDroneã§ã€è‡ªä½œã®Docker imageã‚’ä½¿ã£ã¦ãƒ“ãƒ«ãƒ‰ã‚’è¡Œã£ã¦ã¿ã¾ã—ãŸã®ã§ã€ãã®æ–¹æ³•ãƒ»æ‰‹é †ã‚’å…±æœ‰ã—ã¾ã™ã€‚ ä»Šå›žã¯ã€Go 1.2ã¨Mongo DB 2.4ãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸDocker imageã‚’ä½œæˆã—ã€Droneã§ã¯ãã®Docker imageã‚’ä½¿ã£ã¦ãƒ“ãƒ«ãƒ‰ã‚’è¡Œã„ã¾ã™ã€‚ ãªãŠã€Droneã®servicesã¨ã„ã†æ©Ÿèƒ½ã‚’ä½¿ã†ã“ã¨ã§ãƒ“ãƒ«ãƒ‰æ™‚ã«ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚’ä½¿ç”¨ã§ãã‚‹ãŸã‚ã€é€šå¸¸ã¯ã€ä»Šå›žã®ã‚ˆã†ãªMongo DBãŒã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã•ã‚ŒãŸDocker imageã‚’ä½¿ã†å¿…è¦ã¯ã‚ã‚Šã¾ã›ã‚“ã€‚ä»Šå›žã¯ç·´ç¿’ã¨ã—ã¦ã“ã®ã‚ˆã†ãªDocker imageã‚’ä½œæˆã—ã¦ã„ã¾ã™ã€‚ãŸã ã—ã€Droneã®servicesã§ã¯ã€ç¾åœ¨ã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã‚’æŒ‡å®šã™ã‚‹ã“ã¨ãŒã§ãã¾ã›ã‚“ã®ã§ã€ã‚‚ã—ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã®ç‰¹å®šã®ãƒãƒ¼ã‚¸ãƒ§ãƒ³ã§ãƒ“ãƒ«ãƒ‰ã‚’è¡Œã„ãŸã„å ´åˆã¯ã€ä»Šå›žã®ã‚ˆã†ã«ã€ãƒ“ãƒ«ãƒ‰æ™‚ã«ä½¿ç”¨ã™ã‚‹ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚’ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«ã—ãŸDocker
TokyoIncidents 2014/02/10
docker

ci
ãƒªãƒ³ã‚¯
Drone and Docker, Open Source CI Â· drone.io
Posted by Brad Rydzewski on 2014-02-05 Today weâ€™re excited to announce an open source edition of the Drone CI server! You can find the project at github.com/drone/drone And a very nice writeup in VentureBeat by Jordan Novet: Drone.ioâ€™s shift hints at the future of sending software to clouds Built on Docker We believe containers have a bright future and weâ€™re ready to make a big bet on Docker. Dr
TokyoIncidents 2014/02/08
CI

docker
ãƒªãƒ³ã‚¯
ScaleOut | Supership
2024å¹´4æœˆ1æ—¥ã‚ˆã‚Šã€Supershipæ ªå¼ä¼šç¤¾ã¯è¦ªä¼šç¤¾ã§ã‚ã‚‹Supershipãƒ›ãƒ¼ãƒ«ãƒ‡ã‚£ãƒ³ã‚°ã‚¹æ ªå¼ä¼šç¤¾ã«å¸åŽåˆä½µã•ã‚Œã¾ã—ãŸã€‚ åˆä½µã«ä¼´ã„ã€å˜ç¶šä¼šç¤¾ã§ã‚ã‚‹Supershipãƒ›ãƒ¼ãƒ«ãƒ‡ã‚£ãƒ³ã‚°ã‚¹ã¯ç¤¾åã‚’Supershipã«å¤‰æ›´ã—ã€æ–°ãŸãªçµŒå–¶ä½“åˆ¶ã‚’ç™ºè¶³ã—ã¾ã—ãŸã€‚æœ¬ä»¶ã«é–¢ã™ã‚‹è©³ç´°ã¯ã€ãƒ—ãƒ¬ã‚¹ãƒªãƒªãƒ¼ã‚¹ã‚’ã”ç¢ºèªãã ã•ã„ã€‚ 2024å¹´4æœˆ1æ—¥ã‚ˆã‚Šã€Supershipæ ªå¼ä¼šç¤¾ã¯è¦ªä¼šç¤¾ã§ã‚ã‚‹Supershipãƒ›ãƒ¼ãƒ«ãƒ‡ã‚£ãƒ³ã‚°ã‚¹æ ªå¼ä¼šç¤¾ã«å¸åŽåˆä½µã•ã‚Œã¾ã—ãŸã€‚ åˆä½µã«ä¼´ã„ã€å˜ç¶šä¼šç¤¾ã§ã‚ã‚‹Supershipãƒ›ãƒ¼ãƒ«ãƒ‡ã‚£ãƒ³ã‚°ã‚¹ã¯ç¤¾åã‚’Supershipã«å¤‰æ›´ã—ã€æ–°ãŸãªçµŒå–¶ä½“åˆ¶ã‚’ç™ºè¶³ã—ã¾ã—ãŸã€‚ æœ¬ä»¶ã«é–¢ã™ã‚‹è©³ç´°ã¯ã€ãƒ—ãƒ¬ã‚¹ãƒªãƒªãƒ¼ã‚¹ã‚’ã”ç¢ºèªãã ã•ã„ã€‚
TokyoIncidents 2013/06/19
JavaScript
ãƒªãƒ³ã‚¯
1