Re: Anyway bind a build parameter to a boolean configuration field?

[cchen]

I think it addresses one of the use cases, but not all.  I hope someone 
could come up more general solution where one can create a build parameter 
and bind that to any field of the job config.  

Thanks for your help anyway!

On Saturday, March 16, 2013 11:02:15 AM UTC-7, syl20bnr wrote:
>
> I think there must be a way to do it via groovy script but I can't help 
> you on that side.
> Depending on what checkbox you want to bind, if this is a checkbox of a 
> build step or a publisher you can use the following plugins:
>
>- Conditional BuildStep Plugin
>- Flexible Publish Plugin
>
> If those plugins answer your question you can check for the Job Generator 
> plugin to generate cleaned job configurations without the conditional steps.
>
> Cheers,
> syl20bnr
>
> Le vendredi 15 mars 2013 14:39:40 UTC-4, cchen a écrit :
>>
>> Hello,
>>
>> Is there a way to bind a build parameter such as a boolean parameter to a 
>> checkbox in job configuration?
>>
>> Is there any workaround if there is no directly supported ways?
>>
>> Thanks!
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

New to Peforce Plugin

[anonymous]

Hi,

Can you please correct steps to connect Perforce and checkout the code and 
build the MAVEN project?

Do you have any set of instruction document for that? I am not able to 
connect with Perforce and getting this exception.

Please provide me some useful instruction with screen shot how to configure 
the Perforce source code in to Jenkins by using Perforce Plugin. 

===

at 
com.tek42.perforce.parse.AbstractPerforceTemplate.saveToPerforce(AbstractPerforceTemplate.java:263)
at com.tek42.perforce.parse.Workspaces.saveWorkspace(Workspaces.java:77)
at 
hudson.plugins.perforce.PerforceSCM.saveWorkspaceIfDirty(PerforceSCM.java:1642)
at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:795)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1353)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594)
at hudson.model.Run.execute(Run.java:1567)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
ERROR: Unable to communicate with perforce



Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

How do I change my Jenkins JIRA password?

[Jeff]

I'm trying to update my password on the Jenkins JIRA system after receiving
my temporary auto-generated password, but there is no change password link
anywhere on my profile page.

The help says it is not shown if using an external password management
system.  Assuming this is the case, where do I go to change it?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to upgrade Jenkins manually?

[Mark Waite]

Unfortunately, I'm not a Glassfish user, so I can't offer any helpful insights 
about how to perform an upgrade in that context.

Do you really need to run under Glassfish, or could you simplify your life and 
run with the Winstone server so that Jenkins is trivial to administer?

Mark Waite





>
> From: cjs1976 
>To: jenkinsci-users@googlegroups.com 
>Cc: Mark Waite  
>Sent: Tuesday, March 19, 2013 2:16 AM
>Subject: Re: How to upgrade Jenkins manually?
> 
>
>Hello Mark!
>
>
>I have a Windows 2003 R2 Server, and there runs a GlassFish 3.1.2.2 (build 5) 
>as a service.
>
>
>I created the JENKINS_HOME envoronment variable, restartet the GlassFish, 
>deployed the original Jenkins 1.504 war file, and everything seems to be 
>working. Jenkins uses the directory I want, and the builds are also working.
>
>
>Then there was the 1.505 update, and yesterday the 1.506 update.
>
>
>First I tried to deploy with the overwrite function and a restart of the 
>application, but it doesn't work. This should be the official way for an 
>update when not using Jenkins at a service itself?
>
>
>Then I tried to undeploy the application and deploy it new, but it's still the 
>old version.
>
>
>If I look in the application directory, I see, that the files are new, and 
>also in the MANIFEST.MF I see the right version number (1.506).
>
>
>I also restartet my whole server, but I still see the version 1.504 in my 
>Jenkins.
>
>
>I think, the problem comes because I use a special directory for the Jenkins 
>data. But I need to do this, I don't want the files to be in the user folder.
>
>
>Any idea?
>
>
>Greetings,
>Christian.
>
>
>
>
>Am Dienstag, 19. März 2013 00:16:05 UTC+1 schrieb Mark Waite:
>It depends where you're running Jenkins.
>>
>>If you're on a Windows machine and are running from a Desktop application 
>>(not a service), then stop the Jenkins process, replace the war file, and 
>>restart the Jenkins process.
>>
>>If you're on a Windows machine and are running as a service (installed with 
>>the Jenkins MSI installer), then use the operating system tools (MSI, etc.) 
>>to upgrade to the newer Jenkins version.
>>
>>If you're on a Linux, FreeBSD, or OpenBSD machine, you should use the 
>>operating system package management tools to update Jenkins.
>>
>>Where are you running Jenkins?
>>
>>Are you certain that the war file you deployed is the war file which is being 
>>used to run Jenkins?
>>
>>Mark Waite
>>
>>
>>
>>
>>
>>
>>>
>>> From: cjs1976 
>>>To: jenkins...@googlegroups. com 
>>>Sent: Monday, March 18, 2013 4:24 PM
>>>Subject: How to upgrade Jenkins manually?
>>> 
>>>
>>>Hi!
>>>
>>>
>>>How can I manually update Jenkins?
>>>
>>>
>>>I tried to deploy the new war file, overwriting the existing one, restart 
>>>the application but it still see the old version number.
>>>
>>>
>>>I also tried to delete and install new, but I also see only the old version 
>>>number.
>>>
>>>
>>>I have no idea.
>>>
>>>
>>>Thanks for help,
>>>Christian.
-- 
>>>You received this message because you are subscribed to the Google Groups 
>>>"Jenkins Users" group.
>>>To unsubscribe from this group and stop receiving emails from it, send an 
>>>email to jenkinsci-use...@ googlegroups.com.
>>>For more options, visit https://groups.google.com/ groups/opt_out.
>>> 
>>> 
>>>
>>>
>>>
-- 
>You received this message because you are subscribed to the Google Groups 
>"Jenkins Users" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to jenkinsci-users+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Perforce Plugin] New to this - issues linking hudson with perforce

[Thijs]

I have figured out, I need to add a couple of build steps.µ

The steps I need:

1) get latest files from my perforce server (This works)
2) execute build file with nant (this sort of works, still need to fix a 
bug with flex_home not being set on the machine)
3) let flashbuilder build my project (giving the project file as argument)
4) executing a bat file to let it create the wanted AIR file.

For now, i'm stuck with the 3th step.

how can i let hudson use flashbuilder to build a project? is there a plugin 
for that?

step 4 should be doable, i've seen the build step for a bat file in the 
configuration

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Perforce Plugin] New to this - issues linking hudson with perforce

[Thijs]

I have figured out, I need to add a couple of build steps.µ

The steps I need:

1) get latest files from my perforce server (This works)
2) execute build file with nant
3) let flashbuilder build my project (giving the project file as argument)
4) executing a bat file to let it create the wanted AIR file.

For now, i'm stuck with the 2n step.
I'v added nant to hudson, and i'v given it the path to my build file (it's 
in my workspace, //workspace/General/DKTools/DKTools.build )

For some reason it says now that it has an error loading the buildfile, 
"The Network Path was not found". What else do I need to give as a path so 
it will find my file inside the workspace?

And for step 3, how can i let hudson use flashbuilder to build a project? 
is there a plugin for that?

step 4 should be doable, i've seen the build step for a bat file in the 
configuration

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Re:Job works but Jenkins reports svn access problem

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

Sorry, you didn't post the actual URL in your initial message, and the URL 
shown in the diagnostic message looks like a filesystem path, not an HTTPS URL.

- Original Message -

From: jenkinsci-users@googlegroups.com

To: jenkinsci-users@googlegroups.com

At: Mar 19 2013 12:49:56

 
Hi Kevin

Thanks for your reply.

Ø  Since the URL you have provided is local to the slave's filesystem

Sorry, I don't understand.  In what sense have I specified the url as 'local to 
the slave's filesystem' ?

I have just used a https url.

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kevin Fleming 
(BLOOMBERG/ 731 LEXIN)

Sent: 19 March 2013 16:45

To: jenkinsci-users@googlegroups.com

Subject: Re:Job works but Jenkins reports svn access problem

The checking of this URL is being done on the Jenkins server, not on the slave. 
Since the URL you have provided is local to the slave's filesystem, the check 
will fail when done on the Jenkins server.

If the job works, just ignore this error/warning, because it's irrelevant for 
this job. In general, Jenkins SCM plugins assume that URLs that you provide to 
them will be accessible from *both* the Jenkins server and any slaves used for 
the jobs.

- Original Message -

From: jenkinsci-users@googlegroups.com

To: jenkinsci-users@googlegroups.com

At: Mar 19 2013 12:40:10

Hi

My simple Jenkins job runs on a Windows slave, checks out a Subversion project 
and executes a simple 'dir' command on it.

It works fine but, in the Configure screen, Jenkins reports an error for the 
svn url:

Unable to access /trunk : svn: OPTIONS /subversion/MyProject/trunk 
failed (show 
details)

org.tmatesoft.svn.core.SVNException: svn: OPTIONS /subversion/MyProject/trunk 
failed

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)

The url format I've used works fine for other jobs and, as I said above, the 
job works.

I'm running Jenkins LTS 1.480.3.

Entering svn credentials makes no difference, and I don't normally need to do 
that.

Any suggestions why I am getting an error please?

Best regards

David

--

You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Click 
here
 to report this email as spam.

--

You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

-- 

You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Email-ext plugin Groovy Grab

[Slide]

Pull requests are definitely the best way to get something in. Please
provide tests with your pull requests.


On Tue, Mar 19, 2013 at 10:02 AM, Rahul Somasunderam wrote:

> Would it make sense if I forked and submitted a PR which turns this on?
> I'm assuming anyone using html emails would benefit from this.
>
> R,
> rahul
>
> Rahul Somasunderam
> +1 510 270 2883
>
>
> On Mon, Mar 18, 2013 at 9:51 PM, Rahul Somasunderam 
> wrote:
>
>> https://gist.github.com/rahulsom/5125421
>>
>> These are my script and my template. If I get this going, my plan is to
>> turn images into attachments so we don't have to deal with the nag message
>> about external images.
>>
>> Rahul Somasunderam
>> +1 510 270 2883
>>
>>
>> On Mon, Mar 18, 2013 at 9:45 PM, Rahul Somasunderam 
>> wrote:
>>
>>> This actually gives a compilation error. Can I put a jar somewhere in
>>> the classpath and restart jenkins to let this work?
>>>
>>> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
>>> failed:
>>> Script1.groovy: 4: unable to resolve class org.jsoup.nodes.Document
>>>  @ line 4, column 1.
>>>import org.jsoup.nodes.Document;
>>>^
>>>
>>> Script1.groovy: 6: unable to resolve class org.jsoup.select.Elements
>>>  @ line 6, column 1.
>>>import org.jsoup.select.Elements;
>>>^
>>>
>>> Script1.groovy: 3: unable to resolve class org.jsoup.Jsoup
>>>  @ line 3, column 1.
>>>import org.jsoup.Jsoup;
>>>^
>>>
>>> Script1.groovy: 5: unable to resolve class org.jsoup.nodes.Element
>>>  @ line 5, column 1.
>>>import org.jsoup.nodes.Element;
>>>^
>>>
>>> 4 errors
>>>
>>> at 
>>> org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:302)
>>> at 
>>> org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:858)
>>> at 
>>> org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:548)
>>> at 
>>> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:497)
>>> at 
>>> groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:306)
>>> at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:287)
>>> at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731)
>>> at groovy.lang.GroovyShell.parse(GroovyShell.java:743)
>>> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:578)
>>> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
>>> at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)
>>> at 
>>> hudson.plugins.emailext.ExtendedEmailPublisher.executePresendScript(ExtendedEmailPublisher.java:415)
>>> at 
>>> hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:314)
>>> at 
>>> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:296)
>>> at 
>>> hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:256)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at 
>>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSite.invoke(PojoMetaMethodSite.java:189)
>>> at 
>>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
>>> at 
>>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>>> at 
>>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
>>> at 
>>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:124)
>>> at Script1$_run_closure1.doCall(Script1.groovy:26)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:601)
>>> at 
>>> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>>> at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>>> at 
>>> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
>>> at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
>>> at groovy.lang.Closure.call(Closure.java:412)
>>> at groovy.lang.Closure.call(Closure.java:425)
>>> at 
>>> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1377)
>>> at 
>>> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1349)
>>> at org.codehaus.groovy.runtime.dgm$149.invoke(Unknown Source)
>>> at 
>>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSite

Re: Email-ext plugin Groovy Grab

[Rahul Somasunderam]

Would it make sense if I forked and submitted a PR which turns this on?
I'm assuming anyone using html emails would benefit from this.

R,
rahul

Rahul Somasunderam
+1 510 270 2883


On Mon, Mar 18, 2013 at 9:51 PM, Rahul Somasunderam wrote:

> https://gist.github.com/rahulsom/5125421
>
> These are my script and my template. If I get this going, my plan is to
> turn images into attachments so we don't have to deal with the nag message
> about external images.
>
> Rahul Somasunderam
> +1 510 270 2883
>
>
> On Mon, Mar 18, 2013 at 9:45 PM, Rahul Somasunderam 
> wrote:
>
>> This actually gives a compilation error. Can I put a jar somewhere in the
>> classpath and restart jenkins to let this work?
>>
>> org.codehaus.groovy.control.MultipleCompilationErrorsException: startup 
>> failed:
>> Script1.groovy: 4: unable to resolve class org.jsoup.nodes.Document
>>  @ line 4, column 1.
>>import org.jsoup.nodes.Document;
>>^
>>
>> Script1.groovy: 6: unable to resolve class org.jsoup.select.Elements
>>  @ line 6, column 1.
>>import org.jsoup.select.Elements;
>>^
>>
>> Script1.groovy: 3: unable to resolve class org.jsoup.Jsoup
>>  @ line 3, column 1.
>>import org.jsoup.Jsoup;
>>^
>>
>> Script1.groovy: 5: unable to resolve class org.jsoup.nodes.Element
>>  @ line 5, column 1.
>>import org.jsoup.nodes.Element;
>>^
>>
>> 4 errors
>>
>>  at 
>> org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:302)
>>  at 
>> org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:858)
>>  at 
>> org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:548)
>>  at 
>> org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:497)
>>  at 
>> groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:306)
>>  at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:287)
>>  at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731)
>>  at groovy.lang.GroovyShell.parse(GroovyShell.java:743)
>>  at groovy.lang.GroovyShell.evaluate(GroovyShell.java:578)
>>  at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
>>  at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)
>>  at 
>> hudson.plugins.emailext.ExtendedEmailPublisher.executePresendScript(ExtendedEmailPublisher.java:415)
>>  at 
>> hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:314)
>>  at 
>> hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:296)
>>  at 
>> hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:256)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>  at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>  at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  at java.lang.reflect.Method.invoke(Method.java:601)
>>  at 
>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSite.invoke(PojoMetaMethodSite.java:189)
>>  at 
>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
>>  at 
>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
>>  at 
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
>>  at 
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:124)
>>  at Script1$_run_closure1.doCall(Script1.groovy:26)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>  at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>  at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>  at java.lang.reflect.Method.invoke(Method.java:601)
>>  at 
>> org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
>>  at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
>>  at 
>> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
>>  at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
>>  at groovy.lang.Closure.call(Closure.java:412)
>>  at groovy.lang.Closure.call(Closure.java:425)
>>  at 
>> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1377)
>>  at 
>> org.codehaus.groovy.runtime.DefaultGroovyMethods.each(DefaultGroovyMethods.java:1349)
>>  at org.codehaus.groovy.runtime.dgm$149.invoke(Unknown Source)
>>  at 
>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271)
>>  at 
>> org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMetaMethodSite.java:53)
>>  at 
>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)

RE: Re:Job works but Jenkins reports svn access problem

[David Aldrich]

Hi Kevin

Thanks for your reply.


Ø  Since the URL you have provided is local to the slave's filesystem

Sorry, I don't understand.  In what sense have I specified the url as 'local to 
the slave's filesystem' ?

I have just used a https url.

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Kevin Fleming 
(BLOOMBERG/ 731 LEXIN)
Sent: 19 March 2013 16:45
To: jenkinsci-users@googlegroups.com
Subject: Re:Job works but Jenkins reports svn access problem

The checking of this URL is being done on the Jenkins server, not on the slave. 
Since the URL you have provided is local to the slave's filesystem, the check 
will fail when done on the Jenkins server.

If the job works, just ignore this error/warning, because it's irrelevant for 
this job. In general, Jenkins SCM plugins assume that URLs that you provide to 
them will be accessible from *both* the Jenkins server and any slaves used for 
the jobs.

- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Mar 19 2013 12:40:10

Hi

My simple Jenkins job runs on a Windows slave, checks out a Subversion project 
and executes a simple 'dir' command on it.

It works fine but, in the Configure screen, Jenkins reports an error for the 
svn url:

Unable to access /trunk : svn: OPTIONS /subversion/MyProject/trunk 
failed (show 
details)


org.tmatesoft.svn.core.SVNException: svn: OPTIONS /subversion/MyProject/trunk 
failed

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)

The url format I've used works fine for other jobs and, as I said above, the 
job works.

I'm running Jenkins LTS 1.480.3.

Entering svn credentials makes no difference, and I don't normally need to do 
that.

Any suggestions why I am getting an error please?

Best regards

David

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




Click 
here
 to report this email as spam.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re:Job works but Jenkins reports svn access problem

[Kevin Fleming (BLOOMBERG/ 731 LEXIN)]

The checking of this URL is being done on the Jenkins server, not on the slave. 
Since the URL you have provided is local to the slave's filesystem, the check 
will fail when done on the Jenkins server.

If the job works, just ignore this error/warning, because it's irrelevant for 
this job. In general, Jenkins SCM plugins assume that URLs that you provide to 
them will be accessible from *both* the Jenkins server and any slaves used for 
the jobs.

- Original Message -

From: jenkinsci-users@googlegroups.com

To: jenkinsci-users@googlegroups.com

At: Mar 19 2013 12:40:10

 
Hi

My simple Jenkins job runs on a Windows slave, checks out a Subversion project 
and executes a simple 'dir' command on it.

It works fine but, in the Configure screen, Jenkins reports an error for the 
svn url:

Unable to access /trunk : svn: OPTIONS /subversion/MyProject/trunk 
failed (show 
details)

org.tmatesoft.svn.core.SVNException: svn: OPTIONS /subversion/MyProject/trunk 
failed

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)

The url format I've used works fine for other jobs and, as I said above, the 
job works.

I'm running Jenkins LTS 1.480.3.

Entering svn credentials makes no difference, and I don't normally need to do 
that.

Any suggestions why I am getting an error please?

Best regards

David

-- 

You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Job works but Jenkins reports svn access problem

[David Aldrich]

Hi

My simple Jenkins job runs on a Windows slave, checks out a Subversion project 
and executes a simple 'dir' command on it.

It works fine but, in the Configure screen, Jenkins reports an error for the 
svn url:

Unable to access /trunk : svn: OPTIONS /subversion/MyProject/trunk 
failed (show 
details)


org.tmatesoft.svn.core.SVNException: svn: OPTIONS /subversion/MyProject/trunk 
failed

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)

at 
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)

The url format I've used works fine for other jobs and, as I said above, the 
job works.

I'm running Jenkins LTS 1.480.3.

Entering svn credentials makes no difference, and I don't normally need to do 
that.

Any suggestions why I am getting an error please?

Best regards

David

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Simple Jenkins job fails - wrong working directory

[David Aldrich]

Thanks for your reply.  Just realised that I omitted to tie the job to a node.

Sorry. Works ok now.

I have another problem and will start a new thread.

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of H3llGhost
Sent: 19 March 2013 16:27
To: jenkinsci-users@googlegroups.com
Subject: Re: Simple Jenkins job fails - wrong working directory

Hello David,

did you set up a custom workspace path in the project?

Best Regards

Am 19.03.2013 17:16, schrieb David Aldrich:
Hi

I have created a very simple job for a new Windows slave.  The 'Remote FS root' 
of the slave is set to:

C:\Jenkins

The job checks out a svn repo and executes a very simple Windows batch command:

dir

When it runs, the checkout succeeds but the dir command fails:


FATAL: command execution failed
java.io.IOException: Cannot run program "cmd" (in directory "/data//workspace/"):

Why is Jenkins doing its work in /data/... and not in c:\Jenkins?

Best regards

David

--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.





Click 
here
 to report this email as spam.
--
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Simple Jenkins job fails - wrong working directory

[H3llGhost]

Hello David,

did you set up a custom workspace path in the project?

Best Regards


Am 19.03.2013 17:16, schrieb David Aldrich:


Hi

I have created a very simple job for a new Windows slave.  The 'Remote 
FS root' of the slave is set to:


C:\Jenkins

The job checks out a svn repo and executes a very simple Windows batch 
command:


dir

When it runs, the checkout succeeds but the dir command fails:

FATAL: command execution failed

java.io.IOException: Cannot run program "cmd" (in directory 
"/data//workspace/"):


Why is Jenkins doing its work in /data/... and not in c:\Jenkins?

Best regards

David

--
You received this message because you are subscribed to the Google 
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to jenkinsci-users+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.




--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Simple Jenkins job fails - wrong working directory

[David Aldrich]

Hi

I have created a very simple job for a new Windows slave.  The 'Remote FS root' 
of the slave is set to:

C:\Jenkins

The job checks out a svn repo and executes a very simple Windows batch command:

dir

When it runs, the checkout succeeds but the dir command fails:


FATAL: command execution failed
java.io.IOException: Cannot run program "cmd" (in directory "/data//workspace/"):

Why is Jenkins doing its work in /data/... and not in c:\Jenkins?

Best regards

David

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins 1.506 m2release plugin issue JSONNull cannot be cast to JSONObject

[teilo]

On Monday, 18 March 2013 18:44:18 UTC, Tomek Kaczanowski wrote:
>
> Hi James, 
>
> thanks for the quick response! 
>
> > the simplest quick fix is to downgrade Jenkins... 
> yeah, sure it is 
>
> > What version did you upgrade from - and what options/parameters are you 
> > using? 
> 1.496 
>
 

> what options/parameters you are asking about? 
>

When you release there are options for the username/password, comment 
prefix, tag, nexus pro support..

There was a similar defect raised when the plugin was run in Hudson 2.2 - 
and I think Jenkins recently updated it's json library...  So the problem 
may be how to get this to work in a backwards compatible way.
In the interim there is a pull request that will fix this (not tested on 
older releases yet) so you may be able to grab that, build locally and use 
it to unblock you whilst I look at if anything else is needed. 
 https://github.com/jenkinsci/m2release-plugin/pull/9


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: Build failure Analyzer Plugin’s odd behaviour

[Sandell, Robert]

The BFA uses thread-pools in two different places; One pool is created for 
every finished build to scan the log in parallel (we have a big number of 
builds with 10MB log files or more, so that helped with performance). But those 
pools should be closed down when the scanning is done.
The other is during startup when it needs to convert old build data to the new 
format (<1.3.0 to 1.4.0). That thread pool is not closed because of the lazy 
loading of builds in newer Jenkins cores.
The conversion thread pool should not be created if Jenkins starts up with only 
newer format of build records.


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: Yitzhak Zuriel [mailto:zurie...@gmail.com]
Sent: den 18 mars 2013 11:29
To: jenkinsci-users@googlegroups.com
Cc: Westling, Tomas; Sandell, Robert; jhoomshar...@netscape.net
Subject: Re: Build failure Analyzer Plugin’s odd behaviour

I'm reviving this old thread because I have some new information that was not 
written here before. We moved on to work with a different server and continued 
to monitor and study the problematic one.using some of the Java tools.  And we 
saw that on the machine with the sluggish response there was a proliferation of 
threads in Java that were not being closed. Has anyone seen this behavior, and 
has an explanation of what to do about it?


On Thursday, January 24, 2013 8:44:23 AM UTC+2, 
jhooms...@netscape.net wrote:
No ours not matrix project

I think my issue is same as JENKINS-15948, icon image url looks to be broken, 
the url getting generated for bulb icon image is

http://[host]/jenkins//plugin/build-failure-analyzer/images/16x16/information.png

but in actual it should be

http://[host]/plugin/build-failure-analyzer/images/16x16/information.png

I am using build analyzer plugin v1.3.0

-Original Message-
From: Westling, Tomas >
To: 'jhooms...@netscape.net' 
>; jenkinsci-users 
>
Cc: Sandell, Robert >
Sent: Wed, Jan 23, 2013 5:30 pm
Subject: RE: Build failure Analyzer Plugin’s odd behaviour
Is your project a matrix project? If so then I’ve found the bug and will upload 
a bug fix.

Br Tomas

From: jhooms...@netscape.net 
[mailto:jh...@netscape.net]
Sent: den 23 januari 2013 09:42
To: Westling, Tomas; jenkins...@googlegroups.com
Cc: Sandell, Robert
Subject: Re: Build failure Analyzer Plugin’s odd behaviour


Attaching screen shot related to missing bulb icon

-Original Message-
From: Westling, Tomas >
To: 'jhooms...@netscape.net' 
>; jenkinsci-users 
>
Cc: Sandell, Robert >
Sent: Tue, Jan 22, 2013 5:59 pm
Subject: RE: Build failure Analyzer Plugin’s odd behaviour
Hi Jhoom,

issue number 3 is a known problem which we are working on. The issue is with
logs that are large enough so that the build log has to be split up and the 
“full log”
is visible. We are going to release a bug fix for this issue soon.

As for the other two issues I am not quite sure what you mean, are the bulb 
icons missing for
builds that have identified the problem? Could you attach a screenshot of the 
problem?

Br Tomas

From: jhooms...@netscape.net 
[mailto:jh...@netscape.net]
Sent: den 22 januari 2013 12:58
To: jenkins...@googlegroups.com
Cc: Sandell, Robert; Westling, Tomas
Subject: Build failure Analyzer Plugin’s odd behaviour

Hi
I am seeing strange problem on my Jenkins 1.496 server running on Solaris box,
1.  I cannot see Build Failure Analyzer plugin bulb icon under “Build 
History” section instate of icon a text “Identified problems” is visible
2.  When I click on logs under “Build History” for a particular 
failed/unstable build again bulb icon is missing only following messages are 
visible:

Identified problems

Unit Test Failure
Contains test case failure
Indication 1 Indication 2
3.  When I click on “Indication” links, it takes me to build logs but did 
not show the problem with red highlight, I need to click on “Full log” link and 
then navigate to build log to look for highlighted error.

Anyone faced this problem in their dev environment with Build Failure Analyzer, 
if yes can anyone help me out and resolving this issue.

Thanks,
Jhoom

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to upgrade Jenkins manually?

[cjs1976]

Hello Mark!

I have a Windows 2003 R2 Server, and there runs a GlassFish 3.1.2.2 (build 
5) as a service.

I created the JENKINS_HOME envoronment variable, restartet the GlassFish, 
deployed the original Jenkins 1.504 war file, and everything seems to be 
working. Jenkins uses the directory I want, and the builds are also working.

Then there was the 1.505 update, and yesterday the 1.506 update.

First I tried to deploy with the overwrite function and a restart of the 
application, but it doesn't work. This should be the official way for an 
update when not using Jenkins at a service itself?

Then I tried to undeploy the application and deploy it new, but it's still 
the old version.

If I look in the application directory, I see, that the files are new, and 
also in the MANIFEST.MF I see the right version number (1.506).

I also restartet my whole server, but I still see the version 1.504 in my 
Jenkins.

I think, the problem comes because I use a special directory for the 
Jenkins data. But I need to do this, I don't want the files to be in the 
user folder.

Any idea?

Greetings,
Christian.


Am Dienstag, 19. März 2013 00:16:05 UTC+1 schrieb Mark Waite:
>
> It depends where you're running Jenkins.
>
> If you're on a Windows machine and are running from a Desktop application 
> (not a service), then stop the Jenkins process, replace the war file, and 
> restart the Jenkins process.
>
> If you're on a Windows machine and are running as a service (installed 
> with the Jenkins MSI installer), then use the operating system tools (MSI, 
> etc.) to upgrade to the newer Jenkins version.
>
> If you're on a Linux, FreeBSD, or OpenBSD machine, you should use the 
> operating system package management tools to update Jenkins.
>
> Where are you running Jenkins?
>
> Are you certain that the war file you deployed is the war file which is 
> being used to run Jenkins?
>
> Mark Waite
>
>
>   --
> *From:* cjs1976 >
> *To:* jenkins...@googlegroups.com  
> *Sent:* Monday, March 18, 2013 4:24 PM
> *Subject:* How to upgrade Jenkins manually?
>  
> Hi!
>
> How can I manually update Jenkins?
>
> I tried to deploy the new war file, overwriting the existing one, restart 
> the application but it still see the old version number.
>
> I also tried to delete and install new, but I also see only the old 
> version number.
>
> I have no idea.
>
> Thanks for help,
> Christian.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
>
>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.