Artifactory Plugin with Gems

Trying to configure the Artifactory plugin to install Ruby gems. I have been able to get them to be installed, however, they need to be under the /gems directory or they are not discoverable. I suspect it's the difference in adding the gems to the api url. Has anyone gotten this to work? kw --

Re: [workflow-plugin] Determine current directory

try node('windows') { def myDir = pwd*()* bat "echo ${myDir}" } /James On 05/12/2014 14:30, Rupali wrote: Hi James, Thanks for quick reply. I tried this. But I get same exception. Regards, Rupali On Friday, December 5, 2014 7:25:51 PM UTC+5:30, James Nord wrote: Hi Rupali The

Problem with Jenkins and install plugin

Préparation - Vérification de la connexion à internet - Vérification de la connexion à jenkins-ci.org - Succès CAS1 Plugin Échec - hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/cas1/1.0.1/cas1.hpi (redirected to: http://ftp.nluug

Re: Help with Deploy to Websphere plugin

I use this plugin with WAS 8.5.5 and no problems. Are you running in Thinclient mode or are you point to the IBM JDK? On Thursday, December 4, 2014 1:15:38 PM UTC-5, Marcel F wrote: > > Did you get any further log information. May in the ffdc logs or in the > dmgr logs of WebSphere? > This blog

archive artifact preserve my folder structure

I have a folder at the root of my workspace called "testSuite".  I was archiving this folder and then passing it to a downstream job in order to use it to run basic sanity test cases.  When I archive the folder using the archive artifact plugin by specifying the folder name as "testSuite/", it g

RE: Credentials Plugin : escape characters don't work?

Judging by your output, I would hazard a guess that ‘$’ escapes the ‘$’, so to get ‘$$’ you would use ‘’, not ‘\$\$’. Just a guess though. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Shobha Dashottar Sent: Friday, December 05, 2014 5:00 AM T

Re: [workflow-plugin] Determine current directory

Hi James, Thanks for quick reply. I tried this. But I get same exception. Regards, Rupali On Friday, December 5, 2014 7:25:51 PM UTC+5:30, James Nord wrote: > > Hi Rupali > > The following should work > > node('windows') { > def myDir = pwd > bat "echo ${myDir}" > } > > /James > > On 05/12/

Re: [workflow-plugin] Determine current directory

Hi Rupali The following should work node('windows') { def myDir = pwd bat "echo ${myDir}" } /James On 05/12/2014 13:11, Rupali wrote: Hi, I am using workflow plugin and in one of the workflow steps, I would like to know my current directory (full path) and use that in my b

PermGen space build failure

Hi Everyone, I'm trying to get a maven project of mine to build in jenkins. I've been using one root pom and making modules for every project I've done at school (up to almost 30 modules). To build this on my local machine, I needed to set MAVEN_OPTS="-XX:MaxPermSize=1024m". I've been trying

[workflow-plugin] Determine current directory

Hi, I am using workflow plugin and in one of the workflow steps, I would like to know my current directory (full path) and use that in my bat script. I tried using pwd command but it gives below error: groovy.lang.MissingPropertyException: No such property: pwd for class: WorkflowScript Can so

Re: [workflow-plugin] Error "script.sh: command not found" when running shell script

I added a Linux slave today and ran the step to execute shell script on Linux slave. That worked well. So I am concluding that Shell script in in *workflow step* is not working on Windows slave. Let me know if anyone thinks / knows otherwise. Regards, Rupali On Thursday, December 4, 2014 11:41:

Credentials Plugin : escape characters don't work?

I am using the Credentials Plugin "username:password". I get the credentials using the "use secrets" option into the environment but the special characters are getting messed up. It appears the Plugin is not recognizing the backslash as a special character. I have a $$ in my password string

Re: Filed to build ipa

I add Project -> Build Setting -> code signing resource rules path as $(SDKROOT)/ResourceRules.plist and it works benjamin.a.lau於 2014年12月5日星期五UTC+8下午5時40分53秒寫道： > > This doesn't appear to be a jenkins problem but with the latest > version of XCode. > > Warning: usage of --preserve-metadata wit

Re: Filed to build ipa

I add Project -> Build Setting -> code signing resource rules path as $(SDKROOT)/ResourceRules.plist and it works On Fri, Dec 5, 2014 at 5:40 PM, Benjamin Lau wrote: > This doesn't appear to be a jenkins problem but with the latest > version of XCode. > > Warning: usage of --preserve-metadata w

Re: Filed to build ipa

This doesn't appear to be a jenkins problem but with the latest version of XCode. Warning: usage of --preserve-metadata with option "resource-rules" (deprecated in Mac OS X >= 10.10)! Warning: --resource-rules has been deprecated in Mac OS X >= 10.10! I'd guess that your project file is still set

Filed to build ipa

Hi guys. my environment is Yosemite 10.10.1 xcode 6.1.1 Jenkins 1.592 I cannot build ipa, can anyone tell me how what happen about below error??? thank you all. Done checking the original app ### Codesigning '' with 'iPhone Developer: Chi-Chung KO (NSYHRH336G)' + /usr/bin/codesign --force --pr