Re: Passing environment variables using the parameterized trigger plugin

[Adam Mercer]

On Thu, Nov 13, 2014 at 4:17 PM, Daniel Beck  wrote:

> So it behaves correctly. The label part is only part of the sub-builds (where 
> the project name has the suffix with the active axis values), not the overall 
> build (which does not), and if the trigger is run once for the overall build, 
> the axes values are not part of that.

Ok thanks. Looks like I've going to pass the parameters via a file.

Cheers

Adam

-- 
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/d/optout.

Re: Passing environment variables using the parameterized trigger plugin

[Adam Mercer]

On Fri, Nov 7, 2014 at 7:17 AM, Daniel Beck  wrote:
> Is the downstream build triggered for every matrix axis that finishes 
> building, or only once, when all axes finished?

Sorry for the delay I've been busy with getting a release out of the door.

The downstream build is triggered when all axes are finished.

Cheers

Adam

-- 
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/d/optout.

Re: Passing environment variables using the parameterized trigger plugin

[Adam Mercer]

On Thu, Nov 6, 2014 at 4:15 PM, Ginga, Dick  wrote:
> Change the jobname to labl:sl6? Or labl-sl6?

I can't, that's what Jenkins assigns. The job itself is called LAL and
the matrix plugin adds /label=sl6, /label=wheezy, etc... depending on
which operating system I'm trying to build on. I build the software on
several different operating systems and use the Matrix plugin to run
builds on different systems.

Cheers

Adam

-- 
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/d/optout.

Re: Passing environment variables using the parameterized trigger plugin

[Adam Mercer]

On Thu, Nov 6, 2014 at 7:15 AM, Ginga, Dick  wrote:
> Perhaps the label=sl6 is getting parsed as another parameter?? Try \'ing it:  
> label\=sl6

Interesting idea, that kind of makes sense. The problem is that
there's nothing for me to escape, as label=sl6 is part of JOB_NAME
itself.

Cheers

Adam

-- 
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/d/optout.

Re: Passing environment variables using the parameterized trigger plugin

[Adam Mercer]

On Wed, Nov 5, 2014 at 4:30 PM, Dunnigan, Terrence J
 wrote:

> Are you using a recent version of Jenkins and the parameterized plugin?

The current LTS release and the latest parameterized plugin, at least
Jenkins tells me that no updates are available for my plugins.

> I suspect the problem is that you are defining $PREFIX locally on the 
> machine, and then trying to reference it via a Jenkins job configuration. 
> When I’ve encountered that situation I’ve worked around it by writing the 
> value to a .properties file and then passing that file to the downstream job 
> (using the ‘Parameters from a properties file’) option.

That sounds like what I'm going to need to do.

> As for the other environment variables, passing $JOB_NAME and $BUILD_NUMBER 
> work just fine for me.

BUILD_NUMBER works without an issue, JOB_NAME is only partially
passed. The value is Job1 is "LALSuite/LAL/label=sl6" but only
"LALSuite/LAL" is passed to Job2, the label=sl6 part is dropped.

Cheers

Adam

-- 
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/d/optout.

Passing environment variables using the parameterized trigger plugin

[Adam Mercer]

Hi

According to the documentation for the Parameterized Trigger plugin,
specifically for 'Predefined parameters":

"""
KEY=value pairs, one per line (Java properties file format).
Backslashes are used for escaping, so use "\\" for a single backslash.

Current build parameters and/or environment variables can be used in
form: ${PARAM} or $PARAM
"""

I'm trying to use this to pass the contents of an environment variable
to the next job in line, but it is not passed. In Job1 is essentially
the execution of the following script:

#!/bin/bash
# display job parameters
echo "JOB_NAME = $JOB_NAME"
echo "BUILD_NUMBER = $BUILD_NUMBER"
export PREFIX=/build/$JOB_NAME/$BUILD_NUMBER/lal
echo "Installing in $PREFIX"

And in the "Predetermined parameters" section I have:

LAL_JOB_NAME=$JOB_NAME
LAL_BUILD_NUMBER=$BUILD_NUMBER
LAL_PREFIX=$PREFIX

When Job1 completes successfully and outputs:

JOB_NAME = LALSuite/LAL/label=sl6
BUILD_NUMBER = 6
Installing in /build/LALSuite/LAL/label=sl6/6/lal
Finished: SUCCESS

It then triggers Job2 which is essentially the following script:

#!/bin/bash
# show parameters
echo "LAL_JOB_NAME = $LAL_JOB_NAME"
echo "LAL_BUILD_NUMBER = $LAL_BUILD_NUMBER"
echo "LAL_PREFIX = $LAL_PREFIX"

When executed Job2 displays:

LAL_JOB_NAME = LALSuite/LAL
LAL_BUILD_NUMBER = 6
LAL_PREFIX = ${PREFIX}

So the contents of JOB_NAME isn't being passed correctly the value of
the PREFIX environment variable is being completely ignored.

How can I pass the contents of an environment variable to another job
using the parameterized trigger plugin? Or is there another plugin
that would be better in this situation?

Cheers

Adam

-- 
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/d/optout.

null build slaves when selecting labels to build in matrix plugin

[Adam Mercer]

Hi

I've upgraded my test Jenkins instance to 1.580.1, to validate before
upgrading my production instance, and since doing so the matrix plugin
doesn't seem to be working correctly. When selecting nodes/labels to
build in the Configuration Matrix there doesn't seem to be any match
between label and nodes.

With 1.565.3 when selecting a label in brackets there was a list of
the nodes which satisfies this label, with 1.580.1 there is just
"null". Similarly when selecting nodes 1.565.3 shows the description
of the node whereas 1.580.1 shows "null".

Whilst this just seems to be a cosmetic issue I'm concerned that
because of this jobs could be run on machines without the appropriate
label and lead to unusual build errors.

Cheers

Adam

-- 
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/d/optout.

Re: Stack trace when trying to view buile node workspace

[Adam Mercer]

I'm still seeing this. Any ideas?

Cheers

Adam

On Tue, Oct 28, 2014 at 7:50 AM, Adam Mercer  wrote:
> Hi
>
> I was trying to view a failed test log from the workspace of a project
> this morning and I received the following stack trace:
>
> java.io.IOException: Remote call on builder-sl6-1 failed
> at hudson.remoting.Channel.call(Channel.java:751)
> at hudson.FilePath.act(FilePath.java:1009)
> at jenkins.util.VirtualFile$FilePathVF.run(VirtualFile.java:361)
> at 
> hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:254)
> at 
> hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:123)
> at 
> org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124)
> at 
> org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69)
> at org.kohsuke.stapler.Function.renderResponse(Function.java:113)
> at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:98)
> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
> at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
> at 
> hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at 
> org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
> at 
> hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
> at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
> at 
> org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
> at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
> at 
> hudson.util.CharacterEncodingFilter.d

Re: JOB_NAME not being passed correctly with Parametrized Trigger Plugin

[Adam Mercer]

On Thu, Oct 30, 2014 at 1:31 PM, Ross Aribi  wrote:
> You have two jobs, Job1 calling Job2. The parameter $JOB_NAME is local to
> each job, so in Job2 the value of $JOB_NAME is Job2.
> Add an additional param in Job1 ($JOB_1_NAME=$JOB_NAME) and use it in Job2.

That's exactly what I'm doing, these are the parameters I'm passing
from Job1 to Job2

LAL_JOB_NAME=$JOB_NAME
LAL_BUILD_NUMBER=$BUILD_NUMBER

In Job2 the labl=sl6 is not present in LAL_JOB_NAME even though it is
in the JOB_NAME from Job1.

Cheers

Adam

-- 
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/d/optout.

Re: JOB_NAME not being passed correctly with Parametrized Trigger Plugin

[Adam Mercer]

On Thu, Oct 30, 2014 at 11:56 AM, T. Anthony Rabaa  wrote:
> If you're building on the same node, why not pass in the full path to the 
> libraries as a parameter?

Good idea. I'll give that a go.

Cheers

Adam

-- 
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/d/optout.

Stack trace when trying to view buile node workspace

[Adam Mercer]

Hi

I was trying to view a failed test log from the workspace of a project
this morning and I received the following stack trace:

java.io.IOException: Remote call on builder-sl6-1 failed
at hudson.remoting.Channel.call(Channel.java:751)
at hudson.FilePath.act(FilePath.java:1009)
at jenkins.util.VirtualFile$FilePathVF.run(VirtualFile.java:361)
at 
hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:254)
at 
hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:123)
at 
org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124)
at 
org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69)
at org.kohsuke.stapler.Function.renderResponse(Function.java:113)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:98)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.d

Re: JOB_NAME not being passed correctly with Parametrized Trigger Plugin

[Adam Mercer]

Hi

Anyone? Surely the plugin shouldn't be stripping information when
passing it on to downstream jobs?

Cheers

Adam

On Thu, Oct 23, 2014 at 5:15 PM, Adam Mercer  wrote:
> Hi
>
> I'm trying to tie a couple of jobs together using the Parametrized
> Trigger Plugin and am running into problems with the second job
> finding the libraries built by the first job.
>
> When the first job completes successfully I trigger a build of the
> second job, I'm forcing it to use the same node so that it can find
> the libraries. In the first job I install the libraries to a location
> on the build slave dependent upon the JOB_NAME and BUILD_NUMBER
> variables. I use the Parametrized Trigger Plugin to pass these onto
> the second job. However it look like that value of JOB_NAME that is
> getting passed on is incorrect and as such the library can't be found
> by the second job and the build fails.
>
> In order to start debugging this I printed out the value of JOB_NAME
> from the first job and the value that was passed to the second job,
> they differed. In the first job JOB_NAME is set to
> LALSuite/LAL/label=sl6 whereas is the second job it is seeing
> LALSuite/LAL, i.e. the label=sl6 is being dropped.
>
> Any ideas why this label information is not being passed along?
>
> Cheers
>
> Adam

-- 
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/d/optout.

JOB_NAME not being passed correctly with Parametrized Trigger Plugin

[Adam Mercer]

Hi

Hi

I'm trying to tie a couple of jobs together using the Parametrized
Trigger Plugin and am running into problems with the second job
finding the libraries built by the first job.

When the first job completes successfully I trigger a build of the
second job, I'm forcing it to use the same node so that it can find
the libraries. In the first job I install the libraries to a location
on the build slave dependent upon the JOB_NAME and BUILD_NUMBER
variables. I use the Parametrized Trigger Plugin to pass these onto
the second job. However it look like that value of JOB_NAME that is
getting passed on is incorrect and as such the library can't be found
by the second job and the build fails.

In order to start debugging this I printed out the value of JOB_NAME
from the first job and the value that was passed to the second job,
they differed. In the first job JOB_NAME is set to
LALSuite/LAL/label=sl6 whereas is the second job it is seeing
LALSuite/LAL, i.e. the label=sl6 is being dropped.

Any ideas why this label information is not being passed along?

Cheers

Adam

-- 
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/d/optout.

Re: Getting metadata of another sub-project in Multijob project

[Adam Mercer]

On Tue, Aug 19, 2014 at 8:18 AM, Ginga, Dick  wrote:

> The Parameterized Trigger plugin lets you trigger one job from another and 
> pass to that job a set of parameters. You can use the $BUILD_NUMBER and 
> $JOB_NAME as parameters.

Thanks, that seems to be useful.

> There is also the Build Flow plugin that provide a DSL for scripting job 
> execution. It exposes some underlying Jenkins objects that you can fetch all 
> kinds of information from and pass onto other jobs, again, as parameters.

Thanks, that also looks interesting...

Cheers

Adam

-- 
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/d/optout.

Re: Getting metadata of another sub-project in Multijob project

[Adam Mercer]

Can anyone offer any help regarding this? Or point to some useful
documentation as the plugin documentation is not much help?

Cheers

Adam

On Thu, Aug 14, 2014 at 3:21 PM, Adam Mercer  wrote:
> Hi
>
> I'm trying to use the Multijob plugin write a series of jobs for
> building a connected series of libraries. How can I pass appropriate
> metadata from one project to subsequent projects. For example the
> BUILD_NUMBER and the JOB_NAME?
>
> Or is the Multijob plugin not the best way to achieve this?
>
> Cheers
>
> Adam

-- 
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/d/optout.

Getting metadata of another sub-project in Multijob project

[Adam Mercer]

Hi

I'm trying to use the Multijob plugin write a series of jobs for
building a connected series of libraries. How can I pass appropriate
metadata from one project to subsequent projects. For example the
BUILD_NUMBER and the JOB_NAME?

Or is the Multijob plugin not the best way to achieve this?

Cheers

Adam

-- 
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/d/optout.

Re: Dead threads on build slaves

[Adam Mercer]

Hi

Managed to figure this out, turns out the server running Jenkins ran
into a file system problem and the root filesystem was remounted
read-only. FIxing the file system problem got things running again.

Cheers

Adam

On Sun, Jul 6, 2014 at 11:00 AM, Adam Mercer  wrote:
> Hi
>
> This morning one of my builds slaves was reporting that both it's
> executors were Dead and reported traces such as:
>
> java.io.IOException: Failed to create a temporary file in
> /var/lib/jenkins/jobs/PyLAL_Epydoc
> at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:67)
> at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:54)
> at hudson.util.TextFile.write(TextFile.java:84)
> at hudson.model.Job.saveNextBuildNumber(Job.java:266)
> at hudson.model.Job.assignBuildNumber(Job.java:323)
> at hudson.model.Run.(Run.java:289)
> at hudson.model.AbstractBuild.(AbstractBuild.java:177)
> at hudson.model.Build.(Build.java:92)
> at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:34)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:534)
> at hudson.model.AbstractProject.newBuild(AbstractProject.java:1127)
> at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1349)
> at hudson.model.AbstractProject.createExecutable(AbstractProject.java:156)
> at hudson.model.Executor.run(Executor.java:211)
> Caused by: java.io.IOException: Read-only file system
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.checkAndCreate(File.java:1833)
> at java.io.File.createTempFile0(File.java:1857)
> at java.io.File.createTempFile(File.java:1934)
> at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:65)
> ... 16 more
>
> Looking in the log I get the following extra information:
>
> Jul 06, 2014 10:40:12 AM SEVERE
> hudson.remoting.SynchronousCommandTransport$ReaderThread run
>
> I/O error in channel MacOSX
> java.io.IOException: Unexpected termination of the channel
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> Caused by: java.io.EOFException
> at 
> java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1317)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
> at hudson.remoting.Command.readFrom(Command.java:92)
> at 
> hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
> at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
>
> The first stack track is complaining about being unable to write in
> /var/lib/jenkins/jobs/PyLAL_Epydoc, is this on the server or the
> slave? The slave is a Mac OS X machine and the jenkins user's home
> directory is /Users/jenkins so I'm a little confused as to why is
> trying to write in that directory?
>
> Disconnecting and reconnecting the box results in the same issue, as
> does rebooting the slave.
>
> How can I get more information as to what is going wrong with this box?
>
> Cheers
>
> Adam

-- 
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/d/optout.

Dead threads on build slaves

[Adam Mercer]

Hi

This morning one of my builds slaves was reporting that both it's
executors were Dead and reported traces such as:

java.io.IOException: Failed to create a temporary file in
/var/lib/jenkins/jobs/PyLAL_Epydoc
at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:67)
at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:54)
at hudson.util.TextFile.write(TextFile.java:84)
at hudson.model.Job.saveNextBuildNumber(Job.java:266)
at hudson.model.Job.assignBuildNumber(Job.java:323)
at hudson.model.Run.(Run.java:289)
at hudson.model.AbstractBuild.(AbstractBuild.java:177)
at hudson.model.Build.(Build.java:92)
at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:34)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:534)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1127)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1349)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:156)
at hudson.model.Executor.run(Executor.java:211)
Caused by: java.io.IOException: Read-only file system
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.checkAndCreate(File.java:1833)
at java.io.File.createTempFile0(File.java:1857)
at java.io.File.createTempFile(File.java:1934)
at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:65)
... 16 more

Looking in the log I get the following extra information:

Jul 06, 2014 10:40:12 AM SEVERE
hudson.remoting.SynchronousCommandTransport$ReaderThread run

I/O error in channel MacOSX
java.io.IOException: Unexpected termination of the channel
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at 
java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1317)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at hudson.remoting.Command.readFrom(Command.java:92)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

The first stack track is complaining about being unable to write in
/var/lib/jenkins/jobs/PyLAL_Epydoc, is this on the server or the
slave? The slave is a Mac OS X machine and the jenkins user's home
directory is /Users/jenkins so I'm a little confused as to why is
trying to write in that directory?

Disconnecting and reconnecting the box results in the same issue, as
does rebooting the slave.

How can I get more information as to what is going wrong with this box?

Cheers

Adam

-- 
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/d/optout.

Re: Proxy Error when trying to view workspace

[Adam Mercer]

On Wed, Mar 5, 2014 at 5:20 PM, Daniel Beck  wrote:
> If there are many directory entries in the particular directory you're 
> viewing, likely because of JENKINS-21780:
> https://issues.jenkins-ci.org/browse/JENKINS-21780

That sounds like it. Thanks.

Cheers

Adam

-- 
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: Proxy Error when trying to view workspace

[Adam Mercer]

On Wed, Mar 5, 2014 at 1:19 PM, Daniel Beck  wrote:
> You're running Jenkins behind a reverse proxy (Apache, nginx, ...) and 
> Jenkins takes so long to respond that the proxy gives up.
>
> Increase the timeout.

But why is it taking so long? The machine which is workspace is on is
contented via a private network to the main jenkins server so it
should have fast communication?

Cheers

Adam

-- 
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.

Proxy Error when trying to view workspace

[Adam Mercer]

Hi

Access to a jobs workspace has always been slow for me but this
morning it's timing out and I'm getting an error of the following form
when trying to view the workspace:

"""
Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET
/job/JOBNAME/label=sl6/ws/path/to/files/.

Reason: Error reading from remote server
"""

Could this be due to a configuration issue? Any ideas of where to look
to figure out what's going on here?

Cheers

Adam

-- 
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: Triggering multiple builds with the Git Plugin.

[Adam Mercer]

Sorry, I've no experience with the build flow plugin.

Cheers

Adam

On Fri, Oct 11, 2013 at 5:26 AM, Neetish Jethra  wrote:
> Correction ... I cannot really use your workaround of a custom workspace
> because the build flow plugin does NOT show up the option of setting a
> workspace
>
>
> On Friday, October 11, 2013 3:23:24 PM UTC+11, Neetish Jethra wrote:
>>
>> Hi Adam,
>>
>> I have been facing the same problem for our build and your workaround
>> works fine for normal builds and makes sure new builds are triggered via SCM
>> polling when a build is still in progress.
>>
>> However,  I cannot get this workaround to work when I am using a Build
>> Flow project created using the Build Flow plugin
>> (https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin).
>>
>> So, to summarize, my build flow project triggers a job that builds the
>> artefact that I want to test / deploy, followed by few parallel jobs that
>> test the artefact. If all of the parallel jobs work, I publish the artefact
>> to another repository to make it available for manual tesing (the publish is
>> done via a jenkins job as well).
>>
>> The orchestration of the jobs is done by the build flow project and it is
>> also responsible for git polling.
>>
>> I can see the same behaviour as mentioned by cjo, where the polling starts
>> but then gets stuck while the current job is still running.
>>
>> "
>> This might be a workspace locking issue as the polling log you post seems
>> to indicate that the polling has started [1], but has not completed.
>> even though the concurrent is allowed.
>> "
>>
>> I cannot really use your workaround of a custom workspace because the
>> build flow plugin does NOT show up the option of setting a workspace. From
>> what I understand, the Build Flow job uses a lightweight execution
>> environment and does not require any executors.
>>
>> Is there another way you can think of for achieving this . If you could
>> throw some light on how you arrived at the workaround, it might help me to
>> figure out a solution for my case.
>>
>> Thanks,
>>
>> Neetish.
>>
>>
>>
>>
>>
>>
>>
>> On Thursday, February 7, 2013 4:24:48 PM UTC+11, Adam Mercer wrote:
>>>
>>> On Mon, Jan 28, 2013 at 9:00 PM, Adam Mercer  wrote:
>>>
>>> > That sounds like a reasonable explanation. Is there a way I can have a
>>> > separate workspace for polling, so that this doesn't block?
>>>
>>> Just to close the loop on this, I set a custom workspace for this
>>> project and this allowed multiple jobs to be triggered.
>>>
>>> Cheers
>>>
>>> Adam
>
> --
> 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: hudson.util.IOException2: remote file operation failed

[Adam Mercer]

On Mon, Feb 18, 2013 at 11:32 AM, Christoph Kutzinski  wrote:
> That is an issue with the Git and the CVS plugin.
> You can work around by disabling the CVS plugin.

Thanks, good job none of my projects are using CVS.

Cheers

Adam

-- 
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: hudson.util.IOException2: remote file operation failed

[Adam Mercer]

On Mon, Feb 18, 2013 at 9:53 AM,   wrote:
> The latest Git plugin says:
> Version 1.1.28 (February 17, 2013)
> fix a regression that breaks jenkins remoting

Thanks, that was it, 1.1.28 works without issue.

Cheers

Adam

-- 
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: hudson.util.IOException2: remote file operation failed

[Adam Mercer]

On Mon, Feb 18, 2013 at 8:49 AM, Marek Gimza  wrote:
> We had the same problem.
> After reading through some of the blogs and tickets, we deduced the
> problem to be in the compatibility of the Java JRE on the slave and
> master.

Interesting...

> Try checking the versions of the JAVA that runs the master and slave,
> as well as makign sure that the jenkins slave agent on the slave
> machine is properly restarted.

Finally managed to get things working again, by downgrading the git
plugin. I'd updated to 1.1.27 and after downgrading back to 1.1.26
things started working again? Not sure if that was the actual reason,
I'm just glad things are back to normal.

Cheers

Adam

-- 
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.

hudson.util.IOException2: remote file operation failed

[Adam Mercer]

Hi

All of a sudden all my builds have started failing with errors of the form:

Started by user admin
Building remotely on SL6a in workspace /var/lib/jenkins/jenkins/lalsuite_ci
Checkout:lalsuite_ci / /var/lib/jenkins/jenkins/lalsuite_ci -
hudson.remoting.Channel@5e5edf72:SL6a
Using strategy: Default
Last Built Revision: Revision 8a45d0393eab9741659d075abdeb3c000cdaf02e
(origin/master)
hudson.util.IOException2: remote file operation failed:
/var/lib/jenkins/jenkins/lalsuite_ci at
hudson.remoting.Channel@5e5edf72:SL6a
at hudson.FilePath.act(FilePath.java:848)
at hudson.FilePath.act(FilePath.java:834)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:956)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1123)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1256)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495)
at hudson.model.Run.execute(Run.java:1502)
at hudson.matrix.MatrixBuild.run(MatrixBuild.java:289)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
Caused by: java.io.IOException: Unable to serialize
hudson.FilePath$FileCallableWrapper@11c757a1
at hudson.remoting.UserRequest.serialize(UserRequest.java:166)
at hudson.remoting.UserRequest.(UserRequest.java:62)
at hudson.remoting.Channel.call(Channel.java:671)
at hudson.FilePath.act(FilePath.java:841)
... 12 more
Caused by: java.io.NotSerializableException: hudson.matrix.MatrixBuild
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346)
at hudson.remoting.UserRequest._serialize(UserRequest.java:155)
at hudson.remoting.UserRequest.serialize(UserRequest.java:164)
... 15 more
Finished: FAILURE

For the life of me I can't figure out what is going on here? I've
tried rebooting the build slaves, rebooting master, disconnecting and
reconnecting the build slaves... All to no avail!

Anyone got ideas what's going on here?

Cheers

Adam

-- 
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: Priority Sorter Plugin

[Adam Mercer]

On Tue, Feb 12, 2013 at 4:13 PM, Adam Mercer  wrote:

> Thanks, that's what was confusing me. I've adjusted the priorities
> according and I'll see how that effects the behaviour.

And that did the trick, jobs are now running with the priority I expect. Thanks!

Cheers

Adam

-- 
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: Priority Sorter Plugin

[Adam Mercer]

On Tue, Feb 12, 2013 at 4:07 PM, J Arrizza  wrote:

> And one last bit of confusion that still manages to bite me: the higher the
> priority number, the higher the priority.  For some reason, I think #1 is
> the highest priority... it isn't, it's the lowest. So your job priority of
> 10 is low compared to a 100.

Thanks, that's what was confusing me. I've adjusted the priorities
according and I'll see how that effects the behaviour.

Cheers

Adam

-- 
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: Priority Sorter Plugin

[Adam Mercer]

On Tue, Feb 12, 2013 at 3:45 PM, Merrow, Frank  wrote:
> Yep . . .  . . .
>
> All I know is if I want to temporally boost the priority of a job without 
> losing what the original value "was" . . . I add a zero on the end, save and 
> it jumps to the front of the queue.  At a later time I can come back and 
> remove the zero to return it to its normally assigned priority.
>
> Your mileage may vary.

OK, I'll take a look...

Cheers

Adam

-- 
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: Priority Sorter Plugin

[Adam Mercer]

On Tue, Feb 12, 2013 at 3:26 PM, Merrow, Frank  wrote:

> The priority for this job. Priorities are used when all executors are busy
> to decide which job in the build queue to run next. A job with higher
> priority is ran before jobs with lower priorities.
>
> So the job you want to run first should be 200 . . . not 50.

But that contradicts what the documentation on the plugin webpage says:

"The default priority is 100. Jobs will be ordered in ascending order.
A priority of 50 comes before a priority of 100."

Cheers

Adam

-- 
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: Priority Sorter Plugin

[Adam Mercer]

On Tue, Feb 12, 2013 at 3:21 PM, Mandeville, Rob  wrote:
> Check the open issues list on that plugin.  It looks like jobs kicked off by 
> hand (rather than scheduled automatically) ignore priority sorting.  Someone 
> listed that as a feature there.  If you kicked off the priority 10 job by 
> hand, or the job that gets ahead of you in the queue was kicked off by hand, 
> that may be your problem.  If both were automatically scheduled, I don't know 
> what it is.

I think that may be it, thanks! I've been testing it by manually
queuing builds... I did briefly look over the known issues, not sure
how I missed that one? :-(

Cheers

Adam

-- 
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.

Priority Sorter Plugin

[Adam Mercer]

Hi

I'm using the Priority Sorter Plugin[1] as I'd like one project to use
the next available build host regardless of the other jobs ahead of it
in the queue. According to the documentation for the plugin:

"This plugin allows jobs waiting in the build queue to be sorted by a
static priority rather than the standard FIFO. Each job is assigned a
priority number and jobs with higher priorities are built first. Jobs
with lower priorities will not run until an executor frees up which no
higher-priority jobs in the build queue can use.

The default priority is 100. Jobs will be ordered in ascending order.
A priority of 50 comes before a priority of 100."

So for the job I'd like to "skip the queue", and build on the next
available host, I assigned a priority of 10, but this seems to be
ignored and jobs are assigned to build hosts in the order in which
they appear in the queue.

Any idea why this priority is being ignored?

Cheers

Adam

[1] 

-- 
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: Triggering multiple builds with the Git Plugin.

[Adam Mercer]

On Mon, Jan 28, 2013 at 9:00 PM, Adam Mercer  wrote:

> That sounds like a reasonable explanation. Is there a way I can have a
> separate workspace for polling, so that this doesn't block?

Just to close the loop on this, I set a custom workspace for this
project and this allowed multiple jobs to be triggered.

Cheers

Adam

-- 
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: Triggering multiple builds with the Git Plugin.

[Adam Mercer]

On Mon, Jan 28, 2013 at 6:25 PM, cjo  wrote:

> Try adding a logger for hudson.slaves.WorkspaceList to the log page and see
> if there is a log message
>  " acquired  "
> occurring just after the first build finishes, which would indicate that
> this is the case.

Sorry but I'm very new to Jenkins, I think I've done this but nothing
is showing up. I did:

Manage Jenkins -> System Log -> Add new log recorder.

I set a name and then added "hudson.slaves.WorkspaceList" to logger,
selecting log level "all" and then clicked save.

I pushed a commit to the repository, a build started running. I then
pushed another commit and looked in the hudson.slaves.WorkspaceList
log but it was empty. The "All Jenkins Logs" section shows:

Jan 28, 2013 8:51:52 PM hudson.plugins.git.GitStatus doNotifyCommit
INFO: Triggering the polling of Project
Jan 28, 2013 8:43:09 PM hudson.triggers.SCMTrigger$Runner run
INFO: SCM changes detected in Project. Triggering  #38
Jan 28, 2013 8:42:33 PM hudson.plugins.git.GitStatus doNotifyCommit
INFO: Triggering the polling of Project

Which shows that the polling has been triggered by the new commit but
the polling is not completing.

> Here is the detailed bit if you want to know more!
> and take some thread dumps to prove that the polling thread is "Waiting to
> acquire "
>
> From the code in the git plugin it looks like the polling requires a
> workspace [2]
> and during the poll code in AbstractProject it tries to lock the lastbuild's
> workspace to do this [3].
>
> However this looks like it may block if the last build is the one that is
> building, due to different context in the acquire and allocate calls from
> AbstractProject and AbstractBuild [4] called on WorkspaceList [5].

That sounds like a reasonable explanation. Is there a way I can have a
separate workspace for polling, so that this doesn't block?

Cheers

Adam

-- 
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.

Triggering multiple builds with the Git Plugin.

[Adam Mercer]

Hi

One of my Jenkins projects is configured to poll git and trigger a new
build if appropriate by using a post-receive hook and the Git Plugin.

This specific project has two build slaves which can build the project
but it seems that if a single build is already in progress, with one
slave idle, and a change comes in that should trigger a new build it
isn't started until the running build has completed. No job enters the
queue and the "Git Polling Log" simply states something along the
lines of:

Started on Jan 28, 2013 3:39:44 PM

When the currently running job has completed polling with complete and
a job will be scheduled. The project is configured to "Execute
concurrent builds if necessary". I would expect that as a build slave
is available that another build would enter the queue and be assigned
to this idle node. I can manually schedule a job but I would like the
post-receive hook to be able to trigger a build if a node is
available.

Am I misunderstanding the "Execute concurrent builds if necessary"
option, or do I have some kind of misconfiguration somewhere?

Cheers

Adam

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

Re: Silently triggering a build using the git plugin

[Adam Mercer]

On Mon, Jan 21, 2013 at 7:39 PM, Mark Waite  wrote:
> With the version of curl I'm using (7.26.0 - as delivered with Debian
> "Wheezy"), I can use the arguments -o /dev/null to prevent that output.
> Does that not work for you?

The git server has curl-7.15.5 and I thought I'd already tried that
option. However I tried it again and it seems to have worked, thanks!

Cheers

Adam

Re: Silently triggering a build using the git plugin

[Adam Mercer]

On Mon, Jan 21, 2013 at 5:38 PM, Adam Mercer  wrote:

> this seems to be working great, i.e. a new build is scheduled if
> appropriate. However the post-receive hook outputs:
>
> Scheduled polling of Project

An example is:

$ git push
Counting objects: 9, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 771 bytes, done.
Total 5 (delta 3), reused 0 (delta 0)
remote:   % Total% Received % Xferd  Average Speed   TimeTime
   Time  Current
remote:  Dload  Upload   Total   Spent
   Left  Speed
remote:   0300300 0   3048  0 --:--:--
--:--:-- --:--:--remote:   0300300 0   2851  0
--:--:-- --:--:-- --:--:-- 0
remote: Scheduled polling of Project
To user@server:/repo.git
   bd54189..0c3e1d2  master -> master
$

Cheers

Adam

Silently triggering a build using the git plugin

[Adam Mercer]

Hi

I'm using the git plugin and trying to write a post-receive hook to
trigger polling of the SCM to see if a new build should be triggered.
I'm using the following to get Jenkins to poll the SCM

/usr/bin/curl $JENKINS/git/notifyCommit?url=$REPO&branches=master

this seems to be working great, i.e. a new build is scheduled if
appropriate. However the post-receive hook outputs:

Scheduled polling of Project

I don't want this information displayed, I'd just like the polling to
be scheduled. If I run the curl command from the terminal prompt I
get:

$ curl $JENKINS/git/notifyCommit?url=$REPO&branches=master
[1] 38610
$ Scheduled polling of Project

[1]+  Donecurl $JENKINS/git/notifyCommit?url=$REPO
$

I have been trying to suppress this output by appending "> /dev/null
2>&1" but hat still results in the output.

Is there a way I can suppress this output and just silently schedule a polling?

Cheers

Adam

Re: Stopping the automatic creation of users

[Adam Mercer]

On Mon, Jan 21, 2013 at 12:30 AM, Slide  wrote:
> I don't think its possible to do this.

Thanks, I'm already up to 30+ users and it's only been a few days. I
guess it's just something I'll have to live with.

Cheers

Adam

Re: Stopping the automatic creation of users

[Adam Mercer]

Anyone?

On Wed, Jan 16, 2013 at 9:08 PM, Adam Mercer  wrote:
> Hi
>
> I set up a test installation of Jenkins today and I've noticed that it
> seems to auto create users based on new commits in the repository. I
> know these aren't full user accounts and can't be used to log into the
> system but is there a way to disable the creation of these accounts.
>
> The software I'm building with Jenkins has hundreds of developers and
> I don't want to have hundreds of these users setup as the People tab
> will get a little busy.
>
> Cheers
>
> Adam

Stopping the automatic creation of users

[Adam Mercer]

Hi

I set up a test installation of Jenkins today and I've noticed that it
seems to auto create users based on new commits in the repository. I
know these aren't full user accounts and can't be used to log into the
system but is there a way to disable the creation of these accounts.

The software I'm building with Jenkins has hundreds of developers and
I don't want to have hundreds of these users setup as the People tab
will get a little busy.

Cheers

Adam