date:20140808















































Daniel Beck
 commented on  JENKINS-23744


Using blanks in names that get parsed to URIs cause URISyntaxException















This report is missing Jenkins version.

Is there a warning on the Manage Jenkins page about character set, or Tomcat, or anything like that?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-19310) Incorrect links in build history when view is defined inside a folder















































Daniel Beck
 updated  JENKINS-19310


Incorrect links in build history when view is defined inside a folder
















Change By:


Daniel Beck
(08/Aug/14 11:50 PM)




Labels:


1.554.x-rejected folders
 lts-candidate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-24186) Add option for deleting perforce clients

2014-08-08 Thread cmay...@cisco.com (JIRA)

Caleb Mayeux
commented on JENKINS-24186

Add option for deleting perforce clients

1) True, there is an very easy workaround adding the command as the last step or post build task. It'd just be cleaner inside the plugin (arguably the opposite if you're not using it and concerned about bloat).
2) Yes, it has become an incredibly flexible plugin.
3) Took a look at the code (guess I should've done that part first). I was originally thinking it'd be a checkbox under force sync, which would be pretty attractive. Looking at the SCM class though, the only obvious way I can see to do it would be to add it as a separate post-build step - similar to the way the labeling works (I'm assuming that's why the labeling portion isn't grouped with the rest of the plugin). A post-build step just for that option would be almost as annoying as having to add a generic step with the command line command, so I'm somewhat inclined to side with your reluctance on this feature.

Well, thanks for the time and input! Perhaps we can leave this ticket open for a month or so and see if anyone else wants to weigh in, then close it out?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

[JIRA] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
















































Mark Waite
 closed  JENKINS-24125 as Not A Defect


Git Polling fails for job restricted to Mac OS X slave (with Windows master)
















The git plugin defaults to use "fast remote polling" to reduce the disc and I/O overhead of polling for updates.  That fast remote polling is performed on the master.

If you would rather not use fast remote polling, you can add "Additional Behaviours" to "Force polling using workspace".  That will then require a workspace before performing a poll, and will heed the platform restrictions of the job definition.  

That restriction will cause polling to be significantly slower in certain cases, but it will assure the job restriction is honored by the polling process.





Change By:


Mark Waite
(08/Aug/14 10:49 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-24179) Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"















































Mark Waite
 commented on  JENKINS-24179


Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"















The git commands are logged more clearly with the current git client plugin (1.10.2) than they are with the version you're using.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-24186) Add option for deleting perforce clients

2014-08-08 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 commented on  JENKINS-24186


Add option for deleting perforce clients















A few things:

	You can very easily just run 'p4 client -df $P4CLIENT' as the first step in your job.
	The plugin is already overloaded with options. We should only add new ones if they are absolutely necessary.
	Someone else (possibly you) will need to implement it if we decide to go ahead with adding it.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-23027) Quieter launch















































dogfood
 commented on  JENKINS-23027


Quieter launch















Integrated in  jenkins_main_trunk #3594
 [FIXED JENKINS-23027] Added Launcher.ProcStarter.quiet option. (Revision 11ab9be6ef12e6b4b961809131fc72da86af6d72)

 Result = SUCCESS
Jesse Glick : 11ab9be6ef12e6b4b961809131fc72da86af6d72
Files : 

	core/src/main/java/hudson/Launcher.java
	changelog.html
	test/src/test/java/hudson/LauncherTest.java





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-24186) Add option for deleting perforce clients

2014-08-08 Thread cmay...@cisco.com (JIRA)

Caleb Mayeux
commented on JENKINS-24186

Add option for deleting perforce clients

True, unless you're using the force sync option and wiping your workspace at the end of each build anyway. Maybe it could be a checkbox under the force sync option?

I have no idea how typical this workflow is, but ours relies on us wiping the workspace and force syncing each time. This is done because for a number of branches across a large pool of nodes, there isn't near enough storage space on each build slave to keep a sync'ed workspace on each (Dealing with a few hundred branches of 5-10GB workspace size in each, and a pool of a couple dozen nodes = 100s * (5-10)GB * ~ 24 = many terabytes of expensive SAN). Typical space/bandwidth tradeoff, with a local perforce proxy keeping the traffic across the WAN to a minimum. Additionally, it keeps builds from being contaminated by old artifacts.

Also this proposed enhancement would probably be useful for jobs that are run only rarely.

[JIRA] [perforce] (JENKINS-24186) Add option for deleting perforce clients

2014-08-08 Thread rob.pe...@gmail.com (JIRA)
















































Rob Petti
 assigned  JENKINS-24186 to Unassigned



Add option for deleting perforce clients
















Change By:


Rob Petti
(08/Aug/14 9:02 PM)




Assignee:


Rob Petti



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-24186) Add option for deleting perforce clients

2014-08-08 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 commented on  JENKINS-24186


Add option for deleting perforce clients















Unfortunately, clients need to be preserved in order for subsequent syncs to be more efficient. Deleting them at the end of the job would cause every run to sync everything from scratch, which is a massive waste of time and bandwidth. It's far more efficient to just keep them around.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [conditional-buildstep] (JENKINS-24180) Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'
















































Shannon Kerr
 closed  JENKINS-24180 as Not A Defect


Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'
















Change By:


Shannon Kerr
(08/Aug/14 8:58 PM)




Status:


Resolved
Closed





Assignee:


Dominik Bartholdi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [conditional-buildstep] (JENKINS-24180) Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'















































Shannon Kerr
 commented on  JENKINS-24180


Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'















I didn't see it until I started to ask you why it was invalid.  Should be .* instead of *.

Thanks Daniel.  Always helpful.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [perforce] (JENKINS-24186) Add option for deleting perforce clients

2014-08-08 Thread cmay...@cisco.com (JIRA)

Caleb Mayeux
created JENKINS-24186

Add option for deleting perforce clients

Issue Type:

Improvement

Assignee:

Rob Petti

Components:

perforce

Created:

08/Aug/14 8:54 PM

Description:

It would be much more efficient to have an option for Jenkins to delete the workspace at the end of the build job. While the Jenkins perforce plugin is really good about creating and managing workspaces, currently it ends up creating lots of clients/workspaces without cleaning any up. Since the perforce server has to track a lot of metadata on each client workspace (records on each of the files that are checked out), it can severely limit the scalability of the Jenkins/perforce plugin using workspace management.

In a production atmosphere with hundreds to thousands of jobs that can run on different nodes, the perforce server can even run out of RAM loading all the client records into memory. This often leads to the perforce admin hunting down members of the devops team.

Environment:

Jenkins 1.554.2, perforce plugin 1.3.27, RHEL 5.5

Project:

Jenkins

Priority:

Major

Reporter:

Caleb Mayeux

[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks

2014-08-08 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-1640


Environment variables not passed through to Ant tasks















ok, thanks Jesse



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [conditional-buildstep] (JENKINS-24180) Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'
















































Daniel Beck
 resolved  JENKINS-24180 as Not A Defect


Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'
















That's what you get for an invalid regular _expression_.





Change By:


Daniel Beck
(08/Aug/14 8:41 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-import] (JENKINS-24184) "Password/API Token" box in clear text















































Daniel Beck
 updated  JENKINS-24184


"Password/API Token" box in clear text 
















Unrelated to Credentials plugin, seems to be specific to Job Import.





Change By:


Daniel Beck
(08/Aug/14 8:40 PM)




Assignee:


stephenconnolly





Component/s:


job-import





Component/s:


credentials



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [disk-usage] (JENKINS-24182) Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading

2014-08-08 Thread lorelei.mccol...@gmail.com (JIRA)















































Lorelei McCollum
 commented on  JENKINS-24182


Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading















yep it fixed the issue.. jobs are back.. but wanted to report the issue with latest release



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks
















































Jesse Glick
 assigned  JENKINS-1640 to Unassigned



Environment variables not passed through to Ant tasks
















I have no particular information about this. If it remains reproducible in current versions of Jenkins, someone interested should track down why and offer a fix.





Change By:


Jesse Glick
(08/Aug/14 8:34 PM)




Assignee:


Jesse Glick



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks















































Jesse Glick
 commented on  JENKINS-1640


Environment variables not passed through to Ant tasks















@stefanthurnherr I think this issue was about something unrelated: whether environment variables defined on the Jenkins process (i.e., not something like $WORKSPACE) are picked up by forked build steps it runs.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-23027) Quieter launch















































SCM/JIRA link daemon
 commented on  JENKINS-23027


Quieter launch















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/Launcher.java
 test/src/test/java/hudson/LauncherTest.java
http://jenkins-ci.org/commit/jenkins/11ab9be6ef12e6b4b961809131fc72da86af6d72
Log:
  [FIXED JENKINS-23027] Added Launcher.ProcStarter.quiet option.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-23027) Quieter launch
















































SCM/JIRA link daemon
 resolved  JENKINS-23027 as Fixed


Quieter launch
















Change By:


SCM/JIRA link daemon
(08/Aug/14 8:27 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ant] (JENKINS-1640) Environment variables not passed through to Ant tasks

2014-08-08 Thread ever...@free.fr (JIRA)















































evernat
 updated  JENKINS-1640


Environment variables not passed through to Ant tasks
















Stefan Thurnherr
Wow! It has been years since I have not heard news about an issue with a number such as JENKINS-1640.
So we may be able to close an issue opened for more than 6 years.
That's good news.

Jesse Glick
I have assigned to you, because you are a good source of confirmation for closing.
Feel free to reassign to D. or whatever.





Change By:


evernat
(08/Aug/14 8:17 PM)




Assignee:


Jesse Glick



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ircbot] (JENKINS-24185) IRC bot should prevent bad repo names from being forked

2014-08-08 Thread ch...@orr.me.uk (JIRA)

Christopher Orr
created JENKINS-24185

IRC bot should prevent bad repo names from being forked

Issue Type:

Improvement

Assignee:

Christopher Orr

Components:

ircbot

Created:

08/Aug/14 8:15 PM

Description:

I just made the mistake of forking a plugin repo on GitHub via the IRC bot, which was called something like "jenkins-foo-plugin".

Of course, the "jenkins-" prefix is redundant so we usually remove this, but ensure there is a "-plugin" suffix (well, for plugins at least).

So the IRC bot should block people from forking "jenkins-foo-plugin" (due to the redundant prefix) or "foo" (due to the missing "-plugin" suffix).

The bot probably should block and not automatically alter the name, as not every repo is a plugin (e.g. backend or infra projects which we may clone).

The bot should reply with the correct syntax, e.g.:

Refusing to fork "jenkins-foobar" due to bad repo name — try again with "fork baz/jenkins-foobar as foobar-plugin"

Project:

Jenkins

Priority:

Minor

Reporter:

Christopher Orr

[JIRA] [ircbot] (JENKINS-24185) IRC bot should prevent bad repo names from being forked

2014-08-08 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-24185


IRC bot should prevent bad repo names from being forked















I assigned this to me as a reminder to myself, but until I hit "Start Progress" this task is up for grabs, for anybody interested 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [matrix-auth] (JENKINS-23805) Add support for case insensitive auth realms to matrix auth















































Daniel Beck
 commented on  JENKINS-23805


Add support for case insensitive auth realms to matrix auth















Patric Steffen: I don't think so, see JENKINS-23872 and its comments.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [other] (JENKINS-24169) Script Console updates jobs without save
















































Daniel Beck
 resolved  JENKINS-24169 as Not A Defect


Script Console updates jobs without save
















Not a bug: All actions are immediate, saving just persists to disk.





Change By:


Daniel Beck
(08/Aug/14 8:04 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [matrix-auth] (JENKINS-23805) Add support for case insensitive auth realms to matrix auth

2014-08-08 Thread pat...@psteffen.de (JIRA)















































Patric Steffen
 commented on  JENKINS-23805


Add support for case insensitive auth realms to matrix auth















I think the issue can be closed with JENKINS-22247, right?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [tracking-svn] (JENKINS-24167) IllegalArgumentException: Null value not allowed as an environment variable: TRACKING_SVN_BUILD in Subversion Polling Log















































Daniel Beck
 updated  JENKINS-24167


IllegalArgumentException: Null value not allowed as an environment variable: TRACKING_SVN_BUILD in Subversion Polling Log
















Seems to be an issue with "Tracking SVN Plugin".





Change By:


Daniel Beck
(08/Aug/14 8:01 PM)




Description:



Builds are not triggered via Poll SCM.Subversion Polling Log contains the following error: {noformat}Started on Aug 7, 2014 5:21:46 PMERROR: Failed to record SCM polling for hudson.matrix.MatrixProject@7ad2477b[test]java.lang.IllegalArgumentException: Null value not allowed as an environment variable: TRACKING_SVN_BUILD	at hudson.EnvVars.put(EnvVars.java:356)	at hudson.plugins.trackingsvn.TrackingSVNAction.buildEnvVars(TrackingSVNAction.java:26)	at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:919)	at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1355)	at hudson.scm.SCM.poll(SCM.java:401)	at hudson.model.AbstractProject._poll(AbstractProject.java:1430)	at hudson.model.AbstractProject.poll(AbstractProject.java:1333)	at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119)	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509)	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538)	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)	at java.util.concurrent.FutureTask.run(FutureTask.java:262)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:745){noformat}The job is configured in the following way:{noformat}Build Triggers  Poll SCM   Schedule H 17 * * *{noformat}Version of Jenkins this bug is occurring{noformat}Jenkins ver. 1.574{noformat}How we are running Jenkins{noformat}/usr/java/latest/bin/java -XX:MaxPermSize=1024M -Dhudson.Functions.autoRefreshSeconds=60 -Dhudson.tasks.Fingerprinter.enableFingerprintsInDependencyGraph=true -Dhudson.upstreamCulprits=true -Xmx3000M -Dhudson.scm.SubversionSCM.pollFromMaster=true -Djava.util.logging.ConsoleHandler.level=FINE -jar lib/jenkins.war --httpPort=18080 --webroot=mst/war --ajp13Port=-1{noformat}Environment we are using {noformat}System PropertiesName  ↓	Value   awt.toolkit	sun.awt.X11.XToolkitexecutable-war	/data/ci/lib/jenkins-1.574.warfile.encoding	UTF-8file.encoding.pkg	sun.iofile.separator	/hudson.diyChunking	truehudson.Functions.autoRefreshSeconds	60hudson.scm.SubversionSCM.pollFromMaster	truehudson.tasks.Fingerprinter.enableFingerprintsInDependencyGraph	truehudson.upstreamCulprits	truejava.awt.graphicsenv	sun.awt.X11GraphicsEnvironmentjava.awt.headless	truejava.awt.printerjob	sun.print.PSPrinterJobjava.class.path	lib/jenkins.warjava.class.version	51.0java.endorsed.dirs	/usr/java/jdk1.7.0_60/jre/lib/endorsedjava.ext.dirs	/usr/java/jdk1.7.0_60/jre/lib/ext:/usr/java/packages/lib/extjava.home	/usr/java/jdk1.7.0_60/jrejava.io.tmpdir	/tmpjava.library.path	/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/libjava.runtime.name	Java(TM) SE Runtime Environmentjava.runtime.version	1.7.0_60-b19java.specification.name	Java Platform API Specificationjava.specification.vendor	Oracle Corporationjava.specification.version	1.7java.util.logging.ConsoleHandler.level	FINEjava.vendor	Oracle Corporationjava.vendor.url	http://java.oracle.com/java.vendor.url.bug	http://bugreport.sun.com/bugreport/java.version	1.7.0_60java.vm.info	mixed modejava.vm.name	Java HotSpot(TM) 64-Bit Server VMjava.vm.specification.name	Java Virtual Machine Specificationjava.vm.specification.vendor	Oracle Corporationjava.vm.specification.version	1.7java.vm.vendor	Oracle Corporationjava.vm.version	24.60-b09jna.platform.library.path	/usr/lib64:/lib64:/usr/lib:/libline.separator	mail.smtp.sendpartial	truemail.smtps.sendpartial	trueorg.apache.commons.logging.Log	org.apache.commons.logging.impl.Jdk14Loggeros.arch	amd64os.name	Linuxos.version	2.6.18-308.el5path.separator	:sun.arch.data.model	64sun.boot.class.path	/usr/java/jdk1.7.0_60/jre/lib/resources.jar:/usr/java/jdk1.7.0_60/jre/lib/

[JIRA] [disk-usage] (JENKINS-24182) Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading















































Daniel Beck
 commented on  JENKINS-24182


Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading















Did you try downgrading the plugin?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24183) New UI layout is not properly resizing for build history component















































Daniel Beck
 updated  JENKINS-24183


New UI layout is not properly resizing for build history component
















Oh come on...

Critical
Crashes, loss of data, severe memory leak.





Change By:


Daniel Beck
(08/Aug/14 7:57 PM)




Priority:


Critical
Minor



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24183) New UI layout is not properly resizing for build history component
















































Daniel Beck
 resolved  JENKINS-24183 as Duplicate


New UI layout is not properly resizing for build history component
















Duplicates JENKINS-23829





Change By:


Daniel Beck
(08/Aug/14 7:57 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [credentials] (JENKINS-24184) "Password/API Token" box in clear text

2014-08-08 Thread jbala...@matrox.com (JIRA)















































John Balanca
 created  JENKINS-24184


"Password/API Token" box in clear text 















Issue Type:


Bug



Assignee:


stephenconnolly



Components:


credentials



Created:


08/Aug/14 7:52 PM



Description:


After using the Job import plugin for importing in the past then switching to another location in Jenkins then back shows full password in cleat text.   I was helping someone on how to import tasks from One Jenkins server to another and when I went to the job import plugin page there was my password for all to see in clear text on his computer when I imported on my system.  Either Hide it with "*" or use the Credentials plugin.




Project:


Jenkins



Priority:


Major



Reporter:


John Balanca

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24183) New UI layout is not properly resizing for build history component

2014-08-08 Thread lorelei.mccol...@gmail.com (JIRA)















































Lorelei McCollum
 updated  JENKINS-24183


New UI layout is not properly resizing for build history component
















Change By:


Lorelei McCollum
(08/Aug/14 7:46 PM)




Priority:


Major
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24183) New UI layout is not properly resizing for build history component

2014-08-08 Thread lorelei.mccol...@gmail.com (JIRA)















































Lorelei McCollum
 commented on  JENKINS-24183


New UI layout is not properly resizing for build history component















This is also making it really hard to click on the builds, as the text is overlapping with the rest of the page



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24181) Status icon not showing in the project view when "it" is not a BallColor















































dogfood
 commented on  JENKINS-24181


Status icon not showing in the project view when "it" is not a BallColor















Integrated in  jenkins_main_trunk #3593
 [FIXED JENKINS-24181] Status icon not showing in the project view when "it" is not a BallColor (Revision 6f87e61ebe6ecd3dfdff217aea2b05336de29c47)

 Result = SUCCESS
tom.fennelly : 6f87e61ebe6ecd3dfdff217aea2b05336de29c47
Files : 

	core/src/main/resources/lib/hudson/ballColorTd.jelly





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [ghprb] (JENKINS-22781) Do not trigger build when diff hasn't change

2014-08-08 Thread david.joel.tan...@gmail.com (JIRA)















































David Tanner
 commented on  JENKINS-22781


Do not trigger build when diff hasn't change















I have noticed this behavior when I have the build all checkbox marked.  Otherwise the logs record there was a change, but nothing to trigger the build.  Check your setting.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-24179) Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"

2014-08-08 Thread robd...@hotmail.com (JIRA)















































Rob Duff
 commented on  JENKINS-24179


Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"















No luck with JGit, unfortunately...  I'm getting authentication issues and it doesn't appear to support shallow clones and recursive submodules, so I don't think we can use it as a long-term solution until a few more features are added.

In the meantime though, is there a way to see the exact git commands that are being issued by the git plugin? That will help me reproduce the problem outside of Jenkins.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24183) New UI layout is not properly resizing for build history component

2014-08-08 Thread lorelei.mccol...@gmail.com (JIRA)















































Lorelei McCollum
 created  JENKINS-24183


New UI layout is not properly resizing for build history component















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


buildhistory.png



Components:


core, gui



Created:


08/Aug/14 6:54 PM



Description:


We just upgraded our jenkins server to Jenkins ver. 1.574

There is now a new Skin and UI look to the server. However there is a regression. We use longer names in our "Build History" of jobs,and now with the longer names, the rest of the page is not resizing properly as it did in the past. so it is very hard to read and see the job page

I can provide more details if needed, but it is making it very hard to use the new UI




Environment:


Jenkins Ubuntu server environment




Project:


Jenkins



Priority:


Major



Reporter:


Lorelei McCollum

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [disk-usage] (JENKINS-24182) Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading

2014-08-08 Thread lorelei.mccol...@gmail.com (JIRA)















































Lorelei McCollum
 created  JENKINS-24182


Disk Usage plugin throws severe exception in latest release and prevents maven jobs from loading















Issue Type:


Bug



Affects Versions:


current



Assignee:


Lucie Votypkova



Components:


disk-usage



Created:


08/Aug/14 6:47 PM



Description:


We upgraded to version .24 from .23 of the disk usage plugin, and it caused our Maven Project jobs to no longer show up and were not accessible in Jenkins UI. Config.xml files still existed on the server

From inspecting the logs we saw this stack
Aug 08, 2014 1:51:38 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading job ourjobname
java.lang.NullPointerException
	at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:971)
	at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184)
	at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:740)
	at hudson.maven.MavenModule.updateTransientActions(MavenModule.java:485)
	at hudson.model.AbstractProject.save(AbstractProject.java:304)
	at hudson.plugins.disk_usage.DiskUsageProperty.setOwner(DiskUsageProperty.java:150)
	at hudson.model.Job.onLoad(Job.java:213)
	at hudson.model.AbstractProject.onLoad(AbstractProject.java:318)
	at hudson.maven.MavenModule.onLoad(MavenModule.java:283)
	at hudson.model.Items.load(Items.java:279)
	at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108)
	at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:790)
	at hudson.model.Items.load(Items.java:279)
	at jenkins.model.Jenkins$18.run(Jenkins.java:2599)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:885)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745) 




Environment:


Ubuntu server Jenkins environment




Project:


Jenkins



Priority:


Blocker



Reporter:


Lorelei McCollum

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24181) Status icon not showing in the project view when "it" is not a BallColor















































Tom FENNELLY
 updated  JENKINS-24181


Status icon not showing in the project view when "it" is not a BallColor
















Change By:


Tom FENNELLY
(08/Aug/14 6:47 PM)




Summary:


Status icon not showing in the project view when
 using the CloudBees Folders Plugin
 "it" is not a BallColor



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24181) Status icon not showing in the project view when using the CloudBees Folders Plugin















































SCM/JIRA link daemon
 commented on  JENKINS-24181


Status icon not showing in the project view when using the CloudBees Folders Plugin















Code changed in jenkins
User: tfennelly
Path:
 core/src/main/resources/lib/hudson/ballColorTd.jelly
http://jenkins-ci.org/commit/jenkins/6f87e61ebe6ecd3dfdff217aea2b05336de29c47
Log:
  [FIXED JENKINS-24181] Status icon not showing in the project view when "it" is not a BallColor





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24181) Status icon not showing in the project view when using the CloudBees Folders Plugin
















































SCM/JIRA link daemon
 resolved  JENKINS-24181 as Fixed


Status icon not showing in the project view when using the CloudBees Folders Plugin
















Change By:


SCM/JIRA link daemon
(08/Aug/14 6:44 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-23741) Add support for the Rake plugin

2014-08-08 Thread m...@daniel-spilker.com (JIRA)
















































Daniel Spilker
 assigned  JENKINS-23741 to Daniel Spilker



Add support for the Rake plugin
















Change By:


Daniel Spilker
(08/Aug/14 6:40 PM)




Assignee:


Justin Ryan
Daniel Spilker



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [job-dsl-plugin] (JENKINS-23741) Add support for the Rake plugin

2014-08-08 Thread m...@daniel-spilker.com (JIRA)
















































Daniel Spilker
 resolved  JENKINS-23741 as Fixed


Add support for the Rake plugin
















Will be released in 1.25.





Change By:


Daniel Spilker
(08/Aug/14 6:41 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-23027) Quieter launch















































SCM/JIRA link daemon
 commented on  JENKINS-23027


Quieter launch















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java
 src/main/java/org/jenkinsci/plugins/durabletask/WindowsBatchScript.java
http://jenkins-ci.org/commit/durable-task-plugin/6dc99309d2f242f4606fdcb627b0dcab89d15992
Log:
  JENKINS-23027 Using Launcher.ProcStarter.quiet when available.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-23027) Quieter launch















































Jesse Glick
 updated  JENKINS-23027


Quieter launch
















Change By:


Jesse Glick
(08/Aug/14 6:30 PM)




Component/s:


core



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [delivery-pipeline] (JENKINS-24173) Show Views TabBar in pipeline default view















































Patrik Boström
 commented on  JENKINS-24173


Show Views TabBar in pipeline default view















Created PR
https://github.com/Diabol/delivery-pipeline-plugin/pull/76



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24181) Status icon not showing in the project view when using the CloudBees Folders Plugin















































Tom FENNELLY
 created  JENKINS-24181


Status icon not showing in the project view when using the CloudBees Folders Plugin















Issue Type:


Bug



Assignee:


Tom FENNELLY



Components:


core



Created:


08/Aug/14 6:21 PM



Project:


Jenkins



Labels:


user-experience




Priority:


Major



Reporter:


Tom FENNELLY

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [delivery-pipeline] (JENKINS-24173) Show Views TabBar in pipeline default view















































Patrik Boström
 updated  JENKINS-24173


Show Views TabBar in pipeline default view
















How it will look





Change By:


Patrik Boström
(08/Aug/14 6:16 PM)




Attachment:


ViewTabs.png



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-24179) Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"
















































Mark Waite
 closed  JENKINS-24179 as Won't Fix


Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"
















Your suspicion matches with my suspicion.  I would still be interested to hear if the JGit implementation used in the plugin is able to address the use case you're running.

The JGit implementation is pure java, so it is slower than the command line git implementation, but since it is pure Java, it does not require a git command line client.





Change By:


Mark Waite
(08/Aug/14 6:10 PM)




Status:


Resolved
Closed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout















































Shannon Kerr
 commented on  JENKINS-23146


StringIndexOutOfBoundsException on subversion checkout















Will do.  Thanks.  I only brought it up here because the error message here looks the same and we weren't getting it until I updated the SVN plugin to 2.4.1.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [conditional-buildstep] (JENKINS-24180) Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'

Shannon Kerr
created JENKINS-24180

Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*'

Issue Type:

Bug

Assignee:

Dominik Bartholdi

Components:

conditional-buildstep

Created:

08/Aug/14 6:00 PM

Description:

During a build, we're seeing this in the console output, but it doesn't appear to impact the actual execution. We get what we wanted:

Build step 'Conditional steps (multiple)' changed build result to SUCCESS
Regular _expression_ run condition: _expression_=[*.Windows.*true], Label=[Windows,Linuxfalse]
Exception caught evaluating condition: [java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0
*.Windows.*true
^], action = "" class="error">[Don't run]

We get this consistently. We have a checkbox to run tests when it is checked. We only see the above when it is not checked.

Environment:

Host: Ubuntu 12.04 Server

Project:

Jenkins

Priority:

Minor

Reporter:

Shannon Kerr

[JIRA] [git] (JENKINS-24179) Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"

2014-08-08 Thread robd...@hotmail.com (JIRA)

Rob Duff
commented on JENKINS-24179

Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"

Thanks very much for the very speed reply, Mark! I'll take this up with the msysgit folks.

For the sake of completeness (for those who may wander to this issue), I've found something suspicious. We have two different builds running at the same time on the same machine in two different executors, and they're cloning the same repository. Here is the output of the first, which passed:

11:51:45 Cloning repository ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:47 Checking out Revision 5e4da3e3994dbe8b7aa0b995566c479dce51f474 (core-binaries/master

Here is the output of the second, which failed:

11:51:45 Cloning repository ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
12:01:46 ERROR: Timeout after 10 minutes
12:01:46 FATAL: Failed to fetch from ssh://g...@git.dev.faked:7999/re/core-binaries.git

We have lots of repositories, but I bet it only happens when the same repository is cloned at the same time. The timing makes me suspicious that this might be the issue.

[JIRA] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used

2014-08-08 Thread h...@kabhal.org (JIRA)















































Hugo de Paix de Coeur
 commented on  JENKINS-14193


EnvInject doesn't pass variables defined in prebuild step if maven project is used















Workaround : The older Envfile plugin is working (Jenkins 1.574) with Maven goal and options field.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout















































Daniel Beck
 commented on  JENKINS-23146


StringIndexOutOfBoundsException on subversion checkout















Shannon Kerr I saw failures to switch before, but it's rare enough that I didn't want to investigate further. They didn't look like they were related to this either. If you can provide a reproducible test case, file a new issue.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)

2014-08-08 Thread cdouce...@everyscape.com (JIRA)

Charles Doucette
commented on JENKINS-24125

Git Polling fails for job restricted to Mac OS X slave (with Windows master)

So is it expected that all git installations will work on all platforms, even if the job can only be built on certain platforms? I didn't think so - so I assumed that the polling etc. would occur only on the appropriate node(s). If that is the case, then it seems as if the only appropriate path to the git executable would be "git" as you suggested (assuming the git executable will be found in the path and that the ".exe" suffix for windows is implicit/not-necessary).

For some reason, the PATH variable defined on the OS/X slave for the user running Jenkins didn't seem to be used - thus "git" was not found and therefore we defined an alternate (platform specific) installation of git for Mac with an explicit directory instead of overriding the default installation just for the slave (which I didn't know I could/should do).

[JIRA] [git] (JENKINS-24179) Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"

Mark Waite
resolved JENKINS-24179 as Won't Fix

Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"

As far as I can tell from the command output, the "git fetch" command itself is reporting on its "stderr" that it could not create the .ssh directory.

The git client plugin uses the command line git implementation, and is thus connected to bugs which may exist in the command line git implementation. In this case, the command line implementation appears to have a race condition where it attempts to create a directory that already exists.

You will probably need to take this sort of bug to the msysgit community for a fix. There is not much which the git client plugin can do to prevent the problem.

You could experiment with JGit to see if it shows the same issues, and if it behaves any better in your use case. There are still feature gaps in the JGit portion of the git client plugin, but it is worth a "test drive" to see if it will meet your use cases.

Change By:

Mark Waite
(08/Aug/14 5:06 PM)

Status:

Open
Resolved

Resolution:

Won't Fix

[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec

2014-08-08 Thread jakob.korh...@gmail.com (JIRA)
















































Jakob Korherr
 resolved  JENKINS-22009 as Fixed


Git Polling Keeps Detecting Changes When Variables in refspec
















pull requests were merged in master and 2.2.x





Change By:


Jakob Korherr
(08/Aug/14 5:13 PM)




Status:


In Progress
Resolved





Assignee:


Nicolas De Loof
Jakob Korherr





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-24179) Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"

2014-08-08 Thread robd...@hotmail.com (JIRA)















































Rob Duff
 created  JENKINS-24179


Intermittent git timeouts with error "Could not create directory 'c/users/user/.ssh'"















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git, git-client, ssh



Created:


08/Aug/14 4:57 PM



Description:


The full error received is:


Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
ERROR: Timeout after 10 minutes
FATAL: Failed to fetch from ssh://g...@git.dev.faked:7999/re/core-binaries.git
hudson.plugins.git.GitException: Failed to fetch from ssh://g...@git.dev.faked:7999/re/core-binaries.git
	at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:622)
	at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:854)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:879)
	at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
	at hudson.model.Run.execute(Run.java:1665)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:246)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@git.dev.faked:7999/re/core-binaries.git +refs/heads/master:refs/remotes/core-binaries/master" returned status code 128:
stdout: 
stderr: Could not create directory 'c/users/user/.ssh'.
fatal: Could not read from remote repository.



The git server hardware had been upgraded from a VM to a physical machine with 24 cores and 16G of RAM.  The repositories are pretty small, and the machine isn't under much load at all.  No networking issues are evident.  I am confident this is not a true timeout, but an actual hang.  It is intermittent.  It seems similar to the issue found here:

http://stackoverflow.com/questions/10732940/git-operations-occasionally-hang-in-jenkins-on-windows

It also seems like it could be related to https://issues.jenkins-ci.org/browse/JENKINS-21654.

We are using the "cmd" directory instead of the "bin" directory, i.e. "C:\Program Files (x86)\Git\cmd\git.exe".

The HOME environment variable is set to "c:\users\user"

The c:\users\user\.ssh directory exists, and the permissions seem to be fine (besides, it's intermittent...)

Our c:\users\user\.ssh\config file looks like this:


Host git.dev.faked
StrictHostKeyChecking no
UserKnownHostsFile NUL



We have multiple executors for our build machines, so it could be that another git command is locking the .ssh directory while it's working.  However, the likelihood of locking the database for 10 minutes if very, very unlikely.




Environment:


Windows Server 2008

Jenkins 1.532.2

Git Client Plugin 1.8.0

Git Plugin 2.1.0






Project:


Jenkins



Priority:


Critical



Reporter:


Rob Duff

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout















































Shannon Kerr
 commented on  JENKINS-23146


StringIndexOutOfBoundsException on subversion checkout















OK, I actually saw my issue happen at what appeared to be the "svn switch" (update), so I assumed that a retry might work for that.  Maybe it just appears to be at that point but what is actually happening is the change log computation.  I've added the retry already, so I'll just leave it.  Can't hurt.  Thanks.  I really do hope they port this back and come out with a 2.4.2.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [violations] (JENKINS-24178) Support pep257 validator

2014-08-08 Thread stephenj...@gmail.com (JIRA)















































Stephen Just
 created  JENKINS-24178


Support pep257 validator















Issue Type:


New Feature



Affects Versions:


current



Assignee:


peterkittreilly



Components:


violations



Created:


08/Aug/14 4:30 PM



Description:


Please add support for the python pep257 validator to the Jenkins Violations plugin. This is very similar to the existing pep8 validator, so it should be relatively easy.




Project:


Jenkins



Labels:


plugin
jenkins




Priority:


Minor



Reporter:


Stephen Just

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [durable-task] (JENKINS-23027) Quieter launch















































Jesse Glick
 started work on  JENKINS-23027


Quieter launch
















Change By:


Jesse Glick
(08/Aug/14 4:19 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout















































Daniel Beck
 commented on  JENKINS-23146


StringIndexOutOfBoundsException on subversion checkout















One of the Subversion plugin committers I guess. According to the wiki page there's a large selection to choose from. If one of you is a Cloudbees Jenkins Enterprise customer, file a support request with them.

Retry count wouldn't help. While I doubt that option applies to changelog computation, retrying the same broken string operations wouldn't do any good.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)

Mark Waite
commented on JENKINS-24125

Git Polling fails for job restricted to Mac OS X slave (with Windows master)

The master Jenkins git location is the default and is applied to the master and all slaves (as the default). That usually leads to me preferring to have the default be "git", and then if I'm running a Windows master, I assure that the Jenkins process includes the C:\Program Files(x86)\Git\bin directory in its path.

In your case, I suspect your default is "git.exe", and when that is attempted as the default on OS/X, there is no "git.exe". Thus, if you want the system wide default for the git program to be "git.exe" (possibly because most of your machines will be Windows based), then you'll need to define the git location for each slave that is not Windows.

You need to override tool locations if the default tool location does not work for that slave. You defined the default as "git.exe" and that only work for Windows.

[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading















































Jesse Glick
 updated  JENKINS-24176


Test result trend breaks lazy-loading
















Filed PR 13 with proposed fix.





Change By:


Jesse Glick
(08/Aug/14 3:35 PM)




URL:


https://github.com/jenkinsci/testng-plugin-plugin/pull/13



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading















































Jesse Glick
 commented on  JENKINS-24176


Test result trend breaks lazy-loading















Note that MethodResult.populateDataSetBuilder also searches backward in history, but limited to at most 10 builds, so it is not much of a problem.


Loaded lazy-load-perf #119 in Handling GET /jenkins/job/lazy-load-perf/129/testngreports/test/SomeTest/test1/graph : btpool0-5
hudson.model.RunMap$ThisIsHowItsLoaded
	at hudson.model.RunMap.retrieve(RunMap.java:221)
	at hudson.model.RunMap.retrieve(RunMap.java:56)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:382)
	at jenkins.model.lazy.LazyBuildMixIn$RunMixIn.getPreviousBuild(LazyBuildMixIn.java:366)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:198)
	at hudson.plugins.testng.results.MethodResult.populateDataSetBuilder(MethodResult.java:305)
	at hudson.plugins.testng.results.MethodResult.getGraph(MethodResult.java:276)
	at hudson.plugins.testng.results.MethodResult.doGraph(MethodResult.java:238)
	at …




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [hockeyapp] (JENKINS-24177) Use release notes since last successful build as changelog

2014-08-08 Thread c...@wetter.com (JIRA)















































Cornelius Schiffer
 created  JENKINS-24177


Use release notes since last successful build as changelog















Issue Type:


Improvement



Assignee:


Unassigned


Components:


hockeyapp



Created:


08/Aug/14 3:24 PM



Description:


We are using Jenkins and the Hockeyapp plugin to upload daily builds of an Android app to Hockeyapp. More often than not the Android Emulator installed on the Jenkins server will not be ready before the build times out, so we have to restart the build job.

This unfortunately clears the release notes used by the Hockeyapp plugin as a changelog for Hockeyapp. 

It would be great if the plugin could use the release notes since the last successful build instead of those since the last build.




Project:


Jenkins



Priority:


Major



Reporter:


Cornelius Schiffer

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)

2014-08-08 Thread cdouce...@everyscape.com (JIRA)















































Charles Doucette
 commented on  JENKINS-24125


Git Polling fails for job restricted to Mac OS X slave (with Windows master)















I can confirm that the name and paths of the git executables are correctly specified for the various platforms on the Git installations section of the Jenkins configuration page.

Apparently I could override those tool locations on the OS/X slave node configuration page (I was not aware of this) - but why do I need to do that?

Please explain to me how I can specify the proper git executable to use for both polling and building if they each use the same git executable specified by the job but polling runs on the master node but the job is built on the specified slave node?

Thanks,
Chuck



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading















































Jesse Glick
 commented on  JENKINS-24176


Test result trend breaks lazy-loading















This latter problem is essentially identical to JENKINS-23945 and should be solvable in the same way: by declining to display results for builds which have not yet been loaded for some other reason (such as the BuildHistoryWidget).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading















































Jesse Glick
 commented on  JENKINS-24176


Test result trend breaks lazy-loading















Experimenting with reverting the fix of JENKINS-9839. While that issue might be an annoyance in unusual cases, it is minor compared to the lazy-loading problem, which can bring a large Jenkins installation to a grinding halt—just because someone opened a job index page in a browser. Now the next problem appears:


hudson.model.RunMap$ThisIsHowItsLoaded
	at hudson.model.RunMap.retrieve(RunMap.java:221)
	at hudson.model.RunMap.retrieve(RunMap.java:56)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:382)
	at jenkins.model.lazy.LazyBuildMixIn$RunMixIn.getPreviousBuild(LazyBuildMixIn.java:366)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:198)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:106)
	at hudson.model.Run.getPreviousCompletedBuild(Run.java:819)
	at hudson.plugins.testng.TestNGProjectAction.populateDataSetBuilder(TestNGProjectAction.java:187)
	at hudson.plugins.testng.TestNGProjectAction.doGraph(TestNGProjectAction.java:112)
	at …




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading















































Jesse Glick
 started work on  JENKINS-24176


Test result trend breaks lazy-loading
















Change By:


Jesse Glick
(08/Aug/14 3:09 PM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [testng] (JENKINS-24176) Test result trend breaks lazy-loading















































Jesse Glick
 created  JENKINS-24176


Test result trend breaks lazy-loading















Issue Type:


Bug



Assignee:


Nalin Makar



Components:


testng



Created:


08/Aug/14 3:02 PM



Description:


Setup is the same as in JENKINS-23945 except use the testng branch of the sample project, and configure the TestNG plugin's publisher with **/target/surefire-reports/testng-results.xml. Even with the fix of JENKINS-23945 applied to Jenkins core, after displaying the job index page all builds are loaded:


... FINER hudson.model.Run
reload lazy-load-perf #71 @...
... FINEST hudson.model.RunMap
Loaded lazy-load-perf #71
hudson.model.RunMap$ThisIsHowItsLoaded
	at hudson.model.RunMap.retrieve(RunMap.java:221)
	at hudson.model.RunMap.retrieve(RunMap.java:56)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:382)
	at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:70)
	at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:59)
	at java.util.AbstractMap$2$1.next(AbstractMap.java:385)
	at hudson.util.RunList.size(RunList.java:108)
	at hudson.plugins.testng.TestNGProjectAction.newGraphNotNeeded(TestNGProjectAction.java:141)
	at hudson.plugins.testng.TestNGProjectAction.doGraph(TestNGProjectAction.java:114)
	at ...


The problem is TestNGProjectAction.newGraphNotNeeded calling RunList.size, which is deprecated since it forces all builds to be loaded immediately.




Project:


Jenkins



Labels:


lazy-loading
performance




Priority:


Critical



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24175) Create some functional tests to test the tag to translation















































Tom FENNELLY
 created  JENKINS-24175


Create some functional tests to test the  tag to  translation















Issue Type:


Task



Assignee:


Tom FENNELLY



Components:


core



Created:


08/Aug/14 2:32 PM



Project:


Jenkins



Labels:


user-experience




Priority:


Major



Reporter:


Tom FENNELLY

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24170) Provide icon spec/class alternative to the getIconFileName() method on Action/ManagementLink















































dogfood
 commented on  JENKINS-24170


Provide icon spec/class alternative to the getIconFileName() method on Action/ManagementLink















Integrated in  jenkins_main_trunk #3591
 Use IconSpec.getIconClassName() instead of Action.getIconFileName() where possible JENKINS-24170 (Revision 38ff4f08be317ff28222d7d8e1eaa66ea534c3ff)

 Result = SUCCESS
tom.fennelly : 38ff4f08be317ff28222d7d8e1eaa66ea534c3ff
Files : 

	core/src/main/resources/hudson/model/AbstractProject/main.jelly
	core/src/main/resources/lib/layout/task.jelly
	core/pom.xml
	core/src/main/resources/lib/hudson/summary.jelly
	core/src/main/resources/lib/hudson/actions.jelly
	core/src/main/resources/jenkins/model/Jenkins/manage.jelly





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [master-slave] (JENKINS-5413) SCM polling getting hung















































Daniel Beck
 commented on  JENKINS-5413


SCM polling getting hung















Possible solution to issue with SCMTrigger status page described by Nathaniel Irons proposed: https://github.com/jenkinsci/jenkins/pull/1355



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [delivery-pipeline] (JENKINS-23716) View not correctly displaying branches of the workflow

2014-08-08 Thread jeff_fi...@symantec.com (JIRA)















































Jeff Fiser
 commented on  JENKINS-23716


View not correctly displaying branches of the workflow















Hi Patrik,

I seems that rendering them in stacked columns (top to bottom) would look the best.

Thanks,
Jeff



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [build-failure-analyzer] (JENKINS-24171) BFA is blindly adding text to gzipped log















































Daniel Beck
 commented on  JENKINS-24171


BFA is blindly adding text to gzipped log















Could you explain how you ended up with a gzipped build log? Or in general, how this issue can be reproduced?



From a superficial BFA source code reading, it seems to do everything right.

While the log file could be gzipped, it's safe to assume TaskListener.getLogger() (a PrintStream) is handling this transparently.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [dashboard-view] (JENKINS-22522) Class def not found in Test Statistics Grid (java.lang.ClassNotFoundException: hudson.maven.reporters.SurefireAggregatedReport)

2014-08-08 Thread psama...@yahoo.co.uk (JIRA)















































Paulo Magalhães
 commented on  JENKINS-22522


Class def not found in Test Statistics Grid (java.lang.ClassNotFoundException: hudson.maven.reporters.SurefireAggregatedReport)















I have the same problem here. Is there any solution or known workaround for this problem?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24170) Provide icon spec/class alternative to the getIconFileName() method on Action/ManagementLink
















































Tom FENNELLY
 resolved  JENKINS-24170 as Fixed


Provide icon spec/class alternative to the getIconFileName() method on Action/ManagementLink
















Merged in 38ff4f0





Change By:


Tom FENNELLY
(08/Aug/14 1:54 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24170) Provide icon spec/class alternative to the getIconFileName() method on Action/ManagementLink















































SCM/JIRA link daemon
 commented on  JENKINS-24170


Provide icon spec/class alternative to the getIconFileName() method on Action/ManagementLink















Code changed in jenkins
User: tfennelly
Path:
 core/pom.xml
 core/src/main/resources/hudson/model/AbstractProject/main.jelly
 core/src/main/resources/jenkins/model/Jenkins/manage.jelly
 core/src/main/resources/lib/hudson/actions.jelly
 core/src/main/resources/lib/hudson/summary.jelly
 core/src/main/resources/lib/layout/task.jelly
http://jenkins-ci.org/commit/jenkins/38ff4f08be317ff28222d7d8e1eaa66ea534c3ff
Log:
  Use IconSpec.getIconClassName() instead of Action.getIconFileName() where possible JENKINS-24170





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [mail] (JENKINS-279) Modular email notification

2014-08-08 Thread gentoo.inte...@gmail.com (JIRA)
















































Kanstantsin Shautsou
 resolved  JENKINS-279 as Fixed


Modular email notification
















email-ext plugin is solving this issue.





Change By:


Kanstantsin Shautsou
(08/Aug/14 1:41 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec















































SCM/JIRA link daemon
 commented on  JENKINS-22009


Git Polling Keeps Detecting Changes When Variables in refspec















Code changed in jenkins
User: Mark Waite
Path:
 src/main/java/hudson/plugins/git/util/GitUtils.java
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/1dc2db5cb67c8c1c8dbd004f1c7966d3e86d4d5c
Log:
  Merge pull request #250 from jakobk/2.2.x

fix JENKINS-22009 on 2.2.x branch


Compare: https://github.com/jenkinsci/git-plugin/compare/63b05764bd0e...1dc2db5cb67c




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec















































SCM/JIRA link daemon
 commented on  JENKINS-22009


Git Polling Keeps Detecting Changes When Variables in refspec















Code changed in jenkins
User: Mark Waite
Path:
 src/main/java/hudson/plugins/git/util/GitUtils.java
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/03995f242e9a3ffe6fdbd2a7b00cdb20d5b3f967
Log:
  Merge pull request #245 from jakobk/jenkins_22009

JENKINS-22009 Git Polling Keeps Detecting Changes When Variables in refspec


Compare: https://github.com/jenkinsci/git-plugin/compare/647f3f09814c...03995f242e9a




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec















































SCM/JIRA link daemon
 commented on  JENKINS-22009


Git Polling Keeps Detecting Changes When Variables in refspec















Code changed in jenkins
User: Jakob Korherr
Path:
 src/main/java/hudson/plugins/git/util/GitUtils.java
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/897426d8004155c25f272189052b695c3aaadceb
Log:
  JENKINS-22009 Git Polling Keeps Detecting Changes When Variables in refspec (setup correct environment for polling + test case)





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec















































SCM/JIRA link daemon
 commented on  JENKINS-22009


Git Polling Keeps Detecting Changes When Variables in refspec















Code changed in jenkins
User: Jakob Korherr
Path:
 src/main/java/hudson/plugins/git/util/GitUtils.java
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/027cc051aa87ae0b9b006234a8d53974de42568b
Log:
  JENKINS-22009 Git Polling Keeps Detecting Changes When Variables in refspec (setup correct environment for polling + test case)





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec















































SCM/JIRA link daemon
 commented on  JENKINS-22009


Git Polling Keeps Detecting Changes When Variables in refspec















Code changed in jenkins
User: Jakob Korherr
Path:
 src/main/java/hudson/plugins/git/util/GitUtils.java
http://jenkins-ci.org/commit/git-plugin/f6fd156b4981bcffbb6aa64ee321b41d0db51370
Log:
  JENKINS-22009 Git Polling Keeps Detecting Changes When Variables in refspec (apply API changes in 2.2.x)





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout















































Shannon Kerr
 commented on  JENKINS-23146


StringIndexOutOfBoundsException on subversion checkout















Thanks Daniel Beck.  So who do we have to buy off to get the fix back-ported to 2.4.x?  If 2.5 isn't coming out for a while, someone needs to fix such a significant bug in the 2.4.x line.

Also, would setting the "Retry Count" option to 2 or 3 (or higher) do any good in this instance?  Here is the help text from that option for those that are unfamiliar "If a build fails to checkout from the repository, Jenkins will retry the specified number of times before giving up."



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [maven] (JENKINS-19335) Sudden influx of permgen space issues

2014-08-08 Thread gennady.kup...@gmail.com (JIRA)















































Gennady Kupava
 commented on  JENKINS-19335


Sudden influx of permgen space issues















We have something like this on 554.2. After long uptime (week or so), suddenly we got such error. After the day and logs filled with this, jenkins just hung.

Aug 7, 2014 12:24:46 AM hudson.model.Run execute
INFO: latency #193 main build action completed: SUCCESS
Aug 7, 2014 3:27:25 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Fingerprint cleanup
Aug 7, 2014 3:27:25 AM hudson.model.FingerprintCleanupThread execute
INFO: Cleaned up 0 records
Aug 7, 2014 3:27:25 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Fingerprint cleanup. 6 ms
Exception in thread "http-bio-1050-exec-92" java.lang.OutOfMemoryError: PermGen space
at java.lang.Throwable.getStackTraceElement(Native Method)
at java.lang.Throwable.getOurStackTrace(Throwable.java:591)
at java.lang.Throwable.printStackTrace(Throwable.java:510)
at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:72)
at org.apache.juli.FileHandler.publish(FileHandler.java:200)
at java.util.logging.Logger.log(Logger.java:458)
at java.util.logging.Logger.doLog(Logger.java:480)
at java.util.logging.Logger.logp(Logger.java:680)
at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:185)
at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:151)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Exception in thread "http-bio-1050-exec-96" java.lang.OutOfMemoryError: PermGen space
at java.lang.Throwable.getStackTraceElement(Native Method)
at java.lang.Throwable.getOurStackTrace(Throwable.java:591)
at java.lang.Throwable.printStackTraceAsCause(Throwable.java:529)
at java.lang.Throwable.printStackTrace(Throwable.java:516)
at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:72)
at org.apache.juli.FileHandler.publish(FileHandler.java:200)
at java.util.logging.Logger.log(Logger.java:458)
at java.util.logging.Logger.doLog(Logger.java:480)
at java.util.logging.Logger.logp(Logger.java:680)
at org.apache.juli.logging.DirectJDKLog.log(DirectJDKLog.java:185)
at org.apache.juli.logging.DirectJDKLog.error(DirectJDKLog.java:151)
at org.apache.catalina.core.ApplicationContext.log(ApplicationContext.java:742)
at org.apache.catalina.core.ApplicationContextFacade.log(ApplicationContextFacade.java:325)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:762)

at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
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:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.servi

[JIRA] [delivery-pipeline] (JENKINS-24173) Show Views TabBar in pipeline default view















































Patrik Boström
 updated  JENKINS-24173


Show Views TabBar in pipeline default view
















Change By:


Patrik Boström
(08/Aug/14 11:54 AM)




Issue Type:


Bug
Improvement





Priority:


Major
Minor



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [docker-build-step] (JENKINS-24174) "Waiting for port" waits forever when Jenkins machine is not docker host

2014-08-08 Thread j...@hup.de (JIRA)















































Julian Kassat
 created  JENKINS-24174


"Waiting for port" waits forever when Jenkins machine is not docker host















Issue Type:


Bug



Affects Versions:


current



Assignee:


vjuranek



Components:


docker-build-step



Created:


08/Aug/14 11:49 AM



Description:


When Docker is running on a remote machine controlled via REST API, docker-build-step waits forever for specified ports to open, because it tries to connect though Docker's internal NAT network.

[Docker] INFO: started container id 5d575f0c43d9
[Docker] INFO: Waiting for port 8080 on 172.17.0.11 (conatiner ID 5d575f0c43d9)

172.17.0.11 is the container's IPv4 address, which is only connectable from the Docker host. I'd rather expect the plugin to wait for the open port on the Docker host itself (or at a configurable location).

In this stage, the job can't be cancelled with the stop button and is blocking a build slot until timeout (maybe this timeout value should also be configurable?).




Environment:


Linux amd64 + OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1)

Jenkins 1.565.1

docker-build-step 1.7



Docker 1.01 API 1.12 on remote host




Project:


Jenkins



Priority:


Major



Reporter:


Julian Kassat

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [delivery-pipeline] (JENKINS-24173) Show Views TabBar in pipeline default view















































Patrik Boström
 created  JENKINS-24173


Show Views TabBar in pipeline default view















Issue Type:


Bug



Assignee:


Patrik Boström



Components:


delivery-pipeline



Created:


08/Aug/14 11:39 AM



Description:


Show views tabbar in default view (not fullscreen view)
Makes the navigation easier.

http://stackoverflow.com/questions/9217679/why-arent-the-view-tabs-showing-when-my-view-is-the-selected-view




Project:


Jenkins



Priority:


Major



Reporter:


Patrik Boström

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [core] (JENKINS-24119) Plugin icons on "Manage Jenkins" page are broken















































dogfood
 commented on  JENKINS-24119


Plugin icons on "Manage Jenkins" page are broken















Integrated in  jenkins_main_trunk #3590
 [FIXED JENKINS-24119] Fixed icon src path generation (Revision 2f3e1fff214b2d9fd4d87622ed2b5be4cdabb5cb)

 Result = SUCCESS
tom.fennelly : 2f3e1fff214b2d9fd4d87622ed2b5be4cdabb5cb
Files : 

	core/src/main/resources/lib/hudson/summary.jelly





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







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

[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout