OMG: Jenkins gets restarted from my Ant script

[jabal]

hi!

I'm quite new to Jenkins CI but happy to have assembled a freestyle
project that builds and test my program starting from git checkout. As
the final point I wanted to integrate my Selenium tests into this
process and added a final Ant build step that calls this target. I was
struggling with the display server and playing with the $DISPLAY
environment variable, when suddenly Jenkins started to do something
very strange: when it gets to my ant target it throws a bunch of
exeptions and restarts, with all build history thrown. (Can be
reloaded from disk of after restart.)

In the log I see the messages that are similar to those shown in this
issue:
https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel#issue-tabs

hudson.util.IOException2: Unable to read /proj/nss/tools/jenkins/run/
jobs/myJob/builds/2012-03-06_13-52-08/build.xml
  144019 at hudson.XmlFile.unmarshal(XmlFile.java:160)
  144020 at hudson.model.Run.reload(Run.java:283)

If I run the very same ant target from bash logged in as jenkins, the
tests run perfectly. Do you have any idea how to get this fixed? Do
you have any workaround tips?

Re: Upgrading Jenkins to 1.454 from the command line on Mac OS X caused file permission changes.

[Jerome Lacoste]

On Tuesday, March 6, 2012 12:22:09 PM UTC+1, Jerome Lacoste wrote:
>
> Today I upgraded jenkins on the command line using:
>
> sudo installer -pkg jenkins-1.454.pkg -target /
>
> This changed the permissions of the Jenkins home directory. I had to fix 
> them using:
>
> chown -R jenkins:daemon /Users/Shared/Jenkins/
>
> Is that a bug ? If not, what is the proper procedure to remotely upgrade 
> jenkins on Mac OS X and not loose setup ?
>

OK got it. I am new to Mac OS X. My assumption was that the installer 
command would upgrade the package keeping its original option 
configurations. It doesn't

One has to specify the proper option from the command line using 
the applyChoiceChangesXML argument.

I haven't yet tested the following but it should work. I am waiting for the 
release that will contain the change I just committed (support of permGen 
option): 
https://github.com/jenkinsci/jenkins/commit/fb9f0679c7c75ea1e6c85bbe4f663896714bf63e

To list the option one has by default in the package one does something 
like that

 sudo installer -showChoiceChangesXML -pkg jenkins-1.454.pkg  -target /

which prints out an XML preferences. I stored it 
under jenkins_CLI_install_orig.plist. (omitting the -target / option fails 
with a strange error on my machine  "installer: Cannot install on volume 
(null) because it is disabled.")

and then one can copy that file and edit it to contain the options one 
want. In my case:


http://www.apple.com/DTDs/PropertyList-1.0.dtd";>



attributeSetting
1
choiceAttribute
selected
choiceIdentifier
jenkinslaunchdjenkins


attributeSetting
0
choiceAttribute
selected
choiceIdentifier
jenkinslaunchd




To test the new config:

sudo installer -showChoicesAfterApplyingChangesXML 
jenkins_CLI_install_override.plist -pkg jenkins-1.454.pkg  -target / > 
jenkins_CLI_install_new.plist

# diff  -u jenkins_CLI_install_orig.plist jenkins_CLI_install_new.plist 
--- jenkins_CLI_install_orig.plist 2012-03-07 08:04:30.0 +0100
+++ jenkins_CLI_install_new.plist 2012-03-07 08:21:15.0 +0100
@@ -44,7 +44,7 @@
  
  
  attributeSetting
- 1
+ 0
  choiceAttribute
  selected
  choiceIdentifier
@@ -68,7 +68,7 @@
  
  
  attributeSetting
- 0
+ 1
  choiceAttribute
  selected
  choiceIdentifier


and to finally run the command (untested)

sudo installer 
-applyChoiceChangesXML jenkins_CLI_install_override.plist -pkg 
 jenkins-1.454.pkg  -target /

When tested, I will update the Wiki.

Jerome

Jenkins GitHub OAuth

[Douglas Ferguson]

Howdy,

Sorry about the previous empty message. Not sure what's up with that.

Anyway, I've just installed the GitHub OAuth plugin and it seems to work pretty 
well except
the "Participant in Organization" feature doesn't appear to work. Is there a 
work around?

When it says participant, this is just the user being a "member" of the org on 
github?
The comma separate list, should be the org id that shows up in git hub urls?

Douglas

Re: Upgrading Jenkins to 1.454 from the command line on Mac OS X caused file permission changes.

[Ingo Richter]

Jerome,

How did the permissions look like after the installer ran?

Thanks,
Ingo
--
San Francisco Blog 
"today is tomorrows past blog" 
LinkedIn Profile: 
twitter: 



On Tue, Mar 6, 2012 at 3:40 PM, Sami Tikka  wrote:

> I do not know the answer right now. I think I need to learn more about
> packagemaker to find out how to make the installer automatically choose the
> right installation options.
>
> Could you create a Jira ticket for this at the Jenkins issue tracker?
> Thanks. I will try and check that during the weekend.
>
> -- Sami
>
> Jerome Lacoste  kirjoitti 6.3.2012 kello 13.22:
>
> > Today I upgraded jenkins on the command line using:
> >
> > sudo installer -pkg jenkins-1.454.pkg -target /
> >
> > This changed the permissions of the Jenkins home directory. I had to fix
> them using:
> >
> > chown -R jenkins:daemon /Users/Shared/Jenkins/
> >
> > Is that a bug ? If not, what is the proper procedure to remotely upgrade
> jenkins on Mac OS X and not loose setup ?
> >
> > Jerome
>

Re: Maintain Jobs in SCM

[Didier Durand]

hi,

i would use the label in config to hold branch name asnd then do a
checkout including the label in the scm url via my own checkout in 1st
build step if the if the variable can't be set directly in jenkins.

regards

didier

On Mar 7, 6:38 am, Les Mikesell  wrote:
> On Tue, Mar 6, 2012 at 11:18 PM, Didier Durand  
> wrote:
>
> > You can insert env variables in your paths on Jenkins SCM section in
> > job configuration
>
> > So, what you can do to avoid recreating jobs for branches is to put a
> > variable for the path of the branch and set the value of the variable
> > just before lanching build step ot the job. [I use this technique to
> > be able to easily change at at once the URL root of the source code I
> > am building in my jobs]
>
> > Something that I didn't try is to use a matrix job to set this
> > variable successively to various values (all the possible branch
> > names) and then have Jenkins run them automatically but the odds are
> > good that it should work.
>
> How do you set something different other than the build host/label for
> the matrix axis?
>
> --
>   Les Mikesell
>      lesmikes...@gmail.com

Re: Maintain Jobs in SCM

[Les Mikesell]

On Tue, Mar 6, 2012 at 11:18 PM, Didier Durand  wrote:
>
> You can insert env variables in your paths on Jenkins SCM section in
> job configuration
>
> So, what you can do to avoid recreating jobs for branches is to put a
> variable for the path of the branch and set the value of the variable
> just before lanching build step ot the job. [I use this technique to
> be able to easily change at at once the URL root of the source code I
> am building in my jobs]
>
> Something that I didn't try is to use a matrix job to set this
> variable successively to various values (all the possible branch
> names) and then have Jenkins run them automatically but the odds are
> good that it should work.

How do you set something different other than the build host/label for
the matrix axis?

-- 
  Les Mikesell
 lesmikes...@gmail.com

Re: Jenkins dying regularly -- how to diagnose

[Didier Durand]

Hi,

I would also suggest to use the Monitoring plugin to easily diagnose
memory issues in your jvm

At https://wiki.jenkins-ci.org/display/JENKINS/Monitoring

regards

didier

On Mar 7, 12:27 am, Sami Tikka  wrote:
> Also, check the system log for exceptions. You have probably run out of 
> memory either in heap or in permgen pool. The system log can be viewed 
> easiest by running Console.app in /Applications/Utilities.
>
> -- Sami
>
> John Hinnegan  kirjoitti 6.3.2012 kello 22.17:
>
>
>
>
>
>
>
> > We recently set up a Jenkins server on OS X.  We had been using Jenkins 
> > prior to this in the cloud, but decided it was worth it to just buy a 
> > little machine to do our builds for us. Now our Jenkins is going 
> > unresponsive -- pretty consistently after 12-18 hours with only a couple of 
> > days of observations. I don't know what the issue is, how can I diagnose?
>
> > PS. The worst part of this is that the process doesn't die, it just stops 
> > answering requests. If it would actually die, the the process manager would 
> > restart it (which would be more acceptable)

Re: Maintain Jobs in SCM

[Didier Durand]

Hi,

You can insert env variables in your paths on Jenkins SCM section in
job configuration

So, what you can do to avoid recreating jobs for branches is to put a
variable for the path of the branch and set the value of the variable
just before lanching build step ot the job. [I use this technique to
be able to easily change at at once the URL root of the source code I
am building in my jobs]

Something that I didn't try is to use a matrix job to set this
variable successively to various values (all the possible branch
names) and then have Jenkins run them automatically but the odds are
good that it should work.

regards

didier

On Mar 7, 2:10 am, Conormull  wrote:
> Hi all
>
> As we achieve more advanced build pipeline features with out Jenkins
> jobs, we would now like to maintain those jobs in our SCM. Each time
> we cut a new branch to continue developer we now find ourselves
> recreating our Jenkins jobs to point to the new branch. I was just
> wondering if anyone is doing something similar and who you may have
> gone about it from an end to end perspective. When and how are you
> uploading the newest version of the job etc. Any help would be much
> appreciated.
>
> Kind Regards
> Conor

Maintain Jobs in SCM

[Conormull]

Hi all

As we achieve more advanced build pipeline features with out Jenkins
jobs, we would now like to maintain those jobs in our SCM. Each time
we cut a new branch to continue developer we now find ourselves
recreating our Jenkins jobs to point to the new branch. I was just
wondering if anyone is doing something similar and who you may have
gone about it from an end to end perspective. When and how are you
uploading the newest version of the job etc. Any help would be much
appreciated.

Kind Regards
Conor

Re: Upgrading Jenkins to 1.454 from the command line on Mac OS X caused file permission changes.

[Sami Tikka]

I do not know the answer right now. I think I need to learn more about 
packagemaker to find out how to make the installer automatically choose the 
right installation options. 

Could you create a Jira ticket for this at the Jenkins issue tracker? Thanks. I 
will try and check that during the weekend. 

-- Sami

Jerome Lacoste  kirjoitti 6.3.2012 kello 13.22:

> Today I upgraded jenkins on the command line using:
> 
> sudo installer -pkg jenkins-1.454.pkg -target /
> 
> This changed the permissions of the Jenkins home directory. I had to fix them 
> using:
> 
> chown -R jenkins:daemon /Users/Shared/Jenkins/
> 
> Is that a bug ? If not, what is the proper procedure to remotely upgrade 
> jenkins on Mac OS X and not loose setup ?
> 
> Jerome

Re: Jenkins dying regularly -- how to diagnose

[Sami Tikka]

Also, check the system log for exceptions. You have probably run out of memory 
either in heap or in permgen pool. The system log can be viewed easiest by 
running Console.app in /Applications/Utilities.

-- Sami

John Hinnegan  kirjoitti 6.3.2012 kello 22.17:

> We recently set up a Jenkins server on OS X.  We had been using Jenkins prior 
> to this in the cloud, but decided it was worth it to just buy a little 
> machine to do our builds for us. Now our Jenkins is going unresponsive -- 
> pretty consistently after 12-18 hours with only a couple of days of 
> observations. I don't know what the issue is, how can I diagnose?
> 
> PS. The worst part of this is that the process doesn't die, it just stops 
> answering requests. If it would actually die, the the process manager would 
> restart it (which would be more acceptable)

Re: Jenkins dying regularly -- how to diagnose

[John Hinnegan]

Thanks,

I'll wait for the next hang and get some more details



On Tue, Mar 6, 2012 at 12:21 PM, Jesse Farinacci  wrote:

> Greetings,
>
> On Tue, Mar 6, 2012 at 3:17 PM, John Hinnegan 
> wrote:
> > I don't know what the issue is, how can I diagnose?
>
> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging
>
> -Jesse
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.
>

Re: Jenkins dying regularly -- how to diagnose

[Jesse Farinacci]

Greetings,

On Tue, Mar 6, 2012 at 3:17 PM, John Hinnegan  wrote:
> I don't know what the issue is, how can I diagnose?

https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+is+hanging

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

Jenkins dying regularly -- how to diagnose

[John Hinnegan]

We recently set up a Jenkins server on OS X.  We had been using Jenkins 
prior to this in the cloud, but decided it was worth it to just buy a 
little machine to do our builds for us. Now our Jenkins is going 
unresponsive -- pretty consistently after 12-18 hours with only a couple of 
days of observations. I don't know what the issue is, how can I diagnose?

PS. The worst part of this is that the process doesn't die, it just stops 
answering requests. If it would actually die, the the process manager would 
restart it (which would be more acceptable)

Re: Pipelines in Jenkins...

[Jeff]

I'm sure I'm missing something conceptually, but with a modular
architecture, build artifacts may still be needed in the development
environments, particularly if one team is producing a module consumed by
another team and they want access to the SNAPSHOT build artifacts during
development.

Doesn't the "Jenkins Maven Repository" plugin effectively isolate those
artifacts to the build servers, thus preventing it's use outside the
Jenkins world?

I'm curious also why the standard SNAPSHOT repository can't be used?
Again, I'm sure I'm missing something.
On Tue, Feb 21, 2012 at 3:28 AM, Nigel Magnay wrote:

> This is partially what the jenkins maven repository plugin [1] was built
> for -- each build is exposed as a separate build repository, so you don't
> need to go copying things around.
>
> What we do is :
>
> 1) Install the plugin
> 2) Add the following to the jenkins settings.xml  [2]:
> 3) In the downstream project, add "-Pupstream" into the maven settings
> 4) Check the 'Define upstream maven repository' checkbox (build
> environment), and set the upstream build that you want to add as a build
> repository.
>
> There is a bug to do with snapshot IDs in the current version - there is a
> patch that is in master, but I haven't had a chance to roll a release with
> it yet. I'd use 0.6.1 until it's fixed if you rely on SNAPSHOT artifacts.
>
>
> [1]
> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Maven+Repository+Server
>
> [2]
> 
> upstream
>   
>  
> upstream
> ${env.Jenkins.Repository}
> 
> true
> 
> 
> true
> 
>  
> 
> 
>   
> upstream
> ${env.Jenkins.Repository}
> 
> true
> 
> 
> true
> 
>   
>
> 
>
> 
>
>
> On Thu, Feb 16, 2012 at 1:44 AM, R. Tyler Croy wrote:
>
>>
>> On Wed, 15 Feb 2012, Jeff wrote:
>>
>> > I'm trying to implement Jenkins with Maven as the build CI/CD tool
>> since it
>> > does so well with the technologies we are using out of the box instead
>> of
>> > GO that the larger .NET-based organization is  using.
>> >
>> > I've done Jenkins jobs for stand-alone projects but not jobs chained
>> from
>> > dependent projects.
>> >
>> > Conceptually, I can see how dependent jobs are configured using the
>> build
>> > pipeline plugin (though we only have one project so far).  What is
>> unclear
>> > is how downstream jobs are configured to consume the
>> > artifacts and/or outputs produced upstream.
>>
>>
>> Plugins to check out:
>>
>>  * Join plugin
>>  * Copy Artifacts plugin
>>
>>
>> Those might meet your needs, I use them both heavily to create longish
>> pipelines.
>>
>> - R. Tyler Croy
>> --
>>Code: http://github.com/rtyler
>>  Chatter: http://twitter.com/agentdero
>>  rty...@jabber.org
>>
>
>


-- 
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox  !!

Re: Pipelines in Jenkins...

[Jeff]

Getting back to this...(BTW thanks for the responses)

How do you generate/control the unique ID?  Is the SVN repository revision
a good ID to use?  Seems that it would be good to correlate the builds
based on a known reference point.  That may not work though with multiple
projects that are based on different SVN numbers  hmm.
If you use Maven (and assuming you are also building web applications) it
seems that the POM would be configured to do all the deploy's and possibly
run the tests at any given point.  However, the project with the POM is
part of the workspace of the upstream job and I don't think it would be
good to copy the entire workspace for every job.

Can multiple jobs share the same workspace?

On Mon, Feb 20, 2012 at 4:55 PM, Geoff Bullen
wrote:

> The join plugin doesn't work with the build pipeline plugin.  However you
> can achieve pretty much the same thing by wrapping up multiple jobs a build
> steps using the parametrised triggers plugin
>
> In terms of passing artefacts down a pipeline of jobs, what I tend to do
> is pass a unique identifier along the pipeline that is used to publish the
> built artefact early on and to retrieve built artefacts later on.   You can
> use the copy artefact plugin to pass built artefacts around as well
>
>
> On Thu, Feb 16, 2012 at 12:44 PM, R. Tyler Croy wrote:
>
>>
>> On Wed, 15 Feb 2012, Jeff wrote:
>>
>> > I'm trying to implement Jenkins with Maven as the build CI/CD tool
>> since it
>> > does so well with the technologies we are using out of the box instead
>> of
>> > GO that the larger .NET-based organization is  using.
>> >
>> > I've done Jenkins jobs for stand-alone projects but not jobs chained
>> from
>> > dependent projects.
>> >
>> > Conceptually, I can see how dependent jobs are configured using the
>> build
>> > pipeline plugin (though we only have one project so far).  What is
>> unclear
>> > is how downstream jobs are configured to consume the
>> > artifacts and/or outputs produced upstream.
>>
>>
>> Plugins to check out:
>>
>>  * Join plugin
>>  * Copy Artifacts plugin
>>
>>
>> Those might meet your needs, I use them both heavily to create longish
>> pipelines.
>>
>> - R. Tyler Croy
>> --
>>Code: http://github.com/rtyler
>>  Chatter: http://twitter.com/agentdero
>>  rty...@jabber.org
>>
>
>


-- 
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox  !!

Help with build-pipeline and job options

[Jeff]

Do all of these options affect the pipeline plugin?

   1. Build whenever a SNAPSHOT dependency is built
   2. Build after other projects are built
   3. Build other projects
   4. Trigger parameterized build on other projects
   5. Build Pipeline Plugin -> Manually Execute Downstream Project

Other than #5, does the pipeline plugin use any of these?

Also, if I have a job that builds a shared project (library) that is
upstream of multiple other projects, is there a way to create a pipeline
view that includes only one branch of the job dependency graph?  For
example, if I have:

A -> B -> C
  \
   \-> D -> E

Can I create a pipeline view that only shows A->B->C and another that only
shows A->D->E, etc.?

Thanks!

-- 
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox  !!

Re: Parameterized build not working - plz help

[Andrew Melo]

On Tue, Mar 6, 2012 at 12:57 PM, Jatin D Patel  wrote:

> Andrew,
>
> I wanted to execute list of linux commands, while pointing to linux serv.
>
> So you mean to say that, if i run commands on a slave, i will be able to
> use parametrized  variables ?
> Do you know any link that will help?
>

Yeah, you should just run a slave on your linux machine, have it connect to
your master and use the "execute shell" build step to get commands to run
there with each build.


>
> Thanks,
> Jatin.
>
>
> On Tue, Mar 6, 2012 at 10:38 AM, Andrew Melo wrote:
>
>>
>>
>> On Tue, Mar 6, 2012 at 12:27 PM, Jatin D Patel wrote:
>>
>>> Hi all,
>>>
>>> Hope this attached document with screenshot will be more clear.
>>> I am not able to send parametrized values to build.
>>>
>>> Andrew,
>>> Are you able to echo out parameterized value in build?
>>> If yes, Can you please reply back your output.
>>>
>>> Thanks,
>>> ~Jatin
>>>
>>> ways to reproduce steps
>>>
>>> --
>>> step 1:
>>> Build a free-style software project
>>>
>>> step 2:
>>> IN configuration page, I have selected the option
>>> "This build is parametreized"
>>>
>>> Step 3:
>>> Provide String parameter
>>>
>>> Name  : VERSION
>>> default value  : RELEASE
>>> dESCRIPTION  : abcd
>>>
>>> Step 4:
>>> Under the build section
>>> SSH Site : My personal linux server
>>> Command: : echo JAVA_HOME
>>>  WORKS FINE
>>> echo $VERSION
>>> echo "$version"
>>>  RETURNS Blank line.
>>>
>>>
>>> Step 5
>>> Save the oncfirations
>>>
>>> Step 6
>>> Go to home page of job now.
>>>
>>> Step 7
>>> For triggering build,
>>>
>>> Click on "Build Now"
>>> (Located on Top Left)
>>>
>>> Step 8.
>>> We gets a screen to provide the parametreized values
>>> I provide some default value.
>>>
>>> Step 9
>>> Click on "Build"
>>> This step helps me trigger Build.
>>>
>>
>> Ah, I guess that variable doesn't get passed through the SSH session. Why
>> are you using the SSH command and not running the commands on a slave?
>>
>>
>>
>>>
>>> -
>>>
>>>
>>> On Tue, Mar 6, 2012 at 10:06 AM, Andrew Melo wrote:
>>>


 On Tue, Mar 6, 2012 at 12:02 PM, Jatin D Patel wrote:

> I am trying new string name
>
> String parameter
> Name : myVaraiable
> Default Value: 10
>
> echo $myVaraiable
> echo "$myVaraiable"
> RETURNS Blank line.
>

 This is in a "execute shell" build step? Like this?

 http://cl.ly/2b382H2731262r2J0f08


>
>
>
> On Tue, Mar 6, 2012 at 9:51 AM, Andrew Melo wrote:
>
>>
>>
>> On Tue, Mar 6, 2012 at 11:49 AM, Jatin D Patel 
>> wrote:
>>
>>> Andrew,
>>>
>>> Thanks for quick reply. I have attached the following steps.
>>> I a newbie to jenkins. I might have misunderstood the documentation.
>>>
>>> Please correct me if i am wrong?
>>>
>>> --
>>>
>>> Step 5
>>> Save the oncfirations
>>>
>>> Step 6
>>> Go to home page of job now.
>>>
>>> Step 7
>>> For triggering build,
>>>
>>> Click on "Build Now"
>>> (Located on Top Left)
>>>
>>> Step 8.
>>> We gets a screen to provide the parametreized values
>>> I provide some default value.
>>>
>>> Step 9
>>> Click on "Build"
>>> This step helps me trigger Build.
>>>
>>
>> Hm. Try using a different name (not $VERSION) for your variable.
>> Maybe it's colliding?
>>
>>
>>
>>>
>>> Thanks,
>>> Jatin
>>>
>>>
>>> On Tue, Mar 6, 2012 at 9:33 AM, Andrew Melo 
>>> wrote:
>>>


 On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel <
 depo.ja...@gmail.com> wrote:

> This is the steps which i have followed.
>
>
> 
>
> step 1:
> Build a free-style software project
>
> step 2:
> IN configuration page, I have selected the option
> "This build is parametreized"
>
> Step 3:
> Provide String parameter
>
> Name : VERSION
> default value : RELEASE
> dESCRIPTION : abcd
>
> Step 4:
> Under the build section
> SSH Site : My personal linux server
> Command: : echo JAVA_HOME
> WORKS FINE
>  echo $VERSION
> echo "$version"
>  RETURNS Blank line.
>
> 
>
>
> Hope that i was clear ?
>

 

Re: Parameterized build not working - plz help

[Jatin D Patel]

Andrew,

I wanted to execute list of linux commands, while pointing to linux serv.

So you mean to say that, if i run commands on a slave, i will be able to
use parametrized  variables ?
Do you know any link that will help?

Thanks,
Jatin.


On Tue, Mar 6, 2012 at 10:38 AM, Andrew Melo  wrote:

>
>
> On Tue, Mar 6, 2012 at 12:27 PM, Jatin D Patel wrote:
>
>> Hi all,
>>
>> Hope this attached document with screenshot will be more clear.
>> I am not able to send parametrized values to build.
>>
>> Andrew,
>> Are you able to echo out parameterized value in build?
>> If yes, Can you please reply back your output.
>>
>> Thanks,
>> ~Jatin
>>
>> ways to reproduce steps
>>
>> --
>> step 1:
>> Build a free-style software project
>>
>> step 2:
>> IN configuration page, I have selected the option
>> "This build is parametreized"
>>
>> Step 3:
>> Provide String parameter
>>
>> Name  : VERSION
>> default value  : RELEASE
>> dESCRIPTION  : abcd
>>
>> Step 4:
>> Under the build section
>> SSH Site : My personal linux server
>> Command: : echo JAVA_HOME
>>  WORKS FINE
>> echo $VERSION
>> echo "$version"
>>  RETURNS Blank line.
>>
>>
>> Step 5
>> Save the oncfirations
>>
>> Step 6
>> Go to home page of job now.
>>
>> Step 7
>> For triggering build,
>>
>> Click on "Build Now"
>> (Located on Top Left)
>>
>> Step 8.
>> We gets a screen to provide the parametreized values
>> I provide some default value.
>>
>> Step 9
>> Click on "Build"
>> This step helps me trigger Build.
>>
>
> Ah, I guess that variable doesn't get passed through the SSH session. Why
> are you using the SSH command and not running the commands on a slave?
>
>
>
>>
>> -
>>
>>
>> On Tue, Mar 6, 2012 at 10:06 AM, Andrew Melo wrote:
>>
>>>
>>>
>>> On Tue, Mar 6, 2012 at 12:02 PM, Jatin D Patel wrote:
>>>
 I am trying new string name

 String parameter
 Name : myVaraiable
 Default Value: 10

 echo $myVaraiable
 echo "$myVaraiable"
 RETURNS Blank line.

>>>
>>> This is in a "execute shell" build step? Like this?
>>>
>>> http://cl.ly/2b382H2731262r2J0f08
>>>
>>>



 On Tue, Mar 6, 2012 at 9:51 AM, Andrew Melo wrote:

>
>
> On Tue, Mar 6, 2012 at 11:49 AM, Jatin D Patel 
> wrote:
>
>> Andrew,
>>
>> Thanks for quick reply. I have attached the following steps.
>> I a newbie to jenkins. I might have misunderstood the documentation.
>>
>> Please correct me if i am wrong?
>>
>> --
>>
>> Step 5
>> Save the oncfirations
>>
>> Step 6
>> Go to home page of job now.
>>
>> Step 7
>> For triggering build,
>>
>> Click on "Build Now"
>> (Located on Top Left)
>>
>> Step 8.
>> We gets a screen to provide the parametreized values
>> I provide some default value.
>>
>> Step 9
>> Click on "Build"
>> This step helps me trigger Build.
>>
>
> Hm. Try using a different name (not $VERSION) for your variable. Maybe
> it's colliding?
>
>
>
>>
>> Thanks,
>> Jatin
>>
>>
>> On Tue, Mar 6, 2012 at 9:33 AM, Andrew Melo wrote:
>>
>>>
>>>
>>> On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel >> > wrote:
>>>
 This is the steps which i have followed.


 

 step 1:
 Build a free-style software project

 step 2:
 IN configuration page, I have selected the option
 "This build is parametreized"

 Step 3:
 Provide String parameter

 Name : VERSION
 default value : RELEASE
 dESCRIPTION : abcd

 Step 4:
 Under the build section
 SSH Site : My personal linux server
 Command: : echo JAVA_HOME
 WORKS FINE
  echo $VERSION
 echo "$version"
  RETURNS Blank line.

 


 Hope that i was clear ?

>>>
>>> Right, but how are you actually triggering the builds? The webpage?
>>> The CLI?
>>>
>>>
 Please help.

 On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo 
 wrote:

> Hi there,
>
> How are you submitting the job?
>
> -andrew
>
>
> On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel <
> depo.ja...@gmail.com> wrote:
>
>> Hi all,
>>
>>

Re: Parameterized build not working - plz help

[Andrew Melo]

On Tue, Mar 6, 2012 at 12:27 PM, Jatin D Patel  wrote:

> Hi all,
>
> Hope this attached document with screenshot will be more clear.
> I am not able to send parametrized values to build.
>
> Andrew,
> Are you able to echo out parameterized value in build?
> If yes, Can you please reply back your output.
>
> Thanks,
> ~Jatin
>
> ways to reproduce steps
>
> --
> step 1:
> Build a free-style software project
>
> step 2:
> IN configuration page, I have selected the option
> "This build is parametreized"
>
> Step 3:
> Provide String parameter
>
> Name  : VERSION
> default value  : RELEASE
> dESCRIPTION  : abcd
>
> Step 4:
> Under the build section
> SSH Site : My personal linux server
> Command: : echo JAVA_HOME
>  WORKS FINE
> echo $VERSION
> echo "$version"
>  RETURNS Blank line.
>
>
> Step 5
> Save the oncfirations
>
> Step 6
> Go to home page of job now.
>
> Step 7
> For triggering build,
>
> Click on "Build Now"
> (Located on Top Left)
>
> Step 8.
> We gets a screen to provide the parametreized values
> I provide some default value.
>
> Step 9
> Click on "Build"
> This step helps me trigger Build.
>

Ah, I guess that variable doesn't get passed through the SSH session. Why
are you using the SSH command and not running the commands on a slave?



>
> -
>
>
> On Tue, Mar 6, 2012 at 10:06 AM, Andrew Melo wrote:
>
>>
>>
>> On Tue, Mar 6, 2012 at 12:02 PM, Jatin D Patel wrote:
>>
>>> I am trying new string name
>>>
>>> String parameter
>>> Name : myVaraiable
>>> Default Value: 10
>>>
>>> echo $myVaraiable
>>> echo "$myVaraiable"
>>> RETURNS Blank line.
>>>
>>
>> This is in a "execute shell" build step? Like this?
>>
>> http://cl.ly/2b382H2731262r2J0f08
>>
>>
>>>
>>>
>>>
>>> On Tue, Mar 6, 2012 at 9:51 AM, Andrew Melo wrote:
>>>


 On Tue, Mar 6, 2012 at 11:49 AM, Jatin D Patel wrote:

> Andrew,
>
> Thanks for quick reply. I have attached the following steps.
> I a newbie to jenkins. I might have misunderstood the documentation.
>
> Please correct me if i am wrong?
>
> --
>
> Step 5
> Save the oncfirations
>
> Step 6
> Go to home page of job now.
>
> Step 7
> For triggering build,
>
> Click on "Build Now"
> (Located on Top Left)
>
> Step 8.
> We gets a screen to provide the parametreized values
> I provide some default value.
>
> Step 9
> Click on "Build"
> This step helps me trigger Build.
>

 Hm. Try using a different name (not $VERSION) for your variable. Maybe
 it's colliding?



>
> Thanks,
> Jatin
>
>
> On Tue, Mar 6, 2012 at 9:33 AM, Andrew Melo wrote:
>
>>
>>
>> On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel 
>> wrote:
>>
>>> This is the steps which i have followed.
>>>
>>>
>>> 
>>>
>>> step 1:
>>> Build a free-style software project
>>>
>>> step 2:
>>> IN configuration page, I have selected the option
>>> "This build is parametreized"
>>>
>>> Step 3:
>>> Provide String parameter
>>>
>>> Name : VERSION
>>> default value : RELEASE
>>> dESCRIPTION : abcd
>>>
>>> Step 4:
>>> Under the build section
>>> SSH Site : My personal linux server
>>> Command: : echo JAVA_HOME
>>> WORKS FINE
>>>  echo $VERSION
>>> echo "$version"
>>>  RETURNS Blank line.
>>>
>>> 
>>>
>>>
>>> Hope that i was clear ?
>>>
>>
>> Right, but how are you actually triggering the builds? The webpage?
>> The CLI?
>>
>>
>>> Please help.
>>>
>>> On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo 
>>> wrote:
>>>
 Hi there,

 How are you submitting the job?

 -andrew


 On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel >>> > wrote:

> Hi all,
>
> I have set up a string value
> Name : VERSION
> Default Value : 17
>
> Ref: http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Build
>
> When i try to access, the version value, i get a blank response
>
> echo $JAVA_HOME
> returns Java Home location
>
> *echo $VERSION*
> *returns a blank line*
> *
> *
> *echo "$VERSION"*
> *also returns a blank line*
>
>
> How can i display

Re: Parameterized build not working - plz help

[Andrew Melo]

On Tue, Mar 6, 2012 at 12:02 PM, Jatin D Patel  wrote:

> I am trying new string name
>
> String parameter
> Name : myVaraiable
> Default Value: 10
>
> echo $myVaraiable
> echo "$myVaraiable"
> RETURNS Blank line.
>

This is in a "execute shell" build step? Like this?

http://cl.ly/2b382H2731262r2J0f08


>
>
>
> On Tue, Mar 6, 2012 at 9:51 AM, Andrew Melo  wrote:
>
>>
>>
>> On Tue, Mar 6, 2012 at 11:49 AM, Jatin D Patel wrote:
>>
>>> Andrew,
>>>
>>> Thanks for quick reply. I have attached the following steps.
>>> I a newbie to jenkins. I might have misunderstood the documentation.
>>>
>>> Please correct me if i am wrong?
>>>
>>> --
>>>
>>> Step 5
>>> Save the oncfirations
>>>
>>> Step 6
>>> Go to home page of job now.
>>>
>>> Step 7
>>> For triggering build,
>>>
>>> Click on "Build Now"
>>> (Located on Top Left)
>>>
>>> Step 8.
>>> We gets a screen to provide the parametreized values
>>> I provide some default value.
>>>
>>> Step 9
>>> Click on "Build"
>>> This step helps me trigger Build.
>>>
>>
>> Hm. Try using a different name (not $VERSION) for your variable. Maybe
>> it's colliding?
>>
>>
>>
>>>
>>> Thanks,
>>> Jatin
>>>
>>>
>>> On Tue, Mar 6, 2012 at 9:33 AM, Andrew Melo wrote:
>>>


 On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel wrote:

> This is the steps which i have followed.
>
>
> 
>
> step 1:
> Build a free-style software project
>
> step 2:
> IN configuration page, I have selected the option
> "This build is parametreized"
>
> Step 3:
> Provide String parameter
>
> Name : VERSION
> default value : RELEASE
> dESCRIPTION : abcd
>
> Step 4:
> Under the build section
> SSH Site : My personal linux server
> Command: : echo JAVA_HOME
> WORKS FINE
>  echo $VERSION
> echo "$version"
>  RETURNS Blank line.
>
> 
>
>
> Hope that i was clear ?
>

 Right, but how are you actually triggering the builds? The webpage? The
 CLI?


> Please help.
>
> On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo wrote:
>
>> Hi there,
>>
>> How are you submitting the job?
>>
>> -andrew
>>
>>
>> On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have set up a string value
>>> Name : VERSION
>>> Default Value : 17
>>>
>>> Ref: http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Build
>>>
>>> When i try to access, the version value, i get a blank response
>>>
>>> echo $JAVA_HOME
>>> returns Java Home location
>>>
>>> *echo $VERSION*
>>> *returns a blank line*
>>> *
>>> *
>>> *echo "$VERSION"*
>>> *also returns a blank line*
>>>
>>>
>>> How can i display the value 17 , while *executing shell script on
>>> remot ehost using ssh?*
>>> *
>>> *
>>> Please help.
>>>
>>> --
>>> Thanks,
>>> JD Patel
>>> You Got To Think HIGH to RISE.
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Andrew Melo
>>
>>
>
>
> --
> Thanks,
> Jatin D N Patel
>
> You Got To Think HIGH to RISE.
>
>
>


 --
 --
 Andrew Melo


>>>
>>>
>>> --
>>> Thanks,
>>> Jatin D N Patel
>>> You Got To Think HIGH to RISE.
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Andrew Melo
>>
>>
>
>
> --
> Thanks,
> Jatin D N Patel
> You Got To Think HIGH to RISE.
>
>
>


-- 
--
Andrew Melo

Re: Parameterized build not working - plz help

[Jatin D Patel]

I am trying new string name

String parameter
Name : myVaraiable
Default Value: 10

echo $myVaraiable
echo "$myVaraiable"
RETURNS Blank line.



On Tue, Mar 6, 2012 at 9:51 AM, Andrew Melo  wrote:

>
>
> On Tue, Mar 6, 2012 at 11:49 AM, Jatin D Patel wrote:
>
>> Andrew,
>>
>> Thanks for quick reply. I have attached the following steps.
>> I a newbie to jenkins. I might have misunderstood the documentation.
>>
>> Please correct me if i am wrong?
>>
>> --
>>
>> Step 5
>> Save the oncfirations
>>
>> Step 6
>> Go to home page of job now.
>>
>> Step 7
>> For triggering build,
>>
>> Click on "Build Now"
>> (Located on Top Left)
>>
>> Step 8.
>> We gets a screen to provide the parametreized values
>> I provide some default value.
>>
>> Step 9
>> Click on "Build"
>> This step helps me trigger Build.
>>
>
> Hm. Try using a different name (not $VERSION) for your variable. Maybe
> it's colliding?
>
>
>
>>
>> Thanks,
>> Jatin
>>
>>
>> On Tue, Mar 6, 2012 at 9:33 AM, Andrew Melo wrote:
>>
>>>
>>>
>>> On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel wrote:
>>>
 This is the steps which i have followed.


 

 step 1:
 Build a free-style software project

 step 2:
 IN configuration page, I have selected the option
 "This build is parametreized"

 Step 3:
 Provide String parameter

 Name : VERSION
 default value : RELEASE
 dESCRIPTION : abcd

 Step 4:
 Under the build section
 SSH Site : My personal linux server
 Command: : echo JAVA_HOME
 WORKS FINE
  echo $VERSION
 echo "$version"
  RETURNS Blank line.

 


 Hope that i was clear ?

>>>
>>> Right, but how are you actually triggering the builds? The webpage? The
>>> CLI?
>>>
>>>
 Please help.

 On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo wrote:

> Hi there,
>
> How are you submitting the job?
>
> -andrew
>
>
> On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel wrote:
>
>> Hi all,
>>
>> I have set up a string value
>> Name : VERSION
>> Default Value : 17
>>
>> Ref: http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Build
>>
>> When i try to access, the version value, i get a blank response
>>
>> echo $JAVA_HOME
>> returns Java Home location
>>
>> *echo $VERSION*
>> *returns a blank line*
>> *
>> *
>> *echo "$VERSION"*
>> *also returns a blank line*
>>
>>
>> How can i display the value 17 , while *executing shell script on
>> remot ehost using ssh?*
>> *
>> *
>> Please help.
>>
>> --
>> Thanks,
>> JD Patel
>> You Got To Think HIGH to RISE.
>>
>>
>>
>
>
> --
> --
> Andrew Melo
>
>


 --
 Thanks,
 Jatin D N Patel

 You Got To Think HIGH to RISE.



>>>
>>>
>>> --
>>> --
>>> Andrew Melo
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Jatin D N Patel
>> You Got To Think HIGH to RISE.
>>
>>
>>
>
>
> --
> --
> Andrew Melo
>
>


-- 
Thanks,
Jatin D N Patel
You Got To Think HIGH to RISE.

Re: Parameterized build not working - plz help

[Andrew Melo]

On Tue, Mar 6, 2012 at 11:49 AM, Jatin D Patel  wrote:

> Andrew,
>
> Thanks for quick reply. I have attached the following steps.
> I a newbie to jenkins. I might have misunderstood the documentation.
>
> Please correct me if i am wrong?
>
> --
>
> Step 5
> Save the oncfirations
>
> Step 6
> Go to home page of job now.
>
> Step 7
> For triggering build,
>
> Click on "Build Now"
> (Located on Top Left)
>
> Step 8.
> We gets a screen to provide the parametreized values
> I provide some default value.
>
> Step 9
> Click on "Build"
> This step helps me trigger Build.
>

Hm. Try using a different name (not $VERSION) for your variable. Maybe it's
colliding?



>
> Thanks,
> Jatin
>
>
> On Tue, Mar 6, 2012 at 9:33 AM, Andrew Melo  wrote:
>
>>
>>
>> On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel wrote:
>>
>>> This is the steps which i have followed.
>>>
>>>
>>> 
>>>
>>> step 1:
>>> Build a free-style software project
>>>
>>> step 2:
>>> IN configuration page, I have selected the option
>>> "This build is parametreized"
>>>
>>> Step 3:
>>> Provide String parameter
>>>
>>> Name : VERSION
>>> default value : RELEASE
>>> dESCRIPTION : abcd
>>>
>>> Step 4:
>>> Under the build section
>>> SSH Site : My personal linux server
>>> Command: : echo JAVA_HOME
>>> WORKS FINE
>>>  echo $VERSION
>>> echo "$version"
>>>  RETURNS Blank line.
>>>
>>> 
>>>
>>>
>>> Hope that i was clear ?
>>>
>>
>> Right, but how are you actually triggering the builds? The webpage? The
>> CLI?
>>
>>
>>> Please help.
>>>
>>> On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo wrote:
>>>
 Hi there,

 How are you submitting the job?

 -andrew


 On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel wrote:

> Hi all,
>
> I have set up a string value
> Name : VERSION
> Default Value : 17
>
> Ref: http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Build
>
> When i try to access, the version value, i get a blank response
>
> echo $JAVA_HOME
> returns Java Home location
>
> *echo $VERSION*
> *returns a blank line*
> *
> *
> *echo "$VERSION"*
> *also returns a blank line*
>
>
> How can i display the value 17 , while *executing shell script on
> remot ehost using ssh?*
> *
> *
> Please help.
>
> --
> Thanks,
> JD Patel
> You Got To Think HIGH to RISE.
>
>
>


 --
 --
 Andrew Melo


>>>
>>>
>>> --
>>> Thanks,
>>> Jatin D N Patel
>>>
>>> You Got To Think HIGH to RISE.
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Andrew Melo
>>
>>
>
>
> --
> Thanks,
> Jatin D N Patel
> You Got To Think HIGH to RISE.
>
>
>


-- 
--
Andrew Melo

Re: Parameterized build not working - plz help

[Jatin D Patel]

Andrew,

Thanks for quick reply. I have attached the following steps.
I a newbie to jenkins. I might have misunderstood the documentation.

Please correct me if i am wrong?
--

Step 5
Save the oncfirations

Step 6
Go to home page of job now.

Step 7
For triggering build,

Click on "Build Now"
(Located on Top Left)

Step 8.
We gets a screen to provide the parametreized values
I provide some default value.

Step 9
Click on "Build"
This step helps me trigger Build.

Thanks,
Jatin


On Tue, Mar 6, 2012 at 9:33 AM, Andrew Melo  wrote:

>
>
> On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel wrote:
>
>> This is the steps which i have followed.
>>
>>
>> 
>>
>> step 1:
>> Build a free-style software project
>>
>> step 2:
>> IN configuration page, I have selected the option
>> "This build is parametreized"
>>
>> Step 3:
>> Provide String parameter
>>
>> Name : VERSION
>> default value : RELEASE
>> dESCRIPTION : abcd
>>
>> Step 4:
>> Under the build section
>> SSH Site : My personal linux server
>> Command: : echo JAVA_HOME
>> WORKS FINE
>>  echo $VERSION
>> echo "$version"
>>  RETURNS Blank line.
>>
>> 
>>
>>
>> Hope that i was clear ?
>>
>
> Right, but how are you actually triggering the builds? The webpage? The
> CLI?
>
>
>> Please help.
>>
>> On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo wrote:
>>
>>> Hi there,
>>>
>>> How are you submitting the job?
>>>
>>> -andrew
>>>
>>>
>>> On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel wrote:
>>>
 Hi all,

 I have set up a string value
 Name : VERSION
 Default Value : 17

 Ref: http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Build

 When i try to access, the version value, i get a blank response

 echo $JAVA_HOME
 returns Java Home location

 *echo $VERSION*
 *returns a blank line*
 *
 *
 *echo "$VERSION"*
 *also returns a blank line*


 How can i display the value 17 , while *executing shell script on
 remot ehost using ssh?*
 *
 *
 Please help.

 --
 Thanks,
 JD Patel
 You Got To Think HIGH to RISE.



>>>
>>>
>>> --
>>> --
>>> Andrew Melo
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Jatin D N Patel
>>
>> You Got To Think HIGH to RISE.
>>
>>
>>
>
>
> --
> --
> Andrew Melo
>
>


-- 
Thanks,
Jatin D N Patel
You Got To Think HIGH to RISE.

Re: Parameterized build not working - plz help

[Andrew Melo]

On Tue, Mar 6, 2012 at 11:31 AM, Jatin D Patel  wrote:

> This is the steps which i have followed.
>
>
> 
>
> step 1:
> Build a free-style software project
>
> step 2:
> IN configuration page, I have selected the option
> "This build is parametreized"
>
> Step 3:
> Provide String parameter
>
> Name : VERSION
> default value : RELEASE
> dESCRIPTION : abcd
>
> Step 4:
> Under the build section
> SSH Site : My personal linux server
> Command: : echo JAVA_HOME
> WORKS FINE
>  echo $VERSION
> echo "$version"
>  RETURNS Blank line.
>
> 
>
>
> Hope that i was clear ?
>

Right, but how are you actually triggering the builds? The webpage? The CLI?


> Please help.
>
> On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo  wrote:
>
>> Hi there,
>>
>> How are you submitting the job?
>>
>> -andrew
>>
>>
>> On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel wrote:
>>
>>> Hi all,
>>>
>>> I have set up a string value
>>> Name : VERSION
>>> Default Value : 17
>>>
>>> Ref: http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Build
>>>
>>> When i try to access, the version value, i get a blank response
>>>
>>> echo $JAVA_HOME
>>> returns Java Home location
>>>
>>> *echo $VERSION*
>>> *returns a blank line*
>>> *
>>> *
>>> *echo "$VERSION"*
>>> *also returns a blank line*
>>>
>>>
>>> How can i display the value 17 , while *executing shell script on remot
>>> ehost using ssh?*
>>> *
>>> *
>>> Please help.
>>>
>>> --
>>> Thanks,
>>> JD Patel
>>> You Got To Think HIGH to RISE.
>>>
>>>
>>>
>>
>>
>> --
>> --
>> Andrew Melo
>>
>>
>
>
> --
> Thanks,
> Jatin D N Patel
>
> You Got To Think HIGH to RISE.
>
>
>


-- 
--
Andrew Melo

Re: Parameterized build not working - plz help

[Jatin D Patel]

This is the steps which i have followed.



step 1:
Build a free-style software project

step 2:
IN configuration page, I have selected the option
"This build is parametreized"

Step 3:
Provide String parameter

Name : VERSION
default value : RELEASE
dESCRIPTION : abcd

Step 4:
Under the build section
SSH Site : My personal linux server
Command: : echo JAVA_HOME
WORKS FINE
echo $VERSION
echo "$version"
RETURNS Blank line.




Hope that i was clear ?
Please help.

On Mon, Mar 5, 2012 at 6:30 PM, Andrew Melo  wrote:

> Hi there,
>
> How are you submitting the job?
>
> -andrew
>
>
> On Mon, Mar 5, 2012 at 8:15 PM, Jatin D Patel wrote:
>
>> Hi all,
>>
>> I have set up a string value
>> Name : VERSION
>> Default Value : 17
>>
>> Ref: http://wiki.hudson-ci.org/display/HUDSON/Parameterized+Build
>>
>> When i try to access, the version value, i get a blank response
>>
>> echo $JAVA_HOME
>> returns Java Home location
>>
>> *echo $VERSION*
>> *returns a blank line*
>> *
>> *
>> *echo "$VERSION"*
>> *also returns a blank line*
>>
>>
>> How can i display the value 17 , while *executing shell script on remot
>> ehost using ssh?*
>> *
>> *
>> Please help.
>>
>> --
>> Thanks,
>> JD Patel
>> You Got To Think HIGH to RISE.
>>
>>
>>
>
>
> --
> --
> Andrew Melo
>
>


-- 
Thanks,
Jatin D N Patel
You Got To Think HIGH to RISE.

Upgrading Jenkins to 1.454 from the command line on Mac OS X caused file permission changes.

[Jerome Lacoste]

Today I upgraded jenkins on the command line using:

sudo installer -pkg jenkins-1.454.pkg -target /

This changed the permissions of the Jenkins home directory. I had to fix 
them using:

chown -R jenkins:daemon /Users/Shared/Jenkins/

Is that a bug ? If not, what is the proper procedure to remotely upgrade 
jenkins on Mac OS X and not loose setup ?

Jerome

Re: groovy plugin?

[Vojtech Juranek]

> On Mon, Mar 5, 2012 at 10:19 AM, Vojtech Juranek  
wrote:
> >> I was just missing something obvious.  Along with checking the
> >> 'Install automatically' box in the global config (which might have
> >> been set by default) you have to give it a name and then you have to
> >> pick that name in the job config.   Before getting this right, the job
> >> config only offered the 'default' verision, and until I went back to
> >> the job and changed it, it didn't trigger the install.  And until I
> >> clicked the drop-down on in the job config I don't realize there was a
> >> new option there.
> > 
> > thanks for feedback, IIRC this is standard behavior of any
> > auto-installer, but I'll check if I missed something somewhere
> 
> It makes sense now, but since I didn't understand it at first I set up
> a job with the 'default' groovy version which was the only choice, and
> it continued to fail after giving the install a name.   It would have
> helped to mention that the version names had to match in the ? help
> link in the main and job configs where you enter them.   Or maybe even
> to make the 'default' choice work with the auto-installed copy if you
> don't find one earlier in PATH.   Shouldn't that become the default if
> there is no other?

Yes, make sense, thank. Logged as JENKINS-12988 [1].
As for "default" - it's defined as calling "groovy" command - i.e. it calls the 
installation which you have as the first on the path. In some cases such setup 
can be useful, second problem is backward compatibility. So the only possible 
solution which has come to my mind so far is to keep this behavior and switch 
to some installation defined in global Jenkins config only if calling "groovy" 
fails - i.e. there's no groovy in the path. Does it make sense? 
Another possibility could be to add some checkbox which would allow users to 
define "default" installation in global jenkins config (as the user 
intentionally select the "default", he wants to change "default" behavior, so 
there shouldn't be a problem with backward compatibility).
Logged as JENKINS-12989 [2], feel free to add comments.
Thanks

[1] https://issues.jenkins-ci.org/browse/JENKINS-12988
[2] https://issues.jenkins-ci.org/browse/JENKINS-12989