date:20140930
















































SCM/JIRA link daemon
 resolved  JENKINS-24921 as Fixed


Obsolete "Setup after creation" option appears in the global configuration
















Change By:


SCM/JIRA link daemon
(30/Sep/14 7:43 AM)




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] [ownership-plugin] (JENKINS-24921) Obsolete "Setup after creation" option appears in the global configuration















































SCM/JIRA link daemon
 commented on  JENKINS-24921


Obsolete "Setup after creation" option appears in the global configuration















Code changed in jenkins
User: Oleg Nenashev
Path:
 src/main/java/com/synopsys/arc/jenkins/plugins/ownership/extensions/item_ownership_policy/DropOwnershipPolicy.java
 src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/Messages.properties
 src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPlugin/config.jelly
 src/main/resources/com/synopsys/arc/jenkins/plugins/ownership/OwnershipPluginConfiguration/config.properties
http://jenkins-ci.org/commit/ownership-plugin/4f2a10e3dec284af5b1bff02d95be7d020e4a020
Log:
  [FIXED JENKINS-24921] - Removed obsolete configuration entry.

I've also fixed vague text descriptions. A help entry would be useful

Signed-off-by: Oleg Nenashev 





























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-13153) "Upgrade Automatically" does not seem to work on Windows















































Daniel Beck
 commented on  JENKINS-13153


"Upgrade Automatically" does not seem to work on Windows















Peter: Do you remember the Jenkins version you originally installed, and could look up the creation + last modification dates of jenkins.exe? AFAIK there is a (now resolved) bug that prevented that from getting updated on Jenkins update, and one of the fixed issues was a failure to restart Jenkins as well. So this appears to be an outdated jenkins.exe.

Current jenkins.exe should have a date from early April, assuming it doesn't get changed when packaged into 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-20272) Disconnected nodes don't need to be checked for reponse time

2014-09-30 Thread davida2...@java.net (JIRA)















































davida2009
 commented on  JENKINS-20272


Disconnected nodes don't need to be checked for reponse time















Hi Daniel

Thanks for making the 'Keep Offline Slaves Disconnected Retention Strategy Plugin' available through plugin manager. I have installed the plugin, restarted and set the Availability for nodes I have taken offline to:


Keep this slave online as much as possible, but don't reconnect if temporarily marked offline by the user


I no longer see messages in the log of type:


Attempting to reconnect 


But I do still messages of type:


Making  offline because it’s not responding


Is that what you would expect?

Best regards

David



























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-20272) Disconnected nodes don't need to be checked for reponse time















































Daniel Beck
 commented on  JENKINS-20272


Disconnected nodes don't need to be checked for reponse time















Hi David,

that was all Nicolas – thank him.

Making  offline because it’s not responding

That's a known issue in the response time monitor which doesn't care that a node is disconnected: JENKINS-20272



























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-20272) Disconnected nodes don't need to be checked for reponse time

2014-09-30 Thread davida2...@java.net (JIRA)















































davida2009
 commented on  JENKINS-20272


Disconnected nodes don't need to be checked for reponse time















Well, thank you Nicolas, if you are watching this issue.

Thanks for your reply Daniel. I guess you don't mean JENKINS-20272 because that is this 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] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows

2014-09-30 Thread phan...@dtc.com.au (JIRA)















































Peter Hancox
 commented on  JENKINS-13153


"Upgrade Automatically" does not seem to work on Windows















My jenkins.exe is dated 24-Mar-2014.

Should I uninstall/install the latestWindows package?



























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] [jenkins-multijob-plugin] (JENKINS-24922) Jenkins importer in bamboo does not show all the build plans available on jenkins environment for migration.

2014-09-30 Thread sra...@appfire.com (JIRA)

Sravan Kumar
created JENKINS-24922

Jenkins importer in bamboo does not show all the build plans available on jenkins environment for migration.

Issue Type:

Bug

Assignee:

Unassigned

Components:

jenkins-multijob-plugin

Created:

30/Sep/14 8:01 AM

Description:

I am trying to migrate from Jenkins to bamboo. We are using the default jenkins importer tool in bamboo to migrate the jobs, but when we point importer it to the jenkins_home folder it shows only a part of the builds that are available on jenkins. When we downloaded the import_logs we observed that the importer was unable to access the "config.xml" file under the jobs directory.

We have tried to fix this by disabling the "Project based security" under each project.
We have also tried to run importer by disabling the Matrix Authorization in global settings.

But all the above attempts failed to display the jobs to be migrated.
The exact error message in the importer_logs that is displayed is shown below

--
Job name:
SEVERITY: FATAL
Exception while reading data from /opt/jenkins2/jenkins_home/jobs/: hudson.util.IOException2: Unable to read /opt/jenkins2/jenkins_home/jobs//config.xml
--

Kindly propose a solution to this or else I ll have to manually create jobs(~150) which is preposterous.

Thanks in advance !!

Environment:

Jenkins ver. 1.558

Project:

Jenkins

Labels:

jenkins
jenkns-importer
jobmigration

Priority:

Critical

Reporter:

Sravan Kumar

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-20272) Disconnected nodes don't need to be checked for reponse time

2014-09-30 Thread jenkins-ci....@michael-prokop.at (JIRA)















































Daniel Beck
 commented on  JENKINS-20272


Disconnected nodes don't need to be checked for reponse time















Uh, no, given your response I thought this was the reconnecting issue. This issue is still unresolved and it happens for all disconnected nodes, so yes, I'd expect this to happen.



























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-24213) Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin















































Michael Prokop
 commented on  JENKINS-24213


Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin















I'm still seeing this with Jenkins 1.565.2, is there anything I might help in getting further to resolving this 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] [core] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows















































Daniel Beck
 commented on  JENKINS-13153


"Upgrade Automatically" does not seem to work on Windows















Not sure how to best do this. Possibly through reinstall. IIRC a user reported he just replaced the jenkins.exe, so you could also try the following:

If you find a file identical to your jenkins.exe among the exe files here (as sanity check; I'm not 100% sure this is the correct file): http://repo.jenkins-ci.org/releases/com/sun/winsw/winsw/
... then just replace it with the exe in the 1.16 folder.



























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] [ownership-plugin] (JENKINS-24475) Managing ownership not possible

2014-09-30 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 commented on  JENKINS-24475


Managing ownership not possible















Release ownership-0.5.1 with a fix.
http://repo.jenkins-ci.org/simple/releases/com/synopsys/jenkinsci/ownership/0.5.1/

Probably, an additional hotfix will be required



























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] [copyartifact] (JENKINS-24626) Parameter values of build selector change when upgrading CopyArtifact

2014-09-30 Thread ray.sennew...@gmail.com (JIRA)















































Ray Sennewald
 commented on  JENKINS-24626


Parameter values of build selector change when upgrading CopyArtifact















How difficult would it be to add support for MultiJob's here?  It would be great if I could use this with MultiJobs, but it appears that a job that is triggered as part of a Phase of the MultiJob isn't considered downstream.  Would it be possible to add support for this?



























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-18318) Cannot install any plugin with Chrome

2014-09-30 Thread savema...@gmail.com (JIRA)
















































Maksim Selivanov
 resolved  JENKINS-18318 as Cannot Reproduce


Cannot install any plugin with Chrome
















Change By:


Maksim Selivanov
(30/Sep/14 8:21 AM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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-18318) Cannot install any plugin with Chrome

2014-09-30 Thread savema...@gmail.com (JIRA)















































Maksim Selivanov
 commented on  JENKINS-18318


Cannot install any plugin with Chrome















No. This is not a problem any more.



























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] [ssh] (JENKINS-24913) SSH Plugin displays password parameter values unencrypted in log

2014-09-30 Thread pietro.descom...@ca-suisse.com (JIRA)















































Pietro Descombes
 updated  JENKINS-24913


SSH Plugin displays password parameter values unencrypted in log
















Hi Daniel, sure, here is the config:
Build configuration
Include a build parameter of type Password 

Then add an Execute shell script on remote host using ssh build task. Inside the command block, call a shell script taking a argument. Use the parameter as argument.


Run the build
When running it using the Build with Parameters link, the task is successfully executed, but all the used parameters are printed out in the console output (as well as the script itself).

This would be fine for normal parameters, but it is a security issue for passwords, as they are to be kept secret!





Change By:


Pietro Descombes
(30/Sep/14 8:27 AM)




Attachment:


shell-script.png





Attachment:


password-parameter.png





Attachment:


ssh-log.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] [junit-plugin] (JENKINS-20701) Matrix Project with Combination Filter does not publish JUnit Reports

2014-09-30 Thread aviv.yamsim...@emc.com (JIRA)















































Aviv Yam
 commented on  JENKINS-20701


Matrix Project with Combination Filter does not publish JUnit Reports















Matrix Project does not publish JUnit Reports at all!



























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] [ssh] (JENKINS-24913) SSH Plugin displays password parameter values unencrypted in log













































  
Daniel Beck
 edited a comment on  JENKINS-24913


SSH Plugin displays password parameter values unencrypted in log
















Right, bug is around here:
https://github.com/jenkinsci/ssh-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/VariableReplacerUtil.java

It does not care whether environment variables are declared sensitive (AbstractBuild.getSensitiveBuildVariables()).

(Plus, contains() is a bit weak to determine whether a script references a given value.)



























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] [ssh] (JENKINS-24913) SSH Plugin displays password parameter values unencrypted in log















































Daniel Beck
 commented on  JENKINS-24913


SSH Plugin displays password parameter values unencrypted in log















Right, bug is around here:
https://github.com/jenkinsci/ssh-plugin/blob/master/src/main/java/org/jvnet/hudson/plugins/VariableReplacerUtil.java

It does not care whether environment variables are declared sensitive (AbstractBuild.getSensitiveBuildVariables()).



























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-13153) "Upgrade Automatically" does not seem to work on Windows

2014-09-30 Thread phan...@dtc.com.au (JIRA)















































Peter Hancox
 commented on  JENKINS-13153


"Upgrade Automatically" does not seem to work on Windows















Didn't uninstall. Just installed latest package over existing installation and reapplied changes I'd made to "jenkins.xml".

So far so good.  Have to wait and see if next auto update works.

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

[JIRA] [openid] (JENKINS-22368) Discovery fails when Jenkins is behind a proxy

2014-09-30 Thread hubert.grzeskow...@trustedshops.de (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-22368


Discovery fails when Jenkins is behind a proxy















Code changed in jenkins
User: Stephen Connolly
Path:
 src/main/java/hudson/plugins/openid/GoogleAppSsoSecurityRealm.java
 src/main/java/hudson/plugins/openid/OpenIdSsoSecurityRealm.java
 src/test/java/hudson/plugins/openid/OpenIdSsoSecurityRealmTest.java
http://jenkins-ci.org/commit/openid-plugin/e4ff38c938681d34d06242477534678b9e18e0ad
Log:
  Merge pull request #8 from jenkinsci/JENKINS-22368

fix test failure


Compare: https://github.com/jenkinsci/openid-plugin/compare/6e99fb8c90cb...e4ff38c93868




























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-24923) Support setting and forcing language / locale globally

Hubert Grzeskowiak
created JENKINS-24923

Support setting and forcing language / locale globally

Issue Type:

Improvement

Assignee:

Unassigned

Components:

core

Created:

30/Sep/14 9:38 AM

Description:

Hi,
in many companies from non English speaking countries there is a language policy that suggests using English in all documentations and shared documentation. This is especially true for companies that operate across borders or employ people from other countries.

I like the fact that Jenkins adjusts itself to the browser language, BUT for communication and a common language and glossary is a must-have. In my case it's hard to write tutorials for co-workers and they have a hard time reading those. Many Plugins are not localized and for job and build descriptions there is no option to write multiple entries for different locales. That said if you view our Jenkins installation using a German browser you see a mix of English and German. As far as I've looked it's not possible to change that language except for changing one's browser language (which average users cannot be expected to do).

I did try out the Locale Plugin, but it's very unreliable. After every Jenknis restart you need to go to settings and save without changing anything for it to apply the language. Sometimes (actually recently) it doesn't work at all.

I wish there was a built-in setting in Jenkins for setting the used language explicitly. That setting can be "client language" as default, which would keep backward compatibility. But any other setting should force the global setting.

Thanks
Regards
Hubert Grzeskowiak

Project:

Jenkins

Labels:

user-experience
gui
configuration
jenkins

Priority:

Minor

Reporter:

Hubert Grzeskowiak

[JIRA] [gerrit-trigger] (JENKINS-24924) Gerrit trigger is not wokring with Maven Projects

2014-09-30 Thread dorons...@gmail.com (JIRA)

Doron Shai
created JENKINS-24924

Gerrit trigger is not wokring with Maven Projects

Issue Type:

Bug

Assignee:

rsandell

Components:

gerrit-trigger

Created:

30/Sep/14 9:50 AM

Description:

I am Jenkins(1.581) and the Gerrit Trigger(2.11.1) to launch builds from Gerrit in order to verify code.
This is working fine as long as the project in Jenkins is configured as a "Free style" project.
However, When I'm using the "Build a maven2/3 project" option in order to take advantage of maven specific properties which I can't get from the "Free style" option.
For some reason, Jenkins doesn't seem to trigger builds using this option. Nothing at all happens when I submit code to Gerrit which under normal circumstances should be picked up.
I'm actually wondering if the Gerrit trigger is meant to work with Jenkins projects configured as a maven2/3 job or maybe it is the case that I can only use the Free style option in order to do this.

Please make it work

See discussion here (http://stackoverflow.com/questions/10609598/how-to-trigger-maven-specific-job-in-jenkins-with-gerrit

Environment:

Jenkins 1.581

Gerrit Plugin 2.11.1

Project:

Jenkins

Priority:

Critical

Reporter:

Doron Shai

[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying

2014-09-30 Thread christoph.fors...@swarovski.com (JIRA)















































Christoph Forster
 commented on  JENKINS-19470


Build Graph not displaying















Plugin does not show anyting:
Jenkins 1.582, Build Flow Plugin 0.15, buildgraph-view 1.1.1, Parameterized Trigger Plugin 2.25
Even grabbing the source and installing a fresh hpi did not work.
Also there are no errors nor log-output.



























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] [slave-status] (JENKINS-19445) Jobs randomly stuck with "building remotely on slave-name" message

2014-09-30 Thread ing.jan.rezni...@gmail.com (JIRA)















































Jan Řezníček
 commented on  JENKINS-19445


Jobs randomly stuck with "building remotely on slave-name" message















I am facing the same or similar problem.
I have Jenkins linux master and slaves on the Proxmox Windows XP machines. 
Time to time, a slave stuck. 
The cosole output ends with line - building remotely on ...
No SVN checkout is executed after, the build is totally stuck.
The slave says: Slave successfully connected and online

I have to restart the slave machine and abort the job. If i only abort the job, the next build is stuck too.



























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] [sbt] (JENKINS-24346) Cannot launch sbt when either java or sbt-launcher path contains spaces in Windows

2014-09-30 Thread ankit_bisa...@yahoo.com (JIRA)















































ankit bisaria
 commented on  JENKINS-24346


Cannot launch sbt when either java or sbt-launcher path contains spaces in Windows















Console Output


Started by user Ankit Bisaria
Building in workspace E:\test
[test] $ cmd.exe /C 'C:\Program Files (x86)\Jenkins\"C:\Program Files\Java\jdk1.7.0_60"\bin\java' -Dsbt.log.noformat=true -jar '"C:\Program Files (x86)\sbt\bin\sbt-launch.jar"' clean dist
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Build using sbt' changed build result to FAILURE
Build step 'Build using sbt' marked build as failure
Finished: FAILURE



I can not integrate sbt plugin with jenkins. Please fix this as I need this urgently in a project.

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

[JIRA] [javanet] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.

2014-09-30 Thread sfeat...@gmail.com (JIRA)













































  
Stephen Feather
 edited a comment on  JENKINS-10160


When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
















This started occuring this week with Jenkins 1.552 on OSX.

The "when the network is broken" is a bit vague, be nice to know what that actually 'means' to the original poster.


Sep 30, 2014 7:02:44 AM javax.jmdns.impl.constants.DNSRecordClass classForIndex
WARNING: Could not find record class for index: -1
Sep 30, 2014 7:02:44 AM javax.jmdns.impl.DNSIncoming readAnswer
SEVERE: Could not find record class. domain:  type: TYPE_IGNORE index 0
dns[response,192.168.1.110:5353, length=303, id=0x0, flags=0x8400:r:aa, answers=1
answers:
	[Text@532787820 type: TYPE_TXT index 16, class: CLASS_IN index 1-unique, name: 9C207B8E5E2F@Office Apple TV._raop._tcp.local. ttl: '4499/4500' text: '
cn=0,1,2,3da=tr...']]
	answer:[Text@532787820 type: TYPE_TXT index 16, class: CLASS_IN index 1-unique, name: 9C207B8E5E2F@Office Apple TV._raop._tcp.local. ttl: '4499/4500' text: '
cn=0,1,2,3da=tr...']
   0: 8401 00021c394332 3037423845354532 46404f696365  .9C2 07B8E5E2 F@Office
  20: 204170706c652054 56055f72616f7004 5f746370056c6f63 616c10800100 .Apple.T V._raop. _tcp.loc al..
  40: 00119400b00a636e 3d302c312c322c33 0764613d74727565 0865743d302c332c ..cn =0,1,2,3 .da=true .et=0,3,
  60: 351166743d307835 413746464646372c 307845086d643d30 2c312c320d616d3d 5.ft=0x5 A77, 0xE.md=0 ,1,2.am=
  80: 4170706c65545633 2c3143706b3d6134 6530613364306633 3236336463393339 AppleTV3 ,1Cpk=a4 e0a3d0f3 263dc939
  a0: 6535393532323434 3135383937613830 6531316136643838 6663346632303264 e5952244 15897a80 e11a6d88 fc4f202d
  c0: 6162613535383330 3438383164330773 663d307834340674 703d55445008766e aba55830 4881d3.s f=0x44.t p=UDP.vn
  e0: 3d36353533370976 733d3231302e3938 0476763d3229 05a00018 =65537.v s=210.98 .vv=2..) 
 100: 0004001400970200 0200  2905a000    ..).
 120: 0cfdea0008de 47a811e167e381  G...g..




























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] [javanet] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.

2014-09-30 Thread sfeat...@gmail.com (JIRA)















































Stephen Feather
 commented on  JENKINS-10160


When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.















This started occuring this week with Jenkins 1.552 on OSX.


Sep 30, 2014 7:02:44 AM javax.jmdns.impl.constants.DNSRecordClass classForIndex
WARNING: Could not find record class for index: -1
Sep 30, 2014 7:02:44 AM javax.jmdns.impl.DNSIncoming readAnswer
SEVERE: Could not find record class. domain:  type: TYPE_IGNORE index 0
dns[response,192.168.1.110:5353, length=303, id=0x0, flags=0x8400:r:aa, answers=1
answers:
	[Text@532787820 type: TYPE_TXT index 16, class: CLASS_IN index 1-unique, name: 9C207B8E5E2F@Office Apple TV._raop._tcp.local. ttl: '4499/4500' text: '
cn=0,1,2,3da=tr...']]
	answer:[Text@532787820 type: TYPE_TXT index 16, class: CLASS_IN index 1-unique, name: 9C207B8E5E2F@Office Apple TV._raop._tcp.local. ttl: '4499/4500' text: '
cn=0,1,2,3da=tr...']
   0: 8401 00021c394332 3037423845354532 46404f696365  .9C2 07B8E5E2 F@Office
  20: 204170706c652054 56055f72616f7004 5f746370056c6f63 616c10800100 .Apple.T V._raop. _tcp.loc al..
  40: 00119400b00a636e 3d302c312c322c33 0764613d74727565 0865743d302c332c ..cn =0,1,2,3 .da=true .et=0,3,
  60: 351166743d307835 413746464646372c 307845086d643d30 2c312c320d616d3d 5.ft=0x5 A77, 0xE.md=0 ,1,2.am=
  80: 4170706c65545633 2c3143706b3d6134 6530613364306633 3236336463393339 AppleTV3 ,1Cpk=a4 e0a3d0f3 263dc939
  a0: 6535393532323434 3135383937613830 6531316136643838 6663346632303264 e5952244 15897a80 e11a6d88 fc4f202d
  c0: 6162613535383330 3438383164330773 663d307834340674 703d55445008766e aba55830 4881d3.s f=0x44.t p=UDP.vn
  e0: 3d36353533370976 733d3231302e3938 0476763d3229 05a00018 =65537.v s=210.98 .vv=2..) 
 100: 0004001400970200 0200  2905a000    ..).
 120: 0cfdea0008de 47a811e167e381  G...g..




























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] [sbt] (JENKINS-24346) Cannot launch sbt when either java or sbt-launcher path contains spaces in Windows

2014-09-30 Thread ska...@yahoo.com (JIRA)















































Spyros Kapnissis
 commented on  JENKINS-24346


Cannot launch sbt when either java or sbt-launcher path contains spaces in Windows















Hi, this fix has not been included in a release yet. In the meantime you can try building the master branch yourself with maven (https://github.com/jenkinsci/sbt-plugin), and manually install the plugin jar to 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the "oops page" and a traceback.

2014-09-30 Thread markus.str...@nokia.com (JIRA)















































Markus Strand
 created  JENKINS-24925


When using BFA with MongoDB the causes gives the "oops page" and a traceback.















Issue Type:


Bug



Assignee:


Tomas Westling



Components:


build-failure-analyzer



Created:


30/Sep/14 11:48 AM



Description:


When using BFA with MongoDB the causes gives the "oops page" and a traceback.


javax.servlet.ServletException: com.mongodb.MongoException$Network: can't call something : salmongo01.rnd.nokia.com/10.220.197.139:27017/BuildFailureAnalyzer
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	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.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
	at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
	at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at org.jenkinsci.plugins.suppress_stack_trace.SuppressionFilter.doFilter(SuppressionFilter.java:34)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:52)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.

[JIRA] [core] (JENKINS-24923) Support setting and forcing language / locale globally















































Daniel Beck
 commented on  JENKINS-24923


Support setting and forcing language / locale globally















I did try out the Locale Plugin, but it's very unreliable. After every Jenknis restart you need to go to settings and save without changing anything for it to apply the language. Sometimes (actually recently) it doesn't work at all.

Would be better to request the plugin gets fixed IMO.



























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-5753) Standalone install does not work with Apache + mod_proxy_ajp + SSL















































Daniel Beck
 commented on  JENKINS-5753


Standalone install does not work with Apache + mod_proxy_ajp + SSL















Has this issue been fixed as a side effect of the switch to Jetty in 1.535? Anyone else experience Felix's 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] [robot-plugin] (JENKINS-24868) Add the ability for robot plugin graph to show only failed tests

2014-09-30 Thread ninian_har...@yahoo.com (JIRA)















































Ninian
 updated  JENKINS-24868


Add the ability for robot plugin graph to show only failed tests
















Thanks, yes we've used the zoomed graph. The point though is that the changes show largely the number of tests added, which dwarf the 'interesting' results which are the failures.





Change By:


Ninian
(30/Sep/14 12:27 PM)




Attachment:


Zoomedgraph.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] [core] (JENKINS-24926) Connection to slave constantly breaks, java process can only be kill -9-ed

2014-09-30 Thread christoph.fors...@swarovski.com (JIRA)















































Johannes Wienke
 created  JENKINS-24926


Connection to slave constantly breaks, java process can only be kill -9-ed















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


30/Sep/14 12:27 PM



Description:


Since approximately 9 months we have constant troubles with our master losing connectivity to our mac mavericks slave (via ssh). The issue we observe is that after some time, the master cannot communicate with the slave anymore, so that jobs fail with the following error message:


Building remotely on MAC_OS_mavericks_64bit (macos mavericks java7)FATAL: channel is already closed
hudson.remoting.ChannelClosedException: channel is already closed
	at hudson.remoting.Channel.send(Channel.java:541)
	at hudson.remoting.Request.call(Request.java:129)
	at hudson.remoting.Channel.call(Channel.java:739)
	at hudson.EnvVars.getRemote(EnvVars.java:404)
	at hudson.model.Computer.getEnvironment(Computer.java:912)
	at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:29)
	at hudson.model.Run.getEnvironment(Run.java:2221)
	at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:885)
	at hudson.matrix.MatrixRun$MatrixRunExecution.decideWorkspace(MatrixRun.java:175)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513)
	at hudson.model.Run.execute(Run.java:1706)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:232)
Caused by: java.io.IOException
	at hudson.remoting.Channel.close(Channel.java:1027)
	at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110)
	at hudson.remoting.PingThread.ping(PingThread.java:120)
	at hudson.remoting.PingThread.run(PingThread.java:81)
Caused by: java.util.concurrent.TimeoutException: Ping started on 1412069451954 hasn't completed at 1412069691955
	... 2 more



At some point, the slave is then marked as offline. When trying to reconnect, nothing happens. You see an empty log window with just the circling loading animation. No output is generated ever.

We could not observer any issues with the underlying network connection. Everytime I observe this error, ssh-ing to the slave as the jenkins user is possible without any problems.

This also only happens for the mavericks slave. All other Linux and Windows slave work perfectly.

What is extremely confusing is that in case jenkins ended up in this condition, you cannot restart it in a clean fashion. You first have to kill the java process with SIGKILL, even though it is apparently not completely stuck since operation for everything apart from the mavericks slave continues to work perfectly.

The general log file for jenkins only shows that also the jobs for checking disk space etc. suffer from the connectivity issue:


WARNING: Failed to monitor MAC_OS_mavericks_64bit for Architecture
hudson.remoting.ChannelClosedException: channel is already closed
at hudson.remoting.Channel.send(Channel.java:541)
at hudson.remoting.Request.callAsync(Request.java:208)
at hudson.remoting.Channel.callAsync(Channel.java:766)
at hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMo
nitorDescriptor.java:76)
at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDe
scriptor.java:280)
Caused by: java.io.IOException
at hudson.remoting.Channel.close(Channel.java:1027)
at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110)
at hudson.remoting.PingThread.ping(PingThread.java:120)
at hudson.remoting.PingThread.run(PingThread.java:81)
Caused by: java.util.concurrent.TimeoutException: Ping started on 1412069451954 hasn't complet
ed at 1412069691955
... 2 more



Apart from this, no errors are visible for that slave.

A thread dump from the situation where the master tries to reconnect to the salve but nothing happens is available here:
http://pastebin.com/DxFU8j7C




Environment:


L

[JIRA] [copyartifact] (JENKINS-24626) Parameter values of build selector change when upgrading CopyArtifact

2014-09-30 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-24626


Parameter values of build selector change when upgrading CopyArtifact















> MultiJob support

I don't plan that at least for the first release of this feature.
Please create another ticket.

Anyway, I don't know much about MultiJob (I haven't ever used that)
and I cannot contribute for 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] [buildgraph-view] (JENKINS-19470) Build Graph not displaying













































  
Christoph Forster
 edited a comment on  JENKINS-19470


Build Graph not displaying
















Plugin does not show anyting:
Jenkins 1.582, Build Flow Plugin 0.15, buildgraph-view 1.1.1, Parameterized Trigger Plugin 2.25
Even grabbing the source and installing a fresh hpi did not work.
Also there are no errors nor log-output.
Found JENKINS-24875 which says, that with an older Build Flow Plugion (0.12) it works correct.



























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] [simple-parameterized-builds-report] (JENKINS-24927) no table background colours















































Anders Larsen
 created  JENKINS-24927


no table background colours















Issue Type:


Bug



Assignee:


Unassigned


Components:


simple-parameterized-builds-report



Created:


30/Sep/14 1:21 PM



Description:


The Jenkins pages are HTML5 which does not support 
The background colours should be set using CSS instead.




Environment:


Jenkins 1.581, spbr 1.3




Project:


Jenkins



Priority:


Minor



Reporter:


Anders Larsen

























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] [simple-parameterized-builds-report] (JENKINS-24928) spelling mistake















































Anders Larsen
 updated  JENKINS-24928


spelling mistake
















Change By:


Anders Larsen
(30/Sep/14 1:28 PM)




Assignee:


Nalin Makar



























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] [simple-parameterized-builds-report] (JENKINS-24927) no table background colours















































Anders Larsen
 updated  JENKINS-24927


no table background colours
















Change By:


Anders Larsen
(30/Sep/14 1:29 PM)




Environment:


Jenkins 1.581, spbr 1.3
, Chromium 37.0.2062.120





Assignee:


Nalin Makar



























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] [simple-parameterized-builds-report] (JENKINS-24928) spelling mistake















































Anders Larsen
 created  JENKINS-24928


spelling mistake















Issue Type:


Improvement



Assignee:


Unassigned


Components:


simple-parameterized-builds-report



Created:


30/Sep/14 1:26 PM



Description:


The heading above the table says "Simple Parametized Builds Report", it should be "... Parameterized ..." (as in the page title)




Environment:


spbr 1.3




Project:


Jenkins



Priority:


Minor



Reporter:


Anders Larsen

























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-24926) Connection to slave constantly breaks, java process can only be kill -9-ed















































Daniel Beck
 commented on  JENKINS-24926


Connection to slave constantly breaks, java process can only be kill -9-ed















Make sure the clocks are in sync. Also, configure same time zone.



























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-24926) Connection to slave constantly breaks, java process can only be kill -9-ed















































Daniel Beck
 commented on  JENKINS-24926


Connection to slave constantly breaks, java process can only be kill -9-ed















You forgot to mention Jenkins version.



























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] [parameterized-remote-trigger] (JENKINS-23745) Create links to the running/executed remote job

2014-09-30 Thread skuli.arnlaugs...@gmail.com (JIRA)















































Skuli Arnlaugsson
 commented on  JENKINS-23745


Create links to the running/executed remote job















This would be extremely nice.



























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] [remoting] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin"" was unexpected at this time.' error

2014-09-30 Thread atis.strauj...@gmail.com (JIRA)













































  
Atis Straujums
 edited a comment on  JENKINS-11992


Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin"" was unexpected at this time.' error
















Our solution (workaround) to this problem was to install Java in a location without spaces in the path.



























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] [ownership-plugin] (JENKINS-24475) Managing ownership not possible

2014-09-30 Thread stephan.kr...@ecg-leipzig.de (JIRA)















































Stephan Krull
 commented on  JENKINS-24475


Managing ownership not possible















updated to ownership 0.5.1; changed email resolver in system configuration to ldap; created job and tried to manage ownership - this is the favored use case in production mode - everything works fine. thank you! 



























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] [remoting] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin"" was unexpected at this time.' error

2014-09-30 Thread atis.strauj...@gmail.com (JIRA)















































Atis Straujums
 commented on  JENKINS-11992


Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin"" was unexpected at this time.' error















Our solution was to install Java in a location without spaces in the path.



























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-24926) Connection to slave constantly breaks, java process can only be kill -9-ed















































Johannes Wienke
 commented on  JENKINS-24926


Connection to slave constantly breaks, java process can only be kill -9-ed















Clocks are in sync via NTP. Jenkins is running at LTS version 1.565.1.

This also happened before we upgraded the master to wheezy with openjdk 6.



























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-24929) Deleting job via dropdown menu in job list fails due to crumb issues

2014-09-30 Thread paul.sokolov...@linaro.org (JIRA)















































Paul Sokolovsky
 created  JENKINS-24929


Deleting job via dropdown menu in job list fails due to crumb issues















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


30/Sep/14 3:00 PM



Description:


To reproduce:

1. From a main Jenkins page, listing jobs, hover mouse over a target job, for dropdown triangle to appear.
2. Click triangle to open dropdown menu.
3. Select "Delete Project".
4. Choose "OK" in confirmation dialog.

Error received:


HTTP ERROR 403

Problem accessing /jenkins/job/JOB/doDelete. Reason:

No valid crumb was included in the request

Powered by Jetty://



This looks very similar to JENKINS-18032, but that one apparently happened with "Delete" link on job information page. This one, again, happens in job lists, when using context/dropdown menu.





Project:


Jenkins



Priority:


Minor



Reporter:


Paul Sokolovsky

























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] [jobconfighistory] (JENKINS-24930) Use alternating row colors in history table















































Daniel Beck
 created  JENKINS-24930


Use alternating row colors in history table















Issue Type:


Improvement



Assignee:


Mirko Friedenhagen



Components:


jobconfighistory



Created:


30/Sep/14 3:01 PM



Description:


It's difficult (especially on wider screens) to associate a list entry (based on e.g. date or user who performed the change) with the File A/File B column radio buttons on the right used for diff.

It would be helpful to alternate row background colors so it's easier to see which radio buttons belongs to which row.




Project:


Jenkins



Labels:


user-experience




Priority:


Minor



Reporter:


Daniel Beck

























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-24931) BuildTriggers and ReverseBuildTriggers constantly vanishing

Johannes Wienke
created JENKINS-24931

BuildTriggers and ReverseBuildTriggers constantly vanishing

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

30/Sep/14 3:14 PM

Description:

Since ages we have the problem that from time to time the different build triggers ("Build after other projects are built" and "Build other projects") vanish for some jobs, leaving us in a situation where necessary downstream projects aren't triggered at all. This condition is sometimes really hard to track down and developers do not receive emails about errors they generated etc.

There is nothing we can correlate to the points in time this happens and the jobs that are affected. It seems this randomly appears for some jobs. The one thing that might be of interest is that basically all our jobs are matrix projects.

If there is anything I can do to give you more debug output, please indicate me what to do.

Environment:

Jenkins ver. 1.565.1 (LTS) on Debian Wheezy 64 bit with OpenJDK 7. Multiple Slaves with Linux, Mac and Windows.

Project:

Jenkins

Priority:

Minor

Reporter:

Johannes Wienke

[JIRA] [core] (JENKINS-24932) Build fails if mirror of "unpack archive" Maven installation procedure is unreachable

2014-09-30 Thread ho...@se-rwth.de (JIRA)

Andreas Horst
created JENKINS-24932

Build fails if mirror of "unpack archive" Maven installation procedure is unreachable

Issue Type:

Bug

Assignee:

Unassigned

Attachments:

error.log.txt

Components:

core, maven-plugin

Created:

30/Sep/14 3:21 PM

Description:

Builds seem to fail if the mirror of a "Unpack .zip/.tar.gz Archive" Maven installation procedure is offline even though that same installation is already present.

We configured a Maven installation procedure for Maven 3.2.3 via download from one of the mirrors (see error.log.txt). Maven had been successfully installed and used since a couple of weeks ago. Last weekend builds using that Maven version started to fail with the attached output (see error.log.txt). I checked and found out that the mirror was unreachable.

However, since the installation had been successful weeks ago, the builds should not fail and use the already present installation. It should only fail on new build nodes which did not yet install the version.

Environment:

Jenkins 1.582

Ubuntu 14.04.1

Project:

Jenkins

Labels:

jenkins
maven
installer
tools

Priority:

Minor

Reporter:

Andreas Horst

[JIRA] [git] (JENKINS-24933) Default git repository name for "Merge before build" not effective















































Johannes Wienke
 created  JENKINS-24933


Default git repository name for "Merge before build" not effective















Issue Type:


Bug



Assignee:


Nicolas De Loof



Attachments:


merge-config.png



Components:


git



Created:


30/Sep/14 3:24 PM



Description:


We have a matrix project configured to merge a git feature branch onto the master before starting the build. The exact configuration is attached as screenshot. The documentation for the "Name of repository" oarameter of the "Merge before build" behavior states that:

If left blank, it'll default to the name of the first repository configured above.
However, when leaving this field empty, you receive the following output when triggering the build:

Started by an SCM change
Building remotely on ubuntu_trusty_64bit (trusty gcc ubuntu-next java7 ubuntu linux 64bit) in workspace /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator
selected Git installation does not exists. Using Default
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://code.cor-lab.org/git/rsb.git.cpp
 > git init /home/jenkins/workspace/rsb-cpp-trunk-merge-simulator # timeout=10
Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp
 > git --version # timeout=10
 > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10
 > git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://code.cor-lab.org/git/rsb.git.cpp # timeout=10
Fetching upstream changes from https://code.cor-lab.org/git/rsb.git.cpp
 > git fetch --tags --progress https://code.cor-lab.org/git/rsb.git.cpp +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/0.10
Seen branch in repository origin/0.3
Seen branch in repository origin/0.4
Seen branch in repository origin/0.5
Seen branch in repository origin/0.6
Seen branch in repository origin/0.7
Seen branch in repository origin/0.9
Seen branch in repository origin/agni
Seen branch in repository origin/bug-1285
Seen branch in repository origin/enhancement-1096
Seen branch in repository origin/enhancement-1757
Seen branch in repository origin/enhancement-2034
Seen branch in repository origin/master
Seen branch in repository origin/wip-introspection
Seen branch in repository origin/wip-rosetta
Seen branch in repository origin/wip-static-participants
Seen 16 remote branches
Multiple candidate revisions
Scheduling another build to catch up with rsb-cpp-trunk-merge-simulator
Merging Revision 70a3fd1f2425cdc779d83314c6978955979e9237 (origin/enhancement-1757) onto /master using default strategy
 > git rev-parse /master^{commit} # timeout=10
FATAL: Command "git rev-parse /master^{commit}" returned status code 128:
stdout: /master^{commit}

stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'

hudson.plugins.git.GitException: Command "git rev-parse /master^{commit}" returned status code 128:
stdout: /master^{commit}

stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1437)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1413)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1409)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1112)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1122)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:518)
	at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)
	at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.i

[JIRA] [core] (JENKINS-24932) Build fails if mirror of "unpack archive" Maven installation procedure is unreachable

2014-09-30 Thread ho...@se-rwth.de (JIRA)















































Andreas Horst
 updated  JENKINS-24932


Build fails if mirror of "unpack archive" Maven installation procedure is unreachable
















Change By:


Andreas Horst
(30/Sep/14 3:23 PM)




Description:


Builds seem to fail if the mirror of a "Unpack
 \
 *.zip/
\
*.tar.gz Archive" Maven installation procedure is offline even though that same installation is already present.We configured a Maven installation procedure for Maven 3.2.3 via download from one of the mirrors (see error.log.txt). Maven had been successfully installed and used since a couple of weeks ago. Last weekend builds using that Maven version started to fail with the attached output (see error.log.txt). I checked and found out that the mirror was unreachable.However, since the installation had been successful weeks ago, the builds should not fail and use the already present installation. It should only fail on new build nodes which did not yet install the version.



























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-24934) Git clone with merging tries to checkout non-existing revision since force-push

2014-09-30 Thread henriquerodrig...@notonthehighstreet.com (JIRA)















































Johannes Wienke
 created  JENKINS-24934


Git clone with merging tries to checkout non-existing revision since force-push















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


30/Sep/14 3:30 PM



Description:


We are using special merge simulator projects for feature branches where
the idea is that the feature branch is automatically merged onto the
master before compiling and testing it so that also the merging behavior
is verified. All of these projects are multi configuration jobs. So far
this worked quite well but since a few days we are noticing a weird
behavior:

In one of the feature branches we did some force pushing and after that
we noticed two error conditions.

1. The coordinator performed the merge successfully, which created a new
revision with hash 5af79d528388216aa25a24c27f0a16d8dc55bdb6. All slaves
of the multi configuration project then try to checkout that revision,
which obviously does not exist in their local repositories. Hence, they
end up with

FATAL: Could not checkout master with start point
5af79d528388216aa25a24c27f0a16d8dc55bdb6
hudson.plugins.git.GitException: Could not checkout master with start
point 5af79d528388216aa25a24c27f0a16d8dc55bdb6
	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1448)
	at
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
	at
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)
Caused by: hudson.plugins.git.GitException: Command "git checkout -f
5af79d528388216aa25a24c27f0a16d8dc55bdb6" returned status code 128:
stdout:
stderr: fatal: reference is not a tree:
5af79d528388216aa25a24c27f0a16d8dc55bdb6

	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1276)
	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1253)
	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1249)
	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1065)
	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1075)
	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1431)
	... 11 more



2. After wiping the workspace of that job we ended up in a second error
condition already on the coordinator side:

Merging Revision 5af79d528388216aa25a24c27f0a16d8dc55bdb6 () onto
origin/master using default strategy
FATAL: Could not checkout master with start point
5af79d528388216aa25a24c27f0a16d8dc55bdb6
hudson.plugins.git.GitException: Could not checkout master with start
point 5af79d528388216aa25a24c27f0a16d8dc55bdb6
	at
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$8.execute(CliGitAPIImpl.java:1448)
	at
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
	at
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at

[JIRA] [core] (JENKINS-5753) Standalone install does not work with Apache + mod_proxy_ajp + SSL

2014-09-30 Thread felix.buenem...@gmail.com (JIRA)















































Felix Buenemann
 commented on  JENKINS-5753


Standalone install does not work with Apache + mod_proxy_ajp + SSL















I was already on 1.558 when I experienced the issue, as mentioned in the previous comment. I haven't tried using AJP since then.



























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-24935) Be able to clean workspace before retrying git fetch















































Henrique Rodrigues
 created  JENKINS-24935


Be able to clean workspace before retrying git fetch















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


30/Sep/14 3:37 PM



Description:


We use Jenkins' Git plugin to run our tests, but we prefer not to clean workspace before each build and reuse the code in the workspace instead. This makes testing much faster. Unfortunately, sometimes the Git information on the workspace gets corrupted and git fetch no longer works (unrelated to the Git plugin). This means that future build on that workspace will fail unless the workspace is cleaned.

It would be very good if Jenkins' Git plugin had the ability to clear the workspace before doing a retry.




Project:


Jenkins



Priority:


Major



Reporter:


Henrique Rodrigues

























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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)

2014-09-30 Thread marcus.a.phi...@gmail.com (JIRA)















































Marcus Philip
 commented on  JENKINS-24914


Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)















I agree that the code seems like ot should return. But it doesn't. Here's a test to prove it. The test runs forever.

The method under test is copied from the real Jenkins class. I just remove the Jenkins singleton stuff to make it simpler, but I think it should not change anything.


package jenkins.model;

import java.io.IOException;

import org.junit.Test;

public class JenkinsTest {
private transient volatile boolean isQuietingDown = false;

public void doQuietDown(boolean block,int timeout) throws InterruptedException, IOException {
synchronized (this) {
isQuietingDown  = true;
}
if (block) {
if (timeout > 0) {
timeout += System.currentTimeMillis();
}
while (isQuietingDown
   && (timeout <= 0 || System.currentTimeMillis() < timeout)
   && true) {
System.out.println("time: " + System.currentTimeMillis() + " Sleeping ...");
Thread.sleep(1000);
}
}
System.out.println("doQuietDown returning");
}
@Test
public void testDoQuietDownBooleanInt() throws Exception {
doQuietDown(true, 100);
}
}




























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-24936) Support for Stash Browser for Git plugin

2014-09-30 Thread christian.galste...@gmx.de (JIRA)















































Christian Galsterer
 created  JENKINS-24936


Support for Stash Browser for Git plugin















Issue Type:


New Feature



Assignee:


Christian Galsterer



Components:


job-dsl-plugin



Created:


30/Sep/14 4:00 PM



Description:


Allow to specify Stash as repository browser for the Git plugin




Project:


Jenkins



Priority:


Major



Reporter:


Christian Galsterer

























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] [claim] (JENKINS-16671) Multiple Selective Claiming of Broken Builds

2014-09-30 Thread apu...@yahoo.com (JIRA)















































Andy Pham
 commented on  JENKINS-16671


Multiple Selective Claiming of Broken Builds















Will we also be able to claim multiple test failures once this JIRA is implemented?

It seems like this couldn't be done with the latest version (1.582).  It's a very common scenario where multiple test failures have the same culprit.



























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] [promoted-builds] (JENKINS-24937) Execution of promotion does not set the Java version for MatrixProject

2014-09-30 Thread eric.hartm...@sonarsource.com (JIRA)















































Eric Hartmann
 created  JENKINS-24937


Execution of promotion does not set the Java version for MatrixProject















Issue Type:


Bug



Assignee:


Unassigned


Components:


promoted-builds



Created:


30/Sep/14 4:35 PM



Description:


We are using promoted plugin on a MatrixProject and we need to execute Maven goal during the promotion. 
However with this setup the promoted build is unable to use the JDK version defined in the matrix axis.
In this special case we need to set the JDK version inside the promotion configuration.

I'm preparing a pull request.




Project:


Jenkins



Priority:


Major



Reporter:


Eric Hartmann

























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-24938) On restart Jenkins rewrites some config.xml values

Joseph Hughes
created JENKINS-24938

On restart Jenkins rewrites some config.xml values

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

30/Sep/14 4:37 PM

Description:

I have been seeing this behavior for a while now. I have a standard ubuntu installation using the official package. Every time I reboot the jenkins process to update a plugin of a version my Views and Slave Port configuration are overridden.

For instance my original config.xml includes the following.

views>

All
false
false

iOS
false
false

(?i).IOS-.
false

All
8098

After a restart that section of the config.xml is reduced to.

All
false
false

All
0

I have watched the jenkins.log file closely and seen no errors or warnings in regard to why these two things specifically are being reset. What is also strange is that the rest of the core config is persisted and remains unchanged.

Environment:

Ubuntu 1.582

Project:

Jenkins

Labels:

jenkins

Priority:

Major

Reporter:

Joseph Hughes

[JIRA] [core] (JENKINS-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)















































Daniel Beck
 commented on  JENKINS-24914


Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)















System.currentTimeMillis() doesn't fit into the int, it overflows and is negative, resulting in an infinite loop.



























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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
















































Daniel Beck
 assigned  JENKINS-24914 to Daniel Beck



Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
















Change By:


Daniel Beck
(30/Sep/14 4:54 PM)




Assignee:


Daniel Beck



























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.

Requirement on Java Technical Lead

2014-09-30 Thread sunitha

 

Its contract to hire after 6 months

 

Role Description   - Java Technical Lead

 

Location  - Nashville, TN

 

Experience  - 8+ years

 

Skill Set- Java, J2EE, JSP, SQL,
PL/SQL, Perl, HTML, CSS, JavaScript, ZK Framework, Struts Framework, XML,
Web Services, SOAP, Knowledge of the Healthcare Industry and claim
processing cycle

 

 

 

Required Skills and Abilities include but are not limited to:

 

 

 

* 8+ years of Java/J2EE Web Application Development experience

 

* Knowledge of deploying applications via IBM Console for WebSphere
Application Servers (WAS)

 

* AIX Unix Scripting

 

* Application Development in Eclipse IDE and IBM Rational
Application Developer (RAD)

 

* Experience with IBM Rational ClearCase for source control

 

* Unix and Shell Scripting a must

 

* AWS cloud computing platform experience is a plus

 

* Be able to work as part of an Agile cross-functional team

 

* Knowledge of the Healthcare Industry and claim processing cycle
with a focus on payer Electronic Remittance Advices (ERAs)

 

* Knowledge of the Healthcare Industry and claim processing cycle
with a focus on payer Electronic Claims (837)

 

* Demonstrate solid software engineering skills and willingness to
learn new technologies

 

* Coordinate with offshore and other distributed teams to achieve
project deliverables

 

* Excellent communication skills, both verbal and written and Strong
analytical skills

 

* Have proven creative problem solving skills

 

If you have any questions, please feel free to contact me.

 

 

 

Thanks & Regards

 

Sunitha 

Sr.Recruiter

Sree Infotech LLC

9901 E. Valley Ranch Parkway, Suite 3008,

Irving, TX 75063

Phone: 972-332-3471 Extn 114

Email Id: suni...@sreeinfotech.com

Gtalk: archana.sreeinfo

Yahoo ID:archana.sreeinfo


Note: We respect your Online Privacy. This mail cannot be considered Spam as
long as we include contact information and a method to be removed from our
mailing list. To be removed from our mailing list, please reply with
"REMOVE" in the subject line and your email address in the body. Include
Complete Address and/or Domain/Aliases to be removed.

 

-- 
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-24914) Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)













































  
Daniel Beck
 edited a comment on  JENKINS-24914


Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
















System.currentTimeMillis() doesn't fit into the int, it overflows and is negative (for the next week or so), resulting in an infinite loop.



























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.

Requirement on Java Technical Lead

2014-09-30 Thread sunitha

Its contract to hire after 6 months

 

Role Description   - Java Technical Lead

 

Location  - Nashville, TN

 

Experience  - 8+ years

 

Skill Set- Java, J2EE, JSP, SQL,
PL/SQL, Perl, HTML, CSS, JavaScript, ZK Framework, Struts Framework, XML,
Web Services, SOAP, Knowledge of the Healthcare Industry and claim
processing cycle

 

 

 

Required Skills and Abilities include but are not limited to:

 

 

 

* 8+ years of Java/J2EE Web Application Development experience

 

* Knowledge of deploying applications via IBM Console for WebSphere
Application Servers (WAS)

 

* AIX Unix Scripting

 

* Application Development in Eclipse IDE and IBM Rational
Application Developer (RAD)

 

* Experience with IBM Rational ClearCase for source control

 

* Unix and Shell Scripting a must

 

* AWS cloud computing platform experience is a plus

 

* Be able to work as part of an Agile cross-functional team

 

* Knowledge of the Healthcare Industry and claim processing cycle
with a focus on payer Electronic Remittance Advices (ERAs)

 

* Knowledge of the Healthcare Industry and claim processing cycle
with a focus on payer Electronic Claims (837)

 

* Demonstrate solid software engineering skills and willingness to
learn new technologies

 

* Coordinate with offshore and other distributed teams to achieve
project deliverables

 

* Excellent communication skills, both verbal and written and Strong
analytical skills

 

* Have proven creative problem solving skills

 

If you have any questions, please feel free to contact me.

 

 

 

 

Thanks & Regards

 

Sunitha 

Sr.Recruiter

Sree Infotech LLC

9901 E. Valley Ranch Parkway, Suite 3008,

Irving, TX 75063

Phone: 972-332-3471 Extn 114

Email Id: suni...@sreeinfotech.com

Gtalk: archana.sreeinfo

Yahoo ID:archana.sreeinfo


Note: We respect your Online Privacy. This mail cannot be considered Spam as
long as we include contact information and a method to be removed from our
mailing list. To be removed from our mailing list, please reply with
"REMOVE" in the subject line and your email address in the body. Include
Complete Address and/or Domain/Aliases to be removed.

 

-- 
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-17101) Not able to login with chrome, chromium, opera - Only works with firefox

2014-09-30 Thread br...@whamcloud.com (JIRA)

Brian Murrell
commented on JENKINS-17101

Not able to login with chrome, chromium, opera - Only works with firefox

I have this problem also, no apache proxy involved. It happens when trying to log into jenkins directly. If I access jenkins at a different hostname then I able to log in and not get a redirect back to the log in page.

For example, if my jenkins server is at jenkins.my.example.com:8080 and I get this erroneous redirect, if I try to access it at jenkins.my:8080 (and let my resolver append example.com) then it works. This is simply because to chrome "jenkins.my.example.com" and "jenkins.my" are different servers and it stores the data from them separately.

So this smacks of a cookies problem, right? You'd think. But I have tried clearing all of the cookies in chrome for jenkins.my.example.com and the problem persists.

If I start chrome with a brand-new $HOME it also works fine.

Clearly there is something in chrome that is preventing this from working, but what? My next step would normally be to sniff the HTTP protocol between working and not working and see what is different, but alas, this is all over SSL, so that won't help.

Any other ideas?

[JIRA] [swarm] (JENKINS-21892) Swarm client fails to create slave if CSRF filter is enabled

2014-09-30 Thread peter.joens...@gmail.com (JIRA)
















































Peter Jönsson
 closed  JENKINS-21892 as Fixed


Swarm client fails to create slave if CSRF filter is enabled
















Should be fixed in version 1.17, please report back if this is not the case.





Change By:


Peter Jönsson
(30/Sep/14 5:27 PM)




Status:


Resolved
Closed





Assignee:


Kohsuke Kawaguchi
Peter Jönsson



























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] [repository-connector] (JENKINS-24896) Repoistory Connector plugin fails to resolve LATEST version

2014-09-30 Thread k.evstign...@gmail.com (JIRA)















































Kirill Evstigneev
 commented on  JENKINS-24896


Repoistory Connector plugin fails to resolve LATEST version















"LATEST" is not a valid version string for an arbitrary artifact. It works consistently for maven plugins only. See http://articles.javatalks.ru/articles/32 for some details - it is about Nexus mostly but applies to the other repository managers too.



























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-24936) Support for Stash Browser for Git plugin

2014-09-30 Thread christian.galste...@gmx.de (JIRA)















































Christian Galsterer
 started work on  JENKINS-24936


Support for Stash Browser for Git plugin
















Change By:


Christian Galsterer
(30/Sep/14 5:52 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] [core] (JENKINS-24938) On restart Jenkins rewrites some config.xml values















































Daniel Beck
 commented on  JENKINS-24938


On restart Jenkins rewrites some config.xml values















Are you manually modifying the config.xml while Jenkins is running, or is this change only your observation because your view config is reset upon restart?



























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-24938) On restart Jenkins rewrites some config.xml values















































Joseph Hughes
 commented on  JENKINS-24938


On restart Jenkins rewrites some config.xml values















Also, when I make the changes through the UI then view the xml I see what I would expect to be there, but when I restart it is gone again. It does seem to be limited to just these two config values, Views and the Slave port. Everything else persists correctly. 



























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-24938) On restart Jenkins rewrites some config.xml values















































Joseph Hughes
 commented on  JENKINS-24938


On restart Jenkins rewrites some config.xml values















I am not manually modifying the config.xml while jenkins is running. I backed up the config before I did a restart so I could compare the two files. The result is what you see above. 



























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-24938) On restart Jenkins rewrites some config.xml values















































Daniel Beck
 commented on  JENKINS-24938


On restart Jenkins rewrites some config.xml values















Is there a file named init.groovy, or a folder init.groovy.d in the Jenkins home directory? If so, what are the contents?

Is security in Jenkins enabled?



























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] [swarm] (JENKINS-7543) Set tool locations from Swarm plugin CLI

2014-09-30 Thread nico.mommae...@gmail.com (JIRA)















































Nico Mommaerts
 started work on  JENKINS-7543


Set tool locations from Swarm plugin CLI
















Change By:


Nico Mommaerts
(30/Sep/14 6:39 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] [job-dsl-plugin] (JENKINS-24939) BuildPipelineView doesn't support startsWithParameters

2014-09-30 Thread randomfreque...@gmail.com (JIRA)















































Vincent Janelle
 created  JENKINS-24939


BuildPipelineView doesn't support startsWithParameters















Issue Type:


Improvement



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


30/Sep/14 6:40 PM



Description:


The job-dsl plugin doesn't support startsWithParameters.

I was able to extend the class with:

javaposse.jobdsl.dsl.views.BuildPipelineView.metaClass.startsWithParameters = { boolean startsWithParameters = true ->
  execute {
it / methodMissing('startsWithParameters', startsWithParameters)
  }
}




Project:


Jenkins



Priority:


Minor



Reporter:


Vincent Janelle

























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-24931) BuildTriggers and ReverseBuildTriggers constantly vanishing















































Daniel Beck
 commented on  JENKINS-24931


BuildTriggers and ReverseBuildTriggers constantly vanishing















Install JobConfigHistory Plugin and check which user does it.

Also, it may likely be users who are editing the job in question but have no permission to view (reverse build trigger) or build (forward build trigger) the linked job.



























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-24929) POSTed menu items triggered from dropdown menu fail due to crumb check















































Daniel Beck
 updated  JENKINS-24929


POSTed menu items triggered from dropdown menu fail due to crumb check
















Also affects e.g. Manage Jenkins » Reload Configuration. Updated issue title to match.





Change By:


Daniel Beck
(30/Sep/14 6:50 PM)




Summary:


Deleting job via
POSTed menu items triggered from
 dropdown menu
 in job list fails
 fail
 due to crumb
 issues
 check



























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-24938) On restart Jenkins rewrites some config.xml values















































Joseph Hughes
 commented on  JENKINS-24938


On restart Jenkins rewrites some config.xml values















Security is enabled. I am using Jenkins user database along with the Role Strategy Plugin. https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin

I do not see any init.groovy or a init.groovy.d folder 



























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-24938) On restart Jenkins rewrites some config.xml values















































Daniel Beck
 commented on  JENKINS-24938


On restart Jenkins rewrites some config.xml values















Is JobConfigHistory plugin installed, and if so, does it record changes to the global config.xml? Which user is specified?



























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] [p4] (JENKINS-24203) SCM Polling Throwing an exception

2014-09-30 Thread mr...@sjm.com (JIRA)















































Michael Rose
 commented on  JENKINS-24203


SCM Polling Throwing an exception















I am also seeing this problem. I am running Jenkins version 1.580 and P4 plugin version 1.0.14.


Started on Sep 29, 2014 11:19:01 PM
Polling SCM changes on sjmdev3
P4: Polling with client: jenkins-sjmdev3-velocity-alpha-complete
ERROR: Failed to record SCM polling for hudson.matrix.MatrixProject@2e8c04a[velocity-alpha-complete]
java.lang.NullPointerException
	at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1451)
	at hudson.model.AbstractProject._poll(AbstractProject.java:1421)
	at hudson.model.AbstractProject.poll(AbstractProject.java:1332)
	at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544)
	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)



























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] [analysis-collector] (JENKINS-24940) New Warnings link in Static Analysis results shows all warnings

2014-09-30 Thread kevin.form...@gmail.com (JIRA)















































Kevin Formsma
 created  JENKINS-24940


New Warnings link in Static Analysis results shows all warnings















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


analysis-collector, analysis-core



Created:


30/Sep/14 8:07 PM



Description:


In my views for static analysis results, I get links for 'New Warnings', yet clicking on these links brings up a view with all warnings not just the filtered new warnings.

This occurs for both the collector view and individual PMD, Checkstyle, etc views.

These urls for example, show the same thing:
https://jenkins.../job/analysis/826/analysisResult/new/ 
https://jenkins.../job/analysis/826/analysisResult/




Environment:


Jenkins 1.581

analysis-core 1.59

analysis-collector 1.41




Project:


Jenkins



Priority:


Major



Reporter:


Kevin Formsma

























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-24938) On restart Jenkins rewrites some config.xml values















































Joseph Hughes
 commented on  JENKINS-24938


On restart Jenkins rewrites some config.xml values















It is not installed... but if it would be helpful I could install 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-5318) Allow default view at user level

2014-09-30 Thread lnguyen...@gmail.com (JIRA)















































Linh N
 commented on  JENKINS-5318


Allow default view at user level















I vote for this feature as well. Much needed!



























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-24931) BuildTriggers and ReverseBuildTriggers constantly vanishing















































Johannes Wienke
 commented on  JENKINS-24931


BuildTriggers and ReverseBuildTriggers constantly vanishing















We have that plugin installed and there is never a change recorded that causes this. Neither in the upstream nor in the downstream job.



























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-24939) BuildPipelineView doesn't support startsWithParameters

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
















































Daniel Spilker
 resolved  JENKINS-24939 as Fixed


BuildPipelineView doesn't support startsWithParameters
















Will be released in 1.26.





Change By:


Daniel Spilker
(30/Sep/14 8:48 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-24939) BuildPipelineView doesn't support startsWithParameters















































SCM/JIRA link daemon
 commented on  JENKINS-24939


BuildPipelineView doesn't support startsWithParameters















Code changed in jenkins
User: Vincent Janelle
Path:
 job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/views/BuildPipelineView.groovy
 job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/views/BuildPipelineViewSpec.groovy
http://jenkins-ci.org/commit/job-dsl-plugin/4d10977a159d90e08e575d5aaac2c553914c03dc
Log:
  Add startsWithParameters to BuildPipelineView

JENKINS-24939

The currently BuildPipelineView plugin does not support the
startsWithParameters option.  If you use parameterized builds, you can't
trigger builds.





























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-20882) Java error when we try to update Jenkins from 1.539 to new one















































Daniel Beck
 updated  JENKINS-20882


Java error when we try to update Jenkins from 1.539 to new one
















Does this issue still occur?





Change By:


Daniel Beck
(30/Sep/14 8:53 PM)




Labels:


jna



























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-19771) Fresh LTS installation uses non-LTS update site
















































Daniel Beck
 resolved  JENKINS-19771 as Cannot Reproduce


Fresh LTS installation uses non-LTS update site
















Not (or no longer) a problem, as a different update center JSON is served if the version passed in the parameter is an LTS version.

Compare:
https://updates.jenkins-ci.org/update-center.json?version=1.565.2
https://updates.jenkins-ci.org/update-center.json





Change By:


Daniel Beck
(30/Sep/14 8:55 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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-21677) Jenkins becomes unresponsive from time to time
















































Daniel Beck
 resolved  JENKINS-21677 as Incomplete


Jenkins becomes unresponsive from time to time
















There is not enough information here to investigate further. E.g. thread dumps would be interesting (e.g. using kill -3 ). Therefore resolving this as incomplete.

Also, please note that JIRA is a bug tracker, and nowhere does this indicate this is a bug. Troubleshooting problems like this is best done in a more conversational medium, e.g. on IRC, or maybe even the jenkinsci-users mailing list.





Change By:


Daniel Beck
(30/Sep/14 8:59 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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] [remoting] (JENKINS-13253) Slave connection reset issues since 1.456















































Daniel Beck
 updated  JENKINS-13253


Slave connection reset issues since 1.456
















Change By:


Daniel Beck
(30/Sep/14 9:00 PM)




Component/s:


remoting





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] [remoting] (JENKINS-17003) JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect















































Daniel Beck
 updated  JENKINS-17003


JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect
















Change By:


Daniel Beck
(30/Sep/14 9:01 PM)




Component/s:


remoting





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] [remoting] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel















































Daniel Beck
 updated  JENKINS-6817


FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
















Change By:


Daniel Beck
(30/Sep/14 9:01 PM)




Component/s:


remoting





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] [core] (JENKINS-12787) LOADING overlay does not go away on the Configure System page