Re: All nodes are "Dead" after upgrade to 1.501

[Adrian]

This also occurs on calling the RSS feed for "allRSS"

Caused by: org.apache.commons.jelly.JellyTagException: 
jar:file:/var/lib/tomcat-6/webapps/ROOT/WEB-INF/lib/jenkins-core-1.501.jar!/hudson/atom.jelly:48:44:
  requiresReports : requiresReports
>   at 
> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at org.apache.commons.jelly.impl.StaticTag.doTag(StaticTag.java:65)
>   at 
> org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:124)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
>   at 
> org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63)
>   at 
> org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53)
>   at 
> org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55)
>   ... 71 more
> Caused by: com.thoughtworks.xstream.mapper.CannotResolveClassException: 
> requiresReports : requiresReports
>   at 
> com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:86)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:96)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:231)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:56)
>   at 
> com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29)
>   at 
> com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:136)
>   at 
> com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33)
>   at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:926)
>   at hudson.util.XStream2.unmarshal(XStream2.java:104)
>   at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912)
>   at hudson.XmlFile.unmarshal(XmlFile.java:160)
>   at hudson.model.Run.reload(Run.java:308)
>   at hudson.model.Run.(Run.java:297)
>   at hudson.model.AbstractBuild.(AbstractBuild.java:179)
>   at hudson.model.Build.(Build.java:103)
>   at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41)
>   at sun.reflect.GeneratedConstructorAccessor44.newInstance(Unknown 
> Source)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccesso

All nodes are "Dead" after upgrade to 1.501

[Adrian]

Hi, 

after we've upgraded to 1.501 (from 1.471) all nodes die after some time 
and the logs show the following exception:

Feb 14, 2013 8:47:47 AM hudson.triggers.SafeTimerTask run
> SEVERE: Timer task hudson.model.Queue$MaintainTask@4c4db085 failed
> com.thoughtworks.xstream.mapper.CannotResolveClassException: FindBugsFilter : 
> FindBugsFilter
>   at 
> com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:86)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:96)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:231)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43)
>   at 
> com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
>   at 
> com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:56)
>   at 
> com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29)
>   at 
> com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:136)
>   at 
> com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:33)
>   at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:926)
>   at hudson.util.XStream2.unmarshal(XStream2.java:104)
>   at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:912)
>   at hudson.XmlFile.unmarshal(XmlFile.java:160)
>   at hudson.model.Run.reload(Run.java:308)
>   at hudson.model.Run.(Run.java:297)
>   at hudson.model.AbstractBuild.(AbstractBuild.java:179)
>   at hudson.model.Build.(Build.java:103)
>   at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41)
>   at sun.reflect.GeneratedConstructorAccessor44.newInstance(Unknown 
> Source)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
>   at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1084)
>   at hudson.model.AbstractProject$1.create(AbstractProject.java:282)
>   at hudson.model.AbstractProject$1.create(AbstractProject.java:280)
>   at hudson.model.RunMap.retrieve(RunMap.java:225)
>   at hudson.model.RunMap.retrieve(RunMap.java:59)
>   at 
> jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:645)
>   at 
> jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:608)
>   at 
> jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:347)
>   at 
> jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:505)
>   at 
> jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:358)
>   at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:213)
>   at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:100)
>   at hudson.

Jenkins 1.501 Stack Trace

[Markus KARG]

While 1.501 did run well all through the day, this morning when manually 
triggering a free style project, suddenly it had the idea to throw some 
strange stack trace into the log...:
 
SCHWERWIEGEND: Failed to record SCM polling for 
hudson.model.FreeStyleProject@a94e49[My Project Name]
hudson.remoting.RequestAbortedException: 
hudson.remoting.RequestAbortedException: 
hudson.remoting.Channel$OrderlyShutdown
at hudson.remoting.Request.call(Request.java:174)
at hudson.remoting.Channel.call(Channel.java:672)
at 
hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1278)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject._poll(AbstractProject.java:1493)
at hudson.model.AbstractProject.poll(AbstractProject.java:1410)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468)
at 
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: hudson.remoting.RequestAbortedException: 
hudson.remoting.Channel$OrderlyShutdown
at hudson.remoting.Request.abort(Request.java:299)
at hudson.remoting.Channel.terminate(Channel.java:732)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:850)
at hudson.remoting.Channel$2.handle(Channel.java:435)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
Caused by: hudson.remoting.Channel$OrderlyShutdown
... 3 more
Caused by: Command close created at
at hudson.remoting.Command.(Command.java:56)
at hudson.remoting.Channel$CloseCommand.(Channel.java:844)
at hudson.remoting.Channel$CloseCommand.(Channel.java:842)
at hudson.remoting.Channel.close(Channel.java:909)
at hudson.remoting.Channel.close(Channel.java:892)
at hudson.remoting.Channel$CloseCommand.execute(Channel.java:849)
... 2 more
As I did not change anything between yesterdays successful trials and 
today, I expect this to be a bug in Jenkins.
 
Opinions?

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

username on the Dashboard View

[vijay kumar]

Hi,

I would like to display the 'username' of the Job as we are using 'Unix 
user/group database" as "Security Realm". I would like to display the User 
Name against the Job on the dashboard with the name who has created the 
Job.I Googled for this about a long time & searched in "Available Plugins" 
but couldn't find any for this requirement.

Could you please guide me in providing a solution for this problem.

Thanks & Regards,
Vijay

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

deadlocks when using Multijob plugin

[Alvaro Martinez Echevarria]

Hi,
I'm having trouble using the Multijob plugin... jobs become deadlocked. Let 
me explain...

Say I have a compilation job A which is triggered by a gerrit event (a code 
merge, for example); compilation is able to run in a farm of compilation 
servers. When compilation finishes, A proceeds with a multijob stage with a 
few parallel test jobs (B, C, D...), and A waits for those to be completed; 
test jobs run in parallel, using their own dedicated test servers.

Now that works pretty well, except that it seems that every time a job A is 
triggered (manually or by gerrit) and put in the queue, it blocks *any* 
test jobs from executing, even if they were triggered by a different A. 
Instead of "waiting for next available executor" they show "Upstream Job 
XXX in build queue". This leads to the deadlocks that I mention.

So in a very simplified example: A is compilation, B, C are tests; there's 
one server for compilation (S1), and one for test (S2). A1 is started, and 
starts to execute in S1; it finishes the compilation, it kicks off B1 and 
C1, and waits; B1 is scheduled and starts to run in S2, while C1 stays in 
the queue. Now another merge goes in so A2 is triggered, and put in the 
queue: it will jump to the front of the queue, and it will block C1 from 
being executed, even after B1 is done and S2 becomes available; so A1 will 
never finish, and A2 will never execute. Deadlock.

I've tried to use the priority sorter plugin, but it doesn't help. A always 
trump any B and C.

What am I missing? Is this a bug, or am I completely misunderstanding what 
the plugin provides?
Thanks,
--
Alvaro

-- 
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 does one get the basic jenkins mailer to send raw console?

[Glfk4rt]

There is a builtin , very clever, log filter, that is replacing paths to
artifacts inside logs with the path to the Jenkins artifact.  Is there a
way to send Raw console?

Rodney

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

Dynamic Axis plugin sometimes inserts "default"

[Jonathan Rogers]

I've been using the Dynamic Axis plugin for several weeks to run a set
of test suites the names of which are set in the source code repository.
Normally this works great but once in a while, the word "default" is
inserted into the list of test suite names. Of course, this causes
failures since there is no test suite by that name.

I understand that "default" is the value Dynamic Axis will use when no
variable has been defined for the axis. However, there clearly is a
value set and "default" is added to it, which is definitely the wrong
behavior. Since this only happens in a small minority of job executions,
perhaps there is a race condition.
-- 
Jonathan Ross Rogers

-- 
Jonathan Rogers

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

Deny anonymous access but allow access via command line API

[C. Benson Manica]

I asked this question on Stack Overflow some time ago, and didn't get any 
satisfactory answers 
(http://stackoverflow.com/questions/14266434/jenkins-security-ii-deny-anonymous-access-but-allow-access-via-cli?lq=1),
 
so I'm hoping this list will help me out.  Basically, due to Jenkins' 
overly permissive policy of providing information to anonymous viewers, we 
need to lock down Jenkins.  Unfortunately, locking down Jenkins by using 
matrix-based security to allow authenticated users to do everything and 
anonymous users to do nothing breaks access to the command-line API, 
because apparently authentication via SSH key does not count as a real 
authentication for the matrix-based security.  Is there a way to set up 
matrix-based security to fix this, or is the only solution to switch from 
using SSH-based authentication to a specific user and password combination?

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

Pass exit variables to down stream jobs.

[c . alex . roeber]

If this is a known item I apologize.
I am using the Jenkins system to build environments in AWS using Cloud 
Formation templates.
I need to know how to take the CF outputs and pass them to the next job.
Example:
Build a VPC, Subnet, etc.
Then pass the VPC, Subnet IDs in to the build frontend web server 
CF template so they are created in the new Subnet and VPC.

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.

Periodic even build question

[Octavian Covalschi]

Hello,

I'm trying to setup periodic builds for a few dozens of jobs, but in the
same time I'd like to even the load... so for example, I need to run them
at every 15min, but would like to even the load... is it possible?

I saw the 'H'  token, but I'm not sure If it can help me...

The closest valid syntax I was able to put together is:

H(0-14),H(15-29),H(30-44),H(45-59) * * * *

But, I don't thinks it's what I need, since the 1st H may trigger it at min
13 and 2nd H may trigger it at min 16, so I'll get 3 min interval, but I
need ~15

Thank you in advance.

-- 
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: Monitoring Metrics (eg. code coverage) Degradation

[William Soula]

Sorry I should have read the whole thread cobertura is java only :(
Using some code coverage tool for php you might be able to transform those 
results to cobertura format, with XSLT or something, and then use the cobertura 
plugin.

Will

On 02/13/2013 03:10 PM, Zigster wrote:
Thanks for the hint William!

Does the cobertura plugin work with php and phpunit respectively?

Thanks for info on that!!

Zigster


Am Mittwoch, 13. Februar 2013 16:20:49 UTC+1 schrieb William Soula:
The cobertura plugin allows you to mark a build as unstable if the user 
configured threshold for the coverage metric falls below a certain percentage.  
Might even be able to make it fail.  You could also use the build timeout 
plugin to abort the build after a certain amount of time, or a percentage of 
time.

cobertura:
https://wiki.jenkins-ci.org/display/JENKINS/Cobertura+Plugin

build timeout:
https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin

Will

On 02/13/2013 02:57 AM, Zigster wrote:
I figured, that this would be one way to do.

It's a bit strange, that there's no plugin providing that feature as 
implementing a build fail for deteriorating code coverage or slow tests is 
mentioned in a few reputable books (just as "Continuous Delivery" by 
Humble/Farley)

Thank you for your suggestion!




Am Dienstag, 12. Februar 2013 18:05:01 UTC+1 schrieb Octavian Covalschi:
You may not like this solution, but until someone will post a better solution, 
you could potentially create a simple shell task and run your coverage metrics 
from there... With some magic you could check the results and return 0 or 1 
(i'm not sure the exact value), which will tell jenkins if it failed or not...

This kind of trick helped me a lot when I didn't want to rely on old plugins or 
my requirement was too custom...


On Tue, Feb 12, 2013 at 10:27 AM, Zigster  wrote:
It's a PHP project...

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

Re: SVN & Distributed builds

[William Soula]

The Subversion plugin as part of Jenkins has Excluded Regions and 
Included Regions you could try using that functionality, it's under the 
Advanced button after repository browser.

Will

On 02/13/2013 02:01 PM, Ross Youngblood wrote:
> Howdy sports fans.
> I'm working with Distributed builds, and I have a interesting problem.
> I discovered that using SSD drives was a big help in speeding up the builds 
> of large files (my projects involve crunching large datasets for digital IC 
> testers).
> Some of my build projects are 30Gb or larger.  And I currently have only 2 
> Jenkins build slaves with SSD drives (120Gb on one 60Gb on another), so SSD 
> space for builds is at a premium.
>
> Without going into too much detail, I'd like these small projects that crunch 
> a subset of the data in "trunk" to only check out portions of trunk.
> It looks like I'll have to build separate repositories with portions of the 
> original trunk to do this, but it would have been nice to have a facility to 
> checkout a list of files from the SVN repository as part of the project build 
> instructions.  This way Jenkins could maintain separate smaller workspaces 
> that are independent of each other.
>
> The current method I use to manage this, is to have all the Jenkins slave 
> projects use the same workspace directory, with the leading build doing the 
> SVN checkout, and the subsequent builds just building in that workspace.  On 
> occasion there is resource contention with some common files which makes 
> parallel builds on the slave less reliable.
>
> The copy files plug in might work for me, except that I would have to prepare 
> a subdirectory with the files I want ahead of time.  For that effort, I could 
> have the copy operate via a script as part of the build… so I don't see the 
> copy files plug in as being of as much utility as just having SVN.
>
> What I'd like is a way to specify a region for the checkout.  I know with the 
> SVN repo browser on Tortoise SVN, I can just check out individual files.  So 
> there has to be a command for that.  I suppose I could build a series of SVN 
> commands in the bat script … or probably build my own plug in.   Any 
> resources for plug-in development?  Or if there is a plug-in solution that 
> could help.
>
> I just found the toggle to upgrade from my SVN1.4 to 1.7, so I can have 
> :external support, I could partition my svn repo using that technique… but 
> it's a pain.  I don't like the idea of forcing the SVN tree structure to be 
> shaped by the number of execute engine parallel jobs.
>
> -R
>

-- 
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: "Config File Provider Plugin" does not store new files

[Markus KARG]

Actually it happens with *all* kinds of files, so it is the button that
fails, not the file creation.

 

Jenkins 1.500, current plugin.

 

From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Merrow, Frank
Sent: Dienstag, 12. Februar 2013 19:54
To: Markus KARG; jenkinsci-users@googlegroups.com
Subject: RE: "Config File Provider Plugin" does not store new files

 

I use almost exclusively Chrome . . . though I just tried to create a Config
file using IE9 and had no issues.

 

It might be nice to know exactly the kind of file you are trying to create.

 

Perhaps you have a XML error in an XML file or equal in another file type .
. .

 

Also, what version of Jenkins and the plugin are you using?

 

Frank

 

From: Markus KARG [mailto:mar...@headcrashing.eu] 
Sent: Tuesday, February 12, 2013 10:30 AM
To: jenkinsci-users@googlegroups.com
Cc: Merrow, Frank
Subject: Re: "Config File Provider Plugin" does not store new files

 

"ping"?

 

Am I the only one using IE9?


Am Freitag, 8. Februar 2013 14:23:45 UTC+1 schrieb Markus KARG:

Just noticed that it happens with IE 9 only while it runs well with Safari.
Any ideas?


Am Freitag, 8. Februar 2013 14:04:01 UTC+1 schrieb Markus KARG:

Frank, you don't see the actual problem. "Submit" actually does NOTHING,
hence, the file is NOT available anymore as soon as I click away from the
file edit page. THAT is my problem. "Submit" simply does not store the file.

I have installed "

Config File Provider Plugin 2.4" into "Jenkins 1.500" (running in
TurnKeyLinux Jenkins appliance, based on Debian 6).

The "submit" button does not store any new config file I create using the
"(cfg) Managed files" node. In fact, the "submit" button does not do
*anything*.

The Jenkins log does not contain any error message since the key press.

This happens with all kinds of config file types.

 

What to do?

-- 
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: Monitoring Metrics (eg. code coverage) Degradation

[Zigster]

Thanks for the hint William!

Does the cobertura plugin work with php and phpunit respectively? 

Thanks for info on that!!

Zigster


Am Mittwoch, 13. Februar 2013 16:20:49 UTC+1 schrieb William Soula:
>
>  The cobertura plugin allows you to mark a build as unstable if the user 
> configured threshold for the coverage metric falls below a certain 
> percentage.  Might even be able to make it fail.  You could also use the 
> build timeout plugin to abort the build after a certain amount of time, or 
> a percentage of time.
>
> cobertura:
> https://wiki.jenkins-ci.org/display/JENKINS/Cobertura+Plugin
>
> build timeout:
> https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin
>
> Will
>
> On 02/13/2013 02:57 AM, Zigster wrote:
>  
> I figured, that this would be one way to do. 
>
>  It's a bit strange, that there's no plugin providing that feature as 
> implementing a build fail for deteriorating code coverage or slow tests is 
> mentioned in a few reputable books (just as "Continuous Delivery" by 
> Humble/Farley) 
>
>  Thank you for your suggestion!
>
>  
>  
>  
>  Am Dienstag, 12. Februar 2013 18:05:01 UTC+1 schrieb Octavian Covalschi:
>  
>> You may not like this solution, but until someone will post a better 
>> solution, you could potentially create a simple shell task and run your 
>> coverage metrics from there... With some magic you could check the results 
>> and return 0 or 1 (i'm not sure the exact value), which will tell jenkins 
>> if it failed or not... 
>>
>>  This kind of trick helped me a lot when I didn't want to rely on old 
>> plugins or my requirement was too custom...
>>  
>>
>> On Tue, Feb 12, 2013 at 10:27 AM, Zigster  wrote:
>>
>>> It's a PHP project...
>>>  
>>> --
>>> 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-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.

Re: SVN & Distributed builds

[Les Mikesell]

On Wed, Feb 13, 2013 at 2:01 PM, Ross Youngblood
 wrote:
> Howdy sports fans.
> I'm working with Distributed builds, and I have a interesting problem.
> I discovered that using SSD drives was a big help in speeding up the builds 
> of large files (my projects involve crunching large datasets for digital IC 
> testers).
> Some of my build projects are 30Gb or larger.  And I currently have only 2 
> Jenkins build slaves with SSD drives (120Gb on one 60Gb on another), so SSD 
> space for builds is at a premium.
>
> Without going into too much detail, I'd like these small projects that crunch 
> a subset of the data in "trunk" to only check out portions of trunk.
> It looks like I'll have to build separate repositories with portions of the 
> original trunk to do this, but it would have been nice to have a facility to 
> checkout a list of files from the SVN repository as part of the project build 
> instructions.  This way Jenkins could maintain separate smaller workspaces 
> that are independent of each other.
>
> The current method I use to manage this, is to have all the Jenkins slave 
> projects use the same workspace directory, with the leading build doing the 
> SVN checkout, and the subsequent builds just building in that workspace.  On 
> occasion there is resource contention with some common files which makes 
> parallel builds on the slave less reliable.
>
> The copy files plug in might work for me, except that I would have to prepare 
> a subdirectory with the files I want ahead of time.  For that effort, I could 
> have the copy operate via a script as part of the build… so I don't see the 
> copy files plug in as being of as much utility as just having SVN.
>
> What I'd like is a way to specify a region for the checkout.  I know with the 
> SVN repo browser on Tortoise SVN, I can just check out individual files.  So 
> there has to be a command for that.  I suppose I could build a series of SVN 
> commands in the bat script … or probably build my own plug in.   Any 
> resources for plug-in development?  Or if there is a plug-in solution that 
> could help.
>
> I just found the toggle to upgrade from my SVN1.4 to 1.7, so I can have 
> :external support, I could partition my svn repo using that technique… but 
> it's a pain.  I don't like the idea of forcing the SVN tree structure to be 
> shaped by the number of execute engine parallel jobs.


As long as your code and data components have a structure with
directories for the parts you want to assemble together you should be
able to use a top level project with externals to pull any components
at any revisions you want into a working copy tree.  They don't even
need to be from the same repositories.

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

-- 
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: SVN & Distributed builds

[Larry Shatzer, Jr.]

The feature in Subversion you are looking for is called sparse directories:
http://svnbook.red-bean.com/en/1.7/svn.advanced.sparsedirs.html



On Wed, Feb 13, 2013 at 1:01 PM, Ross Youngblood <
ross.youngbl...@nextest.com> wrote:

> Howdy sports fans.
> I'm working with Distributed builds, and I have a interesting problem.
> I discovered that using SSD drives was a big help in speeding up the
> builds of large files (my projects involve crunching large datasets for
> digital IC testers).
> Some of my build projects are 30Gb or larger.  And I currently have only 2
> Jenkins build slaves with SSD drives (120Gb on one 60Gb on another), so SSD
> space for builds is at a premium.
>
> Without going into too much detail, I'd like these small projects that
> crunch a subset of the data in "trunk" to only check out portions of trunk.
> It looks like I'll have to build separate repositories with portions of
> the original trunk to do this, but it would have been nice to have a
> facility to checkout a list of files from the SVN repository as part of the
> project build instructions.  This way Jenkins could maintain separate
> smaller workspaces that are independent of each other.
>
> The current method I use to manage this, is to have all the Jenkins slave
> projects use the same workspace directory, with the leading build doing the
> SVN checkout, and the subsequent builds just building in that workspace.
>  On occasion there is resource contention with some common files which
> makes parallel builds on the slave less reliable.
>
> The copy files plug in might work for me, except that I would have to
> prepare a subdirectory with the files I want ahead of time.  For that
> effort, I could have the copy operate via a script as part of the build… so
> I don't see the copy files plug in as being of as much utility as just
> having SVN.
>
> What I'd like is a way to specify a region for the checkout.  I know with
> the SVN repo browser on Tortoise SVN, I can just check out individual
> files.  So there has to be a command for that.  I suppose I could build a
> series of SVN commands in the bat script … or probably build my own plug
> in.   Any resources for plug-in development?  Or if there is a plug-in
> solution that could help.
>
> I just found the toggle to upgrade from my SVN1.4 to 1.7, so I can have
> :external support, I could partition my svn repo using that technique… but
> it's a pain.  I don't like the idea of forcing the SVN tree structure to be
> shaped by the number of execute engine parallel jobs.
>
> -R
>
> --
> 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.

SVN & Distributed builds

[Ross Youngblood]

Howdy sports fans.
I'm working with Distributed builds, and I have a interesting problem.
I discovered that using SSD drives was a big help in speeding up the builds of 
large files (my projects involve crunching large datasets for digital IC 
testers).
Some of my build projects are 30Gb or larger.  And I currently have only 2 
Jenkins build slaves with SSD drives (120Gb on one 60Gb on another), so SSD 
space for builds is at a premium.

Without going into too much detail, I'd like these small projects that crunch a 
subset of the data in "trunk" to only check out portions of trunk.
It looks like I'll have to build separate repositories with portions of the 
original trunk to do this, but it would have been nice to have a facility to 
checkout a list of files from the SVN repository as part of the project build 
instructions.  This way Jenkins could maintain separate smaller workspaces that 
are independent of each other.

The current method I use to manage this, is to have all the Jenkins slave 
projects use the same workspace directory, with the leading build doing the SVN 
checkout, and the subsequent builds just building in that workspace.  On 
occasion there is resource contention with some common files which makes 
parallel builds on the slave less reliable.

The copy files plug in might work for me, except that I would have to prepare a 
subdirectory with the files I want ahead of time.  For that effort, I could 
have the copy operate via a script as part of the build… so I don't see the 
copy files plug in as being of as much utility as just having SVN.

What I'd like is a way to specify a region for the checkout.  I know with the 
SVN repo browser on Tortoise SVN, I can just check out individual files.  So 
there has to be a command for that.  I suppose I could build a series of SVN 
commands in the bat script … or probably build my own plug in.   Any resources 
for plug-in development?  Or if there is a plug-in solution that could help.

I just found the toggle to upgrade from my SVN1.4 to 1.7, so I can have 
:external support, I could partition my svn repo using that technique… but it's 
a pain.  I don't like the idea of forcing the SVN tree structure to be shaped 
by the number of execute engine parallel jobs.

-R

-- 
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: Status of wrong job displayed on dashboard

[cjo]

Do you have a custom path set for "Build Record Root Directory", (Advanced 
section of http:///configure at top of page)
if so does this include the job name variable (${ITEM_FULLNAME}) ?

If the path is the same all build results are placed in the same directory 
and the UI will try and display all of them for every job, 

Chris.

On Wednesday, 13 February 2013 16:21:02 UTC, tortoise74 wrote:
>
> Hi,
>
> I have a jenkins configuration consisting of multiple jobs. For some 
> reason builds corresponding to one job are taken as the most recent 
> successful or failing job for another. I have no idea what causes this. I 
> would intuitively expect the build history for each job to be independent 
> of any other job though I typically create a new job by copying an existing 
> but similar job. I also ensure that each job has an separate Jenkins 
> workspace configured. When looking at the config.xml for each job there are 
> no obvious shared values causing this.
>
> I have been stuck with this problem for some time (see 
> https://issues.jenkins-ci.org/browse/JENKINS-14583) but so far I don't 
> have a workaround or fix. 
>
> I am using the long term support version of Jenkins 1.480.1. I did try 
> upgrading a while back but it did not resolve the problem,
>
> I have also tried using the set next build number plugin but this does not 
> seem to have improved thing (could it in fact be aggravating the problem?) 
> This must be a very common scenario so I am surprised I haven't seen 
> others reporting it. I would not be too surprised if it was a newbie 
> mistake of some kind. Can anyone help?
>
> Regards,
>
> Bruce.
>
>
>

-- 
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: slave continually going offline , Disk space is too low

[cjo]

Can you check what the path Jenkins is monitoring for that slave, as by 
default there should be more than 1G free.

Going to http:///computer/ will show a summary of all 
slave and if one is offline due to Diskspace this should be highlighted in 
the relevant column.

Going to the  individual slave 
page http:///computer/, will allow you to find 
out which path is causing the problem, which might be $jenkins_home, or the 
java tmp dir.

And the configure link from http:///computer/ will take 
you to the page where you can see the current values and enable/disable 
them if needed.

Hope this will help you track the issue down.
Chris.


On Wednesday, 13 February 2013 14:30:58 UTC, Kamal Ahmed wrote:
>
> I have one centos 6.3 slave going offline continually while complaining of 
> "Disk Space too Low"
>
> but when i do a df -h, i get:
>
>  df -h
> FilesystemSize  Used Avail Use% Mounted on
> /dev/mapper/vg1-lv_root
>   5.0G  3.2G  1.5G  69% /
> tmpfs 939M 0  939M   0% /dev/shm
> /dev/sda11008M  130M  828M  14% /boot
> /dev/mapper/vg1-lv_home
>   2.0G  1.1G  889M  54% /home
> /dev/mapper/vg1-lv_opt
>   756M   17M  701M   3% /opt
> /dev/mapper/vg1-lv_tmp
>   2.0G   68M  1.9G   4% /tmp
> /dev/mapper/vg1-lv_var
>   2.0G  1.6G  284M  86% /var
> /dev/mapper/vg1-lv_var_log
>   756M   49M  669M   7% /var/log
> /dev/mapper/vg2-lv_extra
>18G  3.7G   14G  22% /extra
>
>

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

Insert the content of a file in a job description

[Yann Salaün]

Hi list,

I'm trying to insert the content of a file inside a job description. Let me 
explain.
My build generates a file and I can find it easily with the following 
URL: http:/[my-domain]job/[my-job]/lastBuild/artifact/[my-file]. In my 
case, this is a text file and I would like to display it in the job's 
description. I can easily insert a link to this file with HTML but how can 
I insert the content of this file ?

Thanks for answers,
Yann

-- 
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 - High or Low?

[J Arrizza]

On Wed, Feb 13, 2013 at 8:59 AM, Les Mikesell  wrote:

> That's an "interesting" interpretation of 'before".  I would never
> have guessed that myself.  I usually think of queues as having a front
> and back with the front being where elements are picked for activity.
>  And I wouldn't expect "before" to mean nearer to the back.
>

Perhaps. But it's just a different way of conceptualizing a queue. You
chose front and back, he chose a more visual interpretation based on what
the queue visually looks like on the web page.

Of course, I'm just guessing what the author -- and you -- is thinking
which is very presumptuous. Apologies to him and you for that.

John

-- 
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 - High or Low?

[Les Mikesell]

On Wed, Feb 13, 2013 at 10:09 AM, J Arrizza  wrote:
>>
>> I’m using the priority sorter plugin, and getting confused.  The page for
>> the plugin at
>> https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin says that
>> “A priority of 50 comes before a priority of 100”, so a lower priority
>> number is a higher priority.
>
> I think the plugin author meant this:
>
> It "comes before" in the queue. Look at the queue literally -- I mean
> literally visually. The top of the list is the lowest priority. The bottom
> of that list is the highest priority, those jobs are going to run next.

That's an "interesting" interpretation of 'before".  I would never
have guessed that myself.  I usually think of queues as having a front
and back with the front being where elements are picked for activity.
 And I wouldn't expect "before" to mean nearer to the back.

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

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

Status of wrong job displayed on dashboard

[tortoise74]

Hi,

I have a jenkins configuration consisting of multiple jobs. For some reason 
builds corresponding to one job are taken as the most recent successful or 
failing job for another. I have no idea what causes this. I would 
intuitively expect the build history for each job to be independent of any 
other job though I typically create a new job by copying an existing but 
similar job. I also ensure that each job has an separate Jenkins workspace 
configured. When looking at the config.xml for each job there are no 
obvious shared values causing this.

I have been stuck with this problem for some time (see 
https://issues.jenkins-ci.org/browse/JENKINS-14583) but so far I don't have 
a workaround or fix. 

I am using the long term support version of Jenkins 1.480.1. I did try 
upgrading a while back but it did not resolve the problem,

I have also tried using the set next build number plugin but this does not 
seem to have improved thing (could it in fact be aggravating the problem?) 
This must be a very common scenario so I am surprised I haven't seen others 
reporting it. I would not be too surprised if it was a newbie mistake of 
some kind. Can anyone help?

Regards,

Bruce.


-- 
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 - High or Low?

[J Arrizza]

On Wed, Feb 13, 2013 at 4:48 AM, Mandeville, Rob wrote:

>  I’m using the priority sorter plugin, and getting confused.  The page
> for the plugin at
> https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin says
> that “A priority of 50 comes before a priority of 100”, so a lower priority
> number is a higher priority.
>
I think the plugin author meant this:

It "comes before" in the queue. Look at the queue literally -- I mean
literally visually. The top of the list is the lowest priority. The bottom
of that list is the highest priority, those jobs are going to run next.


> When I look at the source, PrioritySorterQueueSorter.java runs the compare
> in reverse order, complete with a comment stating “Note that we sort these
> backwards because we want to return higher-numbered items first”.  When I
> tried launching jobs of different priorities from the Web UI, they ran in
> launch order, apparently ignoring the priority sorter plugin.  When I ran a
> build that launches sub-builds of different priorities via “trigger
> parameterized builds on other projects”, they got launched but required a
> label that was completely in uses, so they got queued.  The four jobs with
> priority 100 launched before the one with priority 90.
>
> ** **
>
> Am I correct in assuming that, if two jobs are waiting on an executor on a
> node or label, the one with the higher priority number will get in first?
>
This was already answered in a previous post.

Note, I did post an enhancement request to the plugin author to have the
plugin also look at the jobs in the execution queue.



> And if that is the case, should somebody edit the wiki for the plugin?
>

Post a bug on the plugin site.

-- 
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 - High or Low?

[Merrow, Frank]

Funny . . . and thread on this from someone else just finished up.

The answers to your questions are Yes and Yes.

Frank

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Mandeville, Rob
Sent: Wednesday, February 13, 2013 4:48 AM
To: jenkinsci-users@googlegroups.com
Subject: Priority Sorter - High or Low?

I'm using the priority sorter plugin, and getting confused.  The page for the 
plugin at https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin 
says that "A priority of 50 comes before a priority of 100", so a lower 
priority number is a higher priority.  When I look at the source, 
PrioritySorterQueueSorter.java runs the compare in reverse order, complete with 
a comment stating "Note that we sort these backwards because we want to return 
higher-numbered items first".  When I tried launching jobs of different 
priorities from the Web UI, they ran in launch order, apparently ignoring the 
priority sorter plugin.  When I ran a build that launches sub-builds of 
different priorities via "trigger parameterized builds on other projects", they 
got launched but required a label that was completely in uses, so they got 
queued.  The four jobs with priority 100 launched before the one with priority 
90.

Am I correct in assuming that, if two jobs are waiting on an executor on a node 
or label, the one with the higher priority number will get in first?  And if 
that is the case, should somebody edit the wiki for the plugin?

Thanks in advance,

--Rob
The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.
--
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: Issues after moving to 1.501 With Slave Nodes

[Les Mikesell]

Thanks - if you are looking for security advisories I guess it is
possible to find that.  Not so sure it is possible to figure out how
to make your windows boxes with the slave running as as service work
again from that, though.But my complaint is that someone looking
to update isn't going to be reading security advisories, they will
read the release notes.   And breaking things in the name of security
updates won't encourage people to be more secure, it will encourage
them to never update again - or at least put it off as long as
possible, especially the people using LTS just to avoid such
surprises.

 -Les


On Wed, Feb 13, 2013 at 8:11 AM, Stephen Connolly
 wrote:
> LTS is supposed to include critical security fixes too... otherwise it's
> just a version that stays around for a while.
>
> https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-advisories/P32IpTQNT5o
>
> https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04
>
> "Slaves that are started via Java Web Start will fail to reconnect if the
> *.jnlp file is locally stored. This is because the authentication tokens
> change. An administrator would have to login to the UI, retrieve the *.jnlp
> file and overwrite what's already on the slave. A slave that was launched
> via Java Web Start and then turned into a service through its menu falls
> into this category."
>
> My understanding of this issue, and until now I have stayed off contributing
> to the security advisory list as I don't want that to be seen as too
> CloudBees heavy (there's already KK & Jesse on the list and perhaps Ryan and
> Nicolas too), is that there was no other way to fix the issue at hand.
>
> Perhaps the changelog (http://jenkins-ci.org/changelog-stable) could have
> given a link to the Security Advisory, or at least mentioned that there were
> manual steps to be taken... that would be a good issue to put before the
> biweekly jenkins project meetings (at a time when I am cooking dinner, hence
> why I am never on them)
>
> -Stephen
>
>
> On 13 February 2013 13:39, Les Mikesell  wrote:
>>
>> So, does that mean surprising changes should go undocumented and even
>> backed into revs where they are more surprising?   Or did I just miss
>> the part in the release notes that said previously-working systems
>> would break?
>>
>>
>> On Wed, Feb 13, 2013 at 2:57 AM, Stephen Connolly
>>  wrote:
>> > IIRC this was fallout from fixing a critical security issue
>> >
>> >
>> > On 12 February 2013 16:21, Les Mikesell  wrote:
>> >>
>> >> On Tue, Feb 12, 2013 at 9:37 AM, Fisher, Allen 
>> >> wrote:
>> >> > I did notice something interesting. If I launch via the website, the
>> >> > slaves
>> >> > will connect, until I install the service. After that, they don’t
>> >> > connect.
>> >>
>> >> If it works when you are authenticated in the browser before
>> >> launching, but not as a service it is because the system changed to
>> >> require slaves to authenticate via jnlp but it seems to be mostly
>> >> broken.  I changed mine to start via ssh (linux) and 'let jenkins
>> >> control this windows slave" on the windows systems where that worked.
>> >> Not sure what to do about the windows 2008 systems where none of that
>> >> works.
>> >>
>> >> If you are on a private firewalled LAN, you might be OK with allowing
>> >> anonymous read and slave connect in your main authorization matrix to
>> >> restore the old behavior.
>> >>
>> >> By the way - was this change documented somewhere for the LTS 1.480.2
>> >> release?.  I had seen the problem mentioned for 1.49x versions but
>> >> wasn't expecting it in 1.480.2. - and I thought the point of the LTS
>> >> line was to avoid surprises.
>> >>
>> >> --
>> >>Les Mikesell
>> >>  lesmikes...@gmail.com
>> >>
>> >> --
>> >> 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.
>>
>>
>
> --
> 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-

Re: Monitoring Metrics (eg. code coverage) Degradation

[William Soula]

The cobertura plugin allows you to mark a build as unstable if the user 
configured threshold for the coverage metric falls below a certain percentage.  
Might even be able to make it fail.  You could also use the build timeout 
plugin to abort the build after a certain amount of time, or a percentage of 
time.

cobertura:
https://wiki.jenkins-ci.org/display/JENKINS/Cobertura+Plugin

build timeout:
https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin

Will

On 02/13/2013 02:57 AM, Zigster wrote:
I figured, that this would be one way to do.

It's a bit strange, that there's no plugin providing that feature as 
implementing a build fail for deteriorating code coverage or slow tests is 
mentioned in a few reputable books (just as "Continuous Delivery" by 
Humble/Farley)

Thank you for your suggestion!




Am Dienstag, 12. Februar 2013 18:05:01 UTC+1 schrieb Octavian Covalschi:
You may not like this solution, but until someone will post a better solution, 
you could potentially create a simple shell task and run your coverage metrics 
from there... With some magic you could check the results and return 0 or 1 
(i'm not sure the exact value), which will tell jenkins if it failed or not...

This kind of trick helped me a lot when I didn't want to rely on old plugins or 
my requirement was too custom...


On Tue, Feb 12, 2013 at 10:27 AM, Zigster > 
wrote:
It's a PHP project...

--
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: REST API - How reliable is tag?

[Octavian Covalschi]

Thank you. I had a feeling it's not the proper way, I'll keep looking...

Thanks!


On Wed, Feb 13, 2013 at 3:07 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Keep in mind that not all "items" have a color and/or display the same
> meaning when they report a "color"
>
> Case in point is the [Folders plugin](
> http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/folder.html)
> (which is free - as in give us your email address - but currently closed
> source) or the [Update Center plugin](
> http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/uc.html)
> (which is a non-free - as in give us some money - and closed source)
> plugins available from CloudBees.
>
> Both of these show up as "item"s in the model IOW a Folder called foo will
> show up at /job/foo (yes "items" are bound to the path segment "jobs")
>
> So if it is the case that you are writing an external integration to
> capture status of generic jobs, please don't use the color.
>
> If it is the case that you have a specific job that you know is a job,
> then you should be OK... though it is a hack... and hacks can and do break
> ;-)
>
>
> On 12 February 2013 20:19, Octavian Covalschi <
> octavian.covals...@gmail.com> wrote:
>
>> Hello,
>>
>> We're linking our database entities to a job in jenkins, it's  1 to 1
>> relation. So, as a result we'd like to display real time job's status. I
>> found 2 ways,
>>
>> 1. using /job/job1/api/xml (color tag)
>> 2. using /job/job1/lastBuild/api/xml (building, result tags)
>>
>> In both cases it seems possible to find out if a job is building and/or
>> failed.  But 1st solution seems simpler compared to 2nd which has bit more
>> code especially if there wasn't any build made yet...
>>
>> So, what do you think? Can I rely on  tag, that can have blue,
>> blue_anime, red, red_anime, grey, grey_anime values? Or it may change and I
>> should use 2nd resource?
>>
>> Thank you in advance.
>>
>> --
>> 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: Priority Sorter Plugin

[John A]

 Original Message  From: Adam Mercer  Sent: Tue, 12/02/2013 22:08 To: jenkinsci-users@googlegroups.com CC:  Subject: Re: Priority Sorter PluginOn 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.









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

slave continually going offline , Disk space is too low

[Kamal Ahmed]

I have one centos 6.3 slave going offline continually while complaining of 
"Disk Space too Low"

but when i do a df -h, i get:

 df -h
Filesystem    Size  Used Avail Use% Mounted on
/dev/mapper/vg1-lv_root
  5.0G  3.2G  1.5G  69% /
tmpfs 939M 0  939M   0% /dev/shm
/dev/sda1    1008M  130M  828M  14% /boot
/dev/mapper/vg1-lv_home
  2.0G  1.1G  889M  54% /home
/dev/mapper/vg1-lv_opt
  756M   17M  701M   3% /opt
/dev/mapper/vg1-lv_tmp
  2.0G   68M  1.9G   4% /tmp
/dev/mapper/vg1-lv_var
  2.0G  1.6G  284M  86% /var
/dev/mapper/vg1-lv_var_log
  756M   49M  669M   7% /var/log
/dev/mapper/vg2-lv_extra
   18G  3.7G   14G  22% /extra

-- 
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: Issues after moving to 1.501 With Slave Nodes

[Stephen Connolly]

LTS is supposed to include critical security fixes too... otherwise it's
just a version that stays around for a while.

https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-advisories/P32IpTQNT5o

https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04

"Slaves that are started via Java Web Start will fail to reconnect if the
*.jnlp file is locally stored. This is because the authentication tokens
change. An administrator would have to login to the UI, retrieve the *.jnlp
file and overwrite what's already on the slave. A slave that was launched
via Java Web Start and then turned into a service through its menu falls
into this category."

My understanding of this issue, and until now I have stayed off
contributing to the security advisory list as I don't want that to be seen
as too CloudBees heavy (there's already KK & Jesse on the list and perhaps
Ryan and Nicolas too), is that there was no other way to fix the issue at
hand.

Perhaps the changelog (http://jenkins-ci.org/changelog-stable) could have
given a link to the Security Advisory, or at least mentioned that there
were manual steps to be taken... that would be a good issue to put before
the biweekly jenkins project meetings (at a time when I am cooking dinner,
hence why I am never on them)

-Stephen


On 13 February 2013 13:39, Les Mikesell  wrote:

> So, does that mean surprising changes should go undocumented and even
> backed into revs where they are more surprising?   Or did I just miss
> the part in the release notes that said previously-working systems
> would break?
>
>
> On Wed, Feb 13, 2013 at 2:57 AM, Stephen Connolly
>  wrote:
> > IIRC this was fallout from fixing a critical security issue
> >
> >
> > On 12 February 2013 16:21, Les Mikesell  wrote:
> >>
> >> On Tue, Feb 12, 2013 at 9:37 AM, Fisher, Allen 
> >> wrote:
> >> > I did notice something interesting. If I launch via the website, the
> >> > slaves
> >> > will connect, until I install the service. After that, they don’t
> >> > connect.
> >>
> >> If it works when you are authenticated in the browser before
> >> launching, but not as a service it is because the system changed to
> >> require slaves to authenticate via jnlp but it seems to be mostly
> >> broken.  I changed mine to start via ssh (linux) and 'let jenkins
> >> control this windows slave" on the windows systems where that worked.
> >> Not sure what to do about the windows 2008 systems where none of that
> >> works.
> >>
> >> If you are on a private firewalled LAN, you might be OK with allowing
> >> anonymous read and slave connect in your main authorization matrix to
> >> restore the old behavior.
> >>
> >> By the way - was this change documented somewhere for the LTS 1.480.2
> >> release?.  I had seen the problem mentioned for 1.49x versions but
> >> wasn't expecting it in 1.480.2. - and I thought the point of the LTS
> >> line was to avoid surprises.
> >>
> >> --
> >>Les Mikesell
> >>  lesmikes...@gmail.com
> >>
> >> --
> >> 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.
>
>
>

-- 
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: Issues after moving to 1.501 With Slave Nodes

[Les Mikesell]

So, does that mean surprising changes should go undocumented and even
backed into revs where they are more surprising?   Or did I just miss
the part in the release notes that said previously-working systems
would break?


On Wed, Feb 13, 2013 at 2:57 AM, Stephen Connolly
 wrote:
> IIRC this was fallout from fixing a critical security issue
>
>
> On 12 February 2013 16:21, Les Mikesell  wrote:
>>
>> On Tue, Feb 12, 2013 at 9:37 AM, Fisher, Allen 
>> wrote:
>> > I did notice something interesting. If I launch via the website, the
>> > slaves
>> > will connect, until I install the service. After that, they don’t
>> > connect.
>>
>> If it works when you are authenticated in the browser before
>> launching, but not as a service it is because the system changed to
>> require slaves to authenticate via jnlp but it seems to be mostly
>> broken.  I changed mine to start via ssh (linux) and 'let jenkins
>> control this windows slave" on the windows systems where that worked.
>> Not sure what to do about the windows 2008 systems where none of that
>> works.
>>
>> If you are on a private firewalled LAN, you might be OK with allowing
>> anonymous read and slave connect in your main authorization matrix to
>> restore the old behavior.
>>
>> By the way - was this change documented somewhere for the LTS 1.480.2
>> release?.  I had seen the problem mentioned for 1.49x versions but
>> wasn't expecting it in 1.480.2. - and I thought the point of the LTS
>> line was to avoid surprises.
>>
>> --
>>Les Mikesell
>>  lesmikes...@gmail.com
>>
>> --
>> 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.

Priority Sorter - High or Low?

[Mandeville, Rob]

I'm using the priority sorter plugin, and getting confused.  The page for the 
plugin at https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin 
says that "A priority of 50 comes before a priority of 100", so a lower 
priority number is a higher priority.  When I look at the source, 
PrioritySorterQueueSorter.java runs the compare in reverse order, complete with 
a comment stating "Note that we sort these backwards because we want to return 
higher-numbered items first".  When I tried launching jobs of different 
priorities from the Web UI, they ran in launch order, apparently ignoring the 
priority sorter plugin.  When I ran a build that launches sub-builds of 
different priorities via "trigger parameterized builds on other projects", they 
got launched but required a label that was completely in uses, so they got 
queued.  The four jobs with priority 100 launched before the one with priority 
90.

Am I correct in assuming that, if two jobs are waiting on an executor on a node 
or label, the one with the higher priority number will get in first?  And if 
that is the case, should somebody edit the wiki for the plugin?

Thanks in advance,

--Rob

The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

-- 
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: Warnings plugin configuration ?

[Ulli Hafner]

Yes, please. If there is something what helps to describe the plugin 
configuration then go ahead :-)

Thanks, Ulli
 
Am 13.02.2013 um 12:48 schrieb Jan Goyvaerts :

> just modify this page then ?
> 
> On Tue, Feb 12, 2013 at 5:29 PM, Ulli Hafner  wrote:
>> 
>> 
>> Ok, thanks! I did't update the documentation after changing the 
>> visualization… (It only looks different for Java warnings up to now:-)
>> 
>> Interested in adding any missing documentation parts in the wiki?
>> 
>> Sure ! How ? What pages ?
>> (be aware I just know about this plugin - you seem to have much more code 
>> running out there)
> 
> https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
> 
> Ulli
> 
> 
> -- 
> 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: Warnings plugin configuration ?

[Jan Goyvaerts]

just modify this page then ?

On Tue, Feb 12, 2013 at 5:29 PM, Ulli Hafner wrote:

>
>>
>> Ok, thanks! I did't update the documentation after changing the
>> visualization… (It only looks different for Java warnings up to now:-)
>>
>> Interested in adding any missing documentation parts in the wiki?
>>
>
> Sure ! How ? What pages ?
> (be aware I just know about this plugin - you seem to have much more code
> running out there)
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
>
> Ulli
>
>  --
> 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.

install an update

[Brosh, Yossi]

Hi to all,

I am trying to install a new update 1.501 .
I am working on windows 7, Jenkins 1.489.
I was sure it was a straight forward installation - but it is wasn't.
I am not sure whether to kill the service before the installation? Any 
leftovers?
Am I missing any process?
After restarting my pc I still have the old one .

Best regards,
Yossi



-- 
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: REST API - How reliable is tag?

[Stephen Connolly]

Keep in mind that not all "items" have a color and/or display the same
meaning when they report a "color"

Case in point is the [Folders plugin](
http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/folder.html)
(which is free - as in give us your email address - but currently closed
source) or the [Update Center plugin](
http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/uc.html)
(which is a non-free - as in give us some money - and closed source)
plugins available from CloudBees.

Both of these show up as "item"s in the model IOW a Folder called foo will
show up at /job/foo (yes "items" are bound to the path segment "jobs")

So if it is the case that you are writing an external integration to
capture status of generic jobs, please don't use the color.

If it is the case that you have a specific job that you know is a job, then
you should be OK... though it is a hack... and hacks can and do break ;-)


On 12 February 2013 20:19, Octavian Covalschi
wrote:

> Hello,
>
> We're linking our database entities to a job in jenkins, it's  1 to 1
> relation. So, as a result we'd like to display real time job's status. I
> found 2 ways,
>
> 1. using /job/job1/api/xml (color tag)
> 2. using /job/job1/lastBuild/api/xml (building, result tags)
>
> In both cases it seems possible to find out if a job is building and/or
> failed.  But 1st solution seems simpler compared to 2nd which has bit more
> code especially if there wasn't any build made yet...
>
> So, what do you think? Can I rely on  tag, that can have blue,
> blue_anime, red, red_anime, grey, grey_anime values? Or it may change and I
> should use 2nd resource?
>
> Thank you in advance.
>
> --
> 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: Monitoring Metrics (eg. code coverage) Degradation

[Zigster]

I figured, that this would be one way to do.

It's a bit strange, that there's no plugin providing that feature as 
implementing a build fail for deteriorating code coverage or slow tests is 
mentioned in a few reputable books (just as "Continuous Delivery" by 
Humble/Farley) 

Thank you for your suggestion!




Am Dienstag, 12. Februar 2013 18:05:01 UTC+1 schrieb Octavian Covalschi:

> You may not like this solution, but until someone will post a better 
> solution, you could potentially create a simple shell task and run your 
> coverage metrics from there... With some magic you could check the results 
> and return 0 or 1 (i'm not sure the exact value), which will tell jenkins 
> if it failed or not...
>
> This kind of trick helped me a lot when I didn't want to rely on old 
> plugins or my requirement was too custom...
>
>
> On Tue, Feb 12, 2013 at 10:27 AM, Zigster 
> > wrote:
>
>> It's a PHP project...
>>
>> --
>> 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.

Re: Issues after moving to 1.501 With Slave Nodes

[Stephen Connolly]

IIRC this was fallout from fixing a critical security issue


On 12 February 2013 16:21, Les Mikesell  wrote:

> On Tue, Feb 12, 2013 at 9:37 AM, Fisher, Allen 
> wrote:
> > I did notice something interesting. If I launch via the website, the
> slaves
> > will connect, until I install the service. After that, they don’t
> connect.
>
> If it works when you are authenticated in the browser before
> launching, but not as a service it is because the system changed to
> require slaves to authenticate via jnlp but it seems to be mostly
> broken.  I changed mine to start via ssh (linux) and 'let jenkins
> control this windows slave" on the windows systems where that worked.
> Not sure what to do about the windows 2008 systems where none of that
> works.
>
> If you are on a private firewalled LAN, you might be OK with allowing
> anonymous read and slave connect in your main authorization matrix to
> restore the old behavior.
>
> By the way - was this change documented somewhere for the LTS 1.480.2
> release?.  I had seen the problem mentioned for 1.49x versions but
> wasn't expecting it in 1.480.2. - and I thought the point of the LTS
> line was to avoid surprises.
>
> --
>Les Mikesell
>  lesmikes...@gmail.com
>
> --
> 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.

AnsiColor plugin

[Thijs Kuijpers]

I am trying to use the AnsiColor plugin. I have installed version 0.3.1 on 
Jenkins 1.501 and enabled it in a job using the xterm color scheme.
The job uses the TFS plugin to get the code and the MSBuild plugin to build 
C++ and C# code. I would like to see the colored output just like you see 
when running it in a command prompt (errors red and warnings yellow).
After running the job, links are colored blue. No other colors are there.
Am I doing something wrong? Any help will be appreciated. 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.