date:20130606















































cforce
 commented on  JENKINS-18211


password are commited in plain text















I added a new Security Relam in jenkins admin and in the scm committed config.xml i see the plain passsword i enterered

securityRealm class="hudson.plugins.redmine.RedmineSecurityRealm" plugin="redmine@0.13"
...
dbPasswordMY PLAIN TESXT PASSWORD/dbPassword

...

On other password fields i checked the chars sre hashed.

Maybe its the error of the redmine 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/groups/opt_out.

[JIRA] [robot-plugin] (JENKINS-18230) Parsing output xml: Failed!

2013-06-06 Thread qit...@gmail.com (JIRA)















































tao qi
 created  JENKINS-18230


Parsing output xml:  Failed!  















Issue Type:


Bug



Assignee:


jpiironen



Components:


robot-plugin



Created:


06/Jun/13 7:19 AM



Description:


Robot plug 1.2.1 is ok.
When I update it to 1.2.2, after running test, it was wrong in parsing output.xml
Same bug in 1.2.3
The message is :

-Parsing output xml:
Failed!
hudson.util.IOException2: remote file operation failed: D:\JK\workspace\cfs_counter_reg\Result at hudson.remoting.Channel@132fd12:CNSH021691
	at hudson.FilePath.act(FilePath.java:838)
	at hudson.FilePath.act(FilePath.java:824)
	at hudson.plugins.robot.RobotParser.parse(RobotParser.java:45)
	at hudson.plugins.robot.RobotPublisher.parse(RobotPublisher.java:235)
	at hudson.plugins.robot.RobotPublisher.perform(RobotPublisher.java:257)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
	at hudson.model.Run.execute(Run.java:1527)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)
Caused by: hudson.remoting.ProxyException: java.io.IOException: Parsing of output xml failed!
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:90)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:50)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2236)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1$1.run(Engine.java:60)
	at java.lang.Thread.run(Unknown Source)
Caused by: hudson.remoting.ProxyException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '"' (code 34) excepted space, or '' or "/"
 at row,col {unknown-source}: 28,55
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648)
	at com.ctc.wstx.sr.BasicStreamReader.handleNsAttrs(BasicStreamReader.java:2965)
	at com.ctc.wstx.sr.BasicStreamReader.handleStartElem(BasicStreamReader.java:2936)
	at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2848)
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.processTest(RobotParser.java:190)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.processSuite(RobotParser.java:158)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.parseResult(RobotParser.java:114)
	at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:88)
	... 12 more
Build step 'Publish Robot Framework test results' changed build result to FAILURE
Finished: FAILURE




Environment:


Jenkins: 1.480.1

Robot Plug:1.2.2 or 1.2.3




Project:


Jenkins



Labels:


robot




Priority:


Major



Reporter:


tao qi

[JIRA] [redmine] (JENKINS-18211) password are commited in plain text















































cforce
 updated  JENKINS-18211


password are commited in plain text
















Change By:


cforce
(06/Jun/13 7:22 AM)




Component/s:


redmine



























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/groups/opt_out.

[JIRA] [robot-plugin] (JENKINS-18230) Parsing output xml: Failed!

2013-06-06 Thread qit...@gmail.com (JIRA)















































Jacky qi
 updated  JENKINS-18230


Parsing output xml:  Failed!  
















add output.xml





Change By:


Jacky qi
(06/Jun/13 7:47 AM)




Attachment:


output.xml



























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/groups/opt_out.

[JIRA] [redmine] (JENKINS-18211) password are commited in plain text

2013-06-06 Thread fcamb...@java.net (JIRA)















































Frédéric Camblor
 commented on  JENKINS-18211


password are commited in plain text















Yep, this is related to redmine plugin

It is not in the scope of the scm-sync-config plugin to alter the sync'ed files, particularly for the jenkins plugins galaxy 



























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/groups/opt_out.

[JIRA] [redmine] (JENKINS-18211) password are commited in plain text

2013-06-06 Thread fcamb...@java.net (JIRA)
















































Frédéric Camblor
 closed  JENKINS-18211 as Not A Defect


password are commited in plain text
















not related to scm-sync-config plugin.

Please create a new issue for the redmine component (thus, component's lead will be automatically notified)





Change By:


Frédéric Camblor
(06/Jun/13 8:14 AM)




Status:


Open
Closed





Resolution:


NotADefect



























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/groups/opt_out.

[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts

2013-06-06 Thread aswini.rajaseka...@gmail.com (JIRA)















































Aswini Rajasekaran
 commented on  JENKINS-7641


Slaves hang when archiving artifacts















Hi, I just jenkins version 1.514 and this issues happens for me for the past 1 week. This is a big blocker for me in executing builds in slave.
I have installed jenkins on linux box and all the slaves are also remote linux boxes connected via SSH.
Can anyone advise how to resolve this at the earliest? Thanks a mil for your help in advance.

Regards,
Aswini



























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/groups/opt_out.

[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException

2013-06-06 Thread y...@schli.ch (JIRA)













































 
Marc Günther
 edited a comment on  JENKINS-14362


100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
















Guy Kisel: could you please wrap your stacktrace inside a {quote}, so this ticket remains readable?
EDIT: Thanks a lot 



























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/groups/opt_out.

[JIRA] [redmine] (JENKINS-18231) bad user guide















































cforce
 created  JENKINS-18231


bad user guide















Issue Type:


Improvement



Assignee:


gaooh



Components:


redmine



Created:


06/Jun/13 8:59 AM



Description:


The redmine plugin offer some features which are not documentedt and you can't guess. 
E.g How does the aggregate redmine ticket metrics feature works?
What does the target version settings do. Is it possible to autaomcatically set the target from jenkins variable to a already existing version in redmine for  issues that has been sucessfully "build"? Can i use maven project version, so i only have to use same version numbers in redmine and maven artefacts? Does its create new version in redmine automcatically id they don't exits?

Why do i free text field for redmine.version property for site configuration. What shall i enter here and why..





Project:


Jenkins



Priority:


Major



Reporter:


cforce

























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/groups/opt_out.

[JIRA] [redmine] (JENKINS-18231) bad user guide















































cforce
 updated  JENKINS-18231


bad user guide
















Change By:


cforce
(06/Jun/13 9:06 AM)




Description:


Theredminepluginoffersomefeatureswhicharenotdocumentedtandyoucantguess.
*RedmineMetrics*
E.gHowdoestheaggregateredmineticketmetricsfeatureworks?Whatdoesthetargetversionsettingsdo.Isitpossibletoautaomcaticallysetthetargetfromjenkinsvariabletoaalreadyexistingversioninredmineforissuesthathasbeensucessfullybuild?Caniusemavenprojectversion,soionlyhavetousesameversionnumbersinredmineandmavenartefacts?Doesitscreatenewversioninredmineautomcaticallyidtheydontexits?
*redminesiteconfig*
Whydoifreetextfieldforredmine.versionpropertyforsiteconfiguration.Whatshallienterhereandwhy..
*redmineuserauth*Arethereanyrequuirementsinredmineuserpasswordstroage(hashed,encrypted).Doesitonlyauthenticateusers?Caniselectgroupsfromredmineifiusejenkinsprojectbasesecurity?



























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/groups/opt_out.

[JIRA] [redmine] (JENKINS-18211) password are commited in plain text















































cforce
 updated  JENKINS-18211


password are commited in plain text
















Change By:


cforce
(06/Jun/13 9:12 AM)




Component/s:


scm-sync-configuration



























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/groups/opt_out.

[JIRA] [redmine] (JENKINS-18211) password are commited in plain text















































cforce
 reopened  JENKINS-18211


password are commited in plain text
















Change By:


cforce
(06/Jun/13 9:11 AM)




Resolution:


NotADefect





Status:


Closed
Reopened





Assignee:


FrédéricCamblor
gaooh



























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/groups/opt_out.

[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts

2013-06-06 Thread aswini.rajaseka...@gmail.com (JIRA)













































 
Aswini Rajasekaran
 edited a comment on  JENKINS-7641


Slaves hang when archiving artifacts
















Hi, I use jenkins version 1.514 and this issues happens for me for the past 1 week. This is a big blocker for me in executing builds in slave.
I have installed jenkins on linux box and all the slaves are also remote linux boxes connected via SSH.
Can anyone advise how to resolve this at the earliest? Thanks a mil for your help in advance.

Regards,
Aswini



























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/groups/opt_out.

[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)

2013-06-06 Thread s...@kgu-consulting.de (JIRA)















































Stefan Hirche
 commented on  JENKINS-14026


git plugin doesnt support branch name contains slash (/)















Hi,
I just found the problem with the "remote workaround". I forgot that I renamed my remote. Using the correct remote name works.



























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/groups/opt_out.

[JIRA] [git] (JENKINS-18232) How do I enable slave logging?

2013-06-06 Thread mail+jenk...@nh2.me (JIRA)















































Niklas Hambuechen
 created  JENKINS-18232


How do I enable slave logging?















Issue Type:


Task



Assignee:


Nicolas De Loof



Components:


git



Created:


06/Jun/13 10:39 AM



Description:


I need to see the output of this line:

https://github.com/kpfleming/jenkins-git-plugin/blob/3d9a73d26b129249c51fccfca6060280197b25eb/src/main/java/hudson/plugins/git/util/GitUtils.java#L123

on my slave server since the git plugin runs on 100% somewhere around that code.

What do I have to do in order to see this output?

Where can I set the log level?

Where will I find the output?

I know a bugtracker isn't the best place to ask, but I don't know of another place.

Thank you.




Project:


Jenkins



Priority:


Trivial



Reporter:


Niklas Hambuechen

























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/groups/opt_out.

[JIRA] [artifactdeployer] (JENKINS-18233) Artifacts archiver throws IOException2 ENOENT for files with special file names

2013-06-06 Thread ste...@datenfreihafen.org (JIRA)















































Stefan Schmidt
 created  JENKINS-18233


Artifacts archiver throws IOException2 ENOENT for files with special file names















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


artifactdeployer



Created:


06/Jun/13 10:48 AM



Description:


When trying to archive some files I get the following exception thrown:

00:57:00.704 ERROR: Failed to archive artifacts: git_stats/
00:57:00.927 hudson.util.IOException2: hudson.os.PosixException: /srv/build/workspace/nightly_efl_gcc_x86_64/git_stats/authors/andr��_ribes ENOENT
00:57:01.003 	at hudson.FilePath.copyRecursiveTo(FilePath.java:1942)
00:57:01.045 	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:137)
00:57:01.045 	at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)
00:57:02.258 	at org.jenkins_ci.plugins.run_condition.BuildStepRunner$DontRun.conditionalRun(BuildStepRunner.java:264)
00:57:02.259 	at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)
00:57:02.260 	at org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:88)
00:57:02.260 	at org.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:96)
00:57:02.260 	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
00:57:02.260 	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802)
00:57:02.260 	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774)
00:57:02.260 	at hudson.model.Build$BuildExecution.post2(Build.java:183)
00:57:02.260 	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724)
00:57:02.260 	at hudson.model.Run.execute(Run.java:1600)
00:57:02.260 	at hudson.plugins.project_inheritance.projects.InheritanceBuild.run(InheritanceBuild.java:61)
00:57:02.260 	at hudson.model.ResourceController.execute(ResourceController.java:88)
00:57:02.260 	at hudson.model.Executor.run(Executor.java:237)
00:57:02.260 Caused by: java.util.concurrent.ExecutionException: hudson.os.PosixException: /srv/build/workspace/nightly_efl_gcc_x86_64/git_stats/authors/andr��_ribes ENOENT
00:57:02.260 	at hudson.remoting.Channel$4.adapt(Channel.java:705)
00:57:02.260 	at hudson.remoting.Channel$4.adapt(Channel.java:700)
00:57:02.260 	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
00:57:02.260 	at hudson.FilePath.copyRecursiveTo(FilePath.java:1940)
00:57:02.260 	... 15 more
00:57:02.260 Caused by: hudson.os.PosixException: /srv/build/workspace/nightly_efl_gcc_x86_64/git_stats/authors/andr��_ribes ENOENT
00:57:02.260 	at hudson.os.PosixAPI$1.error(PosixAPI.java:43)
00:57:02.260 	at org.jruby.ext.posix.LinuxPOSIX.stat(LinuxPOSIX.java:89)
00:57:02.260 	at hudson.util.IOUtils.mode(IOUtils.java:125)
00:57:02.260 	at hudson.util.io.TarArchiver.visit(TarArchiver.java:102)
00:57:02.260 	at hudson.util.DirScanner$Glob.scan(DirScanner.java:133)
00:57:02.260 	at hudson.FilePath.writeToTar(FilePath.java:1978)
00:57:02.260 	at hudson.FilePath.access$1000(FilePath.java:168)
00:57:02.260 	at hudson.FilePath$36.invoke(FilePath.java:1919)
00:57:02.260 	at hudson.FilePath$36.invoke(FilePath.java:1915)
00:57:02.260 	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387)
00:57:02.260 	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
00:57:02.260 	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
00:57:02.260 	at hudson.remoting.Request$2.run(Request.java:326)
00:57:02.260 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
00:57:02.260 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
00:57:02.260 	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
00:57:02.260 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
00:57:02.260 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
00:57:02.260 	at java.lang.Thread.run(Thread.java:722)
00:57:02.260 Build step 'Flexible publish' changed build result to FAILURE

The filename on the

[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion

2013-06-06 Thread henri.go...@gmail.com (JIRA)
















































Henri Gomez
 assigned  JENKINS-15156 to Jesse Glick



Builds disappear from build history after completion
















Fix assignee 





Change By:


Henri Gomez
(06/Jun/13 11:03 AM)




Assignee:


VoiculescuBogdanAlexandru
JesseGlick



























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/groups/opt_out.

[JIRA] [envinject] (JENKINS-18234) environment var not set on job process, and not propagated to forked sub-process

2013-06-06 Thread arnaud.nauwynck-...@lyxor.com (JIRA)















































Arnaud Nauwynck
 created  JENKINS-18234


environment var not set on job process, and not propagated to forked sub-process















Issue Type:


Bug



Affects Versions:


current



Assignee:


Gregory Boissinot



Components:


envinject



Created:


06/Jun/13 12:39 PM



Description:


the EnvInject plugin does not really set the "environment variables" at the OS level, using native POSIX call "putenv()". 
It is only available in some jenkins sub-tasks when calling appropriate jenkins API to exec tasks... but not when calling plain old java code "System.exec()" within a Mojo so most Mojo don't work (my problem was when using maven-dotnet-plugin, that forks to execute "Msbuild.exe")

When doing few search over google to set an environment variable in java, I found a piece of code that might be "portable enough", using JNA native calls to standards dlls (msvcrt on Windows / libc on Linux, which solve 100% of my needs)

It simply exposes a method "putenv()" to be called as this:
SetEnvUtil.putenv("testvar", "123", 1); 

So my request is to add such calls within the EnvInject plugin, but I don't know how to patch exactly the EnvInject jenkins plugin 


It depends on the JNA jar, for example using the maven dependency

dependency
	  groupIdnet.java.dev.jna/groupId
	  artifactIdjna/artifactId
	  version3.4.0/version
/dependency

Here is the utility class 

import com.sun.jna.Library;
import com.sun.jna.Native;

public class SetEnvUtil {

// Inside the Environment class...
public interface WinLibC extends Library Unknown macro: {
public String getenv(String name);
public int _putenv(String name);
} 

public interface LinuxLibC extends Library Unknown macro: {
public String getenv(String name);
public int setenv(String name, String value, int overwrite);
public int unsetenv(String name);
} 

private static Object libc;
static {
String osName = System.getProperty("os.name");
if (osName.equals("Linux")) Unknown macro: {
libc = Native.loadLibrary(c, LinuxLibC.class);
}  else Unknown macro: {
libc = Native.loadLibrary(msvcrt, WinLibC.class);
} 
}

public static String getenv(String name) {
if (libc instanceof LinuxLibC) Unknown macro: {
return ((LinuxLibC) libc).getenv(name);
}  else Unknown macro: {
return ((WinLibC) libc).getenv(name);
} 
}

public static int setenv(String name, String value, int overwrite) {
if (libc instanceof LinuxLibC) Unknown macro: {
return ((LinuxLibC) libc).setenv(name, value, overwrite);
}  else Unknown macro: {
return ((WinLibC) libc)._putenv(name + = + value);
} 
}

public static int unsetenv(String name) {
if (libc instanceof LinuxLibC) Unknown macro: {
return ((LinuxLibC) libc).unsetenv(name);
}  else Unknown macro: {
return ((WinLibC) libc)._putenv(name + =);
} 
}

}



I have done a simple Main for testing purpose, so you can convinced it works simply:

public class SetEnvMain {

public static final String TEST_VAR_NAME  = "TEST_VAR";

public static void main(String[] args) Unknown macro: {
dump(before setenv() ... );

// *** first setenv()  } 

public static void dump(String messagePrefix) Unknown macro: {
String var_native = SetEnvUtil.getenv(TEST_VAR_NAME);
String var_cached = System.getenv(TEST_VAR_NAME); // FALSE... cached by java!
System.out.println(messagePrefix +   + TEST_VAR_NAME + } 

}




Project:


Jenkins



Priority:


Major



Reporter:


Arnaud Nauwynck

[JIRA] [envinject] (JENKINS-18234) environment var not set on job process, and not propagated to forked sub-process

2013-06-06 Thread arnaud.nauwynck-...@lyxor.com (JIRA)















































Arnaud Nauwynck
 updated  JENKINS-18234


environment var not set on job process, and not propagated to forked sub-process
















Change By:


Arnaud Nauwynck
(06/Jun/13 12:40 PM)




Description:


theEnvInjectplugindoesnotreallysettheenvironmentvariablesattheOSlevel,usingnativePOSIXcallputenv().Itisonlyavailableinsomejenkinssub-taskswhencallingappropriatejenkinsAPItoexectasks...butnotwhencallingplainoldjavacodeSystem.exec()withinaMojosomostMojodontwork(myproblemwaswhenusingmaven-dotnet-plugin,thatforkstoexecuteMsbuild.exe)Whendoingfewsearchovergoogletosetanenvironmentvariableinjava,Ifoundapieceofcodethatmightbeportableenough,usingJNAnativecallstostandardsdlls(msvcrtonWindows/libconLinux,whichsolve100%ofmyneeds)Itsimplyexposesamethodputenv()tobecalledasthis:{quote}SetEnvUtil.putenv(testvar,123,1);{quote}SomyrequestistoaddsuchcallswithintheEnvInjectplugin,butIdontknowhowtopatchexactlytheEnvInjectjenkinspluginItdependsontheJNAjar,forexampleusingthemavendependency{
quote
{monospaced
}
}
dependency	groupIdnet.java.dev.jna/groupId	artifactIdjna/artifactId	version3.4.0/version/dependency{
quote
{monospaced
}
}
Hereistheutilityclass{
quote
{monospaced
}
}
importcom.sun.jna.Library;importcom.sun.jna.Native;publicclassSetEnvUtil{//InsidetheEnvironmentclass...publicinterfaceWinLibCextendsLibrary{publicStringgetenv(Stringname);publicint_putenv(Stringname);}publicinterfaceLinuxLibCextendsLibrary{publicStringgetenv(Stringname);publicintsetenv(Stringname,Stringvalue,intoverwrite);publicintunsetenv(Stringname);}privatestaticObjectlibc;static{StringosName=System.getProperty(os.name);if(osName.equals(Linux)){libc=Native.loadLibrary(c,LinuxLibC.class);}else{libc=Native.loadLibrary(msvcrt,WinLibC.class);}}publicstaticStringgetenv(Stringname){if(libcinstanceofLinuxLibC){return((LinuxLibC)libc).getenv(name);}else{return((WinLibC)libc).getenv(name);}}publicstaticintsetenv(Stringname,Stringvalue,intoverwrite){if(libcinstanceofLinuxLibC){return((LinuxLibC)libc).setenv(name,value,overwrite);}else{return((WinLibC)libc)._putenv(name+=+value);}}publicstaticintunsetenv(Stringname){if(libcinstanceofLinuxLibC){return((LinuxLibC)libc).unsetenv(name);}else{return((WinLibC)libc)._putenv(name+=);}}}{
quote
{monospaced
}
}
IhavedoneasimpleMainfortestingpurpose,soyoucanconvinceditworkssimply:{
quote
{monospaced
}
}
publicclassSetEnvMain{publicstaticfinalStringTEST_VAR_NAME=TEST_VAR;publicstaticvoidmain(String[]args){dump(beforesetenv()...);//***firstsetenv():addnewenvvarSetEnvUtil.setenv(TEST_VAR_NAME,123,1);dump(aftersetenv(\+TEST_VAR_NAME+,\123\)...);//***secondcallsetenv():overrideexistingvarSetEnvUtil.setenv(TEST_VAR_NAME,456,1);dump(aftersetenv(\+TEST_VAR_NAME+,\456\)...);}publicstaticvoiddump(StringmessagePrefix){Stringvar_native=SetEnvUtil.getenv(TEST_VAR_NAME);Stringvar_cached=System.getenv(TEST_VAR_NAME);//FALSE...cachedbyjava!System.out.println(messagePrefix++TEST_VAR_NAME+:+var_native+,(cached):+var_cached);}}{
quote
{monospaced
}
}




























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/groups/opt_out.

[JIRA] [cvs] (JENKINS-16314) cvs plugin removes sticky branch tag

2013-06-06 Thread rv.s...@hotmail.com (JIRA)















































Ravi Soni
 commented on  JENKINS-16314


cvs plugin removes sticky branch tag















Hi, In which build we will get this Fix. we are using 1.509.1 LTS this does not have this fix available. we urgently need this fix. 

Thanks,



























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/groups/opt_out.

[JIRA] [cvs] (JENKINS-16314) cvs plugin removes sticky branch tag

2013-06-06 Thread michael.m.cla...@gmail.com (JIRA)















































Michael Clarke
 commented on  JENKINS-16314


cvs plugin removes sticky branch tag















This fix has been released in version 2.9 of the CVS plugin. Releases of the CVS plugin are independent of releases of the Jenkins core: you need to go into your Jenkins update centre and check for plugin updates.



























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/groups/opt_out.

[JIRA] [mercurial] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)















































Igor Kostenko
 commented on  JENKINS-15829


hg share always recreating working copy on slave (on master its working fine)















Sorry for long pause, I've changed a job and only now responsible for jenkins again.

Igor: could you, on your slave, create a .hg/hgrc file in the /app/agora/hudsonslave/hgcache/D38534FF4534AE3232A1AB292D5BA54825AE752B-AgoraLight that contains the following information:
It helped: 

[QAF_Test2] $ hg pull --rev default /home/jenkins_local/hgcache/82556880B412DFAE704E615CE9ABB4DA5A38C2EF-doc_source
[QAF_Test2] $ hg update --clean --rev default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved




























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/groups/opt_out.

[JIRA] [build-flow] (JENKINS-16254) Unable to use Build Name Setter Plugin

2013-06-06 Thread msz...@wp.pl (JIRA)















































Marcin Zajączkowski
 commented on  JENKINS-16254


Unable to use Build Name Setter Plugin















Other plugins configurable in a "Build Environment" section are also affected.



























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/groups/opt_out.

[JIRA] [core] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)

2013-06-06 Thread w...@wael.org (JIRA)















































Wael Darwich
 reopened  JENKINS-16474


Slow/hung web UI in 1.483+ (stuck in parseURI)
















Change By:


Wael Darwich
(06/Jun/13 1:54 PM)




Resolution:


Fixed





Status:


Resolved
Reopened



























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/groups/opt_out.

[JIRA] [build-flow] (JENKINS-16254) Unable to use Build Name Setter Plugin

2013-06-06 Thread jurgen.kel...@nuance.com (JIRA)















































Jurgen Keller
 commented on  JENKINS-16254


Unable to use Build Name Setter Plugin















As a workaround you can use

build.setDisplayName 'XYZ'

in the build flow DSL.



























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/groups/opt_out.

[JIRA] [core] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
















































Jesse Glick
 resolved  JENKINS-16474 as Fixed


Slow/hung web UI in 1.483+ (stuck in parseURI)
















@wael your issue may not have anything to do with this fix. Please use a separate ticket (using JIRA links as needed) unless you can confirm at the code level that this fix did not do what it claimed to do.

Also please try the new command-line tuning parameters introduced by the fix (--help for details), and if a thread dump confirms that many threads are still stuck in parseURI, attach that thread dump since it will now contain more information.





Change By:


Jesse Glick
(06/Jun/13 2:04 PM)




Status:


Reopened
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/groups/opt_out.

[JIRA] [grails] (JENKINS-18235) need to add GRAILS_HOME/bin to PATH

2013-06-06 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-18235


need to add GRAILS_HOME/bin to PATH















Issue Type:


Bug



Assignee:


jeffg2one



Components:


grails



Created:


06/Jun/13 2:07 PM



Description:


According to grails installation doc http://grails.org/doc/2.2.1/guide/gettingStarted.html

GRAILS_HOME/bin must be added to PATH
even plugin run grails with full path, some grails tasks fork another grails process (grails test-app for sample) that then require PATH to be set.




Project:


Jenkins



Priority:


Major



Reporter:


Nicolas De Loof

























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/groups/opt_out.

[JIRA] [changes-since-last-success] (JENKINS-16648) changes-since-last-success plugin doesn't work

2013-06-06 Thread ad...@moparisthebest.com (JIRA)
















































Travis Burtrum
 resolved  JENKINS-16648 as Fixed


changes-since-last-success plugin doesnt work
















I'm not sure exactly which version fixed this plugin, but it is definitly working as of Jenkins ver. 1.517





Change By:


Travis Burtrum
(06/Jun/13 2:09 PM)




Status:


Open
Resolved





Fix Version/s:


current





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/groups/opt_out.

[JIRA] [core] (JENKINS-18236) Computer.getUrl wrong when spaces are present















































Jesse Glick
 created  JENKINS-18236


Computer.getUrl wrong when spaces are present















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


core



Created:


06/Jun/13 2:09 PM



Description:


Recording https://github.com/jenkinsci/jenkins/commit/92d96525 (in 1.510) retroactively.




Project:


Jenkins



Labels:


url
lts-candidate




Priority:


Minor



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/groups/opt_out.

[JIRA] [core] (JENKINS-18236) Computer.getUrl wrong when spaces are present

2013-06-06 Thread scm_issue_l...@java.net (JIRA)
















































SCM/JIRA link daemon
 resolved  JENKINS-18236 as Fixed


Computer.getUrl wrong when spaces are present
















Change By:


SCM/JIRA link daemon
(06/Jun/13 2:11 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/groups/opt_out.

[JIRA] [multiple-scms] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.















































Igor Kostenko
 updated  JENKINS-18237


Multiple hg repos vs matrix job - the same revision used for all repositories.
















Change By:


Igor Kostenko
(06/Jun/13 2:23 PM)




Description:


WhenImusingMultipleSCMplugininMatrixjob,configurationsbuildarefailingbecauseofwrongrevisioninhgupdate.Toplevelbuild:{code}[common]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/730F3D6CF2984FE6965438CDBB2F241CA1B4F220-common[common]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[common]$hglog--rev.--template{node}[common]$hglog--rev.--template{rev}[common]$hglog--rev76175d754787279d7888132d364e2847c576134c...[project_engine]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/892EE33C3F9037402D2325A82FC02A50F873F87F-project_engine[project_engine]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[project_engine]$hglog--rev.--template{node}[project_engine]$hglog--rev.--template{rev}[project_engine]$hglog--rev53dbe704b92059332f0af3ebe2d50f56aac7f4d9{code}
If
As
youcanseerevisionsforcommonproject_enginearedifferent.Thesamebuildforeachconfigurationgivesanerrorbecauseofthesamerevisionforbothprojects:{code}[common]$hgupdate--rev76175d754787279d7888132d364e2847c576134c739filesupdated,0filesmerged,0filesremoved,0filesunresolved...[project_engine]$hgupdate--rev76175d754787279d7888132d364e2847c576134cabort:unknownrevision76175d754787279d7888132d364e2847c576134c!{code}ImusinghgsharingandcachingandTemplateprojectforSCM-buttheybothworkfinefornon-matrixprojects.



























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/groups/opt_out.

[JIRA] [multiple-scms] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.















































Igor Kostenko
 updated  JENKINS-18237


Multiple hg repos vs matrix job - the same revision used for all repositories.
















Change By:


Igor Kostenko
(06/Jun/13 2:22 PM)




Description:


WhenImusingMultipleSCMplugininMatrixjob,configurationsbuildarefailingbecauseofwrongrevisioninhgupdate.Toplevelbuild:
Mastercachelockreleased.
{code}[common]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/730F3D6CF2984FE6965438CDBB2F241CA1B4F220-common[common]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[common]$hglog--rev.--template{node}[common]$hglog--rev.--template{rev}[common]$hglog--rev76175d754787279d7888132d364e2847c576134c...[project_engine]$hgpull--revdefault/mnt/imports/data2/users/jenkins/hgcache/892EE33C3F9037402D2325A82FC02A50F873F87F-project_engine[project_engine]$hgupdate--clean--revdefault0filesupdated,0filesmerged,0filesremoved,0filesunresolved[project_engine]$hglog--rev.--template{node}[project_engine]$hglog--rev.--template{rev}[project_engine]$hglog--rev53dbe704b92059332f0af3ebe2d50f56aac7f4d9{code}Ifyoucanseerevisionsforcommonproject_enginearedifferent.Thesamebuildforeachconfigurationgivesanerrorbecauseofthesamerevisionforbothprojects:{code}[common]$hgupdate--rev76175d754787279d7888132d364e2847c576134c739filesupdated,0filesmerged,0filesremoved,0filesunresolved...[project_engine]$hgupdate--rev76175d754787279d7888132d364e2847c576134cabort:unknownrevision76175d754787279d7888132d364e2847c576134c!{code}ImusinghgsharingandcachingandTemplateprojectforSCM-buttheybothworkfinefornon-matrixprojects.



























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/groups/opt_out.

[JIRA] [multiple-scms] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.















































Igor Kostenko
 created  JENKINS-18237


Multiple hg repos vs matrix job - the same revision used for all repositories.















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kevin Bell



Components:


multiple-scms



Created:


06/Jun/13 2:22 PM



Description:


When I'm using Multiple SCM plugin in Matrix job, configurations build are failing because of wrong revision in hg update.
Top level build:
Master cache lock released.

[common] $ hg pull --rev default /mnt/imports/data2/users/jenkins/hgcache/730F3D6CF2984FE6965438CDBB2F241CA1B4F220-common
[common] $ hg update --clean --rev default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
[common] $ hg log --rev . --template {node}
[common] $ hg log --rev . --template {rev}
[common] $ hg log --rev 76175d754787279d7888132d364e2847c576134c
...
[project_engine] $ hg pull --rev default /mnt/imports/data2/users/jenkins/hgcache/892EE33C3F9037402D2325A82FC02A50F873F87F-project_engine
[project_engine] $ hg update --clean --rev default
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
[project_engine] $ hg log --rev . --template {node}
[project_engine] $ hg log --rev . --template {rev}
[project_engine] $ hg log --rev 53dbe704b92059332f0af3ebe2d50f56aac7f4d9

If you can see revisions for common  project_engine are different. The same build for each configuration gives an error because of the same revision for both projects:

[common] $ hg update --rev 76175d754787279d7888132d364e2847c576134c
739 files updated, 0 files merged, 0 files removed, 0 files unresolved
...
[project_engine] $ hg update --rev 76175d754787279d7888132d364e2847c576134c
abort: unknown revision '76175d754787279d7888132d364e2847c576134c'!

I'm using hg sharing and caching and Template project for SCM - but they both work fine for non-matrix projects.




Project:


Jenkins



Priority:


Major



Reporter:


Igor Kostenko

























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/groups/opt_out.

[JIRA] [plugin] (JENKINS-4543) Manually uploaded plugins are incorrectly unpacked















































Jesse Glick
 updated  JENKINS-4543


Manually uploaded plugins are incorrectly unpacked
















Change By:


Jesse Glick
(06/Jun/13 2:24 PM)




Labels:


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/groups/opt_out.

[JIRA] [core] (JENKINS-18236) Computer.getUrl wrong when spaces are present

2013-06-06 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-18236


Computer.getUrl wrong when spaces are present















Integrated in  jenkins_main_trunk #2577
 FIXED JENKINS-18236 Noting retroactively. (Revision b086943a3577aa325767b6be643256e8c84ebd07)

 Result = SUCCESS
Jesse Glick : b086943a3577aa325767b6be643256e8c84ebd07
Files : 

	changelog.html





























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/groups/opt_out.

[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.

Details:
---
org.apache.velocity.exception.MethodInvocationException:
 Invocation of method #39;next#39; in  class java.util.AbstractList$Itr
 threw exception class java.util.NoSuchElementException : null
at
 org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)

at
 
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)

at
 
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)

at
 org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)

at
 org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)

at
 org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)

at
 
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)

at
 
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)

at
 
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)

at
 
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)

at
 
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)

at
 
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)

at
 
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)

at
 
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)

at
 
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)

at
 com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)

at
 com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)

at
 
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)

at
 
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)

at 
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)

at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
 
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)

at
 org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f




























style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and 
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0 
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0 
style=background-color:#ff;border:1px solid 
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33 
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
 
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
 alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;




table align=left border=0 cellpadding=0 cellspacing=0 
width=100% style=width:100%;
tr valign=top
td 
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar 
src=https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292; alt= 
height=48 width=48 border=0 align=left style=padding:0;margin: 0 16px 
16px 0; /
div id=email-action style=padding: 0 0 8px 
0;font-size:12px;line-height:18px;
a class=user-hover rel=walterk82 
id=email_walterk82 
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=walterk82; 
style=color:#355564;Walter Kacynski/a
 commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif; 
height=16 width=16 border=0 align=absmiddle alt=Bug a 
style='color:#355564;text-decoration:none;' 
href='https://issues.jenkins-ci.org/browse/JENKINS-5312'JENKINS-5312/a
/div

[JIRA] [nodeofflinenotification] (JENKINS-14805) Global property 'Node Offline Email Notification' does not work















































Walter Kacynski
 updated  JENKINS-14805


Global property Node Offline Email Notification does not work
















Change By:


Walter Kacynski
(06/Jun/13 3:46 PM)




Component/s:


nodeofflinenotification





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/groups/opt_out.

[JIRA] [build-publisher] (JENKINS-18238) Symbolic link is not updated after publishing build

2013-06-06 Thread stefan.rohle...@biosolveit.de (JIRA)

Stefan Rohleder
created JENKINS-18238

Symbolic link is not updated after publishing build

Issue Type:

Bug

Assignee:

vjuranek

Components:

build-publisher

Created:

06/Jun/13 4:08 PM

Description:

On pushing a build onto an external jenkins, symbolic links are not updated.
e.g. the symbolic link jenkins/jobs/jobName/builds/lastSuccessfulBuild is still directing to #1361 even though successful build #1365 is already pushed.
as a result the web interface is showing the wrong build in Last Successful Artifacts (www.MyJenkinsServer/job/jobName/label=labelXY/lastSuccessfulBuild/artifact/)

if i delete the symbolic link and restart jenkins, a link to the latest build is created but is not updated during the further procedure.

lrwxrwxrwx 1 jenkins jenkins 4 4. Jun 17:17 lastStableBuild - 1361

Environment:

internal jenkins:

build-publisher: 1.12

Jenkins ver. 1.510

external jenkins

Jenkins ver. 1.510

Project:

Jenkins

Priority:

Major

Reporter:

Stefan Rohleder

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/groups/opt_out.

[JIRA] [build-publisher] (JENKINS-18238) Symbolic link is not updated after publishing build

2013-06-06 Thread stefan.rohle...@biosolveit.de (JIRA)















































Stefan Rohleder
 updated  JENKINS-18238


Symbolic link is not updated after publishing build
















Change By:


Stefan Rohleder
(06/Jun/13 4:09 PM)




Description:


Onpushingabuildontoanexternaljenkins,symboliclinksarenotupdated.e.g.thesymboliclinkjenkins/jobs/jobName/builds/lastSuccessfulBuildisstilldirectingto#1361eventhoughsuccessfulbuild#1365isalreadypushed.asaresultthewebinterfaceisshowingthewrongbuildinLastSuccessfulArtifacts(www.MyJenkinsServer/job/jobName/label=labelXY/lastSuccessfulBuild/artifact/)ifideletethesymboliclinkandrestartjenkins,alinktothelatestbuildiscreatedbutisnotupdatedduringthefurtherprocedure.lrwxrwxrwx1jenkinsjenkins4
4
6
.Jun
17
12
:
17lastStableBuild
20lastSuccessfulBuild
-1361



























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/groups/opt_out.

[JIRA] [envinject] (JENKINS-16316) global variable not updated
















































Walter Kacynski
 assigned  JENKINS-16316 to Gregory Boissinot



global variable not updated
















What is the status of this issue?  I'm not sure what version of EnvInject that this problem was introduced but it very cumbersome that these values are not dynamic.  I also noticed that when clicking "System Information" for each slave that these global variables are registered in this list and this does not occur if the EnvInject plugin is not installed.





Change By:


Walter Kacynski
(06/Jun/13 4:10 PM)




Assignee:


GregoryBoissinot



























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/groups/opt_out.

[JIRA] [sectioned-view] (JENKINS-13464) Using Other Views filter, I'm getting a stack overflow error after update to Jenkins 1.459

2013-06-06 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-13464


Using Other Views filter, Im getting a stack overflow error after update to Jenkins 1.459















Do you have reproduced this issue recently? If yes, with which versions of Jenkins and of the plugins?



























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/groups/opt_out.

[JIRA] [cucumber-reports] (JENKINS-18239) An Option to mark build as unstable rather than failed

2013-06-06 Thread flor...@java.net (JIRA)
















































floreal
 closed  JENKINS-18239 as Duplicate


An Option to mark build as unstable rather than failed
















I didn't figure out you use github issues; it is a duplicate of this one: https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java/issues/60
Appologies





Change By:


floreal
(06/Jun/13 5:02 PM)




Status:


Open
Closed





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/groups/opt_out.

[JIRA] [parallel-test-executor] (JENKINS-18241) Can't run Parallel Test Execution jobs

2013-06-06 Thread royar...@gmail.com (JIRA)















































Roy Arnon
 created  JENKINS-18241


Cant run Parallel Test Execution jobs















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


parallel-test-executor



Created:


06/Jun/13 5:24 PM



Description:


I just created a new job that only contains a Parallel Test Execution.
Tried the job with both a matrix job, and a regular maven job.
Both fail with this exception:

Copying file to 
FATAL: Failed to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/parameter-files/test-splits/split.1.txt to /home/builder/workspace/backstage.Test.chrome
hudson.util.IOException2: Failed to copy /var/lib/jenkins/jobs/backstage.ParallelTestExecution/builds/2013-06-06_20-20-25/parameter-files/test-splits/split.1.txt to /home/builder/workspace/backstage.Test.chrome
	at hudson.FilePath.copyTo(FilePath.java:1726)
	at hudson.model.FileParameterValue$FileItemImpl.write(FileParameterValue.java:267)
	at hudson.FilePath.copyFrom(FilePath.java:830)
	at hudson.model.FileParameterValue$2.setUp(FileParameterValue.java:136)
	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
	at hudson.model.Run.execute(Run.java:1576)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:241)
Caused by: java.io.FileNotFoundException: /home/builder/workspace/backstage.Test.chrome (Is a directory)
	at java.io.FileOutputStream.open(Native Method)
	at java.io.FileOutputStream.init(FileOutputStream.java:179)
	at java.io.FileOutputStream.init(FileOutputStream.java:131)
	at hudson.FilePath.write(FilePath.java:1622)
	at hudson.FilePath.copyTo(FilePath.java:1719)
	... 9 more




Project:


Jenkins



Labels:


bug




Priority:


Major



Reporter:


Roy Arnon

























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/groups/opt_out.

[JIRA] [gui] (JENKINS-16175) Dashboard not showing job status

2013-06-06 Thread richard_merr...@yahoo.com (JIRA)
















































Richard Merrill
 resolved  JENKINS-16175 as Duplicate


Dashboard not showing job status
















I haven't seen this bug in several months, so I'm assuming one of the fixes did the trick.





Change By:


Richard Merrill
(06/Jun/13 5:33 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/groups/opt_out.

[JIRA] [envinject] (JENKINS-16316) global variable not updated

2013-06-06 Thread jenk...@gcummings.com (JIRA)















































Geoff Cummings
 commented on  JENKINS-16316


global variable not updated
















I think it is related to the following code in EnvironmentVariablesNodeLoader:


for (NodeProperty? nodeProperty : Hudson.getInstance().getGlobalNodeProperties()) {
if (nodeProperty instanceof EnvironmentVariablesNodeProperty) {
EnvironmentVariablesNodeProperty variablesNodeProperty = (EnvironmentVariablesNodeProperty) nodeProperty;
EnvVars envVars = variablesNodeProperty.getEnvVars();
EnvInjectEnvVars envInjectEnvVars = new EnvInjectEnvVars(logger);
configNodeEnvVars.putAll(envVars);
envInjectEnvVars.resolveVars(configNodeEnvVars, nodeEnvVars);
}
}


Without the "Prepare jobs environment" checked, the if statement above resolves to false so env vars are not updated i think.




























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/groups/opt_out.

[JIRA] [envinject] (JENKINS-16316) global variable not updated















































Walter Kacynski
 commented on  JENKINS-16316


global variable not updated















That workaround doesn't seem to work for me however.



























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/groups/opt_out.

[JIRA] [core] (JENKINS-14992) Can add build other projects trigger to a project we cannot otherwise configure
















































Jesse Glick
 resolved  JENKINS-14992 as Not A Defect


Can add build other projects trigger to a project we cannot otherwise configure
















Not a bug as such, but JENKINS-16956 discusses better ideas.





Change By:


Jesse Glick
(06/Jun/13 7:42 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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/groups/opt_out.

[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.

2013-06-06 Thread dalewk...@gmail.com (JIRA)















































Dale King
 commented on  JENKINS-13995


Would like the ability to disable hover-over context menus.















In my opinion the pop-up menus that popped up with mouse hover were the PRIMARY ADVANTAGE that Jenkins had over Hudson! Bring them back!

I can understand the need to allow it to be disabled, but not for getting rid of it entirely. The hover menus allowed me to get to almost anywhere in Jenkins with a single click. The new version is back to the multiple clicks and page loads to get anywhere that drove me crazy in Hudson.

Note I will be upgrading to an older version until this is fixed.

I wonder if it would be possible to restore old functionality with a grease monkey script



























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/groups/opt_out.

[JIRA] [integrity-plugin] (JENKINS-16036) Failed to record SCM polling for hudson.model.FreeStyle = NullPointerException
















































Cletus DSouza
 resolved  JENKINS-16036 as Not A Defect


Failed to record SCM polling for hudson.model.FreeStyle = NullPointerException
















Based on Vitaliy Golovanev comment, this is not an issue with the Integrity Plugin





Change By:


Cletus DSouza
(06/Jun/13 8:21 PM)




Status:


Open
Resolved





Fix Version/s:


current





Resolution:


NotADefect



























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/groups/opt_out.

[JIRA] [publish-over-cifs] (JENKINS-18242) Publish to Cifs even if build failed

2013-06-06 Thread jmont...@apcc.com (JIRA)















































Joe Montanari
 created  JENKINS-18242


Publish to Cifs even if build failed















Issue Type:


New Feature



Affects Versions:


current



Assignee:


bap



Components:


publish-over-cifs



Created:


06/Jun/13 8:20 PM



Description:


It would be nice if there was an option to publish to Cifs Share Even if the build fails. 
I use the plugin to Archive out logs. I noticed the Failed build logs were getting skipped.
CIFS: Current build result is FAILURE, not going to run.

I saw JENKINS-15590 for SSH But there does not seem to be an equivalent option for Cifs. 





Project:


Jenkins



Priority:


Major



Reporter:


Joe Montanari

























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/groups/opt_out.

[JIRA] [integrity-plugin] (JENKINS-11850) Issue with PMC Integrity Pug in













































 
Cletus DSouza
 edited a comment on  JENKINS-11850


Issue with PMC Integrity Pug in
















In server-install-dir\IntegrityServer10\config\client\IntegrityClientSite.rc:

Disable line 30:

#Connection policy allowing a specific set of IP addresses to connect.
#
#daemon.connectionPolicy=mks.ic.common.policy.ICAllowSpecificConnectionPolicy

Enable line 42:
#
#Connection policy allowing everyone to connect.
#
daemon.connectionPolicy=mks.ic.common.policy.ICAllowAllConnectionPolicy



























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/groups/opt_out.

[JIRA] [integrity-plugin] (JENKINS-11850) Issue with PMC Integrity Pug in
















































Cletus DSouza
 resolved  JENKINS-11850 as Not A Defect


Issue with PMC Integrity Pug in
















In server-install-dir\IntegrityServer10\config\client\IntegrityClientSite.rc:

Disable line 30:
#

	Connection policy allowing a specific set of IP addresses to connect.
#
#daemon.connectionPolicy=mks.ic.common.policy.ICAllowSpecificConnectionPolicy



Enable line 42:
#

	Connection policy allowing everyone to connect.
#
daemon.connectionPolicy=mks.ic.common.policy.ICAllowAllConnectionPolicy







Change By:


Cletus DSouza
(06/Jun/13 8:25 PM)




Status:


Reopened
Resolved





Assignee:


jagankalluri
CletusDSouza





Fix Version/s:


current





Resolution:


NotADefect



























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/groups/opt_out.

[JIRA] [integrity-plugin] (JENKINS-11850) Issue with PMC Integrity Pug in













































 
Cletus DSouza
 edited a comment on  JENKINS-11850


Issue with PMC Integrity Pug in
















In server-install-dir\IntegrityServer10\config\client\IntegrityClientSite.rc:

Disable line 30:


	Connection policy allowing a specific set of IP addresses to connect.



#daemon.connectionPolicy=mks.ic.common.policy.ICAllowSpecificConnectionPolicy

Enable line 42:


	Connection policy allowing everyone to connect.



daemon.connectionPolicy=mks.ic.common.policy.ICAllowAllConnectionPolicy



























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/groups/opt_out.

[JIRA] [deploy] (JENKINS-18243) Cannot Download plugins.

2013-06-06 Thread sandeep.bhano...@gmail.com (JIRA)















































Sandeep Bhanoori
 created  JENKINS-18243


Cannot Download plugins.















Issue Type:


Bug



Assignee:


Unassigned


Components:


deploy



Created:


06/Jun/13 8:42 PM



Description:


I cannot download any plugins via manage plugins ( GUI ) or from http://updates.jenkins-ci.org/download/plugins/


Please help. I'm in need of deploy plugin. Its a big blocker for me. 




Due Date:


07/Jun/13 12:00 AM




Project:


Jenkins



Priority:


Blocker



Reporter:


Sandeep Bhanoori

























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/groups/opt_out.

[JIRA] [plugin] (JENKINS-18244) Passwords should not be stored as clear text in config.xml and should not be printed out to the log

2013-06-06 Thread an...@capital.net (JIRA)















































Eric Anker
 created  JENKINS-18244


Passwords should not be stored as clear text in config.xml and should not be printed out to the log















Issue Type:


Bug



Affects Versions:


current



Assignee:


Praqma Support



Components:


plugin, rqm



Created:


06/Jun/13 9:17 PM



Description:


RQM plugin v1.0 stores the password for the RQM server in clear text in the config.xml for the project

In addition, it prints the password out to the log.

Passwords should be at least obscured.  It's common to use 64 bit encoding to store in flat text config files.

Passwords should probably also NOT be printed to the log... ever.




Project:


Jenkins



Labels:


plugin
security
configuration




Priority:


Major



Reporter:


Eric Anker

























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/groups/opt_out.

[JIRA] [mercurial] (JENKINS-17260) Mercurial Push Notifications: URLs should be compared in canonical form

2013-06-06 Thread d.ja...@gaminglabs.com (JIRA)















































Dan Jasek
 commented on  JENKINS-17260


Mercurial Push Notifications: URLs should be compared in canonical form















Additionally, if the push notification uses '\' instead of '/', an error is thrown.  This can be confusing on Windows servers.

For example, if the URL is: E:\RepoApps\Repo\Track.hg
The job accesses the repo and updates the working directory properly.

If I access http://myjenkins:8080/mercurial/notifyCommit?url="">

I get this error:
java.net.URISyntaxException: Illegal character in opaque part at index 2: E:\RepoApps\Repo\Track.hg

Luckly, hg will work with slashes in either direction, so I was able to fix this by using '/' in both the URL and the push notification.
However, if you are updating this code anyway, it would be nice if '/' worked in the push notification.



























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/groups/opt_out.

[JIRA] [memory-map] (JENKINS-18246) Stacked graphs (Praqma case 8624)















































Bue Petersen
 updated  JENKINS-18246


Stacked graphs (Praqma case 8624)
















Change By:


Bue Petersen
(06/Jun/13 9:25 PM)




Summary:


Stackedgraphs
(Praqmacase8624)



























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/groups/opt_out.

[JIRA] [memory-map] (JENKINS-18246) Stacked graphs















































Bue Petersen
 created  JENKINS-18246


Stacked graphs















Issue Type:


Improvement



Assignee:


Praqma Support



Components:


memory-map



Created:


06/Jun/13 9:25 PM



Description:


Can we implement stacked graphs to let the user decide other types of graphs, just like other plugin does. 
Like warnings for example.




Project:


Jenkins



Priority:


Minor



Reporter:


Bue Petersen

























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/groups/opt_out.

[JIRA] [memory-map] (JENKINS-18247) Add enlarge graph link (Praqma case 8623)















































Bue Petersen
 created  JENKINS-18247


Add enlarge graph link (Praqma case 8623)















Issue Type:


Improvement



Assignee:


Praqma Support



Components:


memory-map



Created:


06/Jun/13 9:27 PM



Description:


just like Warnings graphs have an enlarge graph link.




Project:


Jenkins



Priority:


Major



Reporter:


Bue Petersen

























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/groups/opt_out.

[JIRA] [memory-map] (JENKINS-18248) Changing configuration deletes graph (Praqma case 8598)















































Bue Petersen
 created  JENKINS-18248


Changing configuration deletes graph (Praqma case 8598)















Issue Type:


Bug



Assignee:


Praqma Support



Components:


memory-map



Created:


06/Jun/13 9:30 PM



Description:


Changing the configuration of a graph, removed the old one including all data.

No warning.

It might be a okay decision, but we should warn about maybee in the GUI




Project:


Jenkins



Priority:


Major



Reporter:


Bue Petersen

























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/groups/opt_out.

[JIRA] [memory-map] (JENKINS-18249) Use databound constructor















































Bue Petersen
 created  JENKINS-18249


Use databound constructor















Issue Type:


Improvement



Assignee:


Praqma Support



Components:


memory-map



Created:


06/Jun/13 9:33 PM



Description:


There is a FIXME in the code about

@DataBounConstructor

public MemoryMapGraphConfiguration() { }




Project:


Jenkins



Priority:


Minor



Reporter:


Bue Petersen

























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/groups/opt_out.

[JIRA] [memory-map] (JENKINS-18249) Use databound constructor (Praqma case 8241)