yum install issues for jenkins stable release 2.73.2-1.1

Is anyone else having issues with the latest jenkins stable release 2.73.2 with a repomd.xml error on trying to do a yum install? http://pkg.jenkins.io/redhat-stable/repodata/repomd.xml.asc: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Trying other mirror. To ad

Jenkins build fails, but command line build works

Has anyone seen a build fail in Jenkins but execute fine by the command line? This failure only occurs for one of our branches that we build. The jenkins job is configured: #!/bin/bash -ex cd $GIT_TREE git checkout -q $GERRIT_REFSPEC cd pkt emq DBG=yes This build fails in Jenkins for one

Command line retrigger of a jenkins build with gerrit change set

We are using the build flow plugin to run our Jenkins builds and our builds are triggered with the gerrit plugin.We have a situation where our branches are periodically locked down (for an unknown amount of time) and we need to retrigger these builds. While the builds can be easily re

Queue a build if branch is locked

We have a need to verify whether a given branch is opened or closed before we start a build.If the branch is closed (aka locked) I don't want the build to run, but rather put it in a queue until the branch is open. I've been trying to identify any plugins/steps to help us execute this proc

Rerun a build after a failure, once a restriction is lifted.

We are using the Jenkins build flow dsl plugin to execute our builds When a build fails because a branch is locked, we want to be able to retrigger a build only when the branch has been reopened, without manually going into Jenkins to retrigger it as there could be hundreds of builds that nee

Plugin to cause build to run on alternative slave if preferred slaves are down

I have two slaves I want to run my build job. If those slaves are both down, I want to revert to a different slave which is available but should only be used as a last resort for this specific build job Is there a plugin that will set the priority of where to build? i.e. Slave 1, Sl

Re: Build Flow Plugin with Node Label Parameter Plugin

; BUILD_NODE:”BUILDHERE”) > > > > Where BUILD_NODE is a NODE parameter > > > > *From:* jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] *On Behalf Of *Katie Outram > *Sent:* Tuesday, March 03, 2015 10:41 AM > *To:* jenkins...@g

Build Flow Plugin with Node Label Parameter Plugin

Has anyone had success using the Build Flow Plugin with the Node Label Parameter Plugin? Right now I have a build flow that executes some of the steps on Machine A and other steps on Machine B, eventhough I am passing the NODE_NAME and NODE_LABELS to the children jobs via an Environment Variab

NodeLabel Parameter Plugin doesn't let me stay on the same node

I have two nodes defined with the same label. NodeA (label mygit) NodeB (label mygit) I am using the build flow plugin and have a script that gets called from the main build job that performs the following build(joba.sh) parallel{ {build (jobb.sh), build (jobc.sh), build (jobd.sh

nodelabel parameter plugin configuration questions

I have a build flow plugin configuration for my build job in jenkins(main-build-job). I want to make sure that my build occurs on one of two machines so I installed the nodelabel parameter plugin. My build flow is build ("joba.sh", PARENT_BUILD_ID : build.properties.environment['BUILD_

Dynamically assign workspace depending on what node I'm building on with only one build job

I have a build job, that launches several other jobs using the build flow plugin.I am using the NodeLabel Parameter Plugin to have all of my build steps execute on a specific node. My problem is that node A needs to use the workspace /workspace/git/workspaceA and nodeB needs to use the

Re: Clean up after build using build flow plugin

The information below does work as long as the location can see the child directory that needs to be cleaned up. On Wednesday, February 25, 2015 at 12:15:40 PM UTC-5, Katie Outram wrote: > So what I have done so far is > > cleanup=bParent.build.properties.environment(

Re: Clean up after build using build flow plugin

s anyone have suggestions on how to make this work using the build flow plugin? On Tuesday, February 24, 2015 at 9:43:34 AM UTC-5, Katie Outram wrote: > After the build completes, I need to clean up the workspace that was > created during execution of the build. The workspace is defined

Clean up after build using build flow plugin

After the build completes, I need to clean up the workspace that was created during execution of the build. The workspace is defined in our scripts that get executed during the build. what this comes down to is I want to remove the contents of the directory ( bParent.build.properties.environm

Re: Build Flow Plugin questions on how to access defined values

ild step. > > > > *From:* jenkins...@googlegroups.com [mailto: > jenkins...@googlegroups.com ] *On Behalf Of *Katie Outram > *Sent:* Thursday, February 19, 2015 10:43 AM > *To:* jenkins...@googlegroups.com > *Subject:* Build Flow Plugin questions on how to access defined va

Build Flow Plugin questions on how to access defined values

I am new to the build-flow-plugin and have been asked to add some steps to an existing job. While I have a shell script that does this, it was requested that I use the build-flow-plugin instead. I am familiar with Groovy as I use it to access information within jenkins, but the DSL/Groovy