Paramterized build "List subversion tags" unable to use in rrepoURl

Hi, I am using parameterized build for "List Subversion tags" to populate all the tags in SVN. I want to check the source based on tag selected from this dropdown. I have given the name for this field is svn-tag, I am able to select the tag from svn tags populated, but i am not able to checkout

Re: Global Build Stats Plugin are accessible only for users with Admin permission

Fredric, Can you please share which version o global build stats having featur to share chart to normal users.  As i can see that Global build stats latest version 1.3 not having fature to share chart to normal users.. Regards Hiteswar Original message From: Frédéric Camblor

Starteam plugin with global parameters

Is it possible to use the StarTeam plugin with global parameters for the Label Name? I know that we should be using promotion states in Starteam but we are not and thats another battle that I am working on. We need the ability to easily change what label should be used accross 50+ projects every fe

Jenkins Perforce Plugin - Sync tools outside of label?

Hi there, I have a Jenkins job that syncs to a release label to do a build. Tools needed by the job like Flex 4 SDK are kept in perforce but are not included in the label. Is there a simple addition I can make to the Jenkins job to sync to the label and also sync these build tools from perforce

Attempting to run a Jenkins slave on OS/390 / ASCII vs. EBCDIC encoding issues / blank console log

We have a need to build portable C++ code on OS/390. Our existing builds run on Jenkins so it would be optimal to connect our Z/OS hardware as a slave to our existing master. >From searching I've found references indicating the need to override the default file encoding and set it to ISO8859_1

Re: Passing the environment variables from one job to another

I believe you will need to use the parameterized trigger plugin for this: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin - Original Message - From: "Mayank Jhawar" To: jenkinsci-users@googlegroups.com Sent: Thursday, June 20, 2013 12:04:25 PM Subject: Passin

Re: BuildNameSetter plugin - Unrecognized macro

Hi Bob, I was just encountering this problem today. Try specifying the build name as #${ENV,var="BUILD_NUMBER"} ${ENV,var="GIT_BRANCH_OR_TAG"} I found this suggestion in a Jenkins bug reportJENKINS-13347 . Eric On 6/20/2013 1:54 PM, Bo

BuildNameSetter plugin - Unrecognized macro

Hi, Newbie question here... I am attempting to use the BuildNameSetter plugin to set the Jenkins build name to an input parameter. Specifically, my job has a parameter named "GIT_BRANCH_OR_TAG". I set the Build Name to: #${BUILD_NUMBER} ${GIT_BRANCH_OR_TAG} Which results in: Unrecognized m

Windows XP slave agent launch failure on 1.519

Greetings, Today I upgraded my Jenkins installation from 1.500 to 1.519. I also upgraded some plugins (I can get my plugin list if need be). The upgrade went fine in all respects except one: I now have a Windows XP slave whose agent is failing to launch. My attempts to find an explanation for t

Passing the environment variables from one job to another

Hi Experts I have two jobs Job_1 Job_2 In Job_1 i give the parameter of the tag location on the fly it assigns that particular variable TAG to environment variable, i can see that in environment variables when a build is executed with parameters. After Job_1 is completed another job Job_2 is ex

Setting the PATH on a per Jenkins job basis

I have several jobs that execute TFS commands in wrappers such as ANT tasks or maven goals.  I have had to install two version of the TF command line on my build server in order to get the individual jobs running. One works for the ANT tasks and one works for the maven goal.   If I place the ver

Re: Global Build Stats Plugin are accessible only for users with Admin permission

Hi Frédéric, Thank you for answer, I've created a test chart and send it to a simple user who is not an admin but he couldn't view it, instead he gets and error page "Web page unavailable" He is the link i sent him : http://jenkins-server:8081/jenkins/ plugin/global-build-stats/#buildStat_cLZZ21Jv

Re: Empty Error message box on clicking of apply button

I am neither modifying job name nor renaming the job. I am modifying some of the parameters with in the job. Then I get this message, This error message is very consistent. Is it problem in this Jenkins version i am using 1.157. Thanks Virg On Wednesday, June 19, 2013 11:34:02 AM UTC+5:30, 0

Re: Upgrade to Latest Jenkins - WSOD after running job

Yeah, I'm having exactly the same issue. I have Jenkins running on Ubuntu 12.04, any kind of parameterised build job starts running fine, but I get a white screen rather than a redirect to the job. Annoying but ignorable, for now. On Tuesday, June 18, 2013 10:49:58 PM UTC+1, Jared Griffith wrot

Re: Upgrade to Latest Jenkins - WSOD after running job

I opened a JIRA issue on this , see https://issues.jenkins-ci.org/browse/JENKINS-18423 Amos.s On Wednesday, June 19, 2013 12:49:58 AM UTC+3, Jared Griffith wrote: > > I recently upgraded to the latest Jenkins. When I go to build any job, > instead of directing me to the normal page output page

RE: Upgrade to Latest Jenkins - WSOD after running job

I have opened https://issues.jenkins-ci.org/browse/JENKINS-18425 for this problem. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jared Griffith Sent: 19 June 2013 16:36 To: jenkinsci-users@googlegroups.com Subject: Re: Upgrade to Latest Jenkins - W