<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>Continuous Integration on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/continuous-integration/</link><description>Recent content in Continuous Integration on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Sun, 05 Aug 2018 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/continuous-integration/atom.xml" rel="self" type="application/rss+xml"/><item><title>Jenkins Integrated Robot Framework Automated Testing</title><link>https://www.chenshaowen.com/en/blog/jenkins-integrated-robot-framework-testing.html</link><pubDate>Sun, 05 Aug 2018 00:00:00 +0000</pubDate><atom:modified>Sun, 05 Aug 2018 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/jenkins-integrated-robot-framework-testing.html</guid><description>1. Installing a Headless Browser 1.1 Installing PhantomJS on CentOS Download and extract Visit Phantomjs, find the download link for Download phantomjs-2.1.1-linux-x86_64.tar.bz2, and copy it. Run the following commands on CentOS: 1 2 3 4 5 wget https://bitbucket.org/ariya/phantomjs/downloads/phantomjs-2.1.1-linux-x86_64.tar.bz2 # 如果没有安装 bzip2 可能会报</description><dc:creator>微信公众号</dc:creator><category>RobotFramework</category><category>Automation</category><category>Continuous Integration</category><category>Testing</category><category>DevOps</category><category>Jenkins</category><category>R&amp;D</category></item><item><title>Some Common CI Scripts</title><link>https://www.chenshaowen.com/en/blog/some-common-scripts-in-ci.html</link><pubDate>Tue, 17 Jul 2018 00:00:00 +0000</pubDate><atom:modified>Tue, 17 Jul 2018 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/some-common-scripts-in-ci.html</guid><description>Because I am responsible for the team&amp;rsquo;s shared CI matters, I often need to configure CI pipelines or help others solve problems, so I put together the CI scripts I use most often for easy reference. 1. Structure of .gitlab-ci.yml Below is the structure of a GitLab CI configuration file.</description><dc:creator>微信公众号</dc:creator><category>GitLab</category><category>GitLab-CI</category><category>CI</category><category>DevOps</category><category>Continuous Integration</category><category>R&amp;D</category></item><item><title>Frontend Webpack Practice of GitLab CI</title><link>https://www.chenshaowen.com/en/blog/front-webpack-practice-of-gitlab-ci.html</link><pubDate>Wed, 08 Nov 2017 09:15:56 +0000</pubDate><atom:modified>Wed, 08 Nov 2017 09:15:56 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/front-webpack-practice-of-gitlab-ci.html</guid><description>Starting with GitLab 8.0, GitLab began integrating CI (Continuous Integration) functionality. You only need to add a Runner on the server and a .gitlab-ci.yml file in the project, and you can run CI. In GitLab Setup and Configuration I recorded the whole process of setting up a GitLab service from</description><dc:creator>微信公众号</dc:creator><category>Frontend</category><category>Continuous Integration</category><category>Tools</category><category>DevOps</category><category>GitLab</category><category>CICD</category></item><item><title>Jenkins Pipeline Usage and Debugging</title><link>https://www.chenshaowen.com/en/blog/jenkins-pipeline-usging-and-debug.html</link><pubDate>Mon, 14 Aug 2017 13:13:55 +0000</pubDate><atom:modified>Mon, 14 Aug 2017 13:13:55 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/jenkins-pipeline-usging-and-debug.html</guid><description>1. Basic Concepts master master is where Jenkins is installed and runs; it is responsible for parsing job scripts, handling tasks, and scheduling compute resources. agent agent is responsible for handling tasks dispatched from master; the actual operations are executed through an executor. executor An executor is the compute resource</description><dc:creator>微信公众号</dc:creator><category>Jenkins</category><category>Pipeline</category><category>Continuous Integration</category><category>DevOps</category><category>CICD</category><category>Debugging</category><category>R&amp;D</category></item><item><title>Setting Up and Configuring GitLab</title><link>https://www.chenshaowen.com/en/blog/build-and-configure-of-gitlab.html</link><pubDate>Sat, 12 Aug 2017 00:51:07 +0000</pubDate><atom:modified>Sat, 12 Aug 2017 00:51:07 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/build-and-configure-of-gitlab.html</guid><description>1. Introduction GitLab is an open-source application developed with Ruby on Rails. It implements self-hosted Git project repositories, and public or private projects can be accessed through a web interface. It has features similar to GitHub, and can browse source code, manage defects and comments. It can manage team access</description><dc:creator>微信公众号</dc:creator><category>Tools</category><category>Management</category><category>Continuous Integration</category><category>GitLab</category><category>DevOps</category><category>Operations</category></item></channel></rss>