date:20140403















































SCM/JIRA link daemon
 commented on  JENKINS-22356


No parser found for duplicated code















Code changed in jenkins
User: Ulli Hafner
Path:
 .idea/libraries/Maven__commons_codec_commons_codec_1_6.xml
 .idea/libraries/Maven__commons_logging_commons_logging_1_1_3.xml
 .idea/libraries/Maven__javax_enterprise_cdi_api_1_0.xml
 .idea/libraries/Maven__org_apache_httpcomponents_httpclient_4_3_3.xml
 .idea/libraries/Maven__org_apache_httpcomponents_httpcore_4_3_2.xml
 .idea/libraries/Maven__org_apache_maven_maven_aether_provider_3_1_0.xml
 .idea/libraries/Maven__org_apache_maven_maven_model_3_1_0.xml
 .idea/libraries/Maven__org_apache_maven_maven_model_builder_3_1_0.xml
 .idea/libraries/Maven__org_apache_maven_maven_repository_metadata_3_1_0.xml
 .idea/libraries/Maven__org_codehaus_plexus_plexus_interpolation_1_16.xml
 .idea/libraries/Maven__org_codehaus_plexus_plexus_utils_3_0_10.xml
 .idea/libraries/Maven__org_eclipse_aether_aether_api_0_9_0_v20140226.xml
 .idea/libraries/Maven__org_eclipse_aether_aether_connector_basic_0_9_0_v20140226.xml
 .idea/libraries/Maven__org_eclipse_aether_aether_impl_0_9_0_v20140226.xml
 .idea/libraries/Maven__org_eclipse_aether_aether_spi_0_9_0_v20140226.xml
 .idea/libraries/Maven__org_eclipse_aether_aether_transport_file_0_9_0_v20140226.xml
 .idea/libraries/Maven__org_eclipse_aether_aether_transport_http_0_9_0_v20140226.xml
 .idea/libraries/Maven__org_eclipse_aether_aether_util_0_9_0_v20140226.xml
 .idea/libraries/Maven__org_eclipse_sisu_org_eclipse_sisu_inject_0_2_0.xml
 .idea/libraries/Maven__org_eclipse_sisu_org_eclipse_sisu_plexus_0_2_0.xml
 .idea/libraries/Maven__org_slf4j_jcl_over_slf4j_1_6_2.xml
 .idea/libraries/Maven__org_sonatype_sisu_sisu_guice_no_aop_3_2_0.xml
 dry
http://jenkins-ci.org/commit/analysis-suite-plugin/0488bc1705e7c5f058d2b48ba18627ad3d9099b6
Log:
  FIXED JENKINS-22356 Added native encoding support for CPD.

Latest CPD version does not use UTF8 as default when writing
the results XML files anymore.





























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







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

[JIRA] [dry] (JENKINS-22356) No parser found for duplicated code
















































SCM/JIRA link daemon
 resolved  JENKINS-22356 as Fixed


No parser found for duplicated code
















Change By:


SCM/JIRA link daemon
(03/Apr/14 9:25 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] [git-client] (JENKINS-17462) JGitInternalException exception for UTF-8 file names

2014-04-03 Thread ever...@free.fr (JIRA)















































evernat
 updated  JENKINS-17462


JGitInternalException exception for UTF-8 file names
















changing component





Change By:


evernat
(03/Apr/14 9:31 AM)




Fix Version/s:


current





Affects Version/s:


current





Component/s:


git-client





Component/s:


hudson.sfbay



























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







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

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

2014-04-03 Thread to...@starhill.org (JIRA)















































Tomas Bezdek
 commented on  JENKINS-19470


Build Graph not displaying















Is there any trick to build the plugin from the command line? I'm getting quite a bit of unable to resolve class exceptions for classes FlowRun  and JobExecutionFailureException when compiling FlowDSL.groovy and JobInvocation.groovy



























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







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

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

2014-04-03 Thread to...@starhill.org (JIRA)













































 
Tomas Bezdek
 edited a comment on  JENKINS-19470


Build Graph not displaying
















Is there any trick to build the plugin from command line? I'm getting quite a bit of unable to resolve class exceptions for classes FlowRun  and JobExecutionFailureException when compiling FlowDSL.groovy and JobInvocation.groovy when running "mvn clean package"



























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







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

[JIRA] [jenkins-tracker] (JENKINS-22287) This is regarding SCM Polling from Jenkins Job

2014-04-03 Thread swapnils...@gmail.com (JIRA)















































swapnil soor
 commented on  JENKINS-22287


This is regarding SCM Polling from Jenkins Job















Is there any update on this? Does anybody have any idea about this issue.



























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







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

[JIRA] [jenkins-tracker] (JENKINS-22244) javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1

2014-04-03 Thread swapnils...@gmail.com (JIRA)
















































swapnil soor
 closed  JENKINS-22244 as Not A Defect


javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
















I change java version and it worked.





Change By:


swapnil soor
(03/Apr/14 10:24 AM)




Status:


Resolved
Closed





Assignee:


swapnilsoor



























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







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

[JIRA] [svnmerge] (JENKINS-22284) new field in the feature branch creation form, to manage multi-project repository layout

2014-04-03 Thread webn...@gmail.com (JIRA)















































Verny Quartara Gutierrez
 updated  JENKINS-22284


new field in the feature branch creation form, to manage multi-project repository layout
















Change By:


Verny Quartara Gutierrez
(03/Apr/14 10:37 AM)




Attachment:


adv_options.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] [svnmerge] (JENKINS-22284) new field in the feature branch creation form, to manage multi-project repository layout

2014-04-03 Thread webn...@gmail.com (JIRA)















































Verny Quartara Gutierrez
 commented on  JENKINS-22284


new field in the feature branch creation form, to manage multi-project repository layout















I did a little more analysis on the feature: I'm thinking about something like in the attached picture (adv_options.png).

If "Single Project Repository Layout" is selected, everything works as is now.

If "Multi Project Repository Layout" is selected, the user can optionally specify a "subproject name" (that is the actual subfolder under /branches/branchname).

If "Create a development tag" is checked, a tag will be created and the user can optionally specify a "Tag subfolder" value (that is the actual subfolder under /tags).

Some examples, given job name = "testproject" and Branch Name = 1.6.0
a) with "Single Project Repository Layout" selected, a new branch will be created in /branches/1.6.0 and the new job name will be "testproject-1.6.0
b) with "Multi Project Repository Layout" selected, a new branch will be created in /branches/1.6.0/testproject (unless the user specify another name using the "Subproject name" text input) and the new job name will be "testproject-1.6.0"
c) with "Create a development tag" checked, a new tag will be created in /tags/dev/1.6.0 (unless the user specify another name using the  "Tag subfolder" text input)


I hope this proposal is not too tied to my current development environment, in that case you should provide others scenarios to merge with.



























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







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

[JIRA] [android-emulator] (JENKINS-22481) System images are not installed for Android versions specified as 'android-xx'

2014-04-03 Thread ra...@java.net (JIRA)















































Krzysztof Malinowski
 created  JENKINS-22481


System images are not installed for Android versions specified as android-xx















Issue Type:


Bug



Assignee:


Christopher Orr



Components:


android-emulator



Created:


03/Apr/14 10:50 AM



Description:


When specifying 'Run emulator' with OS version given like 4.0.3, the plugin correctly detects and installs missing images, i.e.:

$ /dev/shm/cp_hudson/tools/android-sdk/tools/android list target
android The configured Android platform needs to be installed: android-15
$ /dev/shm/cp_hudson/tools/android-sdk/tools/android list target
$ /dev/shm/cp_hudson/tools/android-sdk/tools/android list target
android Installing the 'android-15,sysimg-15' SDK component(s)...
$ /dev/shm/cp_hudson/tools/android-sdk/tools/android update sdk -u -a -t android-15,sysimg-15
...
android Using Android SDK: /dev/shm/cp_hudson/tools/android-sdk
android Creating Android AVD: /dev/shm/cp_hudson/workspace/project/.android/avd/hudson_en-US_160_HVGA_android-15_armeabi-v7a.avd
android /dev/shm/cp_hudson/tools/android-sdk/tools/android create avd -f -a -c 100M -s HVGA -n hudson_en-US_160_HVGA_android-15_armeabi-v7a -t android-15 --abi armeabi-v7a
$ /dev/shm/cp_hudson/tools/android-sdk/platform-tools/adb start-server

However, when OS is given like 'android-19', it doesn't seem to perform this check:

$ /dev/shm/cp_hudson/tools/android-sdk/tools/android list target
android Using Android SDK: /dev/shm/cp_hudson/tools/android-sdk
android Creating Android AVD: /dev/shm/cp_hudson/workspace/project/.android/avd/hudson_en-US_160_HVGA_android-19_armeabi-v7a.avd
android /dev/shm/cp_hudson/tools/android-sdk/tools/android create avd -f -a -c 100M -s HVGA -n hudson_en-US_160_HVGA_android-19_armeabi-v7a -t android-19 --abi armeabi-v7a
	Error: Invalid --abi armeabi-v7a for the selected target.
android Could not create Android emulator: Failed to run AVD creation command

It also doesn't help to provide OS version as 4.4.2:

$ /dev/shm/cp_hudson/tools/android-sdk/tools/android list target
android The configured Android platform needs to be installed: 4.4.2
android Using Android SDK: /dev/shm/cp_hudson/tools/android-sdk
android Creating Android AVD: /dev/shm/cp_hudson/workspace/project/.android/avd/hudson_en-US_160_HVGA_4.4.2.avd
android /dev/shm/cp_hudson/tools/android-sdk/tools/android create avd -f -a -c 100M -s HVGA -n hudson_en-US_160_HVGA_4.4.2 -t 4.4.2
android Failed to run AVD creation command
	Error: Target id is not valid. Use 'android list targets' to get the target ids.
android Could not create Android emulator: Failed to run AVD creation command




Environment:


Jenkins 1.556 on RHEL5 x86_64, Android Emulator 2.10




Project:


Jenkins



Priority:


Major



Reporter:


Krzysztof Malinowski

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21475) Multiple LDAP OU support

2014-04-03 Thread brad.macpher...@fmr.com (JIRA)















































Brad Macpherson
 commented on  JENKINS-21475


Multiple LDAP OU support















Not having this ability is a blocker to enterprise deployments - being able to integrate with multiple LDAP trees is vital in our environment. Having multiple sets of LDAP configurations (as is possible in SonarQube and Nexus, for example) means we can try authentication against 'real people' trees as well as 'build account' trees.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22462) can't download jdk from oracle site















































SCM/JIRA link daemon
 commented on  JENKINS-22462


cant download jdk from oracle site















Code changed in jenkins
User: Guillaume Boucherie
Path:
 core/src/main/java/hudson/tools/JDKInstaller.java
http://jenkins-ci.org/commit/jenkins/ef22ba2e568e820750fa977683fa2c862be35eb4
Log:
  JENKINS-22462 update cookie name and value





























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







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

[JIRA] [core] (JENKINS-22462) can't download jdk from oracle site















































SCM/JIRA link daemon
 commented on  JENKINS-22462


cant download jdk from oracle site















Code changed in jenkins
User: Oliver Gondža
Path:
 core/src/main/java/hudson/tools/JDKInstaller.java
http://jenkins-ci.org/commit/jenkins/d67600e7d70e0f6bb1e12054b5b4aba26bd581e0
Log:
  Merge pull request #1171 from gboucherie/JENKINS-22462

JENKINS-22462 update cookie name and value


Compare: https://github.com/jenkinsci/jenkins/compare/9313b5f6b746...d67600e7d70e




























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







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

[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion

2014-04-03 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-22199


Jenkins throwing errors in SCM Polling and Updates with Subversion















Cees, what would be valuable, would be testing a snapshot build with the fix (i.e. https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/335/org.jenkins-ci.plugins$subversion/artifact/org.jenkins-ci.plugins/subversion/2.3-SNAPSHOT/subversion-2.3-SNAPSHOT.hpi) to check if there are any other regressions in 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-22469) SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI
















































ikedam
 assigned  JENKINS-22469 to ikedam



SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI
















Change By:


ikedam
(03/Apr/14 12:31 PM)




Assignee:


ikedam



























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







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

[JIRA] [hockeyapp] (JENKINS-19636) Enable Ant style file name patterns for the .ipa and .dSYM.zip names

2014-04-03 Thread lacos...@java.net (JIRA)
















































lacostej
 resolved  JENKINS-19636 as Fixed


Enable Ant style file name patterns for the .ipa and .dSYM.zip names
















Coming in 1.0.6





Change By:


lacostej
(03/Apr/14 12:44 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [hockeyapp] (JENKINS-19636) Enable Ant style file name patterns for the .ipa and .dSYM.zip names

2014-04-03 Thread lacos...@java.net (JIRA)















































lacostej
 stopped work on  JENKINS-19636


Enable Ant style file name patterns for the .ipa and .dSYM.zip names
















Change By:


lacostej
(03/Apr/14 12:44 PM)




Status:


InProgress
Open



























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







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

[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time















































Zihao Yu
 created  JENKINS-22482


Display pipeline total build time















Issue Type:


New Feature



Assignee:


Unassigned


Components:


delivery-pipeline



Created:


03/Apr/14 1:00 PM



Description:


It would be a nice feature to display total build time of each pipeline in the title.




Project:


Jenkins



Priority:


Minor



Reporter:


Zihao Yu

























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







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

[JIRA] [delivery-pipeline] (JENKINS-22423) Pipelines are mixed up when same stage/step names are used

2014-04-03 Thread pat...@diabol.se (JIRA)
















































Patrik Boström
 closed  JENKINS-22423 as Fixed


Pipelines are mixed up when same stage/step names are used
















Released





Change By:


Patrik Boström
(03/Apr/14 1:18 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] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time

2014-04-03 Thread tommy.ty...@diabol.se (JIRA)















































Tommy Tynjä
 commented on  JENKINS-22482


Display pipeline total build time















Is this issue associated with pull request https://github.com/Diabol/delivery-pipeline-plugin/pull/58/ ? Could you attach a screenshot of the proposed view?

In which use cases is the total pipeline build time interesting? There is currently work on allowing manual triggers in pipelines (see JENKINS-21009), so a concern is how this would affect the total build time calculation.



























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







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

[JIRA] [delivery-pipeline] (JENKINS-21009) Allow manual trigger

2014-04-03 Thread tommy.ty...@diabol.se (JIRA)















































Tommy Tynjä
 commented on  JENKINS-21009


Allow manual trigger















What is the current status for this issue?



























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







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

[JIRA] [authorize-project] (JENKINS-22469) SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI















































ikedam
 commented on  JENKINS-22469


SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI
















	uploading XML is allowed with Item.CONFIGURE permission. This means anyone who can configure the project can bypass the authentication.
	It is performed via AbstractItem#doComfigDotXml, AbstractItem#updateByXml.





























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







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

[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time















































Zihao Yu
 updated  JENKINS-22482


Display pipeline total build time
















Change By:


Zihao Yu
(03/Apr/14 2:05 PM)




Attachment:


ScreenShot2014-04-03at9.53.12AM.png





Attachment:


ScreenShot2014-04-03at10.04.54AM.png





Description:


Itwouldbeanicefeaturetodisplaytotalbuildtimeofeachpipelineinthetitle.




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22483) Job execution deadlock on safeRestart

2014-04-03 Thread kl...@ite-web.de (JIRA)















































Jan Klass
 created  JENKINS-22483


Job execution deadlock on safeRestart















Issue Type:


Bug



Assignee:


Unassigned


Components:


jenkins-multijob-plugin



Created:


03/Apr/14 2:12 PM



Description:



	Start a multijob build with multiple phases
	Plan a safe restart (URL/safeRestart)
	The multijob subjobs/phase will finish
	The multijob itself will not finish as the next subjob is scheduled
	
		But the subjob is not started as "jenkins is preparing to shut down"
	
	






Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Jan Klass

























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







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

[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time















































Zihao Yu
 commented on  JENKINS-22482


Display pipeline total build time















Screenshots are attached. 

For our project we have requirements on total build time of each pipeline, from unit tests all the way to production. This feature will make the total build time very easy to read. 

In my opinion manual triggers do not make too much sense because pipelines should be automatic and autonomous. If one stage or task in the pipeline fails for some reason, it's better to start a new pipeline build, not resume from where it fails. 

That being said, when the pipeline is restarted manually, new build time will be used for calculation.



























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







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

[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time













































 
Zihao Yu
 edited a comment on  JENKINS-22482


Display pipeline total build time
















Screenshots are attached. 

For our project we have requirements on total build time of each pipeline, from unit tests all the way to production. This feature will make the total build time very easy to read. 

In my opinion manual triggers do not make too much sense because pipelines should be automatic and autonomous. If one stage or task in the pipeline fails for some reason, it's better to start a new pipeline build, (e.g. fixing test failures, committing new code which kicks off the pipeline), not resume from where it fails. 

That being said, when the pipeline is restarted manually, new build time will be used for calculation.



























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







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

[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time

2014-04-03 Thread tommy.ty...@diabol.se (JIRA)















































Tommy Tynjä
 commented on  JENKINS-22482


Display pipeline total build time















Thank you for the screenshots associated with the pull request.

I would prefer to display the actual time for the pipeline to finish, rather than just adding up the build task duration for each task. In a pipeline with parallel stages the figure would otherwise be deceptive.



























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







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

[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time















































Zihao Yu
 commented on  JENKINS-22482


Display pipeline total build time















Thanks for the comment. I think you are right about the concurrent builds. I will update the 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] [maven] (JENKINS-22484) Clashing URL for test results

2014-04-03 Thread rab...@java.net (JIRA)















































raboof
 created  JENKINS-22484


Clashing URL for test results















Issue Type:


Bug



Assignee:


Unassigned


Components:


maven



Created:


03/Apr/14 2:44 PM



Description:


The SurefireAggregatedReport Action does not override 'getUrlName()', which causes the URL to remain '/jobnr/testResults'. 

When there's also another instance of AbstractTestResultAction (i.e. a TestResultAction from e.g. the xUnit plugin), those URL's overlap, so one gets shadowed over the other.

As far as I can see, any subclass of AbstractTestResultAction should override getUrlName() to prevent this issue - but in reality I see none of its subclasses do this. 

Can anybody clarify how this is supposed to work?




Project:


Jenkins



Priority:


Major



Reporter:


raboof

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22485) Cannot save job configuration after deleting a parameter

2014-04-03 Thread igor_koyf...@agilent.com (JIRA)















































Igor Koyfman
 created  JENKINS-22485


Cannot save job configuration after deleting a parameter















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core, parameters



Created:


03/Apr/14 2:54 PM



Description:


After deleting a job parameter Save and Apply buttons don't work. Jenkins 1.555




Project:


Jenkins



Priority:


Major



Reporter:


Igor Koyfman

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21999) Computer does not exist returns NPE
















































SCM/JIRA link daemon
 resolved  JENKINS-21999 as Fixed


Computer does not exist returns NPE
















Change By:


SCM/JIRA link daemon
(03/Apr/14 3:02 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-21999) Computer does not exist returns NPE















































SCM/JIRA link daemon
 commented on  JENKINS-21999


Computer does not exist returns NPE















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/43f218cd79223d96691a0957c7befed6f85ff868
Log:
  JENKINS-21999 Noting merge of #1145.


Compare: https://github.com/jenkinsci/jenkins/compare/44a8ec110459...43f218cd7922




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21999) Computer does not exist returns NPE















































SCM/JIRA link daemon
 commented on  JENKINS-21999


Computer does not exist returns NPE















Code changed in jenkins
User: christ66
Path:
 core/src/main/java/hudson/Launcher.java
 core/src/main/java/hudson/model/Slave.java
http://jenkins-ci.org/commit/jenkins/d2a2ec589f4728fa2cfa35371155bce7cc95a0a7
Log:
  FIXED JENKINS-21999 If a slave node does not exist it will throw a
null pointer exception. Instead we create a dummy launcher and return
that if it is unable to get the slave node.





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21999) Computer does not exist returns NPE















































SCM/JIRA link daemon
 commented on  JENKINS-21999


Computer does not exist returns NPE















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/Launcher.java
 core/src/main/java/hudson/model/Slave.java
http://jenkins-ci.org/commit/jenkins/e7c7bbd541d091923fceb6a2613881944ae8c810
Log:
  Merge branch 'JENKINS-21999' of github.com:christ66/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] [gerrit-trigger] (JENKINS-22473) GERRIT_CHANGE_SUBJECT value not updated after first patch set

2014-04-03 Thread rin...@java.net (JIRA)















































rin_ne
 commented on  JENKINS-22473


GERRIT_CHANGE_SUBJECT value not updated after first patch set















Could you provide Gerrit version?



























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







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

[JIRA] [maven] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.

2014-04-03 Thread nitza...@taboola.com (JIRA)















































Nitzan Volman
 created  JENKINS-22486


API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. 















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


maven



Created:


03/Apr/14 3:22 PM



Description:


Using maven 3.2.1 with the -T (parallel) option causes the build to fail with a NoSuchMethodException

method org.apache.maven.execution.MavenExecutionRequest.setPerCoreThreadCount was removed from maven in 3.2.1 and is being called from jenkins.  


java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
	at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.NoSuchMethodError: org.apache.maven.execution.MavenExecutionRequest.setPerCoreThreadCount(Z)V
	at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.populateRequest(DefaultMavenExecutionRequestBuilder.java:978)
	at org.apache.maven.cli.DefaultMavenExecutionRequestBuilder.getMavenExecutionRequest(DefaultMavenExecutionRequestBuilder.java:172)
	at org.jvnet.hudson.maven3.launcher.Maven31Launcher.getMavenExecutionRequest(Maven31Launcher.java:153)
	at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:130)
	... 22 more
channel stopped
ERROR: Failed to parse POMs
hudson.util.IOException2
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:178)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
	... 10 more
Caused by: java.lang.Exception: java.lang.reflect.InvocationTargetException
	at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:184)
	... 15 more
Caused by:

[JIRA] [gerrit-trigger] (JENKINS-22473) GERRIT_CHANGE_SUBJECT value not updated after first patch set

2014-04-03 Thread brot...@gmail.com (JIRA)















































Kevin Brotcke
 updated  JENKINS-22473


GERRIT_CHANGE_SUBJECT value not updated after first patch set
















Change By:


Kevin Brotcke
(03/Apr/14 3:39 PM)




Environment:


Jenkinsver.1.532.1GerritTrigger2.11.0
GerritCodeReview(2.1.7)



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22460) Support artifacts permission

2014-04-03 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 updated  JENKINS-22460


Support artifacts permission
















Marking as a bug since the current behavior is actually a security vulnerability: the plugin can be used to bypass an intentionally restricted permission.





Change By:


Jesse Glick
(03/Apr/14 3:40 PM)




Issue Type:


Improvement
Bug





Labels:


security



























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







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

[JIRA] [gerrit-trigger] (JENKINS-22473) GERRIT_CHANGE_SUBJECT value not updated after first patch set

2014-04-03 Thread brot...@gmail.com (JIRA)















































Kevin Brotcke
 commented on  JENKINS-22473


GERRIT_CHANGE_SUBJECT value not updated after first patch set















Yes, updated details with Gerrit version.



























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







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

[JIRA] [perforce] (JENKINS-22487) reporting p4.prog name to perforce server

2014-04-03 Thread jaroslaw.kap...@gmail.com (JIRA)















































Jarek Kapica
 created  JENKINS-22487


reporting p4.prog name to perforce server















Issue Type:


New Feature



Assignee:


Rob Petti



Components:


perforce



Created:


03/Apr/14 3:45 PM



Description:


I have created a pull request on github that enables reporting p4 program name to Perforce server. I'm currently using the patch on top of perforce-1.3.27. It is is very useful for identifying the connections that come from automated systems and account for them.

There is a global setting that allows setting system wide default value, as well as per job specific value. If desired it is also possible to specify different value just for polling queries.

More details are in help snippets.

Poll request link:
https://github.com/jenkinsci/perforce-plugin/pull/46




Project:


Jenkins



Priority:


Major



Reporter:


Jarek Kapica

























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







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

[JIRA] [perforce] (JENKINS-22487) reporting p4.prog name to perforce server

2014-04-03 Thread jaroslaw.kap...@gmail.com (JIRA)















































Jarek Kapica
 updated  JENKINS-22487


reporting p4.prog name to perforce server
















Change By:


Jarek Kapica
(03/Apr/14 3:46 PM)




Description:


Ihavecreatedapullrequestongithubthatenablesreportingp4programnametoPerforceserver.Imcurrentlyusingthepatchontopofperforce-1.3.27.Itisisveryusefulforidentifyingtheconnectionsthatcomefromautomatedsystemsandaccountforthem.Thereisaglobalsettingthatallowssettingsystemwidedefaultvalue,aswellasperjobspecificvalue.Ifdesireditisalsopossibletospecifydifferentvaluejustforpollingqueries.Moredetailsareinhelpsnippets.
Poll
Pull
requestlink:https://github.com/jenkinsci/perforce-plugin/pull/46



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-18588) Git polling builds same branch multiple times when 'Execute concurrent builds if necessary' turned on

2014-04-03 Thread jskj...@rei.com (JIRA)















































Jeff Skjonsby
 commented on  JENKINS-18588


Git polling builds same branch multiple times when Execute concurrent builds if necessary turned on















The hacky workaround I'm using that basically works (some side-effects but those are tolerable for us for now):

Add this groovy script as a build pre-step:

println "checking for duplicate builds"

// get current thread / Executor
def thr = Thread.currentThread()
// get current build
def currentBuild = thr?.executable
def build = currentBuild.previousBuild
for(i in 0..10) {
  if (build == null || !build.building) { return; }
  def gitRevision = build.environmentGIT_COMMIT
  println "${build.state} - building: ${build.building}"
  if (build.number != currentBuild.number  gitRevision  == currentBuild.environmentGIT_COMMIT) {
  println "build for revision $gitRevision already in progress, ABORTING..."
  build.executor.interrupt()
  }
}

This basically will at the start of a build look for already in-progress builds for a given revision and cancel it. You could allow the older build to "win" but we needed the newer one to win because we're using Stash for pull requests and needed the newer build so that Stash knows the build was successful.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-19922) Build after other projects are built job trigger causes permission check errors in case of enabled security

2014-04-03 Thread jgl...@cloudbees.com (JIRA)

Jesse Glick
commented on JENKINS-19922

Build after other projects are built job trigger causes permission check errors in case of enabled security

Pseudo-triggers are rather misleading. They always add a post-build step BuildTrigger (which is not a Trigger! rather a Notifier; and really should be a Recorder) to the upstream project. You do not need permission to configure the upstream project to do this. The downstream project is not changed, despite the appearance in the configuration screen.

SECURITY-55 (and SECURITY-109) force anyone configuring a job to have build permission on any specified downstream jobs (whether added by a pseudotrigger or not). JENKINS-16956 reverts that, doing the permission check at runtime instead.

Note that BuildTrigger is even weirder than the above description would imply because its perform method does nothing! It exists solely to be a DependencyDeclarer, thus adding an edge to the project dependency graph. And then in AbstractBuildExecution.cleanUp, BuildTrigger.execute is called, which triggers downstream builds for all dependencies from this upstream project—whether added by BuildTrigger or not—in topological order, regardless of what order those project configuration elements were added in (for example in the publishers section). So for example if you use the Parameterized Build plugin, and add a non-blocking trigger to your publishers section, running it does nothing per se, except insofar as that is marked as a dependency in the graph. As compared to adding a blocking trigger as a build step, which does not affect the dependency graph, and does exactly what it looks like it does. Confused yet?

JENKINS-22397, recently implemented, allows the Build Result trigger to display a node in the dependency graph—but for now it is purely informational: not used during BuildTrigger.execute. Currently that trigger (which is a true trigger) runs on a polling schedule, meaning that there is a delay before the downstream build is scheduled. Probably this should be changed to immediately schedule the downstream build, though the rather complex implementation there is tightly tied to polling.

Perhaps there should be a fresh, simple plugin added implementing a Trigger based on an upstream project’s completion, and a Notifier/Builder which schedules a downstream project, both implementing an informational edge in the dependency graph and performing intuitive access control checks. (If you really want the automated topological sort functionality that Jenkins core offers, and understand the implications, you can continue to use BuildTrigger.)

[JIRA] [http_request] (JENKINS-22488) HTTP Redirection 301 and 302 are not followed

2014-04-03 Thread f.pr...@mb-line.com (JIRA)















































Fred Prost
 created  JENKINS-22488


HTTP Redirection 301 and 302 are not followed















Issue Type:


Improvement



Assignee:


Unassigned


Components:


http_request



Created:


03/Apr/14 3:57 PM



Environment:


we have some http scripts which redirect to others scripts. THis works fine using wget which correctly execute the redirect.



But when we use http_request plugin, the redirects are not followed, and so the scripts are not executed.



Whould it be possible to add the ability to follow 301 or 302 redirects like wget does ?



Thank you,



Fred




Project:


Jenkins



Priority:


Major



Reporter:


Fred Prost

























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







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

[JIRA] [gerrit-trigger] (JENKINS-22473) GERRIT_CHANGE_SUBJECT value not updated after first patch set

2014-04-03 Thread rin...@java.net (JIRA)















































rin_ne
 commented on  JENKINS-22473


GERRIT_CHANGE_SUBJECT value not updated after first patch set















Parameters are provided by event stream. Basically, triggered build does not use the past event values.

Your Gerrit version is too old. Your Gerrit might have issue regarding patchset-created event.

Could you do the followings?

	Capture events using ssh command when this issue was reproduced
	Reproduce it after upgrading Gerrit





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21999) Computer does not exist returns NPE

2014-04-03 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-21999


Computer does not exist returns NPE















Integrated in  jenkins_main_trunk #3278
 FIXED JENKINS-21999 If a slave node does not exist it will throw a (Revision d2a2ec589f4728fa2cfa35371155bce7cc95a0a7)
JENKINS-21999 Noting merge of #1145. (Revision 43f218cd79223d96691a0957c7befed6f85ff868)

 Result = SUCCESS
schristou88 : d2a2ec589f4728fa2cfa35371155bce7cc95a0a7
Files : 

	core/src/main/java/hudson/model/Slave.java
	core/src/main/java/hudson/Launcher.java



Jesse Glick : 43f218cd79223d96691a0957c7befed6f85ff868
Files : 

	changelog.html





























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







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

[JIRA] [maven] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.

2014-04-03 Thread nitza...@taboola.com (JIRA)















































Nitzan Volman
 updated  JENKINS-22486


API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. 
















Change By:


Nitzan Volman
(03/Apr/14 4:29 PM)




Environment:


Jenkinsver.1.532.2org.jenkins-ci.main:maven-plugin:2.0.3



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-19922) Build after other projects are built job trigger causes permission check errors in case of enabled security

2014-04-03 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 commented on  JENKINS-19922


Build after other projects are built job trigger causes permission check errors in case of enabled security 















On our installations "Build Trigger" is slightly patched and prohibited by policies. Unfortunately, we cannot completely remove it due to the migration of legacy Jenkins instances.

It makes sense to slightly refactor your clarification and move it to the built-in help as a first step. Since there are well-known workarounds like Parameterized Trigger, the proper fix does not have a big priority.

P.S: It would be very useful to mark descriptors as "deprecated" and somehow display warnings icon (with expandable text box) near the help icon.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-19922) Build after other projects are built job trigger causes permission check errors in case of enabled security

2014-04-03 Thread o.v.nenas...@gmail.com (JIRA)













































 
Oleg Nenashev
 edited a comment on  JENKINS-19922


Build after other projects are built job trigger causes permission check errors in case of enabled security 
















On our installations "Build Trigger" is slightly patched and prohibited by policies. Unfortunately, we cannot completely remove it due to the migration of legacy Jenkins instances.

It makes sense to slightly refactor your clarification and move it to the built-in help as a first step. Since there are well-known workarounds like Parameterized Trigger, the complete fix does not have a big priority.

P.S: It would be very useful to mark descriptors as "deprecated" and somehow display warnings icon (with expandable text box) near the help icon.



























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







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

[JIRA] [perforce] (JENKINS-22487) reporting p4.prog name to perforce server

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
















































Rob Petti
 assigned  JENKINS-22487 to Unassigned



reporting p4.prog name to perforce server
















Change By:


Rob Petti
(03/Apr/14 5:17 PM)




Assignee:


RobPetti



























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







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

[JIRA] [conditional-buildstep] (JENKINS-22471) Do not save Gradle version on single build step

2014-04-03 Thread d...@fortysix.ch (JIRA)















































Dominik Bartholdi
 commented on  JENKINS-22471


Do not save Gradle version on single build step















any more information on this?

	how to reproduce?
	whats the issue?
	what does it cause?
	what versions are you using?
...
please follow this steps to properly report an issue:
https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking#IssueTracking-Reportinganissue






























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







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

[JIRA] [postbuildscript] (JENKINS-22489) Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job.

2014-04-03 Thread amy.mitch...@nokia.com (JIRA)















































amy mitchell
 created  JENKINS-22489


Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job.















Issue Type:


Improvement



Assignee:


Gregory Boissinot



Components:


postbuildscript



Created:


03/Apr/14 5:40 PM



Description:


Currently when you add a set of scripts to execute as a postbuild step in a matrix job, you can only choose to run all of the scripts on the axes, parent, or both. We would like the ability to run each script on the axes, parent or both.  




Project:


Jenkins



Priority:


Major



Reporter:


amy mitchell

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22338) Safari silently overwrites various username or password fields

2014-04-03 Thread y...@schli.ch (JIRA)















































Marc Günther
 updated  JENKINS-22338


Safari silently overwrites various username or password fields
















Change By:


Marc Günther
(03/Apr/14 6:09 PM)




Summary:


Safari
siltenly
silently
overwritesvarioususernameorpasswordfields





Description:


IamusingSafarionMac,andhaveitsetituptoremembermyusername/passwordfortheloginscreen.Nowinvariousother(non-login)pagesinJenkins,thereisausernameorpasswordfield,andSafarioverwritesthosefieldswithmystoreduserinfooneachpageload,eveniftheyalreadycontainothervalues.The
onlyindicationisthatthe
fieldsareshownwithayellowbackground.Thishappensforexample:-IntheproxyconfigurationofPluginManager-Advanced-WhenaddingorEDITING(!)acredential-WhenaddingacredentialofkindCertificate:the{{filename}}fieldisfilledwithmyusername,butthepasswordfieldisnottouched.-WhengoingtoManageCredentialspage,IhaveaSSHusernamewithprivatekeyandaUsernamewithpasswordcredential,anditreplacesthe{{username}}ofthefirst,andthe{{password}}fieldofthesecondentryItdoesNOThappeninsomeotherplaces,forexampletheJiraSetup.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22490) weather icon also for test failures, not only build failures

2014-04-03 Thread y...@schli.ch (JIRA)















































Marc Günther
 created  JENKINS-22490


weather icon also for test failures, not only build failures















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


03/Apr/14 6:13 PM



Description:


The current weather status icon only takes failed (red) builds into account, but ignores instable (yellow) ones.

We almost never have failing builds, but we have test failures, so the weather icon is very useless to us.

It would still be nice to have though, if it would take instable builds into account.




Project:


Jenkins



Priority:


Trivial



Reporter:


Marc Günther

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22491) HP ALM Tools Plug-In Restricts Results to 100 Test Cases When Using ALM Lab Management

2014-04-03 Thread keith.jac...@garmin.com (JIRA)

Keith Jacobs
created JENKINS-22491

HP ALM Tools Plug-In Restricts Results to 100 Test Cases When Using ALM Lab Management

Issue Type:

Bug

Affects Versions:

current

Assignee:

Ofir Shaked

Attachments:

Jenkins_LabMgmt.png, Jenkins_NonLabMgmt.png, Jenkins_TestResults.png

Components:

hp-application-automation-tools-plugin

Created:

03/Apr/14 6:26 PM

Description:

After setting up a new HP ALM Lab Management build in Jenkins, a test set containing 127 tests executes completely, but the results only display in Jenkins for 100 test cases. We confirmed within ALM that all 127 tests executed. Note: It is not the first 100 test cases executed. The first test case executed is written to the results, and so is the last test case.

For comparison, we also set up a standard "HP tests from HP ALM" build in Jenkins. This is non-Lab Management. The results displayed all 127 tests within Jenkins.

The only obvious difference between the two builds is the build type ... the first is Lab Management, and the second is not Lab Management.

The reason for the number of test case results being limited to 100 tests appears to be related to how the HP plug-in is writing the results to XML files. Two files (junitResult.xml and Resultstimestamp.xml) are written during test execution. Both files only contain results for 100 tests, instead of all 127 tests.

junitResult.xml resides in "\jenkins\jobs\job_name\builds\build_num\". Each test case is written to the node "resultsuitessuitecasescasetestName". There are only 100 of these nodes in the file.

Resultstimestamp.xml resides in "\jenkins\jobs\job_name\workspace\". Each test case is written to the node "testsuitestestsuitetestcase". There are only 100 of these nodes in the file.

Attachments:

1. Jenkins_LabMgmt.png - shows the header within Jenkins for the build. The build type is "HP tests using HP ALM Lab Management". This is the build type that limits results to 100 test cases.

2. Jenkins_NonLabMgmt.png - shows the header within Jenkins for the build. The build type is "HP tests from HP ALM". This is the build type that does not limit results.

3. Jenkins_TestResults.png - this is the header for the Test Results page. It shows that the results for only 100 tests are displayed.

Project:

Jenkins

Priority:

Major

Reporter:

Keith Jacobs

[JIRA] [groovy] (JENKINS-6797) Add @DataBoundConstructor

2014-04-03 Thread tim.w...@salesforce.com (JIRA)















































Tim Wood
 commented on  JENKINS-6797


Add @DataBoundConstructor















Another vote for an expert to fix this issue, it also arises using a Groovy step with Conditional Build Step plugin (J-15833).  



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-20492) Re-Execute promotion button is gone

2014-04-03 Thread j...@refresh.io (JIRA)















































Jeff Wehrwein
 commented on  JENKINS-20492


Re-Execute promotion button is gone















I also have this problem. The re-execute promotion option seems to disappear only when I've checked the "only when manually approved" checkbox.  If I uncheck that box, the re-execute button reappears.

The manually approved "re-execute" button just moved into the Badge:

Forgive my ignorance, but I don't understand this explanation - where exactly do I find the re-execute button then?

The previous re-execute should was preserved for the non-manual promotion (as you pointed out).

Are you saying that manual promotions are not allowed to be re-executed?  If so, why not?  Put another way, Damien Nozay pointed out an if condition for manual promotions - why does that condition exist?



























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







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

[JIRA] [unity3d-plugin] (JENKINS-22492) java.io.IOException: Pipe broken

2014-04-03 Thread juanfor...@batovi.com (JIRA)

Juan Fornos
created JENKINS-22492

java.io.IOException: Pipe broken

Issue Type:

Bug

Assignee:

lacostej

Components:

unity3d-plugin

Created:

03/Apr/14 9:05 PM

Description:

Sometimes (it seems to happen when the build duration is considerable, like building for the webplayer), the plugin fails with:

... NORMAL BUILD OUTOUT ...

LZMA 4.43 Copyright (c) 1999-2006 Igor Pavlov 2006-06-04
Failure on remote
java.io.IOException: Pipe broken
at java.io.PipedInputStream.read(Unknown Source)
at java.io.PipedInputStream.read(Unknown Source)
at java.io.InputStream.read(Unknown Source)
at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64)
... Jenkins internal stack trace ...

It fails after the LZMA compression ends (the process lasts several minutes).

Environment:

Windows Master. OSX Slave Node Running Unity.

unity3d-plugin: 0.6.

Project:

Jenkins

Priority:

Major

Reporter:

Juan Fornos

[JIRA] [unity3d-plugin] (JENKINS-22492) java.io.IOException: Pipe broken

2014-04-03 Thread juanfor...@batovi.com (JIRA)















































Juan Fornos
 updated  JENKINS-22492


java.io.IOException: Pipe broken
















Change By:


Juan Fornos
(03/Apr/14 9:10 PM)




Environment:


WindowsMaster.OSXSlaveNode
Running
running
Unity.unity3d-plugin:0.6.





Description:


Sometimes
Whenexecutingthebuildontheslave,sometimes
(itseemstohappenwhenthebuilddurationisconsiderable,likebuildingforthewebplayer),thepluginfailswith:...[NORMALBUILDOUTOUT]...LZMA4.43Copyright(c)1999-2006IgorPavlov2006-06-04Failureonremotejava.io.IOException:Pipebroken	atjava.io.PipedInputStream.read(UnknownSource)	atjava.io.PipedInputStream.read(UnknownSource)	atjava.io.InputStream.read(UnknownSource)	atorg.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64)...[Jenkinsinternalstacktrace]...ItfailsaftertheLZMAcompressionends(theprocesslastsseveralminutes).



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22425) safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)

2014-04-03 Thread michkapop...@gmail.com (JIRA)















































Michka Popoff
 commented on  JENKINS-22425


safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)















I have the same problem on my Cubietruck, with an ARM processor, on Fedora 20.
I can even not start jenkins with the "service jenkins start" command line.

I installed java-1.7.0-openjdk and jna 3.5.2-2.fc20

I found the libjnidispatch.so in /usr/lib/jna. So it seems it's not looking at the right place.



























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







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

[JIRA] [maven2] (JENKINS-18403) Jenkins 1.518 causes Java 5 Maven builds to fail















































SCM/JIRA link daemon
 commented on  JENKINS-18403


Jenkins 1.518 causes Java 5 Maven builds to fail















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/hudson/remoting/Channel.java
 src/main/java/hudson/remoting/RemoteClassLoader.java
http://jenkins-ci.org/commit/remoting/09f20f11498cade0043e4400b91dec4b3531b0ab
Log:
  JENKINS-18403 More reliable way of enforcing maximum bytecode version on a remoting channel.





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21952) Git Plugin fails to resolve tags containing a slash since 2.0.1

2014-04-03 Thread dejan2...@gmail.com (JIRA)















































Dejan Stojadinovic
 commented on  JENKINS-21952


Git Plugin fails to resolve tags containing a slash since 2.0.1















Mark Waite Sorry for the late reply; just to confirm that upgrade to Jenkins Git plugin 2.1.0 and Jenkins Git client plugin 1.7.0 solved my issues (mentioned above).
Thanx !



























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







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

[JIRA] [maven2] (JENKINS-22466) Allow disabling of site archiving















































SCM/JIRA link daemon
 commented on  JENKINS-22466


Allow disabling of site archiving















Code changed in jenkins
User: Lieven Govaerts
Path:
 src/main/java/hudson/maven/MavenBuild.java
 src/main/java/hudson/maven/MavenBuildProxy.java
 src/main/java/hudson/maven/MavenModuleSet.java
 src/main/java/hudson/maven/reporters/MavenSiteArchiver.java
 src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly
 src/main/webapp/siteArchivingDisabled.html
 src/test/java/hudson/maven/reporters/SurefireArchiverUnitTest.java
http://jenkins-ci.org/commit/maven-plugin/a88c6cd268f62bb6c9da43ce77cdd6b7d80223a4
Log:
  JENKINS-22466

Add a new option ""Disable automatic site documentation artifact
archiving" in maven build jobs.





























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







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

[JIRA] [maven2] (JENKINS-22466) Allow disabling of site archiving















































SCM/JIRA link daemon
 commented on  JENKINS-22466


Allow disabling of site archiving















Code changed in jenkins
User: Olivier Lamy
Path:
 src/main/java/hudson/maven/MavenBuild.java
 src/main/java/hudson/maven/MavenBuildProxy.java
 src/main/java/hudson/maven/MavenModuleSet.java
 src/main/java/hudson/maven/reporters/MavenSiteArchiver.java
 src/main/resources/hudson/maven/MavenModuleSet/configure-entries.jelly
 src/main/webapp/siteArchivingDisabled.html
 src/test/java/hudson/maven/reporters/SurefireArchiverUnitTest.java
http://jenkins-ci.org/commit/maven-plugin/db65e0e7a1086b70cf6154d56efe9536b9384a05
Log:
  Merge pull request #20 from lgov/JENKINS-22466

JENKINS-22466 - Disable automatic site documentation artifact archiving


Compare: https://github.com/jenkinsci/maven-plugin/compare/606dd38942c2...db65e0e7a108




























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







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

[JIRA] [parameterized-remote-trigger] (JENKINS-22493) 400 when remote job has default parameters

2014-04-03 Thread pyrogx1...@gmail.com (JIRA)

Ronald Chen
created JENKINS-22493

400 when remote job has default parameters

Issue Type:

Bug

Assignee:

Maurice W.

Components:

parameterized-remote-trigger

Created:

03/Apr/14 10:22 PM

Description:

My remote job has a single string parameter with a default value but when I attempt to trigger it using this plugin I get this error:

Triggering this remote job: remote-job
Not checking if the remote job remote-job is building.
This job is build #[1522] on the remote server.
Triggering remote job now.
ERROR: Remote build failed for the following reason, but the build will continue:
ERROR: Server returned HTTP response code: 400 for URL: http://remote.jenkins.server/job/remote-job/build?delay=0
Not blocking local job until remote job completes - fire and forget.

The problem is /build is used instead of /buildWithParameters

This plugin needs to use the job api to check if there are parameters and call /buildWithParameters even if the caller did not specify any parameters (the caller expects the default value to be used)

Project:

Jenkins

Priority:

Major

Reporter:

Ronald Chen

[JIRA] [parameterized-remote-trigger] (JENKINS-22493) 400 when remote job has default parameters

2014-04-03 Thread pyrogx1...@gmail.com (JIRA)















































Ronald Chen
 updated  JENKINS-22493


400 when remote job has default parameters
















Change By:


Ronald Chen
(03/Apr/14 10:23 PM)




Description:


MyremotejobhasasinglestringparameterwithadefaultvaluebutwhenIattempttotriggeritusingthispluginIgetthiserror:{code}Triggeringthisremotejob:remote-jobNotcheckingiftheremotejobremote-jobisbuilding.Thisjobisbuild#[1522]ontheremoteserver.Triggeringremotejobnow.ERROR:Remotebuildfailedforthefollowingreason,butthebuildwillcontinue:ERROR:ServerreturnedHTTPresponsecode:400forURL:http://remote.jenkins.server/job/remote-job/build?delay=0Notblockinglocaljobuntilremotejobcompletes-fireandforget.{code}Theproblemis/buildisusedinsteadof/buildWithParametersThispluginneedstousethejobapitocheckifthereareparametersandcall/buildWithParametersevenifthecallerdidnotspecifyanyparameters(thecallerexpectsthedefaultvaluetobeused)
WORKAROUND:Havethecallersetabogusparametertomakethepluginuse/buildWithParameters



























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







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

[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2014-04-03 Thread rob.coll...@healthcarepays.com (JIRA)















































Rob Collins
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















I ran into this issue as well. As an attempt at a workaround, I added a pre-build step that runs "svn upgrade" and my Jenkins jobs appear to be back in working order. This probably also has a side-effect of requiring a fresh checkout each 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] [parameterized-remote-trigger] (JENKINS-22493) 400 when remote job has default parameters

2014-04-03 Thread pyrogx1...@gmail.com (JIRA)















































Ronald Chen
 updated  JENKINS-22493


400 when remote job has default parameters
















Change By:


Ronald Chen
(03/Apr/14 10:29 PM)




Description:


MyremotejobhasasinglestringparameterwithadefaultvaluebutwhenIattempttotriggeritusingthispluginIgetthiserror:{code}Triggeringthisremotejob:remote-jobNotcheckingiftheremotejobremote-jobisbuilding.Thisjobisbuild#[1522]ontheremoteserver.Triggeringremotejobnow.ERROR:Remotebuildfailedforthefollowingreason,butthebuildwillcontinue:ERROR:ServerreturnedHTTPresponsecode:400forURL:http://remote.jenkins.server/job/remote-job/build?delay=0Notblockinglocaljobuntilremotejobcompletes-fireandforget.{code}Theproblemis/buildisusedinsteadof/buildWithParametersThispluginneedstousethejobapitocheckifthereareparametersandcall/buildWithParametersevenifthecallerdidnotspecifyanyparameters(thecallerexpectsthedefaultvaluetobeused)WORKAROUND:Havethecallersetabogusparametertomakethepluginuse/buildWithParameters
,eg.WORKAROUND_JENKINS_22493=true



























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







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

[JIRA] [ui-changes] (JENKINS-22476) Create new job using Copy existing item autocomplete does not work

2014-04-03 Thread m2spr...@springdot.org (JIRA)















































Max Spring
 updated  JENKINS-22476


Create new job using Copy existing item autocomplete does not work
















Change By:


Max Spring
(03/Apr/14 10:52 PM)




Assignee:


MaxSpring





Component/s:


ui-changes





Component/s:


jenkow-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] [master-slave] (JENKINS-22494) Multiconfiguration project does not respect label restrictions

2014-04-03 Thread courtla...@gamesalad.com (JIRA)

Courtland Jones
created JENKINS-22494

Multiconfiguration project does not respect label restrictions

Issue Type:

Bug

Assignee:

Unassigned

Components:

master-slave

Created:

03/Apr/14 10:56 PM

Description:

When running a multi-configuration project defined in Jenkins, it does not respect the "Label _expression_" to "Restrict where this project can be run" under the project's "Advanced Project Options" configuration. If multiple slaves nodes exist, but are not included in the Label _expression_ for the project, they can still be sent build configurations anyway, which can result in build failures or erroneous builds made in incorrect environments.

Prerequisites:

Jenkins master installed.
Multiple slave nodes connected to Jenkins master.
Multiple discrete labels to contain nodes.

Steps to reproduce:

Create new Jenkins project. (Click "New Item".)
Give new item a name, and select Multi-Configuration project by selecting "Build multi-configuration project".
Create at least one user-defined axis with at least two values, e.g. the axis name TestAxis and the values TestValue1 and TestValue2.
Restrict the project to include one node but exclude all other nodes.

Under "Advanced Project Options", tick the checkbox "Restrict where this project can be run"
Refer to the labels you have defined from the above pre-requisite and use a label which refers only to one node. Optionally, use the specific node's name, e.g. if a node is named TestNode1, use this value.

Define a build step of some sort. For simplicity's sake, I used a shell script that simply consisted of one line: echo ${TestAxis}
Run the project.

Results:
The project's build configuration will be sent to slave nodes other than the ones explicitly defined in the "Restrict where this project can be run" configuration.

Expected results:
Label restrictions are enforced/respected on Multi-Configuration Projects, as they are on other project types.

Notes:

Even using a label _expression_ such as TestNode1 !TestNode2, project configurations were still sent to TestNode2 to be built.
A workaround is to add the Slaves axis to the project's configuration matrix, and select which slaves nodes to use there, and to not use label restriction in Advanced Project Options.
This is not a duplicate of the quite similar issue JENKINS-5987, as it described repository checkouts occurring on incorrect nodes, and does not describe the steps listed above.

Project:

Jenkins

Labels:

multi-configuration

Priority:

Major

Reporter:

Courtland Jones

[JIRA] [build-timeout] (JENKINS-22467) Conditional Builder doesn't render correctly with build-timeout 1.13
















































ikedam
 resolved  JENKINS-22467 as Wont Fix


Conditional Builder doesnt render correctly with build-timeout 1.13
















This is caused for dropdownDescriptorSelector does not pass it to conditional-buildstep when dynamic-loading.
This is a limitation of Jenkins and this can be fixed not in build-timeout plugin nor in conditional-buildstep, but only in Jenkins core.

Workaround: Save the configuration once with empty builder in conditional-buildstep. Then open the configuration page again. The builder dropdown would be filled up.





Change By:


ikedam
(03/Apr/14 11:24 PM)




Status:


Open
Resolved





Resolution:


WontFix



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-21865) LDAP plugin classes missing on LTS 1.532.2

2014-04-03 Thread mishael...@yahoo.com (JIRA)















































Mishael Kim
 commented on  JENKINS-21865


LDAP plugin classes missing on LTS 1.532.2















I just upgraded to LTS 1.532.2 using my old backed up versions of my plugins and I didn't have any issues.  It worked initially with LDAP plugin version 1.4 and it also seemed to work just fine when upgrading to version 1.8.  Cannot reproduce 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] [authorize-project] (JENKINS-22469) SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI

ikedam
commented on JENKINS-22469

SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI

example details steps to reproduce the problem using REST:

Install authorize-project plugin
Go to "Manage Jenkins" "Configure Global Security"

Check "Enable security"
Check "Jenkins's own user database" for "Security Realm"
Check "Matrix-based security" for "Authorization"
Add user "admin" to "Matrix-based security" and check all permissions.
Add user "devel" to "Matrix-based security" and check all permissions execpt "Administer".

Admin is not really registered to Jenkins's user database, but that doesn't matter in this case.

Add "Configure Build Authorizations in Project Configuration" for "Access Control for Builds"

Create users by signing up.

Create "admin"
Create "devel"

Create a new free-style project
Check "Configure Build Authorization"
Check "Run as Specific User"
Enter "admin" for "User ID"
Leave empty for "Password"
Save the configuration. It will cause an error for failure of authentication.

Create a project that run as "devel"

Create a new free-style project
Check "Configure Build Authorization"
Check "Run as Specific User"
Enter "devel" for "User ID"
Save the configuration.

retreive current config.xml

curl -u devel:devel -o config.xml http://[path to jenkins]/[projectname]/config.xml

wget does not work, as Jenkins returns not 401 but 403 (wget requires 401 before sending a username and a password).

modify "useriddevel/userid" to "useridadmin/userid" in config.xml
Overwrite the configuration

curl -u devel:devel -d @config.xml http://[path to jenkins]/[projectname]/config.xml

Open the configuration page. The project is configured to run as "admin".

[JIRA] [core] (JENKINS-22425) safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)

Dan Rollo
commented on JENKINS-22425

safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)

FWIW, I found the following discussion that appears to indicate this native lib is missing from the version of jna included in jenkins:
http://stackoverflow.com/questions/14635999/jna-native-support-com-sun-jna-linux-arm-libjnidispatch-so-not-found-in-resou

I checked on my Pi, and found the following jna jars:
/var/cache/jenkins/war/WEB-INF/lib/jna-3.3.0-jenkins-3.jar
/var/lib/jenkins/plugins/pam-auth/WEB-INF/lib/jna-3.4.0.jar

I verified the v3.3.0 jna jar does not include a linux-arm lib.
I also verified the v3.4.0 jna jar does include a linux-arm lib: (found here: com/sun/jna/linux-arm/libjnidispatch.so)

It seems a workaround might be to install libjnidispatch.so manually (not sure how to do that).
And a fix for Jenkins might be to upgrade the version of jna used (say to 3.4.0+) (not sure how best to do that either).

[JIRA] [plugin] (JENKINS-22495) When rundeck job option values have hyphens in them, they don't get correctly parsed in RDECK_EXEC_ARG_

2014-04-03 Thread rosh...@gmail.com (JIRA)















































Roshan Revankar
 created  JENKINS-22495


When rundeck job option values have hyphens in them, they dont get correctly parsed in RDECK_EXEC_ARG_















Issue Type:


Bug



Assignee:


Roshan Revankar



Components:


plugin, rundeck



Created:


04/Apr/14 12:35 AM



Description:


When rundeck job option values have hyphens in them, they don't get correctly parsed. 

For example: If the argString is "-optionWithHyphen value-value", $RDECK_EXEC_ARG_optionWithHyphen will be set to "value" instead of "value-value"




Project:


Jenkins



Priority:


Minor



Reporter:


Roshan Revankar

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22425) safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)

Dan Rollo
edited a comment on JENKINS-22425

safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)

I checked on my Pi, and found the following jna jars:
/var/cache/jenkins/war/WEB-INF/lib/jna-3.3.0-jenkins-3.jar
/var/lib/jenkins/plugins/pam-auth/WEB-INF/lib/jna-3.4.0.jar

I verified the v3.3.0 jna jar does not include a linux-arm lib.
I also verified the v3.4.0 jna jar does include a linux-arm lib: (found here: com/sun/jna/linux-arm/libjnidispatch.so)

...more info:
I tried copying the jna v3.4.0 jar in place of the 3.3.0 version (and removed the v3.3.0 version), restarted Jenkins, and still get the same error. I then checked the 3.4.0 version found it does include linux-arm/libjnidispatch.so, but for some reason, it is not working.

Next, replaced v3.3.0 with v4.1.0 (the latest release). = Joy! I can now invoke safeRestart via the web browser without errors.

Any pointers on how I can go about submitting a patch to update the jna version used by Jenkins to v4.1.0?

[JIRA] [core] (JENKINS-22425) safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)

Dan Rollo
edited a comment on JENKINS-22425

safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)

I checked on my Pi, and found the following jna jars:
/var/cache/jenkins/war/WEB-INF/lib/jna-3.3.0-jenkins-3.jar
/var/lib/jenkins/plugins/pam-auth/WEB-INF/lib/jna-3.4.0.jar

I verified the v3.3.0 jna jar does not include a linux-arm lib.
I also verified the v3.4.0 jna jar does include a linux-arm lib: (found here: com/sun/jna/linux-arm/libjnidispatch.so)

Next, replaced v3.3.0 with v4.1.0 (the latest release). = Joy! I can now invoke safeRestart via the web browser without errors.

I guess I'll try submitting a pull request to update the jna version used by Jenkins to v4.1.0. Forking now...

[JIRA] [git-client] (JENKINS-17462) JGitInternalException exception for UTF-8 file names

2014-04-03 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-17462


JGitInternalException exception for UTF-8 file names















Usually the stack trace will also include further hints about the cause of the failure.  For example, JENKINS-22434 includes a mention in the stack trace that there are unmappable characters (though it is using JDK 7, while you appear to be using a relatively older version of JDK 6).  As another example, JENKINS-20410 includes a mention of unmappable characters as well.

Is there more to the stack trace?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22354) Maven job type performance improvement















































SCM/JIRA link daemon
 commented on  JENKINS-22354


Maven job type performance improvement















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 core/src/main/java/hudson/model/Result.java
http://jenkins-ci.org/commit/jenkins/8a530bb14b4325ff1a75ce89b63b53b7271a6702
Log:
  JENKINS-22354

Reduce classloader activities.

This brings in Stapler and commons bean-utils that we don't need on the
slaves.


Compare: https://github.com/jenkinsci/jenkins/compare/dcfeaf3c2a12...8a530bb14b43




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22354) Maven job type performance improvement















































SCM/JIRA link daemon
 commented on  JENKINS-22354


Maven job type performance improvement















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 core/src/main/java/hudson/FilePath.java
 core/src/main/java/hudson/Launcher.java
 core/src/main/java/hudson/cli/ClientAuthenticationCache.java
 core/src/main/java/hudson/os/SU.java
 core/src/main/java/hudson/slaves/SlaveComputer.java
 core/src/main/java/hudson/util/ProcessTree.java
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/test/java/hudson/LauncherTest.java
http://jenkins-ci.org/commit/jenkins/0b27f364f99ec98cb616d4f0cfc0858ecf339852
Log:
  JENKINS-22354

Avoid having FilePath to depend on Jenkins, which increases the amount of classloading that has to happen during remoting





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22425) safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)
















































Dan Rollo
 assigned  JENKINS-22425 to Dan Rollo



safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)
















Change By:


Dan Rollo
(04/Apr/14 3:20 AM)




Assignee:


DanRollo



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-22425) safeRestart (and restart) via url causes exception (missing libjnidispatch.so) on RaspberryPi (ARM)