[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Sebastian Schuberth edited a comment on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows Maybe something specific to my Git plugin configuration is causing this? In general, I'm a bit confused about how the Git plugin works. Does it use the configured Git client for cloning / checkout, or does it use some internal JGit implementation? Knowing this would help me narrowing down the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Sebastian Schuberth commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows Maybe something specific to my Git plugin configuration is changing this? In general, I'm a bit confused about how the Git plugin works. Does it use the configured Git client for cloning / checkout, or does it use some internal JGit implementation? Knowing this would help me narrowing down the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [release] (JENKINS-21849) Maven Release Plugin throws Authentication Required error
Vijay D started work on JENKINS-21849 Maven Release Plugin throws Authentication Required error Change By: Vijay D (19/Feb/14 6:36 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-9250) Clone workspace does not work well with multiple scm plugin
millergarym commented on JENKINS-9250 Clone workspace does not work well with multiple scm plugin Same issue. I'm a trying to use this plug-in to aggregated the artifacts from multiple other build. My work around is to do a wget of lastest builds' artifacts. Would be nice if this plug had a checkbox to just use the same glob as the artifacts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
SCM/JIRA link daemon commented on JENKINS-21159 buildTimeTrend only shows last day of builds Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/RunList.java core/src/test/java/hudson/util/RunListTest.java http://jenkins-ci.org/commit/jenkins/20c4b06f8c5176bfe85ca7edfd62a65b49f46a93 Log: Merge branch 'master_g' of github.com:ialbors/jenkins [FIXED JENKINS-21159] Merged #663. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
SCM/JIRA link daemon commented on JENKINS-21159 buildTimeTrend only shows last day of builds Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/test/java/hudson/util/RunListTest.java http://jenkins-ci.org/commit/jenkins/b09f828706c9a16b8acc4158f2161117f9359047 Log: JENKINS-21159 Noting #663 merge. Compare: https://github.com/jenkinsci/jenkins/compare/2ae83f6ab099...b09f828706c9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
SCM/JIRA link daemon resolved JENKINS-21159 as Fixed buildTimeTrend only shows last day of builds Change By: SCM/JIRA link daemon (19/Feb/14 4:11 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
amargono commented on JENKINS-18678 Builds disappear some time after renaming job The LTS 1.532.2 is now available, however after upgrading, I can't authenticate with LDAP. It turned out the whole ldap plugins classes missing. Copying the the ldap classes from the previous version to: /plugins/ldap/WEB-INF/classes solved the authentication issue. I have logged the issue at: https://issues.jenkins-ci.org/browse/JENKINS-21865 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ldap] (JENKINS-21865) LDAP plugin classes missing on LTS 1.532.2
amargono created JENKINS-21865 LDAP plugin classes missing on LTS 1.532.2 Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ldap Created: 19/Feb/14 12:40 AM Description: After upgrading to LTS 1.532.2, I can't authenticate with LDAP. It turned out the whole ldap plugins classes missing. Copying the the ldap classes from the previous version to: /plugins/ldap/WEB-INF/classes solved the issue. Environment: CentOS - 2.6.18-238.19.1.el5 Fix Versions: current Project: Jenkins Priority: Blocker Reporter: amargono This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-21864) Rename jclouds plugin to better reflect what it *does*
Andrew Phillips created JENKINS-21864 Rename jclouds plugin to better reflect what it *does* Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: jclouds-jenkins Created: 19/Feb/14 12:23 AM Description: I heard KK say at a Jenkins talk recently that the name "jclouds plugin" doesn't exactly make it easy for users going through the plugin list to understand what the plugin does, which seems like a fair point. Would it make sense to think about renaming it "Cloud Slaves Plugin" or "Multi-cloud Slaves Plugin" or something like that..? Project: Jenkins Priority: Major Reporter: Andrew Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Caleb Mayeux commented on JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Another workaround is to use what Mr. Kohsuke said: In the slave configuration, under the Advanced method of Launch Option, Put the following in the Suffix Start Slave Command " -jar-cache " (no quotes) Make sure there's a leading space so the parameters aren't tacked directly onto the slave.jar itself. Still, I'd much prefer if the default jar cache was in the slave FS root. I have a number of slaves using an automounted home directory, and am hitting the quota exceeded error when upgrading from 1.544 to 1.551. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21521) Submodules are disabled by default as of git plugin 2.0.1
wernight commented on JENKINS-21521 Submodules are disabled by default as of git plugin 2.0.1 That's actually NOT a minor issue as it break existing products and makes setup much harder. Submodules are an important part of Git and should be checked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Mark Waite commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows Using a default msysgit installation on multiple Windows machines, I was unable to duplicate this problem with git-client-plugin 1.6.2 and git-plugin 2.0.1. When the checkout is performed on Windows 2011 home server, Windows 7, and Windows 8.1 (in my Jenkins environment) with a symbolic link to a file in the root directory, and with a symbolic link to a directory in the root directory, the checkout is successful. The Windows based checkout of the symbolic links is not very useful on Windows, but it does not prevent the checkout. Can you provide any further hints that could help with verifying the bug still exists? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds] (JENKINS-21363) JClouds plugin starts on-demand slaves even when Jenkins is shutting down
abayer resolved JENKINS-21363 as Fixed JClouds plugin starts on-demand slaves even when Jenkins is shutting down Fixed in next release (2.6, I think) Change By: abayer (18/Feb/14 11:45 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-19935) Instances on EC2 don't get random suffix
abayer commented on JENKINS-19935 Instances on EC2 don't get random suffix Pretty sure this was a bug in the version of jclouds - can you try the latest build from https://jenkins.ci.cloudbees.com/job/plugins/job/jclouds-plugin/lastStableBuild/org.jenkins-ci.plugins$jclouds-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/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-18752) NPE while provisioning a slave and the slave machine does not get destroyed after failure
abayer assigned JENKINS-18752 to abayer NPE while provisioning a slave and the slave machine does not get destroyed after failure Change By: abayer (18/Feb/14 11:40 PM) Assignee: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds] (JENKINS-21186) multiple network failure
abayer resolved JENKINS-21186 as Duplicate multiple network failure Change By: abayer (18/Feb/14 11:37 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds] (JENKINS-17350) Provision via JClouds fails, possibly because of upgrading SSH Slaves plugin
abayer commented on JENKINS-17350 Provision via JClouds fails, possibly because of upgrading SSH Slaves plugin No, that was unrelated - are you still seeing this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-18753) Instance limit ignored when provisioning slaves
abayer assigned JENKINS-18753 to abayer Instance limit ignored when provisioning slaves Change By: abayer (18/Feb/14 11:38 PM) Assignee: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-20919) Add generic networks selection support
abayer assigned JENKINS-20919 to abayer Add generic networks selection support Change By: abayer (18/Feb/14 11:38 PM) Assignee: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds] (JENKINS-21186) multiple network failure
abayer commented on JENKINS-21186 multiple network failure This did make it into 1.7.1, so I just need to figure out the UI changes here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-20921) Spinning up Windows instances via Jenkins+jclouds on OpenStack
abayer resolved JENKINS-20921 as Won't Fix Spinning up Windows instances via Jenkins+jclouds on OpenStack Yeah, we can't do anything to a box we can't SSH into. In general, I would assume this doesn't support Windows slaves. Change By: abayer (18/Feb/14 11:36 PM) Status: Open Resolved Assignee: abayer Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-20831) jclouds plugin leaving slaves that cannot be deleted
abayer resolved JENKINS-20831 as Not A Defect jclouds plugin leaving slaves that cannot be deleted Change By: abayer (18/Feb/14 11:37 PM) Status: Open Resolved Assignee: abayer Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds] (JENKINS-21363) JClouds plugin starts on-demand slaves even when Jenkins is shutting down
SCM/JIRA link daemon commented on JENKINS-21363 JClouds plugin starts on-demand slaves even when Jenkins is shutting down Code changed in jenkins User: Andrew Bayer Path: jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsCloud.java http://jenkins-ci.org/commit/jclouds-plugin/7dcedcbe6df1800c0ec71e14b5edbfde13034f2e Log: JENKINS-21363. Don't provision slaves while we're in quietdown or shutting-down This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "
abayer commented on JENKINS-21717 openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; " Yeah, you may hit problems with JDK7u51. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds] (JENKINS-21363) JClouds plugin starts on-demand slaves even when Jenkins is shutting down
abayer commented on JENKINS-21363 JClouds plugin starts on-demand slaves even when Jenkins is shutting down Interesting - lemme fix that! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Jesse Glick updated JENKINS-21159 buildTimeTrend only shows last day of builds Change By: Jesse Glick (18/Feb/14 11:31 PM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Jesse Glick assigned JENKINS-21159 to Jesse Glick buildTimeTrend only shows last day of builds Change By: Jesse Glick (18/Feb/14 11:14 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Jesse Glick started work on JENKINS-21159 buildTimeTrend only shows last day of builds Change By: Jesse Glick (18/Feb/14 11:15 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-combinations-parameter] (JENKINS-21851) No combinations are built in a scheduled build with Matrix Combinations Parameter
Lars W
commented on JENKINS-21851
No combinations are built in a scheduled build with Matrix Combinations Parameter
The reason is probably the method createValue(StaplerRequest) in MatrixCombinationsParameterDefinition.java
which always returns
new MatrixCombinationsParameterValue(getName(),new Boolean[]{},new String[]{})
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21863) WebSphere deployer: deploy to cluster
leonardo Costantini created JENKINS-21863 WebSphere deployer: deploy to cluster Issue Type: Improvement Assignee: Unassigned Components: websphere-deployer Created: 18/Feb/14 10:22 PM Description: At the moment the plugin can deploy application to single servers Improvement request is to add cluster name as option for application deployment. chosing cluster, the node and server options should be disabled Project: Jenkins Labels: plugin Priority: Minor Reporter: leonardo Costantini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-12843) Failure with maven 3 jobs and shade plugin
Henri Gomez commented on JENKINS-12843 Failure with maven 3 jobs and shade plugin I didn't get comment notification. Feel free to close it, so many things changed, Jenkins core, Jenkins Maven Plugin, Artifactory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [view-job-filters] (JENKINS-21862) Build Filter (Wrapper) column not properly showing results for Parameterized builds
Patricia Wright created JENKINS-21862 Build Filter (Wrapper) column not properly showing results for Parameterized builds Issue Type: Bug Affects Versions: current Assignee: Jacob Robertson Components: view-job-filters Created: 18/Feb/14 9:33 PM Description: All test jobs are called with the BRANCH parameter. I create a view as follows: New List View Under Job Filters i have nothing checked. I select "Parameterized job filter" from the Add Job Filter dropdown. Under Name: I enter "BRANCH" Under Value: I enter the exact parameter I seek to make this view for. "main" for example (with no quotes of course) Match Type: I select "Include Matched" Under columns, I select Build Filter (Wrapper) Column from the add columns I select "Number of Builds" Repeat for Status and Weather Delete the Number of Builds, Status, and Weather, (last successful, etc..) default columns. Save the view. Now when I look at the view, I see the all of the test jobs that have been run with the BRANCH parameter "main". The bug is that the counts for success/failure/etc..., weather, and status, are not filtered to include only jobs with the parameter I specified. Instead they show the values for all jobs no matter what the parameter. It is as if the Build Filter (Wrapper) Column is doing nothing. I've tried several other permutations of the filter: include all, exclude not matching param. include matching param, exclude not matching param None work. Environment: linux, jenkins 1.550, view job filters 1.26 Project: Jenkins Priority: Major Reporter: Patricia Wright This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl started work on JENKINS-21861 option to include attachment with console.txt from failed slaves Change By: Alex Earl (18/Feb/14 8:52 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman created JENKINS-21861 option to include attachment with console.txt from failed slaves Issue Type: Improvement Assignee: Alex Earl Components: email-ext Created: 18/Feb/14 8:51 PM Description: 1. It would be nice to have configuration checkbox in email-ext, to attach zip file with job console logs from failed slaves, like: failed_console.zip: slave1_console.txt slave2_console.txt slave3_console.txt Currently, the build.zip from master node is ~useless because all interesting info is at slaves and requires manual work to extract. 2. Also, the build.zip attached in the email-ext contains file named "log", can you change it to log.txt to let "double click" open it in notepad automatically? Project: Jenkins Priority: Major Reporter: Mike Dubman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add "shell" variable into "pre-send" groovy script context
Mike Dubman closed JENKINS-21228 as Fixed add "shell" variable into "pre-send" groovy script context +1 Change By: Mike Dubman (18/Feb/14 8:46 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add "shell" variable into "pre-send" groovy script context
Mike Dubman resolved JENKINS-21228 as Fixed add "shell" variable into "pre-send" groovy script context managed script will do the trick Change By: Mike Dubman (18/Feb/14 8:46 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21625) Subversion Polling does not work properly whenever using variables in the Repository URL
Jérémie Faucher-Goulet commented on JENKINS-21625 Subversion Polling does not work properly whenever using variables in the Repository URL I had the credential issue as well when upgrading... Which I fixed! And now I get the exact same issue as Fernando Rubbo. Since the plugin fails to get the revision, it assumes there were changes and schedules a build every 5 minutes. The builds are successfuls (the checkout works fine). Only the 'check for changes' doesn't work with variables! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21228) add "shell" variable into "pre-send" groovy script context
Mike Dubman commented on JENKINS-21228 add "shell" variable into "pre-send" groovy script context yes, thanks! will open two feature requests for other items. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21774) Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit
Mark Waite commented on JENKINS-21774 Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit Interesting. I'll need to learn more about the specific impact of "shallow clone" on the contents of a git repository. I thought that "shallow clone" was only retrieving a subset of the history, so I would expect it to have some risk of not correctly detecting the "before" state of the repository due to the shallow clone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21774) Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit
Anil Chintapatla commented on JENKINS-21774 Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit Mark, Not sure how to reproduce this problem, since this an intermittent problem we noticed. Pull request is done thro' the Jenkins job itself. Here is the configuration we use in the Jenkins Job: Source Code Management pass in git repo url, with branch set as 'origin/master' setup to do a 'Shallow Clone' Build Triggers Poll SCM set to @daily This is the same configuration we use for other Jenkins jobs. When we have this issue, the git plugin reports all the files as new files added. thanks/Anil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [authorize-project] (JENKINS-21856) Authorization - Matrix-based security - Removing Cancel Right Has No Effect
Jesse Glick assigned JENKINS-21856 to Unassigned Authorization - Matrix-based security - Removing Cancel Right Has No Effect Change By: Jesse Glick (18/Feb/14 7:44 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
Heather Fraser-Dube assigned JENKINS-21857 to Heather Fraser-Dube com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF Change By: Heather Fraser-Dube (18/Feb/14 7:40 PM) Assignee: Heather Fraser-Dube This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5723) Allow setting arbitrary command line arguments when defining a mercurial executable
SCM/JIRA link daemon commented on JENKINS-5723 Allow setting arbitrary command line arguments when defining a mercurial executable Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/hudson/plugins/mercurial/HgExe.java src/main/java/hudson/plugins/mercurial/MercurialInstallation.java src/main/resources/hudson/plugins/mercurial/MercurialInstallation/config.jelly src/main/resources/hudson/plugins/mercurial/MercurialInstallation/help-config.html src/test/java/hudson/plugins/mercurial/CustomConfigTest.java src/test/java/hudson/plugins/mercurial/HgExeFunctionalTest.java http://jenkins-ci.org/commit/mercurial-plugin/c777dc9cbef3abbb0da25fdca9bcfa14622d77e2 Log: [FIXED JENKINS-5723] Permit arbitrary --config options to be defined for a given Mercurial installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5723) Allow setting arbitrary command line arguments when defining a mercurial executable
SCM/JIRA link daemon resolved JENKINS-5723 as Fixed Allow setting arbitrary command line arguments when defining a mercurial executable Change By: SCM/JIRA link daemon (18/Feb/14 7:29 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
dvaske commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart @Shannon, no I didn't have any issues, but I currently do not have any slaves attached. I'll keep an eye on stability. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copy-to-slave] (JENKINS-21770) Copy to slave injects erroneous drive letter (e.g. "E:") to full cygwin workspace path /e/.hudson/jobs/job1/workspace
Gemini A resolved JENKINS-21770 as Fixed Copy to slave injects erroneous drive letter (e.g. "E:") to full cygwin workspace path /e/.hudson/jobs/job1/workspace Resolved by changing, on the master node, the node configuration for the Windows slave node (Manage Jenkins --> Manage Nodes) and specifying a Windows format path (including the windows drive specifier E instead of the cygwin path format for the "Remote FS root" definition of the Windows slave node. Change By: Gemini A (18/Feb/14 7:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Jesse Glick resolved JENKINS-17632 as Won't Fix Please add an option for uncompressed cloning Closing in favor of JENKINS-5723 which provides this ability and others more generically (but gives the syntax for uncompressed cloning in the inline help as an example). Change By: Jesse Glick (18/Feb/14 7:20 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-21860) Title image "title.png" scaled to 139px × 34px regardless of size
Paul Landolt created JENKINS-21860 Title image "title.png" scaled to 139px × 34px regardless of size Issue Type: Bug Assignee: Unassigned Attachments: JenkinsImageScaled.PNG, PageInfo.PNG, title.png Components: gui Created: 18/Feb/14 7:19 PM Description: Attempting to replace "images/title.png" with a custom image, 267px X 34px. Jenkins re-scales image to 139px X 34px. It should be easy to drop in an image and have it picked up as the native size. Environment: Windows Server 2008, but unsure if OS is relevant Project: Jenkins Labels: gui images Priority: Minor Reporter: Paul Landolt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5723) Allow setting arbitrary command line arguments when defining a mercurial executable
Jesse Glick commented on JENKINS-5723 Allow setting arbitrary command line arguments when defining a mercurial executable Developing a feature allowing .hgrc-like configuration to be specified as part of a Mercurial installation definition. Might also be useful to allow such configuration to be specified for a particular job, which would be useful so that job configurers without overall administrative permission could turn on or off compression and so on, but this would be a bit more work so I am not doing it right now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5723) Allow setting arbitrary command line arguments when defining a mercurial executable
Jesse Glick started work on JENKINS-5723 Allow setting arbitrary command line arguments when defining a mercurial executable Change By: Jesse Glick (18/Feb/14 7:18 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jacoco] (JENKINS-21859) ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception Caught error while checking for symbolic links
gabe schna created JENKINS-21859 ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception Caught error while checking for symbolic links Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 18/Feb/14 6:53 PM Description: ... ... BUILD SUCCESSFUL Total time: 5 minutes 37 seconds Recording test results Build step 'Publish JUnit test result report' changed build result to UNSTABLE [JaCoCo plugin] Collecting JaCoCo coverage data... [JaCoCo plugin] */.exec;/xyz/bin;*/xyz/src; locations are configured ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception Caught error while checking for symbolic links at org.apache.tools.ant.DirectoryScanner.causesIllegalSymlinkLoop(DirectoryScanner.java:1887) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1267) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1211) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1173) at org.apache.tools.ant.DirectoryScanner.checkIncludePatterns(DirectoryScanner.java:955) at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:909) at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:499) at hudson.FilePath.glob(FilePath.java:1621) at hudson.FilePath.access$700(FilePath.java:172) at hudson.FilePath$30.invoke(FilePath.java:1599) at hudson.FilePath$30.invoke(FilePath.java:1596) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at hudson.FilePath.list(FilePath.java:1596) at hudson.FilePath.list(FilePath.java:1581) at hudson.FilePath.list(FilePath.java:1567) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:339) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at h
[JIRA] [teamconcert] (JENKINS-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
Simon Kaufmann
updated JENKINS-21857
com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
Change By:
Simon Kaufmann
(18/Feb/14 6:36 PM)
Description:
The com.ibm.team.build.hjplugin-rtc is an eclipse-plugin-project, i.e. it uses the manifest-first approach. However, the MANIFEST.MF file is missing in the repository. In fact, it is excluded from versioning since "/META-INF" is added to the .gitignore.Please add the missing files.---This is happens when trying to build it:{code}[ERROR] Internal error: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc. -> [Help 1]org.apache.maven.InternalErrorException: Internal error: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST C:\
Users\kai7si\
git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc.at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)Caused by: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc.at org.eclipse.tycho.core.osgitools.DefaultBundleReader.convertPluginManifest(DefaultBundleReader.java:138)at org.eclipse.tycho.core.osgitools.DefaultBundleReader.loadManifestFromDirectory(DefaultBundleReader.java:106)at org.eclipse.tycho.core.osgitools.DefaultBundleReader.doLoadManifest(DefaultBundleReader.java:65)at org.eclipse.tycho.core.osgitools.DefaultBundleReader.loadManifest(DefaultBundleReader.java:56)at org.eclipse.tycho.core.osgitools.OsgiBundleProject.readArtifactKey(OsgiBundleProject.java:142)at org.eclipse.tycho.core.osgitools.OsgiBundleProject.setupProject(OsgiBundleProject.java:131)at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:62)at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:77)at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274)at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)... 11 moreCaused by: org.eclipse.osgi.service.pluginconversion.PluginConversionException: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc.at org.eclipse.core.runtime.internal.adaptor.PluginConverterImpl.fillPluginInfo(PluginConverterImpl.java:114)at org.eclipse.core.runtime.internal.adaptor.PluginConverterImpl.convertManifest(PluginConverterImpl.java:714)at org.eclipse.core.runtime.internal.adaptor.PluginConverterImpl.convertManifest(PluginConverterImpl.java:722)at org.eclipse.tycho.core.osgitools.DefaultBundleReader.convertPluginManifest(DefaultBundleReader.java:124)... 20 more{code}
[JIRA] [dependency-check-jenkins] (JENKINS-21858) Inconsistent display of results between actual findings and findings visualized
Steve Springett created JENKINS-21858 Inconsistent display of results between actual findings and findings visualized Issue Type: Bug Assignee: Steve Springett Components: dependency-check-jenkins Created: 18/Feb/14 6:16 PM Description: The number of findings at the end of a dependency-check job are displayed in the console output. At times, the visualization of the findings (via analysis-core) may vary slightly (less) than the number of actual findings displayed in the console. Project: Jenkins Priority: Minor Reporter: Steve Springett This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
Simon Kaufmann created JENKINS-21857 com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: teamconcert Created: 18/Feb/14 6:15 PM Description: The com.ibm.team.build.hjplugin-rtc is an eclipse-plugin-project, i.e. it uses the manifest-first approach. However, the MANIFEST.MF file is missing in the repository. In fact, it is excluded from versioning since "/META-INF" is added to the .gitignore. Please add the missing files. — This is happens when trying to build it: [ERROR] Internal error: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST C:\git\teamconcert-plugin\com .ibm.team.build.hjplugin-rtc: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamconcert-plugin\com.ibm.team.build.h jplugin-rtc. -> [Help 1] org.apache.maven.InternalErrorException: Internal error: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST C:\Users\ kai7si\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamco ncert-plugin\com.ibm.team.build.hjplugin-rtc. at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.eclipse.tycho.core.osgitools.OsgiManifestParserException: Exception parsing OSGi MANIFEST C:\git\teamconcert-plugin\com.ibm.team.bui ld.hjplugin-rtc: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc. at org.eclipse.tycho.core.osgitools.DefaultBundleReader.convertPluginManifest(DefaultBundleReader.java:138) at org.eclipse.tycho.core.osgitools.DefaultBundleReader.loadManifestFromDirectory(DefaultBundleReader.java:106) at org.eclipse.tycho.core.osgitools.DefaultBundleReader.doLoadManifest(DefaultBundleReader.java:65) at org.eclipse.tycho.core.osgitools.DefaultBundleReader.loadManifest(DefaultBundleReader.java:56) at org.eclipse.tycho.core.osgitools.OsgiBundleProject.readArtifactKey(OsgiBundleProject.java:142) at org.eclipse.tycho.core.osgitools.OsgiBundleProject.setupProject(OsgiBundleProject.java:131) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:62) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:77) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 11 more Caused by: org.eclipse.osgi.service.pluginconversion.PluginConversionException: Could not find a META-INF/MANIFEST.MF, plugin.xml or a fragment.xml in C:\git\teamconcert-plugin\com.ibm.team.build.hjplugin-rtc. at org.eclipse.core.runtime.internal.adaptor.PluginConverterImpl.fillPluginInfo(PluginConverterImpl.java:114) at org.eclipse.core.runtime.internal.adaptor.PluginConverterImpl.convertManifest(PluginConverterImpl.java:714) at org.eclipse.core.runtime.internal.adaptor.P
[JIRA] [mercurial] (JENKINS-19719) Integration with Config File Provider plugin
Jesse Glick resolved JENKINS-19719 as Won't Fix Integration with Config File Provider plugin Playing with this integration in the config-file-provider-JENKINS-19719 branch but (CC @domi @imod) it does not seem very useful since only Jenkins administrators can create or edit config files, whereas I would want regular job configurers to be able to specify per-job options. Change By: Jesse Glick (18/Feb/14 6:13 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-19719) Integration with Config File Provider plugin
SCM/JIRA link daemon commented on JENKINS-19719 Integration with Config File Provider plugin Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/hudson/plugins/mercurial/MercurialIniConfig.java src/main/resources/hudson/plugins/mercurial/MercurialIniConfig/MercurialIniConfigProvider/newInstanceDetail.jelly src/main/resources/hudson/plugins/mercurial/MercurialIniConfig/edit-config.jelly http://jenkins-ci.org/commit/mercurial-plugin/d5ba22010daea9503b7f6e02f46d403c075e1609 Log: JENKINS-19719 Sketch of Config File Provider plugin integration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-5723) Allow setting arbitrary command line arguments when defining a mercurial executable
Jesse Glick commented on JENKINS-5723 Allow setting arbitrary command line arguments when defining a mercurial executable By the way the original request is now better handled by the Credentials plugin integration. So now treating this as a variant option to JENKINS-19719. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20663) file name encoding broken in zip archives
Lauri Taaleš
commented on JENKINS-20663
file name encoding broken in zip archives
I have the same problem with filenames that contain 'õ', 'ä', 'ö' or 'ü'. Prior to version 1.532 it could be fixed by adding -Dfile.encoding=Cp775 to element in jenkins.xml. I have traced this particular "regression" back to this commit, which replaced usage of hudson.util.io.ZipArchiver with java.util.zip.ZipOutputStream in hudson.model.DirectoryBrowserSupport. As a temporary work-around I have compiled version 1.532.1 from source on Java 7, which adds an additional Charset parameter to ZipOutputStream constructor and passed in the value of System.getProperty("file.encoding"), but I don't feel like doing this for every update.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Jose Sa commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I see similar issue with some externals (not all) with following exception: Feb 18, 2014 7:19:48 PM hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify WARNING: Failed to handle Subversion commit notification org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svnroot/repo/path/to/external failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148) at hudson.scm.SubversionSCM$ModuleLocation.getUUID(SubversionSCM.java:2700) at hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl.onNotify(SubversionRepositoryStatus.java:202) at hudson.scm.SubversionRepositoryStatus.doNotifyCommit(SubversionRepositoryStatus.java:136) at sun.reflect.GeneratedMethodAccessor348.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurity
[JIRA] [authorize-project] (JENKINS-21856) Authorization - Matrix-based security - Removing Cancel Right Has No Effect
Tim Bassett created JENKINS-21856 Authorization - Matrix-based security - Removing Cancel Right Has No Effect Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Attachments: auth-problem.JPG Components: authorize-project, matrix, matrix-auth, security Created: 18/Feb/14 5:21 PM Description: We are using LDAP to authenticate users. For "Authenticated Users" we have removed the "Job-Cancel" right by unchecking the checkbox. We have four build masters that are specifically added with their LDAP user name that have more rights. All authenicated users still have the ability to cancel (abort) a build job run. In the attached screenshot, you should see that all "authenticated" users have the "Cancel" right taken away. Please advise. Environment: RHEL LDAP Plugin 1.2 Matrix Auth Strategy Plugin 1.1 Project: Jenkins Priority: Minor Reporter: Tim Bassett This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect The bug was originally assigned to two components, the git-plugin and the git-client-plugin. I investigated the source code and confirmed that in order to fix this bug, the only component that needs to change is the git-plugin, not the git-client-plugin. Since no change would be required to the git-client-plugin to fix this bug, I removed it from list of components. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
John Dyer commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect Hello, Sorry, I am not sure I understand your last comment.. -John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13905) install IPS jenkins package failed
Adam Paul reopened JENKINS-13905 install IPS jenkins package failed This issue still exists in the current Jenkins build, and prevents us from using the otherwise very-convenient IPS packages provided: ~ $ pkg publisher jenkins Publisher: jenkins Alias: Origin URI: http://ips.jenkins-ci.org/ips/ Proxy: SSL Key: None SSL Cert: None Client UUID: 5c6cd1cc-97fd-11e3-98fc-80144ffa0831 Catalog Updated: February 14, 2014 04:28:34 PM Enabled: Yes ~ $ sudo pkg install jenkins Creating Plan (Checking for conflicting actions): / pkg install: The requested change to the system attempts to install multiple actions for dir 'var/lib' with conflicting attributes: 1 package delivers 'dir group=sys mode=0755 owner=root path=var/lib': pkg://jenkins/jenkins@1.551,0-0:20140215T002823Z 2 packages deliver 'dir group=other mode=0755 owner=root path=var/lib': pkg://solaris/file/slocate@3.1,5.11-0.175.1.0.0.15.0:20120501T195037Z pkg://solaris/system/library/dbus@1.2.28,5.11-0.175.1.0.0.24.2:20120919T184016Z These packages may not be installed together. Any non-conflicting set may be, or the packages must be corrected before they can be installed. The fix is to simply remove the system directory entries in the package manifest, and only provide dir entries for directories owned by the jenkins package. Change By: Adam Paul (18/Feb/14 5:02 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Reynald Borer commented on JENKINS-21842 Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551 Ok thanks for the clarification and sorry for my misunderstanding then. I also vote in favor of a configuration parameter as proposed in x-frame-filter plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Christian Matzat commented on JENKINS-21842 Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551 No, the xframe-filter-plugin won't help, sorry for misunderstanding. I put this hint for how to integrate a configuration option into Jenkins. The whole xframe-filter-plugin will be obsolete once this is done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21855) Add markup formatter preview for parameter descriptions
Daniel Beck created JENKINS-21855 Add markup formatter preview for parameter descriptions Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 18/Feb/14 4:25 PM Project: Jenkins Priority: Major Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20607) GIT Plugin 2.0: Polling ignores commit from certain users not working
Onur Ozardic commented on JENKINS-20607 GIT Plugin 2.0: Polling ignores commit from certain users not working I also hit the issue, the workaround does not work for me, too. I am using Jenkins ver. 1.551 with Git Plugin 2.01. I upgraded from 1.543 and 2.0 which it was not working too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Reynald Borer commented on JENKINS-21842 Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551 I'm having the same issue here, and unfortunately the X-Frame-Filter plugin cannot help as it's adding another X-Frame-Options header. This plugin should use to replace the header content instead (https://github.com/stapler/stapler/blob/master/jelly/src/main/java/org/kohsuke/stapler/jelly/SetHeaderTag.java) That of course does not solve this issue, seems stapler does not provide any tag to remove a header. And the HttpServletResponse API does not provide this ability too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20618) upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException
SCM/JIRA link daemon commented on JENKINS-20618 upgrade from LTS 1.509.4 to LTS 1.532.1-SNAPSHOT -- layout.jelly java.io.IOException Code changed in jenkins User: Jesse Glick Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/2ae83f6ab099d46d01a2f70c77be069d3050267d Log: Corrected a (now-)misleading comment. JENKINS-20618 diagnostics (also in 1.532.2) are on top of jzlib 1.1.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/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "
Matt Fischer commented on JENKINS-21717 openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; " I have not tried since this as I got tired of fighting with it. What version of Java works for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-13125) HTTP Content-Range Header one byte past file length and missing "bytes" unit
Daniel Beck updated JENKINS-13125 HTTP Content-Range Header one byte past file length and missing "bytes" unit Change By: Daniel Beck (18/Feb/14 3:43 PM) Labels: 1.532.2-fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16871) Inconsistent use of XML escaping in config.xml when uploading through API
Magnus Jacobsson commented on JENKINS-16871 Inconsistent use of XML escaping in config.xml when uploading through API Yes, I just tried with version 1.544 and it was the same issue. At the moment, I cannot upgrade Jenkins to try an even later 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/groups/opt_out.
[JIRA] [core] (JENKINS-19004) Channel's executorService's pool should have a name
Daniel Beck updated JENKINS-19004 Channel's executorService's pool should have a name Change By: Daniel Beck (18/Feb/14 3:40 PM) Labels: 1.532.2-fixed 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/groups/opt_out.
[JIRA] [core] (JENKINS-19004) Channel's executorService's pool should have a name
Daniel Beck reopened JENKINS-19004 Channel's executorService's pool should have a name Reopening temporarily to note inclusion in LTS. Change By: Daniel Beck (18/Feb/14 3:40 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19004) Channel's executorService's pool should have a name
Daniel Beck resolved JENKINS-19004 as Fixed Channel's executorService's pool should have a name Change By: Daniel Beck (18/Feb/14 3:41 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-20023) Make CLI interface help more accesible
Daniel Beck commented on JENKINS-20023 Make CLI interface help more accesible Noting inclusion of partial solution in LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.
SCM/JIRA link daemon commented on JENKINS-18237 Multiple hg repos vs matrix job - the same revision used for all repositories. Code changed in jenkins User: Brandon Turner Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java src/test/java/hudson/plugins/mercurial/MatrixProjectTest.java http://jenkins-ci.org/commit/mercurial-plugin/1a33ebc7d1337659d07d995fc55a008cb9155897 Log: Fix matrix builds with multiple SCMs This fixes a bug that causes Matrix Builds to fail when using two or more Mercurial repositories (via the multiple-scms plugin). Previously, each SCM tried to checkout the changeset from the first Mercurial repository. This checks for the presence of the multiple-scms plugin and, if the build uses it, looks up the parent changeset using multiple-scms. I also modified the MatrixBuild tests to fail faster when builds fail (added an await timeout). JENKINS-18237 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.
SCM/JIRA link daemon commented on JENKINS-18237 Multiple hg repos vs matrix job - the same revision used for all repositories. Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/hudson/plugins/mercurial/MercurialSCM.java src/test/java/hudson/plugins/mercurial/MatrixProjectTest.java src/test/java/hudson/plugins/mercurial/MultiSCM.java src/test/java/hudson/plugins/mercurial/MultiSCMChangeLogParser.java src/test/java/hudson/plugins/mercurial/MultiSCMChangeLogSet.java src/test/java/hudson/plugins/mercurial/SCMTestBase.java http://jenkins-ci.org/commit/mercurial-plugin/5dfe7720d202bc8102f87f9eed26e144761eadb0 Log: Merge pull request #55 from blt04/fix-matrix-multi [FIXED JENKINS-18237] Fix matrix multiple scm builds Compare: https://github.com/jenkinsci/mercurial-plugin/compare/1b5c20155dd0...5dfe7720d202 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-18237) Multiple hg repos vs matrix job - the same revision used for all repositories.
SCM/JIRA link daemon resolved JENKINS-18237 as Fixed Multiple hg repos vs matrix job - the same revision used for all repositories. Change By: SCM/JIRA link daemon (18/Feb/14 3:33 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-failure-analyzer] (JENKINS-21854) Allow failure reason to propogate to upstream jobs
Aidan McGinley created JENKINS-21854 Allow failure reason to propogate to upstream jobs Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer Created: 18/Feb/14 3:28 PM Description: If we could get an option added to a job's configuration to propogate the failure reason to upstream jobs that would be very beneficial. Right now if a triggered job fails because of one of it's downstream jobs then you must navigate through the build graph to the failed job, it would be nice if the failure surfaced on the parent job instead. Project: Jenkins Priority: Major Reporter: Aidan McGinley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16871) Inconsistent use of XML escaping in config.xml when uploading through API
evernat commented on JENKINS-16871 Inconsistent use of XML escaping in config.xml when uploading through API Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-12843) Failure with maven 3 jobs and shade plugin
evernat resolved JENKINS-12843 as Incomplete Failure with maven 3 jobs and shade plugin No response from the reporter, so resolving as incomplete. Change By: evernat (18/Feb/14 3:25 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-11920) All jobs (even a job with no steps) hang for twenty minutes after completion on Solaris
evernat resolved JENKINS-11920 as Incomplete All jobs (even a job with no steps) hang for twenty minutes after completion on Solaris No response from the reporter, so resolving as incomplete. Change By: evernat (18/Feb/14 3:27 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-auth] (JENKINS-21847) Project based authentication not showing in configure project
Jesse Glick resolved JENKINS-21847 as Cannot Reproduce Project based authentication not showing in configure project Working fine for me in 1.553-SNAPSHOT. Make sure you have selected Project-based Matrix Authorization Strategy, not Matrix-based security. If you still encounter the issue you will need to debug it yourself I think. Change By: Jesse Glick (18/Feb/14 3:09 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21853) Assigned node text field should be made an editable combo box
Jesse Glick created JENKINS-21853 Assigned node text field should be made an editable combo box Issue Type: Improvement Assignee: Unassigned Components: core Created: 18/Feb/14 3:03 PM Description: While the typing completion in the label _expression_ field is nice, it is lousy for exploring available labels, since it only starts to offer completion after you have typed the first letter, which only lets you see them all if you go through all 26! An editable combo box listing all known label atoms would be more helpful. (Must be editable, since you can type in boolean expressions, and it is legal to request a label which does not correspond to any slave yet attached.) Project: Jenkins Labels: ui usability slaves labels Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite updated JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect Removed git-client-plugin from the list of components, since the bitbucket URL is included in the git-plugin, not in the git-client-plugin Change By: Mark Waite (18/Feb/14 2:41 PM) Component/s: git-client This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21139) Git client fails to handle slashes in branch refs
Mark Waite resolved JENKINS-21139 as Fixed Git client fails to handle slashes in branch refs Submitter notes that the problem was a configuration issue. Previous versions of the plugin assumed "origin" if the remote name field from the advanced tab was left blank. Current versions seem to require that field when referring to the remote. Change By: Mark Waite (18/Feb/14 2:40 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21139) Git client fails to handle slashes in branch refs
Mark Waite closed JENKINS-21139 as Fixed Git client fails to handle slashes in branch refs Change By: Mark Waite (18/Feb/14 2:40 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/groups/opt_out.
[JIRA] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
Mark Waite closed JENKINS-17413 as Cannot Reproduce Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM Unfortunately, I don't think the exception you were seeing is related to the refspec. I'm not sure what causes those types of JSON conversion errors, but the cases I've detected have seem to be related to jobs defined with git-plugin 1.x versions that are now being edited with git-plugin 2.x. There were significant improvements in usability with git-plugin 2.x, but those improvements caused some compatibility changes. Change By: Mark Waite (18/Feb/14 2:36 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/groups/opt_out.
[JIRA] [git] (JENKINS-12103) git polling constantly triggers for new (empty) git repos
Mark Waite closed JENKINS-12103 as Fixed git polling constantly triggers for new (empty) git repos Change By: Mark Waite (18/Feb/14 2:33 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/groups/opt_out.
[JIRA] [git] (JENKINS-12103) git polling constantly triggers for new (empty) git repos
Mark Waite resolved JENKINS-12103 as Fixed git polling constantly triggers for new (empty) git repos As far as I can tell from my initial verification attempt, this bug is resolved in git-plugin 2.0.1 and git-client-plugin 1.6.2. I don't have a gerrit server, so I created an empty bare repository using git protocol on my Debian git server, then defined a job which read that git protocol repository. I ran the job interactively once. It failed because there was no version to build. I then confirmed that the polling did not cause further jobs to be launched. I think failing because there is no version to build is a reasonable behavior, since an empty repository is quite exceptional and I'd rather have the failure indicate that exceptional condition, rather than having to read log files to realize that a successful job had no revision to build. Change By: Mark Waite (18/Feb/14 2:33 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
David Walend commented on JENKINS-17413 Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM Don't worry about reproducing it. It's been eleven months! Can you change the message to something telling us what's wrong with the ref spec? That'd be most helpful. I was able to provide a ref spec that the code could digest, even though they worked fine with command-line git. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-12703) jenkins and git over windows7 permission denied
Mark Waite closed JENKINS-12703 as Fixed jenkins and git over windows7 permission denied Change By: Mark Waite (18/Feb/14 2:24 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/groups/opt_out.
[JIRA] [git] (JENKINS-12703) jenkins and git over windows7 permission denied
Mark Waite resolved JENKINS-12703 as Fixed jenkins and git over windows7 permission denied Credentials support has been added to git-client-plugin and git-plugin to simplify both the use and the diagnosis of this type of failure. Try credentials with the most recent plugins and the long term support version of Jenkins. Change By: Mark Waite (18/Feb/14 2:24 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15020) Fails to build a successful build
Mark Waite resolved JENKINS-15020 as Fixed Fails to build a successful build The current git-client-plugin and git-plugin no longer call git --version, so I believe this is resolved. Change By: Mark Waite (18/Feb/14 2:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16523) Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command: --version)
Mark Waite resolved JENKINS-16523 as Fixed Git plugin fails with NullPointerException (Error trying to determine the git version: Error performing command: --version) The current git-client-plugin and git-plugin releases do not call "git --version", so I believe this is resolved Change By: Mark Waite (18/Feb/14 2:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Mark Waite resolved JENKINS-16693 as Fixed Heap error while polling Git Plug-in after upgrade to 1.1.26. As far as I can tell, there are no uses of "git show" in the git-client-plugin 1.6.2 or in the git-plugin 2.0.1. There is a single use of the "git whatchanged" command which might cause this type of problem, but was not listed in the original analysis of the bug. Can the original submitter or others who have seen the problem confirm it is fixed? Change By: Mark Waite (18/Feb/14 2:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-17413) Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instant
Mark Waite resolved JENKINS-17413 as Cannot Reproduce Unhelpful exception caused by a NullPointerException while attempting to use a git refspec -- javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.git.GitSCM I tried to duplicate this problem using git-client-plugin 1.6.2 and git-plugin 2.0.1 without success. Does the original submitter or the first person who commented still see the problem with the most recent versions of those plugins? Change By: Mark Waite (18/Feb/14 2:07 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18303) Cannot do checkout of a git repository in BitBucket in Jenkins
Mark Waite resolved JENKINS-18303 as Fixed Cannot do checkout of a git repository in BitBucket in Jenkins The addition of credentials support to the git-client-plugin and the git-plugin has made this type of failure much less frequent. I have a bitbucket test job which regularly performs a checkout and build of the git-client-plugin source code from a copy I keep on bitbucket. Could you check if this bug is fixed with git-client-plugin 1.6.2 (or later) and git-plugin 2.0.1 (or later)? Change By: Mark Waite (18/Feb/14 1:58 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
