hudson

Is there any way in jenkins to block a given task on all its downstream tasks? I have a series of functional test phases, and each needs to run against a server after deployment. The server should not be updated while tests are running, however. So I have jobs: A -> B -> C I need A to block until C completes. How can I do this? Take a look at the Advanced Project Options, "Block build when downstream project is building" option for project A. I believe that will prevent multiple instances of A running until all downstream projects (ie, B and C) have completed. As Jason mentioned the setting is

well i need to execute a batch file in my Hudson Job, I have a parameter(Jenkis parameter) and i need to pass this value like param to batch file, i tried this: Deploy.cmd -configuration=${DEPLOYCONFIGURATION} -source=${DeploySource} My Deploy.cmd is configurated for get this values but Jenkis doesn't assign the values.. For example, i have this: ${DEPLOYCONFIGURATION} = DEV ${DeploySource} = c:\myFolder Then,the batch file take this values %DEPLOYCONFIGURATION% = ${DEPLOYCONFIGURATION} %DeploySource% = ${DeploySource} Takes the parameter name not its value Madhan Execute your Batch file as

I am using Parameterized Trigger Plugin to trigger a downstream build. How do I specify that my upstream job should fail if the downstream fails? The upstream job is actually is dummy job with parameters being passed to the downstream. Andrew Make sure you are using the correct step to execute your downstream jobs; I discovered that since I was executing mine as a "post build step", I didn't have the "Block until the triggered projects finish their builds" option. Changing that to "build task" as opposed to a "post build task", allowed me to find the options you are looking for within the

I installed the SetEnv plugin and it works fine for getting the variables during a task. unfortunately when i try to use the env variable in the resulting status email I have no luck at all. Is this supposed to work? I've tried both $VARNAME and ${VARNAME} - neither of which get replaced correctly in the email. The simplest way to use environment variables (or any variables) in your email notifications is by using the Email-ext plugin . Check their "Content token reference" for specifics but in short you get much more sophisticated substitution. Heres a few I use regularly: ${ENV, var} -

I've just installed Hudson and it is running beautifully. It builds, runs JUnit-tests and also CheckStyle analysis. Next step for us would be to create an installation, install it and then run automated tests on the actual installation. I would then like to fail the build if the tests fail or at least publish the results somehow. I think we would set it up so that part runs periodically or manually triggered. We use InstallAnywhere for installation and IBM Rational Functional Tester for automated tests. So questions are: anyone created a similar setup? are there any plugins, tutorials or other

On my current project we're using Jenkins to monitor our builds. Now they want me to write a Jenkins plugin to add some more monitoring parameters. I've taken a look at how the status monitor plugin works, and I can't figure some things out. I've tried to look for documentation for writing a plugin, but that seems to be sorely lacking. (the site only mentions how to generate the base project, and refers to a tutorial that's not that informative) What I'm trying to do is just add some options to each build, add a link, and a monitoring page. Adding to the main page is apparently done by adding

I have just set up a post-commit script in our subversion repository that triggers a build by requesting a hudson build URL. This works fine as expected, however now I only want to trigger this build if the commit was to the trunk. our post-commit script looks like this: SET REPOS=%1 SET REV=%2 SET DIR=%REPOS%/hooks SET PATH=%PATH%;%DIR% wget http://circus-09:8080/job/UE/build?delay=0sec How to I check that the commit was to the trunk? Here's a quick code snippet, that outputs different messages when something in trunk changed or nothing has: set repos=%~1 set rev=%~2 call :did_it_change "

What I'm basically trying to do is allow jenkins access my android-sdk-linux folder and all the sub-directories. My boss does not want to change permissions on the folder himself. I am supposed to do it during the build process. I have seen some examples that run some commands in the execute shell during the build process. Is there some commands that can I can run in that execute shell so that jenkins can have read write and execute authority on my android-sdk-linux folder? kthieling As bcolfer said, you should be able to just run your shell commands with "sudo" in front of it. You will want