1.634 not downloading zip archives on Windows

2015-10-20 Thread Trinition
We just updated to 1.634 but our promotion jobs that start by downloading the archived artifacts. That is failing because the download link itself is returning an HTTP 500. For example: http://jenkins/job/MyJob/1046/artifact/*zip*/archive.zip I get an "Oops!" evil Jenkins, and a stack trace t

Re: Polling out of control

2015-05-18 Thread Trinition
SourceGear Vault. We wrote our own plug-in for it. -- 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. To view this d

Re: Polling out of control

2015-05-18 Thread Trinition
independently polling. On Friday, May 15, 2015 at 3:58:09 PM UTC-4, Trinition wrote: > > Our Windows Jenkins 1.613 server is presently going out of control with > polling. > > We have about 50 jobs configured. Each is set for either "H/5 * * * *" or > "H/10 * * * *"

Polling out of control

2015-05-15 Thread Trinition
Our Windows Jenkins 1.613 server is presently going out of control with polling. We have about 50 jobs configured. Each is set for either "H/5 * * * *" or "H/10 * * * *". Yet as soon as we start out server, dozens of polling's are kicked off (we have no slaves; our polling is done via a comma

Re: Jenkins Warnings Plugin Slow?

2015-01-19 Thread Trinition
1:57:59 PM UTC-5, Trinition wrote: > > We're using the Warnings Plugin > <https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin> in our CI > build, and doing some time-stamp logging in our build, I've found that 1 > miunte of our 13 minute build is spent he

Jenkins Warnings Plugin Slow?

2015-01-19 Thread Trinition
We're using the Warnings Plugin in our CI build, and doing some time-stamp logging in our build, I've found that 1 miunte of our 13 minute build is spent here: 11:13.1 00:10.6 [WARNINGS] Parsing warnings in console log with parser M

Re: Moved Workspace Root Directory; Jenkins Ignores It

2015-01-16 Thread Trinition
Workspace link in the page for a Jenkins job looks at what workspace was last used, not what the workspace should be from now on? On Friday, January 16, 2015 at 9:54:25 AM UTC-5, Trinition wrote: > > I have a simple master-only set up (Jenkins 1.596), but I was low on disk > space, so I

Moved Workspace Root Directory; Jenkins Ignores It

2015-01-16 Thread Trinition
I have a simple master-only set up (Jenkins 1.596), but I was low on disk space, so I moved my workspaces to a second disk: 1. Set up the new location (e.g. E:\Workspace) 2. Changed Jenkins "Workspace Root Directory" to " E:/Workspace/${ITEM_FULLNAME}" 3. Shut down Jenkins 4. Move

Re: BUG? Archived arctifacts OK in Jenkins; 0-bytes in downloaded ZIP

2013-09-25 Thread Trinition
Someone else discovered this issue new in 1.532. It works fine in 1.531. Someone has submitted a fix. https://issues.jenkins-ci.org/browse/JENKINS-19752 On Wednesday, September 25, 2013 1:47:10 PM UTC-4, Trinition wrote: > > We've recently upgraded to Jenkins 1.532 and h

Re: BUG? Archived arctifacts OK in Jenkins; 0-bytes in downloaded ZIP

2013-09-25 Thread Trinition
FWIW, there were some recent ZLIB issues that may be related (loose lay opinion): https://issues.jenkins-ci.org/browse/JENKINS-19473 On Wednesday, September 25, 2013 1:47:10 PM UTC-4, Trinition wrote: > > We've recently upgraded to Jenkins 1.532 and have started experiencing a &g

BUG? Archived arctifacts OK in Jenkins; 0-bytes in downloaded ZIP

2013-09-25 Thread Trinition
We've recently upgraded to Jenkins 1.532 and have started experiencing a new problem. When we view the archived artifacts of a build, they're fine (e.g. local.config is 1kb). But if we ask for "All Files As Zip", the files in the zip are 0 bytes. The files are all present, but empty. -- You

Re: Launcher and environment variables on Windows

2013-09-10 Thread Trinition
I finally realized what the problem was. Launching a process does *not* interpolate environment variables in its arguments. The arguments are passed verbatim. It's not the process launching mechanism's job to do so. It works through cmd.exe because it *is* a command interpreter. I was launchin