hudson

Why does cucumber keep failling on jenkins, although tests pass?

由 别来无恙 提交于 2020-01-14 02:24:46
问题 My cucumber test work well on command line, but when I run them in Jenkins/Hudson continuous integration, I get the following, but am not sure how to fix it: 11 scenarios (3 skipped, 3 pending, 5 passed) 78 steps (51 skipped, 3 pending, 24 passed) 0m3.238s Build step 'Execute shell' marked build as failure Recording test results Failed to send e-mail to kamilski81 because no e-mail address is known, and no default e-mail domain is configured Failed to send e-mail to i.wooten because no e-mail

Jenkins Packages on Groovy Classpath?

由 做~自己de王妃 提交于 2020-01-13 10:23:12
问题 When using the Groovy Jenkins plugin (not the Groovy Post Build Plugin, which is a different thing) as a Post Step, I can't resolve classes in the hudson.model package. Do I need to add the Jenkins .war onto the classpath, or should these packages already be there? Script: import hudson.model.*; import hudson.util.*; AbstractBuild currentBuild = (AbstractBuild) Thread.currentThread().executable; def mavenVer = currentBuild.getMavenArtifacts().getModuleRecords()[0].mainArtifact.version;

Passing the Maven Debug Flag from Hudson

由 ♀尐吖头ヾ 提交于 2020-01-13 08:19:09
问题 I'm having an issue with a maven build in hudson. This issue would be fairly easy to resolve if I could see the output of maven with the -X flag passed in. However I can't find a way to do this. If I specify "-X" in the "Goals and options" field of the "Build" section in the job configuration my console output looks exactly the same as if I had not passed the "-X" flag at all. Is the debug logging going somewhere else? Or is there some other way I need to pass the "-X" flag? UPDATE: The

Trigger Hudson build on SVN commit

由 荒凉一梦 提交于 2020-01-12 03:15:13
问题 I have already set up a version control system (Subversion) which is going to be used by developers to commit and update their code (let's say that its address is https://server/svn/project ). Only authenticated users will be able to have access to project's SVN. On the other hand, I have installed Hudson as the project's continuous integration server (address of the project is server:8080/job/project ). I'd like to achieve the following: Hudson builds to be triggered automatically when there

Integrating Hudson with UCM Clearcase on windows machine

由 懵懂的女人 提交于 2020-01-11 12:30:12
问题 I've installed Hudson on my windows machine and trying to integrate it with UCM Clearcase (the repository we are using). There are no help docs available on Hudson wiki to explain how to do that. I select New Job --> Project Name I give as Test --> select Build a free style software project --> click Ok --> This leads me to Configure Project screen --> Under Source Code management I select UCM Clearcase --> I give a dynamic view name I've already created and the name of the integration stream

How to reload hudson configuration without restarting?

由 空扰寡人 提交于 2020-01-09 07:53:06
问题 I have a large task ahead of me...modifying several hudson jobs' configuration. What I would want is to do it from command line. But per my experience, hudson will not re-read the configuration unless you force it to "reload configuration from disk". I don't want to restart hudson just for a small change...like doing a "reload" in apache. Don't know how to read a java code but I'm guessing that what I am looking for lies in the part after saving configuration changes. 回答1: Hudson / Jenkins

使用Hudson进行持续集成

由 ぃ、小莉子 提交于 2020-01-08 04:01:54
持续集成就是快速且高频率地自动构建项目的所有源码，并为项目成员提供丰富的反馈信息。 一次完整的集成往往会包括以下6个步骤： 　　持续编译：所有正式的源代码都应该提交到源码控制系统中，持续集成服务器按一定频率检查源码控制系统，如有新的代码，就出发一次集成，旧的已编译的字节码应当全部清除，然后服务器编译所有最新的源码 　　持续数据库集成：在很多项目中，源代码不仅仅值Java代码，还包括了数据库SQL脚本。每次发现新的SQL脚本。就应该清理集成环境的数据库，重新创建表结构，并填入预备的数据 　　持续测试：单元测试和集成测试都应该在每次集成的时候运行，并且在发生问题的时候能产生具体报告 　　持续审查：持续集成可以使用Checkstyle和PMD之类的工具来生成个类报告，当审查发现问题时，可以给开发人员反馈警告信息 　　持续部署 　　持续反馈：将集成失败报告发送给这次集成相关的代码提交者，项目经理应该受到所有失败报告 持续集成的好处：尽早暴露问题；减少重复操作；简化项目发布；建立团队信心 在创建Hudson持续集成任务之前，用户需要对Hudson系统做一些基本的配置，包括JDK安装位置和Maven安装等在内的重要信息都不必须首先配置正确。 对于一般的Maven项目，可选择的类型有Build a free-style software project和Build a maven2

Hudson + Ant + SVN + Tomcat配置详解

由 …衆ロ難τιáo~ 提交于 2020-01-08 01:30:07
一、配置背景： 要想介绍Hudson，就要从持续集成开始介绍。持续集成，最开始知道有这个概念的时候是从一本叫做《.NET中的持续集成》，但是本人熟悉的是Java，而不是.Net平台，所以这本书就放下了，没有仔细的看。如今，我们需要用SSH架构开发一个知识管理平台，项目组长给我的任务恰好就是配置持续集成的开发环境。 说了这么半天看来是有点跑题了，还是没有说持续集成是个什么概念。所谓持续集成（Continuous integration）就是：持续集成是一种软件开发实践，即团队开发成员经常集成它们的工作，通常每个成员每天至少集成一次，也就意味着每天可能会发生多次集成。每次集成都通过自动化的构建（包括编译，发布，自动化测试)来验证，从而尽快地发现集成错误。许多团队发现这个过程可以大大减少集成的问题，让团队能够更快的开发内聚的软件。 上述定义是来源于软件大师：马丁福勒（Martin Fowler），大师就是大师，反正我没看懂。我来说说我的理解，在这里，我用举一个例子来说吧…… 现在我们已经进行完了前期的工作（包括：需求的确定，原型的设计等等），到了开始编程的阶段了，我们现在很少有孤军奋战的了吧？大多是小组内各个成员进行配合，编写系统，这样就有个问题，大家的编程环境可能出现差距

git and hudson/jenkins - how to do incremental builds only?

由 喜你入骨 提交于 2020-01-06 05:31:05
问题 How would I configure hudson/jenkins to checkout only the files/submodules,etc.. that have changed since the last nightly build? In our build system(ant/ivy), if it is checked out it gets built. So, I need to only checkout what has changed in order to do an incremental build. 回答1: Thats the default behaviour with the git plugin unless you set the project to do a clean build. What have you set up for it NOT to work? 来源： https://stackoverflow.com/questions/5383136/git-and-hudson-jenkins-how-to

Init.d script to start Hudson doesn't run at boot on Ubuntu

由 落花浮王杯 提交于 2020-01-06 05:00:07
问题 I'm trying to start Hudson on Ubuntu automatically on boot with an init.d script. The script works fine when invoked manually (ie with ./hudson start), and has update-rc.d-generated sym-links in rc2-rc5, but it doesn't start on rebooting. Does anyone know what might be causing it to not work? The script is as follows (the hudson.log logfile is created at boot, but doesn't contain any output): #!/bin/sh ### BEGIN INIT INFO # Provides: hudson # Required-Start: $remote_fs $syslog # Required-Stop
订阅 hudson