免费视频一区二区三区在线观看,中文字幕有码在线视频,国产在线91

JENKINS 部��v agularjs

paulwong — Tue, 25 Jan 2022 03:02:00 GMT

This article assumes that you have a running Jenkins instance on your Linux machine with a valid domain (not localhost), GitLab and that you are familiar with the Angular framework.

For Jenkins, please install the GitLab and NodeJS plugins. For simplicity’s sake, this article is going to use simple shell commands to run automated tests and to deploy an app to production.

***Note. If you can’t decide where to test all this, there is an article I wrote that might help you: CI/CD Cloud Voyage with Jenkins.

Configuring Gitlab and Jenkins

Jenkins: Access Rights to GitLab

In order to use GitLab with Jenkins, you’ll need to generate an access token in GitLab, which you can do in User menu > Settings > Access tokens

and configure GitLab Connection on Jenkins by adding the newly generated token.

In Jenkins, go to Manage Jenkins > Configure system and find the GitLab section.

To add a token that you previously generated, click on Add by the Credentials input and choose Jenkins. In the credentials dialog, choose GitLab API token in the Kind input and paste your token from GitLab into the API token input field.

Jenkins: Configure NodeJSInstaller

In order to be able to run npm scripts, it is necessary to configure NodeJSInstaller. In Jenkins, go to Manage Jenkins > Global Tool Configuration > NodeJS installations.

Jenkins: Create CI build for Angular

In order to be able to run Angular tests and check your code style in Jenkins on the created merge request in GitLab you’ll have to:

1. Click on the New item link in the Jenkins dashboard

2. Enter a job name and choose Freestyle project

3. Choose the GitLab Connection that we’ve just created in the Gitlab Connection section.

4. Choose Git as your source code management. Enter your repository URL. Create new credentials on Jenkins. These credentials are for cloning the project. You use them to log in to Gitlab.

5. Next, configure build triggers, i.e. on which GitLab event to run a build. In this particular example, angular-ci-build is going to trigger when a new merge request gets created.

In this step, we need to go back to GitLab and create a hook that will trigger this build under Settings > Integrations. Copy the URL provided by Jenkins and paste it into the project hook form and finally click Add webhook.

6. Provide the configured NodeJsInstaller in the global configuration to be able to run npm commands.

7. And finally, in the Build section choose Add build step > Execute shell. Write shell scripts to test the Angular app code and run tests.

Click Save and we are good to go. At this point everything should work.

When you create a new merge request, GitLab should trigger angular-ci-build on Jenkins and you should see status pending on that particular merge request page.

When Jenkins is done, the status on GitLab should automatically be updated. Depending on whether the build passed or not, the merge button will change color.

Jenkins: Create CD Build for Angular

In order to be able to deploy Angular to another Linux machine, we need to:

Repeat steps 1–4 from Jenkins: Create CI Build for Angular, changing only the name of the build. This time, it can be angular-deploy.

5. For step five, we now choose a different configuration for deployment. We are going to run this build when a merge request gets accepted.

Just like for the CI build, we have to create a new GitLab hook that will hit the Jenkins build endpoint.

6. This step is also the same as in CI; we need to provide the NodeJSInstaller we already configured globally.

7. This step is different from CI; this time we don’t have to test and check linting, but only build the application and copy-paste it to another machine with ssh.

If we are going to do it with ssh like in the example, we need to create a private and public key pair for the Jenkins user on the machine Jenkins is running on. The private key needs to stay on the Jenkins machine, and the public key needs to be copied to the remote machine.

With the scp command we simply copy our build to the remote machine. In this case, Jenkins does not have permission to put it anywhere but in the user folder. In the last step, we need to ssh into the remote machine and move our files (in this case to /var/www/html).

Voila, our app is deployed to the production server when the merge request is accepted via Jenkins.

Angular: Karma Unit Test Runner Configuration

To run Angular tests on Jenkins, we need to configure some parts of the karma.conf file. Below is the configuration that adds a custom launcher that runs ChromeHeadles.

module.exports = function(config) {   config.set({     basePath: "",     frameworks: ["jasmine", "@angular-devkit/build-angular"],     plugins: [       require("karma-jasmine"),       require("karma-chrome-launcher"),       require("karma-jasmine-html-reporter"),       require("karma-coverage-istanbul-reporter"),       require("@angular-devkit/build-angular/plugins/karma")     ],     client: {       clearContext: false // leave Jasmine Spec Runner output visible in browser     },     coverageIstanbulReporter: {       dir: require("path").join(__dirname, "../coverage/jenkins-test-app"),       reports: ["html", "lcovonly", "text-summary"],       fixWebpackSourcePaths: true     },     reporters: ["progress", "kjhtml"],     port: 9876,     colors: true,     logLevel: config.LOG_INFO,     autoWatch: true,     browsers: ["Chrome", "ChromeHeadless"],     singleRun: false,     restartOnFileChange: true,     customLaunchers: {       ChromeHeadless: {         base: "Chrome",         flags: [           "--headless",           "--disable-gpu",           "--no-sandbox",           "--remote-debugging-port=9222"         ],                },     }   }); };

We can then simply store our command in the package.json scripts property.

On Jenkins, we would now run our tests with npm run test:ci.

 "scripts": {     "ng": "ng",     "start": "ng serve",     "build": "ng build",     "test": "ng test",     "test:ci": "ng test --browsers=ChromeHeadless --watch=false",     "lint": "ng lint",     "e2e": "ng e2e"   },

I hope you enjoyed this article and that it was helpful in your quest for automating angular deployment and testing.

paulwong 2022-01-25 11:02 发表评论

Jenkins environment variables

paulwong — Mon, 16 Aug 2021 07:46:00 GMT

https://medium.com/@mukeshsingal/access-jenkins-global-environment-variables-using-groovy-or-java-b5c1e6b53685

paulwong 2021-08-16 15:46 发表评论

【DevOps】Jenkins��d��Z��Tag�q�行构徏

paulwong — Thu, 22 Apr 2021 03:00:00 GMT

手动触发:
https://blog.csdn.net/justyman/article/details/89857577

如果是自动触发B(t��i)UILD�Ӟ��则可以以最新徏立的TAG为基��q�行BUILD�Q�而无需人手选TAG�q�行BUILD�?br /> 配置�Q�注意应取消参数化配�|�工�E�：(x��)

Add the following refspec to the Git plugin:

+refs/tags/*:refs/remotes/origin/tags/*
Add the following branch specifier:

*/tags/*
Enable SCM polling, so that the job detects new tags.

paulwong 2021-04-22 11:00 发表评论

如何在JENKINS中��用HTTP下蝲 NEXUS上的ZIP

paulwong — Fri, 31 Jul 2020 12:18:00 GMT

需��d��如下PLUGIN�Q?a target="_blank">File Operations

��d��如下STEP�Q�File Download Operation

NEXUS上的下蝲地址按如下模式：(x��)http://localhost:8081/service/rest/v1/search/assets/download?group=org.osgi&name=org.osgi.core&version=4.3.1&maven.extension=jar&maven.classifier

paulwong 2020-07-31 20:18 发表评论

JENKINS TOURIAL

paulwong — Tue, 07 Apr 2020 02:29:00 GMT

https://huongdanjava.com/jenkins-2

paulwong 2020-04-07 10:29 发表评论

paulwong — Fri, 14 Feb 2020 06:37:00 GMT

�׃��jenkins是调用windows的git取代码，因此是git的问题，�q�行如下配置卛_��Q?br />

git config --global core.longpaths true

paulwong 2020-02-14 14:37 发表评论

使用 Jenkins 部��v Spring Boot

paulwong — Thu, 19 Sep 2019 09:44:00 GMT

https://mp.weixin.qq.com/s?__biz=MzI4NDY5Mjc1Mg==&mid=2247489278&idx=2&sn=a48342d706bfd1651e277e1c24e81e3e&chksm=ebf6ce81dc81479764d1e6ff7b207257a78d52bed5ef8c2f16c76f70660d1da9609167ed7bbb&mpshare=1&scene=1&srcid=&sharer_sharetime=1568861026830&sharer_shareid=24856bf403968a883e437b859be0a9b5&pass_ticket=qB9yWQbj%2FGo7PDZNogjBwishDCx5Suu%2BvBWnS1TpKmY%3D#rd

paulwong 2019-09-19 17:44 发表评论

publish over ssh 实现 Jenkins �q�程部��v

paulwong — Thu, 25 Jul 2019 01:33:00 GMT

Jenkins�q�程部��v�Q�一开始没有�Q何头�l�，想了很多�Ҏ(gu��)��. 因�ؓ(f��)两台机器都是windows�pȝ��Q�所以想到publish over cifs, 但是�q�个�|�上资料太少�Q�貌似只能内�|��用。又惛_��了Jenkins 分布式构建，但是Jenkins构徏的代码和产物最后自动拷贝到主节炏V��而远�E�机器其实是客户方的机器�Q�所以这个分布式构徏�q�不适用。最后还是选定publish over ssh来实现远�E�部�|�Ӏ?nbsp;

��h��意：(x��)在进行远�E�部�|�操作前�Q�先要确保客��h��能ssh ��d��到远�E�机器。如果不知道SSH怎么登陆�Q�请参考http://blog.csdn.net/flyingshuai/article/details/72897692

1. 安装publish over ssh 插�g�Q�安装很��单，在此不表�?nbsp;

2. 在Jenkins�pȝ��讄��里找到Publish over SSH模块

3. 用户�?密码方式��d��的，�pȝ��讄��里设�|�如下：(x��)

4. 如果是证书登录的�Q�系�l�设�|�里讄��如下�Q?nbsp;

5. Job讄��Q�点��d��加构建后操作步骤�Q�选择send build artifacts over ssh, 讄��如下�Q?nbsp;

6. 文�g上传到远�E�服务器后，�q�有一些后�l�操作，比如�Q�替换数据库配置文�g。可以把bat命��o(h��)写到一个批处理文�g中，存到服务器上。Exec command填写批处理文件的�l�对路径。如上图所�C��?/div>

关于bat脚本�Q?nbsp;

如果每次都需要替换同��L(f��ng)��文�g�Q�用copy /y 是无条�g覆盖�Q�不�?x��)询问。而xcopy可以实现扚w��拯��文�g和文件夹。如果文件较多可用此命��o(h��)

注意脚本�q�行��p�|�Q�构��Z��?x��)显�C��色成功图标，所以一定要打开控制台输出，看是否真的成功�?/div>

---------------------

作者：(x��)flyingshuai

来源�Q�CSDN

原文�Q?a target="_blank">https://blog.csdn.net/flyingshuai/article/details/72898665

paulwong 2019-07-25 09:33 发表评论

How do I clear my Jenkins/Hudson build history?

paulwong — Wed, 24 Jul 2019 08:18:00 GMT

摘要: 问题:I recently updated the configuration of one of my hudson builds. The build history is out of sync. Is there a way to clear my build history?Please and thank you回答1:If you click Manage Hudson / Relo... 阅读全文

paulwong 2019-07-24 16:18 发表评论

持箋部��v�Q��ƈ不简单！

paulwong — Thu, 14 May 2015 12:38:00 GMT

摘要: �q�几�q�_(d��)��持箋集成随着敏捷在国内的推广而持�l�走热，与之�怼�的持�l�部�|�也一直备受关注。自前两�q�_(d��)��持箋交付�q�个延箋性概念又闯进了国内IT圈，慢慢开始在�C�֌�和会(x��)议中展露头角。许多不明真相的��众跟风哭着喊着要“上”，而许多前CI的半吊子玩家换�g衣服��接着�qԌ��有的甚至衣服都来不及换……国内的�q�些土胦��d��果不巧请了某些所谓的战略�Ӟ��除了��Z��一堆持�l�集成环境，以及每天嚷嚷着要这个要那个�Q��؜��q��状况在根本上没有得到改善。本文无意费力探讨持�l�集成和持箋交付的概念，而是打算谈谈对于大型软�g企业�Q�以持箋集成为基��实现持箋部��v�Q�交付）�Ӟ��所要面对的问题以及可行的解��x��案。地主老胦们，夜黑风正猛，山高路又�q�，注意脚下…�?nbsp; 阅读全文

paulwong 2015-05-14 20:38 发表评论

PMD for Jenkins

paulwong — Sat, 12 Jul 2014 07:04:00 GMT

PMD jenkins plugin is only displaying the PMD check results. You need to run PMD using Maven as part of your build triggered by Jenkins. For example this could look like that in your pom.xml

<reporting>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.pluginsgroupId>
            <artifactId>maven-pmd-pluginartifactId>
            <version>2.7.1version>
            <configuration>
                <linkXRef>falselinkXRef>
                <targetJdk>1.6targetJdk>
                <rulesets>
                    <ruleset>/rulesets/basic.xmlruleset>
                rulesets>
            configuration>
        plugin>
    plugins>
reporting>

Then PMD-jenkins will know where to pick up the results and publish them for you.

To get the results you will need to add this code to your pom.xml and execute the according target in Jenkins, yes.

Note that this is not related to PMD-plugin in Eclipse. The Eclipse PMD plugin just shows the result of the local analysis, not related to Jenkins.

paulwong 2014-07-12 15:04 发表评论

搭徏��Z��Jenkins+SVN+Maven持箋集成环境(CI)

paulwong — Fri, 11 Jul 2014 16:11:00 GMT

一、准备工�?/p>

1. 下蝲jenkins.war�Q�也可以使用特定环境的安装包。将其拷贝到c:\Dev\Jenkins目录

2. SVN, Maven

二、启动Jenkins

在命令行启动Jenkins

java -jar jenkins.war --httpPort=8080�Q?--httpPort 用来指定端口受��?/p>

在地址栏输入http://localhost:8080, 看到Jenkins�ȝ��面，��p��明安装成功了�?/p>

三、Jenkins插�g

��保SVN和Maven插�g都已�l�安装好了，可以到Jenkins配置里面��L��看，如果没有可以装上�?/p>

Manage Jenkins->Manage Plugins->Installed

默认情况下，SVN和Maven插�g都是安装好的�Q�如果你需要安装其他的插�g可以在Available中查找�?/p>

四、配�|�Jenkins

新安装的Jenkins需要配�|�一些环境，例如JAVA_HOME,MAVEN_HOME�{?/p>

Manage Jenkins->Configure System

# of executors 用来指定同一旉��最多能跑的job数量�?/p>

SCM checkout retry count 如果从版本库�{�և�代码��p�|�Q�jenkins�?x��)按照这个次数重试�?/p>

JDK 配置Java环境, Maven 配置Maven环境�?/p>

五、创建Maven��d��

New Job-> 新徏��d��

Job name->home-ci�Q�ci指代commit阶段�Q�说明这个job是用来不断集成我们的代码的�?/p>

Build a maven2/3 project->我们的项目是用maven来管理的�Q�所以我们选择maven job

1. 首先我们配置SVN�Q�选择Subversion,填上��目的Repository URL,然后可以指定从这个地址�{�և�的代码保存的位置。其他默认选择�?/p>

2. Build Trigger

该选项是用来配�|�自动构建的�Q�比如我们想让项目每天中午一点和晚上一点自动构建，只需要在Build periodically中写�? 13,1 * * *.在这里我们��用Poll SCM�Q?Poll SCM"用来定期��查版本库是否有更斎ͼ�如果有更斎ͼ�触发构徏。我们就让它每分钟检查一�ơ，输入* * * * *�?/p>

3. 配置Maven

pom.xml文�g�Q�jenkins�?x��)去��L��需要执行的maven pom文�g�Q�需要给定�?/p>

我们需要运行maven �?clean install 命��o(h��)�Q�在Goals and options中指定�?/p>

4. 生成打包文�g

Post-build Actions �q�里我们可以使用一些分析工��P��比如checkstyle, 代码��试覆盖率等�{��?/p>

�q�里我们只指定需要生产的最�l�文件War或者Jar�Q�在Archive the artifacts 中输入你惌��的打包方式�?/p>

/trunk/home/home-ci/*.war;/trunk/home/test-report/*.html

六、运行构�?/p>

点击左侧的Build Now按钮�Q�点击Build History中的数字��可以看到本�ơ构建的详细�?/p>

每次构徏可以点击Changes查看是否有更改， Console output可以看到本次构徏的详�l�输出�?/p>

paulwong 2014-07-12 00:11 发表评论

Jenkins+Maven+SVN快速搭建持�l�集成环�?�?

paulwong — Fri, 11 Jul 2014 14:55:00 GMT

Jenkins是一个可扩展的持�l�集成引擎，Jenkins非常易于安装和配�|�，��单易用，下面看看我们是如何几分钟��快速搭��Z��个持�l�集成环境吧�?/p>

假设我们目前已经�?个maven��目�Q�entities(JAVA�c�d��)�Q�web(Web应用�Q�依赖entities)�?/p>

一、安装Jenkins

地址http://mirrors.jenkins-ci.org/下蝲适合的Jenkins版本�?/p>

Windows最新稳定版的Jenkins地址为：(x��)http://mirrors.jenkins-ci.org/windows-stable/jenkins-1.409.1.zip

https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+as+a+Windows+service

把Jenkins 1.409.1版解压，把得到的war包直接扔到tomcat下，启动tomcat�Q�Jenkins��安装完毕，是不是很��单啊�?/p>

redhat�pȝ��下安装流�E�：(x��)https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Red+Hat+distributions

二、配�|�Jenkins

1、打开http://10.3.15.78:8080/jenkins/�Q�第一�ơ进入里面没有数据，我们需要创建job�Q�我们这�?个项目，需要创�?个job�?span style="line-height: 1.5; text-decoration: underline;">http://10.3.34.163:9890/jenkins/

2、点��d��上角的new job�Q�在new job��面需要选择job的类型，Jenkins支持几种�c�d��Q�我们选择“构徏一个maven2/3��目”�Q�Job名�ؓ(f��)�Q�guan_caijing�Q�如图所�C�：(x��)

3、点击OK按钮后，�q�会(x��)�q�入详细配置界面�Q�详�l�配�|�界面的配置��很多，不过不用怕，大部分��用默认配�|�就可以了，下面��p��说我们需要修改的几个地方�Q?/p>

3.1�Q�Source Code Management

因�ؓ(f��)我们使用SVN��理源码�Q�所以这里选择Subversion�Q��ƈ在Repository URL中输入我们的SVN地址�Q?/p>

http://10.3.34.163:9880/guan_caijing/trunk/

输入SVN库的URL地址后，Jenkins�?x��)自动验证地址�Q��ƈ�l�予提示�?/p>

点击�U�色字体部分的enter credential链接�Q�进入如下页面：(x��)

讄��好访问SVN库的用户名和密码后，点击OK按钮�Q�显�C�：(x��)

说明讄��成功。点击Close按钮�Q�返回之前的Source Code Management��面。此时不再有�U�色警告信息了�?/p>

3.2�Q�配�|�自动构建的计划�Q�假设我们想让项目中每天12点和晚上8点自动构��Z��ơ，只需要在Build Triggers中选择Build periodically�Q��ƈ在Schedule中输�?0 12,20 * * *�?/strong>

我配�|�的是每�?点自动构�?/strong>

注：(x��)Schedule的配�|�规则是�?个空格隔开的字�W�组成，从左到右分别代表�Q�分 �?nbsp;�?nbsp;�?nbsp;�q��?代表所有，0 12,20 * * * 表示“在�Q何年��M��月�Q何天�?2�?0�?�?#8221;�q�行构徏�?/strong>

3.3�Q�配�|�到�q�里�Q�可能有人发现在Build配置节点�Q�有�U�色错误信息�Q�提�C?/p>

Jenkins needs to know where your Maven2 is installed.
Please do so from the system configuration.

如图所�C�：(x��)

�q�是因�ؓ(f��)Jenkins找不到maven的原因，点击"system configuration"�Q�是system configuration的maven配置中添加maven目录��O(ji��n)K�Q�如下图�Q?/p>

我设�|�了JRE 6和MAVEN 3的安装目录�?/p>

点击左下角的SAVE按钮�Q�保存设�|��?/p>

3.4�Q�保存好所有配�|�后�Q�我们第1个job��q��是完成了�?/p>

3.5�Q�创建第2个job�Q�配�|�和上面的配�|�相同。只需把svn地址�Ҏ(gu��)��Q?span style="line-height: 1.5; text-decoration: underline;">http://localhost/svn/Web

三、手动构�?/h4>
在经�q�上面的配置后，回到Jenkins首页�Q�在首页可以看到刚才��d��?个job�Q�如下图�Q?/p>
点击�?个job后后面的"Schedule a build"囄��手动构徏�Q�点��d��后，�?x��)在左边的Build Queue或�?span style="line-height: 1.5; text-decoration: underline;">Build Executor Status 昄��正在构徏的�Q务，在自动构建完后，��h��面�Q�就可以看到构徏�l�果了，如何某个��目构徏��p�|�Q�点击项目后面的构徏数字(�?开始递增)�q�入��目�?Console Output "可以查看��目构徏��p�|的原因。当然我们也可以配置把构建失败的�l�果发到邮箱�?/p>
到目前�ؓ(f��)止，1个简单的自动构徏环境?y��u)��搭建好了，很简单吧�?/p>
四、自动部�|?/h4>
看完上面发现Jenkins配置真的很简单，几分钟就搭徏好自动构建环境，但环境搭建好后发�?个问题，现在是能自动构徏了，但是构徏好的web.war都还是在Jenkins目录下，�q�没有发布到tomcat中，�q�需要手动copy�q�去�Q?/p>
�q�是个问题，不过别急，要达到自动部�|�的目的�Q�需要安�?个Jenkins的部�|�插件。选择“�pȝ��理”菜单�?#8220;��理插�g”�Q?/p>
选择“可选插�?#8221;�Q�找到Deploy Plugin 1.8插�g�Q�选择它�?/p>
注：(x��)Deploy Plugin 1.8插�g支持Tomcat 4.x/5.x/6.x/7.x �Q�JBoss 3.x/4.x �Q�Glassfish 2.x/3.x
点击底部�?#8220;安装”按钮�Q�显�C�：(x��)
耐心�{�待�Q?/p>
直到Deploy Plugin完成�Q�显�C�Success�Q?/p>
选择框打钩，Jenkins�?x��)自动重启�?x��)
此时�Q�在插�g��理�?#8220;已安�?#8221;Tab��，可以看到部��v插�g已安装完毕�?/p>
重新�q�入web的configure 配置界面�Q�在最下面�?x��)发现多�?个配�|�项�Q�我们配�|�如下：(x��)
注：(x��)war file使用的是Jenkinsworkspace的相对目录，hudon默认的目录在�Q?/p>
C:\Documents and Settings\用户名\.Jenkins\
workspace目录�Q�C:\Documents and Settings\用户名\.Jenkins\ jobs\web\workspace\
最�l��生的war在：(x��)C:\Documents and Settings\用户名\.Jenkins\ jobs\web\workspace\Web\target\web.war
保存配置再重新构��Z��ơ，打开tomcat的webapps目录�Q�发现web.war�l�于�q�来了，大功告成�?/p>

paulwong 2014-07-11 22:55 发表评论

paulwong — Wed, 26 Sep 2012 15:15:00 GMT
http://www.aygfsteel.com/Nirvana/archive/2012/09/10/387404.html

http://www.aygfsteel.com/Nirvana/archive/2012/09/10/387408.html

paulwong 2012-09-26 23:15 发表评论

一个完整的JENKINS下的ANT BUILD.XML文�g

paulwong — Wed, 08 Feb 2012 10:40:00 GMT
摘要: Code highlighting produced by Actipro CodeHighlighter (freeware)http://www.CodeHighlighter.com/-->阅读全文

paulwong 2012-02-08 18:40 发表评论

JENKINS使用步骤

paulwong — Tue, 31 Jan 2012 10:19:00 GMT
从代码仓库获取代码用SVN�Q�做单元��试用JUNIT�Q�做代码��查用PMD、FINDBUGS�Q�代码编译、打包用ANT�Q�拷贝文件到部��v服务器上用SHELL�Q�出现BUG了通知开发�h员要发EMAIL�Q�工具一多了�Q�整合�v来用�Ӟ��不断切换界面�Q�输入命令的复杂性可惌��知�Q�有没有一站式的工具可以代力_��Q?

有，�q�就是JENKINS�Q�有了她�Q�你��可以：(x��)通过�l�一的WEB界面做各�U�配�|�工作、查看工��L(f��ng)��LOG输出、即使是历史的日志查看也没问题；通知配置排程�Q�可以自动的获取代码、编译、打包和部��v�Q�发邮�g�Q�无��M�h工干预�?

安装JENKINS�Q�其实就是把一个WAR包放到容器中

安装插�g�Q�发邮�g插�gJenkins Email Extension Plugin和部�|�插�?a >Deploy to container Plugin

配置JDK和邮件服务器地址

新徏��d��Q�配�|�SVN地址/配置构徏排程@hourly/配置构徏步骤�Q�如先用ANT�~�译打包再传到服务器/配置成功或失败后发邮仉��知的地址

手动执行��d��或等待时间到了后执行��d��

各种插�g的安�?

ANT�Q�如果在JENKINS中��用了ANT-JUNIT�Q�由于JENKINS是直接调用操作系�l�的ANT命��o(h��)的，所以要在LINUX下安装ANT�Q�配�|�ANT_HOME�Q��ƈ��BIN加入到PATH中：(x��)
ANT_HOME=/opt/ant/apache-ant-1.8.2
JAVA_HOME=/usr/java/jdk1.6.0_29
JRE_HOME=/usr/java/jdk1.6.0_29/jre
PATH=$ANT_HOME/bin:$JAVA_HOME/bin:JRE_HOME/bin:$PATH
CLASSPATH=.:$JAVA_HOME/lib/jt.jar:$JAVA_HOME/lib/tools.jar:$JRE_HOME/lib
export ANT_HOME JAVA_HOME JRE_HOME PATH CLASSPATH

http://hanqunfeng.iteye.com/category/138233

paulwong 2012-01-31 18:19 发表评论