[JIRA] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger

2014-09-25 Thread martin.me...@inftec.ch (JIRA)














































Martin Meyer
 created  JENKINS-24860


Allow to disable build trigger















Issue Type:


Improvement



Assignee:


huybrechts



Components:


parameterized-trigger



Created:


25/Sep/14 6:02 AM



Description:


Problem

Currently, it is not possible to just disable a parameterized trigger, so the workaround is to either set the projects to build to disabled or to completely delete the trigger.

Suggestion / Feature Request

Could you add an entry to Trigger when build is to simply disable the trigger, e.g. Disabled (never triggered)?




Project:


Jenkins



Priority:


Trivial



Reporter:


Martin Meyer

























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-22639) Configuration for CloudSlaves Ephemeral Nodes is persisted

2014-09-25 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22639


Configuration for CloudSlaves  Ephemeral Nodes is persisted















Code changed in jenkins
User: Stefan Brausch
Path:
 src/main/java/hudson/plugins/jobConfigHistory/ComputerHistoryListener.java
http://jenkins-ci.org/commit/jobConfigHistory-plugin/e9c4b003463a7aff44b71eee5560858bfb70520f
Log:
  Merge pull request #27 from jenkinsci/ephemeral

JENKINS-22639 Don't record changes to AbstractCloudSlaves or Ephemeral Nodes


Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/ba17efff74b2...e9c4b003463a




























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] [artifactory] (JENKINS-23795) error connecting jenkins to artifactory

2014-09-25 Thread sunil.ga...@mastek.com (JIRA)














































sunil garje
 commented on  JENKINS-23795


error connecting jenkins to artifactory















I am facing the same issue checked Maven and JDK installation its correct but then also facing this issue please help.



























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-22639) Configuration for CloudSlaves Ephemeral Nodes is persisted

2014-09-25 Thread stefan.brau...@1und1.de (JIRA)















































Stefan Brausch
 resolved  JENKINS-22639 as Fixed


Configuration for CloudSlaves  Ephemeral Nodes is persisted
















Available in version 2.10.
Thanks Ryan and Jesse





Change By:


Stefan Brausch
(25/Sep/14 6:35 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] [artifactory] (JENKINS-23795) error connecting jenkins to artifactory

2014-09-25 Thread sunil.ga...@mastek.com (JIRA)














































sunil garje
 commented on  JENKINS-23795


error connecting jenkins to artifactory















Solution for this is As a workaround save the configuration page and re-enter "Configure System". Now when you try the "Test Connection" it will show the Artifactory that you are connected to.



























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] [warnings] (JENKINS-22386) Warnings Plugin cannot show details for MSBuild warnings

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














































davida2009
 commented on  JENKINS-22386


Warnings Plugin cannot show details for MSBuild warnings















This problem still manifests itself in Warnings plugin 4.42.



























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] [monitoring] (JENKINS-24838) Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context

2014-09-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-24838


Monitoring Plugin links from slaves are incorrect when Jenkins deployed with a context
















Not a blocker, and it's trivial to work around.





Change By:


Daniel Beck
(25/Sep/14 7:41 AM)




Priority:


Blocker
Minor



























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







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


[JIRA] [ldap] (JENKINS-24859) LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security

2014-09-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-24859


LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security
















Change By:


Daniel Beck
(25/Sep/14 7:44 AM)




Assignee:


stephenconnolly
KohsukeKawaguchi





Component/s:


ldap





Component/s:


credentials



























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







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


[JIRA] [master-slave] (JENKINS-18205) Archiving Artifacts slow with Windows JNLP Slave

2014-09-25 Thread rgg...@gmail.com (JIRA)














































rggjan
 commented on  JENKINS-18205


Archiving Artifacts slow with Windows JNLP Slave















Same problem here, happens for a linux jenkins with a Mac OS X slave. Archiving ~100MB of data takes 10 minutes, while copying it manually over the network only takes around 10 econds...



























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







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


[JIRA] [master-slave] (JENKINS-18205) Archiving Artifacts slow with Windows JNLP Slave

2014-09-25 Thread rgg...@gmail.com (JIRA)














































rggjan
 commented on  JENKINS-18205


Archiving Artifacts slow with Windows JNLP Slave















Might be a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-18276 ?



























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-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+

2014-09-25 Thread rgg...@gmail.com (JIRA)














































rggjan
 commented on  JENKINS-18276


Archiving artifacts from a slave node is extremely slow even with 1.509.1+















Same problem here, happens for a linux jenkins with a Mac OS X slave. Archiving ~100MB of data takes 10 minutes, while copying it manually over the network only takes around 10 econds...
Jenkins ver. 1.565.2



























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







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


[JIRA] [text-finder] (JENKINS-3612) Allow text-finder plugin to carry out multiple searches.

2014-09-25 Thread tim-christian.bl...@elaxy.de (JIRA)














































Tim-Christian Bloss
 commented on  JENKINS-3612


Allow text-finder plugin to carry out multiple searches.















This would also be very helpfull for our complex automated remote deployment tasks.

Should be possible to trigger different behaviour based on console output:

	deployment successfull but application not working - unstable, developers have to fix this
	deployment failed - fail the build, admins have to track down the 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] [credentials] (JENKINS-21051) Add new credential plugin displays help text in Japanese characters

2014-09-25 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-21051


Add new credential plugin displays help text in Japanese characters















Code changed in jenkins
User: Afriza N. Arief
Path:
 src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/FileOnMasterKeyStoreSource/help-keyStoreFile.html
 src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/FileOnMasterKeyStoreSource/help-keyStoreFile_ja.html
http://jenkins-ci.org/commit/credentials-plugin/0679ab506a54f1871adb233b5f641b3dcdc051ed
Log:
  FIXED JENKINS-21051 fix inverted English-Japanese translation





























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







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


[JIRA] [credentials] (JENKINS-21051) Add new credential plugin displays help text in Japanese characters

2014-09-25 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-21051


Add new credential plugin displays help text in Japanese characters















Code changed in jenkins
User: Harald Albers
Path:
 src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/FileOnMasterKeyStoreSource/help-keyStoreFile.html
 src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/FileOnMasterKeyStoreSource/help-keyStoreFile_ja.html
http://jenkins-ci.org/commit/credentials-plugin/c9f15648e4a8c9e409370a2fb35a6a38fd57a09a
Log:
  Merge pull request #14 from afriza/master

FIXED JENKINS-21051 fix inverted English-Japanese translation


Compare: https://github.com/jenkinsci/credentials-plugin/compare/a95668277144...c9f15648e4a8




























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] [clearcase-ucm] (JENKINS-24861) Print warning in console log when version path gets long

2014-09-25 Thread m...@praqma.net (JIRA)














































Mads Nielsen
 created  JENKINS-24861


Print warning in console log when version path gets long















Issue Type:


Improvement



Assignee:


Praqma Support



Components:


clearcase-ucm



Created:


25/Sep/14 8:17 AM



Project:


Jenkins



Priority:


Minor



Reporter:


Mads Nielsen

























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







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


[JIRA] [credentials] (JENKINS-21051) Add new credential plugin displays help text in Japanese characters

2014-09-25 Thread afriza...@gmail.com (JIRA)















































Afriza Noor Arief
 closed  JENKINS-21051 as Fixed


Add new credential plugin displays help text in Japanese characters
















fixed in commit 0679ab506a54f1 and merged in commit c9f15648e4a8c9





Change By:


Afriza Noor Arief
(25/Sep/14 8:17 AM)




Status:


Resolved
Closed



























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







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


[JIRA] [plugin] (JENKINS-24862) Allow Textfinder to optionally change failed builds to unstable

2014-09-25 Thread tim-christian.bl...@elaxy.de (JIRA)














































Tim-Christian Bloss
 created  JENKINS-24862


Allow Textfinder to optionally change failed builds to unstable















Issue Type:


Improvement



Assignee:


drlewis



Components:


plugin, text-finder



Created:


25/Sep/14 8:22 AM



Description:


Background:

We have many very complex automated deployment tasks which get started using "Send Files or execute commands over SSH", calling some bash shell scripts on one target system connecting to other systems (database, loadbalancer...).

We use the "Editable Email Notification" to get informed about success and failulre of the builds/deployments.


Our problem:

We must use the option "Fail the build if an error occurs" for the SSH remote access, in order to catch up all errors.

In certain condition, when exectly one text message (echo) gets printed when the build fails, we know for sure it is no deployment/admin failure but definately an application/development issue.

If the message occurs during "successfull" builds, the developrs can get an automated email, informing them about the not successfully starting up application.

If the message occurs during a build that "failed" due to some application startup issues, the developers do not get immediately informed about the issue, and the system administrators have to dig into the logs, just to find out deployment failed due to some regression.


What would solve this for us:

It would be very nice to have an additional option (separate checkbox, unchecked by default to retain current plugin behaviour) to change even a "failed" build to "unstable" if a specific text pattern occurs in the logs.




Environment:


Jenkins 1.554.3, Debian GNU/Linux 7, AMD64, Tomcat 7, Oracle JRE 7u67




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Tim-Christian Bloss

























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] [plugin] (JENKINS-24862) Allow Textfinder to optionally change failed builds to unstable

2014-09-25 Thread tim-christian.bl...@elaxy.de (JIRA)














































Tim-Christian Bloss
 updated  JENKINS-24862


Allow Textfinder to optionally change failed builds to unstable
















Change By:


Tim-Christian Bloss
(25/Sep/14 8:28 AM)




Description:


Background:WehavemanyverycomplexautomateddeploymenttaskswhichgetstartedusingSendFilesorexecutecommandsoverSSH,callingsomebashshellscriptsononetargetsystemconnectingtoothersystems(database,loadbalancer...).WeusetheEditableEmailNotificationtogetinformedaboutsuccessand
failulre
failure
ofthebuilds/deployments.Ourproblem:WemustusetheoptionFailthebuildifanerroroccursfortheSSHremoteaccess,inordertocatchupallerrors.Incertaincondition,whenexectlyonetextmessage(echo)getsprintedwhenthebuildfails,weknowforsureitisnodeployment/adminfailurebutdefinatelyanapplication/developmentissue.Ifthemessageoccursduringsuccessfullbuilds,thedeveloprscangetanautomatedemail,informingthemaboutthenotsuccessfullystartingupapplication.Ifthemessageoccursduringabuildthatfailedduetosomeapplicationstartupissues,thedevelopersdonotgetimmediatelyinformedabouttheissue,andthesystemadministratorshavetodigintothelogs,justtofindoutdeploymentfailedduetosomeregression.Whatwouldsolvethisforus:Itwouldbeverynicetohaveanadditionaloption(separatecheckbox,uncheckedbydefaulttoretaincurrentpluginbehaviour)tochangeevenafailedbuildtounstableifaspecifictextpatternoccursinthelogs.
EDIT:Spellingcorrected



























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







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


[JIRA] [matrix-auth] (JENKINS-15464) Matrix-based security -Job cancel privilege not working

2014-09-25 Thread ogon...@gmail.com (JIRA)














































Oliver Gondža
 updated  JENKINS-15464


 Matrix-based security -Job cancel privilege not working
















Change By:


Oliver Gondža
(25/Sep/14 8:28 AM)




Component/s:


matrix-auth





Component/s:


matrix



























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-24454) Windows GIT SCM fetch code hung

2014-09-25 Thread sharon....@emc.com (JIRA)














































sharon xia
 updated  JENKINS-24454


Windows GIT SCM fetch code hung
















Change By:


sharon xia
(25/Sep/14 8:43 AM)




Summary:


WindowsGITSCM
Polling
fetchcode
hung





Description:


Wemetrandomlyfailureofgitscm
polling
,ithungatthefetchprocessforalongtimeandwilltimeout.Whenittimeoutitsays02:56:20Causedby:hudson.plugins.git.GitException:Commandgitfetch--tags--progreh://bmcdiags@*.*.*.*/ghts/ta+refs/heads/*:refs/remotes/origin/*returnedstatuscode-1:02:56:20stdout:02:56:20stderr:Couldnotcreatedirectoryc/Users/Administrator/.ssh.



























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-24454) Windows GIT SCM fetch code hung

2014-09-25 Thread sharon....@emc.com (JIRA)














































sharon xia
 commented on  JENKINS-24454


Windows GIT SCM fetch code hung















It has two symptoms:
1. When multiple jobs fetching git code at the same time, e.g. set these jobs with the same GIT SCM code repository, we will randomly meet this issue. However, next time you kicked off the build, it will not have this issue.
2. The build always failed with the same message. You have to restart jenkins slave to resolve this issue. We observed there are a lot of git process in process management console.



























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] [configurationslicing] (JENKINS-24863) Please add support for the text-finder plugin

2014-09-25 Thread tim-christian.bl...@elaxy.de (JIRA)














































Tim-Christian Bloss
 created  JENKINS-24863


Please add support for the text-finder plugin















Issue Type:


Improvement



Assignee:


mdonohue



Components:


configurationslicing



Created:


25/Sep/14 9:05 AM



Description:


Hi,

would be nice if you could add support for the text-finder plugin.
https://wiki.jenkins-ci.org/display/JENKINS/Text-finder+Plugin

Would definately help us to modify our checks after builds, without using bash scripts (wrapping cat,grep,find,sed) as we do by now.




Environment:


all




Project:


Jenkins



Priority:


Minor



Reporter:


Tim-Christian Bloss

























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] [discard-old-build] (JENKINS-24799) Plugin removes the logs but the job directory still remains

2014-09-25 Thread cosmin.malu...@softvision.ro (JIRA)














































Cosmin Malutan
 commented on  JENKINS-24799


Plugin removes the logs but the job directory still remains















This has already been fixed in https://github.com/jenkinsci/discard-old-build-plugin/commit/e05d0e3021e08399910ded0bdb6639f413276ab4
All we need now is a new release.



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread philipp.marek+jenk...@linbit.com (JIRA)














































Philipp Marek
 created  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















Issue Type:


Bug



Assignee:


Nicolas De Loof



Attachments:


stacktrace.txt



Components:


git-client



Created:


25/Sep/14 9:21 AM



Description:


Enabling the Git Client plugin gives an error in the "/configure" URL, see the attached file.




Environment:


Jenkins ver. 1.565.2, on Debian wheezy/sid, amd64

Git client plugin 1.10.2




Project:


Jenkins



Labels:


plugin




Priority:


Critical



Reporter:


Philipp Marek

























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] [ldap] (JENKINS-24859) LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security

2014-09-25 Thread stephenconno...@java.net (JIRA)














































stephenconnolly
 commented on  JENKINS-24859


LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security















See https://github.com/jenkinsci/ldap-plugin/commit/6ab61de8a9408e8741c5187c33b768b75ff83c44

We are awaiting a LTS release that has the https://github.com/jenkinsci/jenkins/commit/554e087a0a64007fa4a251d1de1d32e5eaeb812e change in it before we push the ldap plugin changes that allow selecting the case sensitivity strategy for the field that you use as username



























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-trigger] (JENKINS-24860) Allow to disable build trigger

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














































ikedam
 commented on  JENKINS-24860


Allow to disable build trigger















Conditional Buildstep and Flexible Publish help 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] [credentials] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.

2014-09-25 Thread jhofmeis...@gmx.de (JIRA)














































Jennifer Hofmeister
 commented on  JENKINS-22542


Subversion polling not work with externals or variables in URL -  E200015: No credential to try.















I've been experiencing the error with every checkout attempt, not only externals, and it's persistent. Windows 7 master and slaves. Jenkins 1.565.2 (official latest stable) and Subversion 2.4.3. I decided to upgrade from 1.561/2.0 after encountering some SVN external issues that suddenly occurred (J refused to check out and then complained things were missing).

Although it seems like a pure Subversion issue, downgrading Subversion plugin to 2.0 and 1.5.4 didn't help. Eventually, I upgraded it back to 2.4.3 and manually reconfigured all affected jobs in the above way ... but needless to say, that was a drag^^ 



























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-24851) downstreamParameterized step does not block on completion of downstream job

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














































ikedam
 updated  JENKINS-24851


downstreamParameterized step does not block on completion of downstream job
















That's an issue of job-dsl.





Change By:


ikedam
(25/Sep/14 10:27 AM)




Component/s:


parameterized-trigger



























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















Can you provide some further details?

For example, was this a fresh install of Jenkins 1.565.2 on Debian, from the Debian package, followed immediately by an installation of only the git-client-plugin 1.10.2?

Did you restart Jenkins after installing the git-client-plugin?

Did you install any other plugins?

Did you perform any other steps or have any other plugins installed that might be relevant?

What were you intending to accomplish by installing the git client plugin without installing the git plugin, or did you also install the git plugin at the same time?

Is the "git server plugin" installed (it is not needed, and has had some problems in the past)?

Is the multi-SCMs plugin installed, and if so, what version number?  It has also had some interaction problems with the git client plugin?



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 assigned  JENKINS-24864 to Mark Waite



java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild
















Change By:


Mark Waite
(25/Sep/14 11:04 AM)




Assignee:


NicolasDeLoof
MarkWaite



























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] [cmakebuilder] (JENKINS-24865) cmakebuilder removes backslash from $WORKSPACE

2014-09-25 Thread armin.no...@thincast.com (JIRA)














































armin novak
 created  JENKINS-24865


cmakebuilder removes backslash from $WORKSPACE















Issue Type:


Bug



Assignee:


Unassigned


Components:


cmakebuilder



Created:


25/Sep/14 11:15 AM



Description:


Trying to set CMAKE defines in 	Other CMake Arguments using $WORKSPACE

Example:
Assume $WORKSPACE=c:\foo\bar

Setting
-DOPENSSL_INCLUDE_DIR=$WORKSPACE

When run, the path is c:foobar




Environment:


Jenkins 1.581

Windows 8.1, 64 bit

cmakebuilder 1.9






Project:


Jenkins



Priority:


Major



Reporter:


armin novak

























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-16213) the downstream build result was not updated correctly when it is triggered by multiple builds

2014-09-25 Thread kari.sivo...@nsn.com (JIRA)















































Kari Sivonen
 assigned  JENKINS-16213 to Kari Sivonen



the downstream build result was not updated correctly when it is triggered by multiple builds 
















Change By:


Kari Sivonen
(25/Sep/14 11:37 AM)




Assignee:


liwei
KariSivonen



























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-16213) the downstream build result was not updated correctly when it is triggered by multiple builds

2014-09-25 Thread kari.sivo...@nsn.com (JIRA)














































Kari Sivonen
 commented on  JENKINS-16213


the downstream build result was not updated correctly when it is triggered by multiple builds 















To do this more cleaver, I take example from copy artifact plugin where is introduced global and job's parameter upstreamFilterStrategy. In Global parameter there is options UseOldest and UseNewest. In job configuration there is als option UseGlobalSetting. Depending selection latest or oldest job is promoted.



























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread philipp.marek+jenk...@linbit.com (JIRA)














































Philipp Marek
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















I had 1.509 installed, then tried to update. This went wrong, so I moved /var/lib/jenkins aside and reinstalled jenkins.

 Did you restart Jenkins after installing the git-client-plugin?
IIRC it did ask to be restarted anyway.

 Did you install any other plugins?
Yes, these ones:
 credentials git-client git git-parameter instant-messaging ircbot
 ldap mailer scm-api ssh-credentials ssh

 Did you perform any other steps or have any other plugins installed that might be relevant?
See above.

 What were you intending to accomplish by installing the git client plugin without installing the git plugin, or did you also install the git plugin at the same time?
git plugin was installed.

 Is the "git server plugin" installed (it is not needed, and has had some problems in the past)?
no.

 Is the multi-SCMs plugin installed, and if so, what version number? It has also had some interaction problems with the git client plugin?
See the above list. scm-api, if that is what you mean, is 0.2.


I verified that the problem disappears if I disable the "git-client" plugin, and restart jenkins.
No further changes were necessary.


Due to other problems I went back to 1.509, though.




























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-22514) Zip generated from all files in zip contains the wrong slashes

2014-09-25 Thread jenk...@voormann.de (JIRA)














































Holger Voormann
 commented on  JENKINS-22514


Zip generated from all files in zip contains the wrong slashes















@Daniel You are probably right, but ZipArchiver is a different issue. And you are right, this issue has been introduced in 1.532 (see your comment from May). This commit will fix this issue. Could you verify and apply 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] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters

2014-09-25 Thread judo...@gmail.com (JIRA)














































Ole Christian Langfjæran
 commented on  JENKINS-24750


Cannot find user credentials when job is triggered with parameters















Jenkins: 1.580
Parameterized trigger: 2.25
SSH-Agent: 1.5
Authorize project: 1.0.3

If I uncheck "Configure Build Authorization" then it fails with the same output. But of course this time the "Running as Superman" is not printed/run.

I could elaborate on why I'd like it to work.
Every developer has his own public ssh-key on app-servers
Every developer adds his private key to his user
When promoting a build the developer must choose a valid ssh-private-key
This key is sent to a deploy job
Ssh-agent uses the deploy-key and voila.

This works well for Global keys or if the deploy job itself is invoked by a logged in user.

A workaround might be to restrict the number of users authorized to run the deploy 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] [swarm] (JENKINS-20668) Persist Jenkins swarm slaves when they go offline

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














































Nico Mommaerts
 commented on  JENKINS-20668


Persist Jenkins swarm slaves when they go offline















Another use case for persisting swarm slave info is when you configure the slave (eg add tool locations). When a network hiccup occurs the slave automatically reconnects, but lost all its configuration.



























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







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


[JIRA] [jira] (JENKINS-24331) [JIRA Plugin] Progress JIRA issue by workflow action does not work if field is required

2014-09-25 Thread rjrome...@gmail.com (JIRA)














































Rodolfo Romero
 commented on  JENKINS-24331


[JIRA Plugin] Progress JIRA issue by workflow action does not work if field is required















That works if you have Admin access to the JIRA instance but that is not my case and I'm sure many people cannot modify workflows due to permissions restrictions.



























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-20035) see exclusively and possible assigned jobs (by tags) in node view

2014-09-25 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 resolved  JENKINS-20035 as Fixed


see exclusively and possible assigned jobs (by tags) in node view
















Covered by v2 of Label Linked Jobs Plugin





Change By:


Dominique Brice
(25/Sep/14 1:01 PM)




Status:


InProgress
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] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies

2014-09-25 Thread ohtake_tomoh...@java.net (JIRA)














































OHTAKE Tomohiro
 created  JENKINS-24866


github-oauth does not work behind proxies nor authentication proxies















Issue Type:


Bug



Assignee:


OHTAKE Tomohiro



Components:


github-oauth



Created:


25/Sep/14 1:01 PM



Description:


github-oauth merged jenkinsci/github-oauth-plugin#15 and now uses jenkins proxy configuration jenkinsci/github-oauth-plugin@09dc928f24a633cd5dc41033be3196e6eb47b325.

But proxy support is incomplete.


	It does not work behind non-authentication proxies, because github-api does not support proxies in some cases. (kohsuke/github-api#109 and kohsuke/github-api#124)
	It does not support authentication proxies.







Environment:


github-oauth-0.19

Jenkins 1.581

OpenJDK 7u65-2.5.2-3~14.04

Ubuntu 14.04.1 LTS x86_64




Project:


Jenkins



Priority:


Minor



Reporter:


OHTAKE Tomohiro

























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] [label-linked-jobs] (JENKINS-24615) Labels Dashboard in label-linked-jobs plugin

2014-09-25 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 closed  JENKINS-24615 as Fixed


Labels Dashboard in label-linked-jobs plugin
















Covered by v2 of Label Linked Jobs Plugin





Change By:


Dominique Brice
(25/Sep/14 1:00 PM)




Status:


Resolved
Closed



























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







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


[JIRA] [label-linked-jobs] (JENKINS-24615) Labels Dashboard in label-linked-jobs plugin

2014-09-25 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 resolved  JENKINS-24615 as Fixed


Labels Dashboard in label-linked-jobs plugin
















Covered by v2 of Label Linked Jobs Plugin





Change By:


Dominique Brice
(25/Sep/14 1:00 PM)




Status:


InProgress
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] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies

2014-09-25 Thread ohtake_tomoh...@java.net (JIRA)














































OHTAKE Tomohiro
 started work on  JENKINS-24866


github-oauth does not work behind proxies nor authentication proxies
















Change By:


OHTAKE Tomohiro
(25/Sep/14 1:02 PM)




Status:


Open
InProgress



























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-agent] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters

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














































ikedam
 updated  JENKINS-24750


Cannot find user credentials when job is triggered with parameters
















Change By:


ikedam
(25/Sep/14 1:01 PM)




Component/s:


authorize-project



























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] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies

2014-09-25 Thread ohtake_tomoh...@java.net (JIRA)














































OHTAKE Tomohiro
 updated  JENKINS-24866


github-oauth does not work behind proxies nor authentication proxies
















Change By:


OHTAKE Tomohiro
(25/Sep/14 1:03 PM)




Description:


github-oauthmerged[jenkinsci/github-oauth-plugin#15|https://github.com/jenkinsci/github-oauth-plugin/pull/15]andnowusesjenkinsproxyconfiguration[jenkinsci/github-oauth-plugin@09dc928f24a633cd5dc41033be3196e6eb47b325|https://github.com/jenkinsci/github-oauth-plugin/commit/09dc928f24a633cd5dc41033be3196e6eb47b325].Butproxysupportisincomplete.#Itdoesnotworkbehindnon-authenticationproxies,becausegithub-apidoesnotsupportproxiesinsomecases.([kohsuke/github-api#109|https://github.com/kohsuke/github-api/issues/109]and[kohsuke/github-api#124|https://github.com/kohsuke/github-api/pull/124])#Itdoesnot
respectJenkinsnoProxyHost.#Itdoesnot
supportauthenticationproxies.



























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] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies

2014-09-25 Thread ohtake_tomoh...@java.net (JIRA)














































OHTAKE Tomohiro
 commented on  JENKINS-24866


github-oauth does not work behind proxies nor authentication proxies















I have create a pull request. https://github.com/jenkinsci/github-oauth-plugin/pull/30



























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] [copy-to-slave] (JENKINS-24867) CopyToSlave Git files cannot be copied

2014-09-25 Thread shaun.ad...@metoffice.gov.uk (JIRA)














































Shaun Adams
 created  JENKINS-24867


CopyToSlave Git files cannot be copied















Issue Type:


Bug



Assignee:


Vivekanand SV



Components:


copy-to-slave



Created:


25/Sep/14 1:20 PM



Description:


When copying from on slave to master .git folders and .gitignore files are not being copied to the master




Environment:


Jenkins Jenkins ver. 1.554.1

Copy to slave 1.4.3 

Linux platforms




Project:


Jenkins



Labels:


plugin




Priority:


Minor



Reporter:


Shaun Adams

























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] [checkstyle] (JENKINS-17287) Provide support for ScalaStyle warnings

2014-09-25 Thread sergej.schm...@uni-ulm.de (JIRA)














































sergej schmidt
 reopened  JENKINS-17287


Provide support for ScalaStyle warnings
















Problem mentioned in last comments still seems to exist in current version of the plugin. Checkstyle seems to not recognize ScalaStyle warnings. To reproduce the issue you could use the version 0.5.0 of ScalaStyle and Scala version 2.11.2. I think this is a generic Scala problem so code of an arbitary github project would do the trick to reproduce the issue. Contact me if you need any other info or support. thx





Change By:


sergej schmidt
(25/Sep/14 1:55 PM)




Resolution:


CannotReproduce





Status:


Resolved
Reopened



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















Your original report says "enabling the plugin".  Which plugins are enabled and which are disabled in the problem environment?

There have been cases where users reported that the git plugin was not working.  At least one of those cases was caused because the user disabled the credentials plugin.  The credentials plugin must be enabled for the git client plugin and the git plugin to operate.  

Unfortunately, if the credentials plugin is disabled, the core messages are not as helpful as one would hope.  If I recall correctly, there isn't anything obvious in the message which warns that the user may have disabled a critical infrastructure plugin (like credentials).



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread philipp.marek+jenk...@linbit.com (JIRA)














































Philipp Marek
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















No, AFAIR I didn't run into that problem.

I could trigger the error by just enabling/disabling the Git Client plugin (and restarting jenkins); "credentials" was enabled all the time.



























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread ricardo.riba...@gmail.com (JIRA)












































 
Ricardo Ribalda
 edited a comment on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild
















Apparently hudson.matrix classes were removed from jenkins on 4aad749cbe282ef33134ea924a4e547c4767ca07

https://github.com/jenkinsci/jenkins/commit/4aad749cbe282ef33134ea924a4e547c4767ca07

but it is still used by the plugin


ricardo@neopili:/tmp/git-plugin$ git grep hudson.matrix
src/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixAggregatable;
src/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixAggregator;
src/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixBuild;
src/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixRun;
src/main/java/hudson/plugins/git/GitSCM.java:import hudson.matrix.MatrixBuild;
src/main/java/hudson/plugins/git/GitSCM.java:import hudson.matrix.MatrixRun;
src/test/java/hudson/plugins/git/AbstractGitTestCase.java:import hudson.matrix.MatrixBuild;
src/test/java/hudson/plugins/git/AbstractGitTestCase.java:import hudson.matrix.MatrixProject;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.Axis;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.AxisList;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.MatrixBuild;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.MatrixProject;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.Axis;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.AxisList;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.MatrixBuild;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.MatrixProject;
ricardo@neopili:/tmp/git-plugin$ 





























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







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


[JIRA] [hp-application-automation-tools-plugin] (JENKINS-19374) issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run mach

2014-09-25 Thread marlene.macdon...@adp.com (JIRA)














































Marlene Macdonald
 updated  JENKINS-19374


issue with HP Application Automation Tools plugin - error: Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://Almserver:Portnumber/qcbin/TDConnectivity_index.html 
















Change By:


Marlene Macdonald
(25/Sep/14 3:30 PM)




Description:


HiAll,wearefacingtheattachederrorwhentriedtoexecutethehptestscriptsunderhpALM(Version11.0)fromjenkins(Version1.476)usingHPApplicationAutomationToolsplugin(currentVersion).ReferringsolutionfromJENKINS-16464issue(https://issues.jenkins-ci.org/browse/JENKINS-16464)Ihadalsotriedafterdownloadingcontentfromurl(http://AlmServer:8080/qcbin/start_a.jsp?common=true)butsameerrorrepeated.Thanksinadvance,anyhelpisverymuchappreciatedandpleasecommentifanyfurtherinfoisneededontheissue,Update:ErrorisalsooccurringinourenvironmentonALM11.52sincepatch4wasinstalled.Itwasworkingfinebeforeinstallingpatch4.WehavetestedonJenkinsversion1.517andversion1.581withtheHPApplicationAutomationToolspluginversion3.0.5.
Additionalinformation:TheEventViewerontheJenkinsserverreportsanapplicationerrorwithwexectrl.exe,version11.52.536.0.Pleaseseeattachmentforfurtherdetail.





Attachment:


eventviewererror.png



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















I think that disabling the git client plugin would require that you also disable plugins which depend on that client being enabled (like the git plugin).  Did you disable all plugins which depend on the git client plugin, or only the git client plugin?



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread ricardo.riba...@gmail.com (JIRA)














































Ricardo Ribalda
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















Apparently hudson.matrix classes were removed from jenkins on 4aad749cbe282ef33134ea924a4e547c4767ca07

https://github.com/jenkinsci/jenkins/commit/4aad749cbe282ef33134ea924a4e547c4767ca07

but it is still used by the pluginsrc/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixAggregatable;
src/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixAggregator;
src/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixBuild;
src/main/java/hudson/plugins/git/GitPublisher.java:import hudson.matrix.MatrixRun;
src/main/java/hudson/plugins/git/GitSCM.java:import hudson.matrix.MatrixBuild;
src/main/java/hudson/plugins/git/GitSCM.java:import hudson.matrix.MatrixRun;
src/test/java/hudson/plugins/git/AbstractGitTestCase.java:import hudson.matrix.MatrixBuild;
src/test/java/hudson/plugins/git/AbstractGitTestCase.java:import hudson.matrix.MatrixProject;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.Axis;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.AxisList;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.MatrixBuild;
src/test/java/hudson/plugins/git/GitPublisherTest.java:import hudson.matrix.MatrixProject;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.Axis;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.AxisList;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.MatrixBuild;
src/test/java/hudson/plugins/git/GitSCMTest.java:import hudson.matrix.MatrixProject;
ricardo@neopili:/tmp/git-plugin$ 



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















Ricardo Ribalda thanks very much for the pointer to MatrixBuild as a possible problem area.  As far as I can tell from the Jenkins source code, the tip of the Jenkins core master branch still references hudson.matrix.MatrixBuild in JenkinsRule and in HudsonTestCase.

I assume the change by Jesse Glick was to move those classes to another location in the source tree.  Had they been removed entirely from the system, the compilation of the git client plugin would fail on the tip of the master branch.  Had they been removed, the elastic axis plugin, the gerrit trigger plugin, and Jenkins core itself would have failed to compile, since there are references to the MatrixBuild class in their source code.



























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] [skip-certificate-check] (JENKINS-24830) Certificate isn't ignored when using Javamail

2014-09-25 Thread corneil.duples...@gmail.com (JIRA)














































Corneil du Plessis
 commented on  JENKINS-24830


Certificate isnt ignored when using Javamail















Yes, I expected the plugin to ensure that SSL or TLS doesn't checking the certificate since the mail config doesn't provide that option.



























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







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


[JIRA] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread philipp.marek+jenk...@linbit.com (JIRA)














































Philipp Marek
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















The git plugin explicitly says that it was last compiled against 1.509 or so... it might really fail with newer 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-17658) Provide a token so that build failure causes can be included in build failure emails

2014-09-25 Thread smok...@softpixel.com (JIRA)














































Steve Mokris
 commented on  JENKINS-17658


Provide a token so that build failure causes can be included in build failure emails















Works nicely.  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] [git-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)












































 
Mark Waite
 edited a comment on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild
















I think you've misunderstood what it is saying.  The git plugin and the git client plugin support Jenkins versions 1.509 and later.  Those plugins are actively used at many sites with Jenkins versions newer than 1.509, including 1.532 and 1.565.*.  I use the plugins heavily at two different locations that I manage.  It doesn't fail in general with newer Jenkins.

I think there is something specific either about the steps you took, compared to others.

For example, if you disabled the git client plugin without disabling the git plugin, then your Jenkins was in an inconsistent state.  It would be good for the Jenkins core to present a better message for those types of inconsistencies, but it is an inconsistency which the plugin itself is not able to repair.



























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















I think you've misunderstood what it is saying.  The git plugin and the git client plugin support Jenkins versions 1.509 and later.  Those plugins actively used at many sites with Jenkins versions newer than 1.509, including 1.532 and 1.565.*.  I use the plugins heavily at two different locations that I manage.  It doesn't fail in general with newer Jenkins.

I think there is something specific either about the steps you took, compared to others.

For example, if you disabled the git client plugin without disabling the git plugin, then your Jenkins was in an inconsistent state.  It would be good for the Jenkins core to present a better message for those types of inconsistencies, but it is an inconsistency which the plugin itself is not able to repair.



























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-14843) OpenID SSO should use POST to submit details to google apps endpoint

2014-09-25 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-14843


OpenID SSO should use POST to submit details to google apps endpoint















Code changed in jenkins
User: Stephen Connolly
Path:
 src/main/java/hudson/plugins/openid/OpenIdExtension.java
 src/main/java/hudson/plugins/openid/OpenIdSsoSecurityRealm.java
http://jenkins-ci.org/commit/openid-plugin/e0c69e3cf3367eca7bff4e6279540e97455f42c0
Log:
  JENKINS-14843 Allow extensions to determine whether it is appropriate for specific security realms





























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-24540) MultiJob does not ask parameters values if Phase jobs are parameterized

2014-09-25 Thread mcan...@coveo.com (JIRA)














































Mathieu Cantin
 commented on  JENKINS-24540


MultiJob does not ask parameters values if Phase jobs are parameterized















Exemple:

	Job A (multi job)
	- Job 1
	- Job 2
	- Job 3



If the Job 1 ask for a name with a string parameter (exemple: myTagName), you must call the Job 1 with the good parameter in the "Job A". In advanced section in "Job A" for the "Job 1" add "Predefined parameters" and type myTagName=SuperTagName, the Job 1 was called with this argument. If you can configure the arguments, you can make the "Job A" parameterized and add a string parameter myTagNameForJob1 (or whatever) and in the "Predefined parameters" you can use this parameter (exemple : myTagName=${myTagNameForJob1}).



























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-17658) Provide a token so that build failure causes can be included in build failure emails

2014-09-25 Thread hugo.fons...@beubi.com (JIRA)














































hugo fonseca
 commented on  JENKINS-17658


Provide a token so that build failure causes can be included in build failure emails















I've being struggling to get this token in my groovy template. Anyone knows how can I get this token from there?
Sorry if this is not the right place for this question. I'm newbie at it and this is the first time I ask something here.



























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-23161) Aborted or failed job in a phase does not immediately cause the multi-job to fail

2014-09-25 Thread mcan...@coveo.com (JIRA)














































Mathieu Cantin
 commented on  JENKINS-23161


Aborted or failed job in a phase does not immediately cause the multi-job to fail















Yes, I have submit a pull request to fix this bug.



























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-11753) Enable OpenID Plugin behind proxy

2014-09-25 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-11753


Enable OpenID Plugin behind proxy















Code changed in jenkins
User: Justin Harringa
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/ac607f380ce1945cf3d13bc389c1475b49696d8c
Log:
  FIXED JENKINS-22368 Discovery fails behind proxy

This commit addresses the problem described in FIXED JENKINS-22368 and
may also correct JENKINS-11753. Proxy settings in openid4java's
HttpClientFactory will now be initialized when calling the constructor of
the OpenIdSsoSecurityRealm  GoogleAppSsoSecurityRealm classes in addition
to the existing call in the commenceLogin process.





























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-25 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-22368


Discovery fails when Jenkins is behind a proxy















Code changed in jenkins
User: Justin Harringa
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/ac607f380ce1945cf3d13bc389c1475b49696d8c
Log:
  FIXED JENKINS-22368 Discovery fails behind proxy

This commit addresses the problem described in FIXED JENKINS-22368 and
may also correct JENKINS-11753. Proxy settings in openid4java's
HttpClientFactory will now be initialized when calling the constructor of
the OpenIdSsoSecurityRealm  GoogleAppSsoSecurityRealm classes in addition
to the existing call in the commenceLogin process.





























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] [release] (JENKINS-13728) Have Role Stragegy support the Release plugin

2014-09-25 Thread icker...@java.net (JIRA)














































ickersep
 updated  JENKINS-13728


Have Role Stragegy support the Release plugin
















Change By:


ickersep
(25/Sep/14 4:52 PM)




Component/s:


role-strategy



























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-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread sw...@java.net (JIRA)














































swolk
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















After doing some more digging I think I've narrowed down the culprit. This issue was introduced to LTS line after Jenkins ver. 1.532.3. In 1.532.3, the maven plugin user is version 2.0.X. After 1.32.3 when I start seeing the issue, the maven plugin is moved to version 2.1. Between 2.0 and 2.1, the most likely change that caused this regression is https://issues.jenkins-ci.org/browse/JENKINS-19801 (Abort module build when maven build is aborted.)



























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-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread sw...@java.net (JIRA)












































 
swolk
 edited a comment on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted
















After doing some more digging I think I've narrowed down the culprit. This issue was introduced to LTS line after Jenkins ver. 1.532.3. In 1.532.3, the maven plugin user is version 2.0.X. After 1.532.3 when I start seeing the issue, the maven plugin is moved to version 2.1. Between 2.0 and 2.1, the most likely change that caused this regression is https://issues.jenkins-ci.org/browse/JENKINS-19801 (Abort module build when maven build is aborted.)



























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)












































 
Mark Waite
 edited a comment on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild
















I think you've misunderstood what it is saying.  The git plugin and the git client plugin support Jenkins versions 1.509 and later.  Those plugins are actively used at many sites with Jenkins versions newer than 1.509, including 1.532 and 1.565.*.  I use the plugins heavily at two different locations that I manage.  It doesn't fail in general with newer Jenkins.

I think there is something specific about the steps you took, compared to others.

For example, if you disabled the git client plugin without disabling the git plugin, then your Jenkins was in an inconsistent state.  It would be good for the Jenkins core to present a better message for those types of inconsistencies, but it is an inconsistency which the plugin itself is not able to repair.



























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-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















Would be helpful if we knew in which non LTS version it was introduced if it started between 1.532.3 and 1.554.1...



























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







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


[JIRA] [robot-plugin] (JENKINS-24868) Add the ability for robot plugin graph to show only failed tests

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














































Ninian
 created  JENKINS-24868


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















Issue Type:


Improvement



Assignee:


jpiironen



Components:


robot-plugin



Created:


25/Sep/14 5:17 PM



Description:


The robot plugin's trend graph is a great way to show test status over time. 

However, over time the number of tests in our projects overall grow, and we keep on top of the number of failures, so the number of tests is fairly high now (around 9000) and the number of failures at any point is quite low (between 5 to 30), so the trend graph doesn't give us much indication of the number of failures compared to previous points in time (we just see a green graph). It would help us a lot to be able to see a trend graph which was filtered for just failed tests. 




Project:


Jenkins



Priority:


Major



Reporter:


Ninian

























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-21750) Promoted Builds Plugin

2014-09-25 Thread stevejansen_git...@icloud.com (JIRA)














































Steve Jansen
 commented on  JENKINS-21750


Promoted Builds Plugin















For community visibility, I recently rebased Thomas' pull request with the lastest updates to the plugin and added a small fix.  This PR is now able to merge Thomas' work into master: https://github.com/jenkinsci/job-dsl-plugin/pull/291




























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread ricardo.riba...@gmail.com (JIRA)














































Ricardo Ribalda
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















Huge DISCLAIMER: I am not a Java Developer

Mark Waite. Maybe there is a dependency missing for the git plugin. Which? I have no idea. Could you check if the MatrixBuild.class is in your war?

It seems that  Jesse Glick removed completely that library. Check merge of tree extract-matrix-project 6883b915239b7a8e46b5376f65353c85d3e482c7

All the missing references to MatrixBuild seems to be in test code, so there is a chance that this is not detected on build time.

many@pececin:/tmp/jenkins$ git grep MatrixBuild
core/src/main/java/hudson/FileSystemProvisioner.java: * but for example {@code MatrixBuild} would call this after
core/src/main/java/hudson/WebAppMain.java://at hudson.matrix.MatrixBuild.run(MatrixBuild.java:149)
core/src/main/java/jenkins/scm/SCMCheckoutStrategy.java: * liCheck out will only happen once in {@code MatrixBuild}, and its state will be then sent
core/src/main/java/jenkins/scm/SCMCheckoutStrategy.java: * li{@code MatrixBuild} does no check out of its own, and check out is only done on {@code MatrixRun}s
test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java:import hudson.matrix.MatrixBuild;
test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java:if(r instanceof MatrixBuild) {
test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java:MatrixBuild mb = (MatrixBuild)r;
test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java:import hudson.matrix.MatrixBuild;
test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java:if(r instanceof MatrixBuild) {
test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java:MatrixBuild mb = (MatrixBuild)r;
test/src/test/java/hudson/model/QueueTest.java:import hudson.matrix.MatrixBuild;
test/src/test/java/hudson/model/QueueTest.java:ListFutureMatrixBuild r = new ArrayListFutureMatrixBuild();
test/src/test/java/hudson/model/QueueTest.java:for (FutureMatrixBuild f : r)
test/src/test/java/hudson/model/QueueTest.java:MatrixBuild build;




























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















Ricardo Ribalda I'm the current maintainer of the git plugin and the git client plugin.  I build it in continuous integration setups on Windows and Linux, with two different branches.  I build the git client plugin in many different configurations as well.  One of those branches is based on code very near the tip of the master branch.  The MatrixBuild class is not missing from Jenkins.

As far as I understand it, the change by Jesse Glick was to move the MatrixBuild classes from the Jenkins core to a Jenkins plugin, plugins/matrix-project.

I suspect this is a case where the error message from Jenkins core is not leading directly to the root of the 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] [skip-certificate-check] (JENKINS-24830) Certificate isn't ignored when using Javamail

2014-09-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 updated  JENKINS-24830


Certificate isnt ignored when using Javamail
















The plugin only handles HTTPS connections, so this is a feature request at best, and addressing a completely wrong component at worst.

References:
https://github.com/jenkinsci/skip-certificate-check-plugin/blob/master/src/main/java/org/jenkinsci/plugins/skipcert/ItemListenerImpl.java#L33
https://github.com/jenkinsci/skip-certificate-check-plugin/blob/master/src/main/java/org/jenkinsci/plugins/skipcert/ItemListenerImpl.java#L35





Change By:


Daniel Beck
(25/Sep/14 5:53 PM)




Issue Type:


Bug
NewFeature





Priority:


Critical
Major



























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-24832) Failed maven builds using -T are showing up as Aborted

2014-09-25 Thread sw...@java.net (JIRA)














































swolk
 commented on  JENKINS-24832


Failed maven builds using -T are showing up as Aborted















The bug was introduced in 1.545. That is the first version that used Maven Project Plugin 2.1. Looking at the code I'm very confident was introduced by changes for https://issues.jenkins-ci.org/browse/JENKINS-19801. That code assumes if modules are still building that main build was aborted, it doesn't take into account the case of parallel module building through -T option and another module failed causing the main build to terminate.



























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















How precisely is this reproducible? (Without reference to Debian packages; by starting with an empty $JENKINS_HOME, running different versions of Jenkins using java -jar jenkins.war, managing plugins, etc.)

The matrix-project-plugin was split out of core in 1.561, moved to its own repository. (References from core test code use a binary test-scope dependency.) As of 1.561, it is a bundled plugin, so enabled by default when you run Jenkins. Other plugins compiled against 1.560 or earlier, including old versions of git-plugin (I think git-client-plugin is irrelevant here) automatically get an implicit dependency on it for compatibility; plugins compiled against 1.561 get such a dependency only if explicitly declared, which applies to new versions (currently just betas) of git-plugin. So all this is fine.

My guess is that you started with an old version of core (and an old version of the Git plugin); updated to 1.565.x, causing the bundled plugin to be extracted to $JENKINS_HOME/plugins/matrix-project/; then rolled back core, whereupon matrix-project would still be listed as installed and enabled. (Despite its expressly requiring core 1.561+; currently Jenkins does not enforce plugin-to-core version dependencies at startup. This is filed separately. If JIRA were not so slow to search I would tell you where.) At that point everything should still be fine, since classes in the class loader for git-plugin referring to MatrixBuild and the like should link to the versions of those class loaded from the Jenkins core class loader, ignoring the matrix-project-plugin class loader.

But my suspicion is that something in Stapler doing reflective calls is picking up classes from the matrix-project-plugin class loader and somehow mixing them up with other classes. I cannot offhand see how this would result in a NoClassDefFoundError. Unfortunately the stack trace does not give adequate information about the chain of class loading events (this is a limitation in HotSpot).

At any rate, if my guess about the means of reproduction is correct, then this can just be closed, with the workaround of deleting/disabling the now-unusable Matrix Project Plugin after the downgrade, noting that the future robustness fix is to enforce plugin dependencies better.



























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















If 1.565.x is the currently installed version, you need to verify that matrix-project-plugin is enabled in Manage Plugins » Installed. If it's not, enable it and restart 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] [maven] (JENKINS-24869) POM_VERSION is not resetted

2014-09-25 Thread tobias.scha...@gmx.de (JIRA)














































tobias schaber
 created  JENKINS-24869


POM_VERSION is not resetted















Issue Type:


Bug



Assignee:


Unassigned


Components:


maven



Created:


25/Sep/14 6:58 PM



Description:


Hi,

I'm currently facing an issue with the variable $POM_VERSION.
I perform the following operations:

1. Clean Workspace
2. Checkout from Git (including the pom with Version 1.0.0)
3. Execute Shell (or execute maven goal, both leads to the same result):
   mvn versions:set -DnewVersion=${POM_VERSION}-${BUILD_NUMBER};

Now the POM-Version is set to e.g. 1.0.0-25.

4. Publish 1.0.0-25 to Nexus

So everything fine until now. I now Trigger the process the next time, but the variable $POM_VERSION still contains the value "1.0.0-25" from the last run, so the next artifact would be deployed as "1.0.0-25-26" and so on.

I tried many things line unsetting the variables or copying them into other temp variables but I did not found a solution for this.

Could you please check if POM_VERSION could be resetted at the beginning?

Kind regards,

Tobias




Environment:


Jenkins 1.581

Maven 3.0.5




Project:


Jenkins



Priority:


Minor



Reporter:


tobias schaber

























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







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


[JIRA] [maven] (JENKINS-24869) POM_VERSION is not resetted

2014-09-25 Thread tobias.scha...@gmx.de (JIRA)













































 
tobias schaber
 assigned  JENKINS-24869 to Unassigned



POM_VERSION is not resetted
















Automatic assign.



























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] [naginator] (JENKINS-21241) Plugin should expose environment variables to tell how many times naginator has restarted the build

2014-09-25 Thread jbsi...@gmail.com (JIRA)














































Jesse Silverstein
 commented on  JENKINS-21241


Plugin should expose environment variables to tell how many times naginator has restarted the build















Yes, please build this! It's especially needed after your change to preserve Build Cause!



























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-24786) Since 2.2.6, environment variables are not expanded in git publisher

2014-09-25 Thread sp...@spali.ch (JIRA)














































Thomas Spalinger
 commented on  JENKINS-24786


Since 2.2.6, environment variables are not expanded in git publisher















Hi Mark
You were right. I stripped down the config as much as possible.
Create the job:
1. add parameter TargetUrl with repo url of a target.
2. in the scm section add an origin repo with any url directly put in and set credentials. name it origin
3. create a second repo with ${TargetUrl} and name it target
4. put "master" in branch to build
5. add git publisher to "target" repo branch master.

so the only dynamic parameter is the TargetUrl used in scm section for the second repo. I even removed EnvInject plugin, so this doesn't make any difference. You don't need this plugin to reproduce it.
The described build fails. But as soon as I replaced the ${TargetUrl} in the repo url field, it works.

So I assume, the permission error is just because it does not expand the TargetUrl env var (as you already told) and then it will try to push to the origin repo instead of the target. And I don't have the permissions there.
Due the fact it works during the fetch, it seems to be, that just git publisher does not resolve the env var during the push operation.
Not sure whats responsible usually to resolve the env vars, the plugin or if it is usually done just by the shell. But it seems to be that the shell does resolve it to an empty string (that's why git try to push to the origin). 

Hope this helps to identify the root cause.
































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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread jgl...@cloudbees.com (JIRA)














































Jesse Glick
 commented on  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild















True, that is perhaps a more plausible scenario, that the newly split plugin somehow got disabled, without git-plugin also being disabled to match. (There is another filed issue that plugin-to-plugin dependencies are not enforced at startup either.)



























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-24786) Since 2.2.6, environment variables are not expanded in git publisher

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 commented on  JENKINS-24786


Since 2.2.6, environment variables are not expanded in git publisher















Thomas Spalinger thanks very much for investigating!  I'm still a little surprised that you successfully found a feature (environment expansion in Git publisher) that I think may have existed for only one version of the plugin.  I'll need to do further experimenting with older versions of the plugin to see how it behaved prior to the changes for JENKINS-22009.  I'll keep this bug report updated as I learn 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] [groovy] (JENKINS-24870) / in script parameters becomes \ (Regression in 1.21)

2014-09-25 Thread candr...@integralblue.com (JIRA)














































candrews
 created  JENKINS-24870


/ in script parameters becomes \ (Regression in 1.21)















Issue Type:


Bug



Assignee:


vjuranek



Attachments:


groovy-forwardslash-becomes-backslash.png



Components:


groovy



Created:


25/Sep/14 8:17 PM



Description:


This works fine in 1.20 but not in 1.21. I'm betting it's a regression due to changes made for JENKINS-24757.

Set the script parameters to a value with a "/" in it. Then run the job, and in the logs you'll see the parameter has it's "/"s changed into "\"s which causes problems.

For example, set the script parameter to as show in the attached screenshot groovy-forwardslash-becomes-backslash.png:

https://mfds1apf22:9443/pagetemplates/index


and you'll get output like this in the job console:

[workspace] $ C:\jenkins\tools\hudson.plugins.groovy.GroovyInstallation\Groovy_latest_\bin\groovy.bat C:\jenkins\jobs\deploy-marketing-to-FIT2\workspace\deploy\waitForUrl.groovy https:\\mfds1apf22:9443\pagetemplates\index

Caught: java.lang.IllegalArgumentException: protocol = https host = null
java.lang.IllegalArgumentException: protocol = https host = null
	at waitForUrl.run(waitForUrl.groovy:59)
Build step 'Execute Groovy script' marked build as failure






Environment:


Windows 7, Jenkins 1.581, Java 8u20




Project:


Jenkins



Priority:


Critical



Reporter:


candrews

























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







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


[JIRA] [maven] (JENKINS-21903) Not all maven downstream jobs get triggered

2014-09-25 Thread scm_issue_l...@java.net (JIRA)














































SCM/JIRA link daemon
 commented on  JENKINS-21903


Not all maven downstream jobs get triggered















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/hudson/maven/AbstractMavenProject.java
 src/main/java/hudson/maven/MavenModuleSet.java
 src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly
 src/main/webapp/blockTriggerWhenBuilding.html
 src/test/java/hudson/maven/MavenModuleSetTest.java
http://jenkins-ci.org/commit/maven-plugin/8aed1aa0e352d51229daba470d1664488a3441c4
Log:
  JENKINS-21903 Amending 0ff6a1b with flag blockTriggerWhenBuilding to control the new behavior, rather than overloading blockBuildWhenUpstreamBuilding.
Allows more detailed control that may be needed in some setups.
Also preserves the default behavior from older plugin versions to avoid surprises.





























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-client] (JENKINS-24864) java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild

2014-09-25 Thread mark.earl.wa...@gmail.com (JIRA)














































Mark Waite
 updated  JENKINS-24864


java.lang.ClassNotFoundException: hudson.matrix.MatrixBuild
















Change By:


Mark Waite
(25/Sep/14 8:47 PM)




Description:


EnablingtheGitClientplugingivesanerrorinthe/configureURL,seetheattachedfile.
{noformat}Stacktracejavax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:/run/jenkins/war/WEB-INF/lib/jenkins-core-1.565.2.jar!/lib/form/section.jelly:48:21:d:invokeBodyhudson/matrix/MatrixBuild	atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103)	atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858)	atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631)	atorg.kohsuke.stapler.Stapler.service(Stapler.java:225)	atjavax.servlet.http.HttpServlet.service(HttpServlet.java:727)	atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)	atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)	athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)	athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)	atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)	athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)	atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)	athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)	athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)	athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)	atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)	atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)	atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)	athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)	atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1476)	atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)	atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)	atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)	atorg.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)	atorg.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)	atorg.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)	atorg.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)	atorg.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)	atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)	atorg.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)	atorg.eclipse.jetty.server.Server.handle(Server.java:370)	atorg.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)	atorg.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:971)	atorg.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1033)	atorg.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)	atorg.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)	atorg.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)	atorg.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)	atorg.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)	atwinstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)	atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	atjava.lang.Thread.run(Thread.java:745)Causedby:org.apache.commons.jelly.JellyTagException:jar:file:/run/jenkins/war/WEB-INF/lib/jenkins-core-1.565.2.jar!/lib/form/section.jelly:48:21:d:invokeBodyhudson/matrix/MatrixBuild	atorg.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)	atorg.apache.commons.jelly.impl.TagScript.run(TagScript.java:289)	

[JIRA] [ownership] (JENKINS-24475) Managing ownership not possible

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














































Oleg Nenashev
 commented on  JENKINS-24475


Managing ownership not possible















Unfortunately, I have not managed to reproduce the issue on RHEL5/Java 1.7
Could you provide more info about your server?



























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-24453) Jenkins server got blue screen to death

2014-09-25 Thread vynce...@gmail.com (JIRA)














































Michael Vincent
 commented on  JENKINS-24453


Jenkins server got blue screen to death















We've been running into this issue since at least March 2013. One out of our 5 nodes seems to blue screen every few days. I always figured it was something in Java or driver issue since I didn't think it was possible for a userspace program to crash the whole machine, so I just worked around it.

We're currently running Jenkins LTS 1.565.2 on a Linux master with Windows 7 64-bit slaves.

I have a complete crash dump (8.3 GB) from a BSOD today. Here's it's bugcheck analysis. I'm not familiar enough with Windows internals to really dig much deeper, but let me know if I can help debug further.


Kernel Complete Dump File: Full address space is available

Symbol search path is: srv*D:\MSSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xf800`03049000 PsLoadedModuleList = 0xf800`0328c6d0
Debug session time: Thu Sep 25 13:58:37.568 2014 (UTC - 5:00)
System Uptime: 2 days 1:04:26.686
Loading Kernel Symbols
...


Loading User Symbols
...
Loading unloaded module list
Unable to enumerate user-mode unloaded modules, NTSTATUS 0xC147
***
* *
*Bugcheck Analysis*
* *
***

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fa800aa49060, fa800aa49340, f800033c50d0}

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for winp.x64.FEF9CB80B43534DCA303AC36686258E8.dll - 
Probably caused by : _

Followup: MachineOwner
-

2: kd !analyze -v
***
* *
*Bugcheck Analysis*
* *
***

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0003, Process
Arg2: fa800aa49060, Terminating object
Arg3: fa800aa49340, Process image file name
Arg4: f800033c50d0, Explanatory message (ascii)

Debugging Details:
--


PROCESS_OBJECT: fa800aa49060

IMAGE_NAME:  _

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: _

FAULTING_MODULE:  

PROCESS_NAME:  java.exe

BUGCHECK_STR:  0xF4_java.exe

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from f8000344cd92 to f800030beb80

STACK_TEXT:  
f880`072b89c8 f800`0344cd92 : `00f4 `0003 fa80`0aa49060 fa80`0aa49340 : nt!KeBugCheckEx
f880`072b89d0 f800`033f91db : ` fa80`10987b50 fa80`0aa49060 fa80`0a3ccb30 : nt!PspCatchCriticalBreak+0x92
f880`072b8a10 f800`03378ec4 : ` `0001 fa80`0aa49060 `0008 : nt! ?? ::NNGAKEGL::`string'+0x17476
f880`072b8a60 f800`030bde13 : fa80`0aa49060 ` fa80`10987b50 ` : nt!NtTerminateProcess+0xf4
f880`072b8ae0 `770c157a : 07fe`fd35402f ` ` `12c2ec30 : nt!KiSystemServiceCopyEnd+0x13
`12c2e998 07fe`fd35402f : ` ` `12c2ec30 `0ab0 : ntdll!NtTerminateProcess+0xa
`12c2e9a0 07fe`fa3c193c : `075c `0001 ` `075c : 

[JIRA] [support-core] (JENKINS-24871) Track/detect/analyze contended lock

2014-09-25 Thread k...@kohsuke.org (JIRA)














































Kohsuke Kawaguchi
 created  JENKINS-24871


Track/detect/analyze contended lock















Issue Type:


New Feature



Assignee:


Steven Christou



Components:


support-core



Created:


25/Sep/14 10:32 PM



Description:


Often, the extreme slowness in the UI or executors come from lock contention.

Today, I catch them mainly by looking at thread dumps and noticing large number of threads waiting for the same lock. But thread dump is a fairly crude tool for this purpose.


	If the average duration of one locking is very long, it won't take too many threads to cause a long delay, but they won't be as visible in thread dumps.
	We need to ask the thread dumps be taken while the problem is exhibiting itself.



This seems like something a tool can help. I don't know what is easy to do, what's possible, and what isn't, but some ideas include:


	track contended locks across JVMs over time and report them?
	If doing it across the JVMs is difficult, maybe we can do it for specific objects or specific classes?
	Or instead of doing this proactively, perhaps the plugin would let us specify an _expression_ to designate an object, then we just monitor that object somehow?



I wonder JMX or Java agent offer anything in this space. 




Project:


Jenkins



Priority:


Major



Reporter:


Kohsuke Kawaguchi

























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-timeout] (JENKINS-10439) IOException while archiving AND wrong build status

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















































ikedam
 resolved  JENKINS-10439 as Incomplete


IOException while archiving AND wrong build status
















The reporter seems no longer here.





Change By:


ikedam
(26/Sep/14 12:26 AM)




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] [external-monitor-job] (JENKINS-24837) Viewing In Progress Status for external-monitor-job

2014-09-25 Thread anandparaj...@gmail.com (JIRA)














































AN2D
 commented on  JENKINS-24837


Viewing In Progress Status for external-monitor-job















Hi,

If someone could confirm whether the behaviour I am seeing is expected or something that could be fixed, it would be great.

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] [copyartifact] (JENKINS-16019) Copy Artifact Plugin isn't copying the last successful correctly

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














































ikedam
 commented on  JENKINS-16019


Copy Artifact Plugin isnt copying the last successful correctly















Let me know the version of copyartifact you use.
And please report steps to reproduce the problem.



























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







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


[JIRA] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+

2014-09-25 Thread kay...@shift.gr.jp (JIRA)














































Akihiro KAYAMA
 commented on  JENKINS-18276


Archiving artifacts from a slave node is extremely slow even with 1.509.1+















Total 11GB artifacts copy takes 30 minutes from Windows slave to Linux master. 
There is another critical bug https://issues.jenkins-ci.org/browse/JENKINS-10629 also.
I decided copy artifacts directly to $JENKINS_HOME/jobs/$JOB_NAME/builds/$BUILD_ID/archive/.

	create public directory in Windows slave allowing anonymous read access
	kick network copy shell script using smbclient on Linux master from Windows batch script via ssh(putty's plink)
11GB copy using smbclient takes only 3 minutes.
Archive directories in matrix project has more complicated path so bothersome but possible 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] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+

2014-09-25 Thread kay...@shift.gr.jp (JIRA)












































 
Akihiro KAYAMA
 edited a comment on  JENKINS-18276


Archiving artifacts from a slave node is extremely slow even with 1.509.1+
















Total 11GB artifacts copy takes 30 minutes from Windows slave to Linux master. 
There is another critical bug https://issues.jenkins-ci.org/browse/JENKINS-10629 also.
I decided copy artifacts directly to $JENKINS_HOME/jobs/$JOB_NAME/builds/$BUILD_ID/archive/.

	create public directory in Windows slave allowing anonymous read access
	kick network copy shell script using smbclient on Linux master from Windows batch script via ssh(putty's plink)



11GB copy using smbclient takes only 3 minutes.
Archive directories in matrix project has more complicated path so bothersome but possible 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] [sidebar-link] (JENKINS-24124) Support sidebar links for computers

2014-09-25 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 started work on  JENKINS-24124


Support sidebar links for computers
















Change By:


Daniel Beck
(26/Sep/14 2:42 AM)




Status:


Open
InProgress



























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] [nested-view] (JENKINS-23283) nested view plugin get list of jobs in a sub view ?

2014-09-25 Thread manoj.thak...@gmail.com (JIRA)














































Manoj Thakkar
 commented on  JENKINS-23283


nested view plugin get list of jobs in a sub view ?















this will work actually, i was trying to get nested views items and this will do the trick



























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.