[JIRA] [core] (JENKINS-23383) Console output live feed is broken
Orgad Shaneh commented on JENKINS-23383 Console output live feed is broken Well, it never happened before 1.566. Are you sure this isn't a bug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-18849) java.lang.ClassNotFoundException: hudson.maven.AbstractMavenProject
Daniel Beck commented on JENKINS-18849 java.lang.ClassNotFoundException: hudson.maven.AbstractMavenProject Right, I checked this issue in more detail and they're only superficially the same: Due to IO problems of some kind it failed to extract the Maven Plugin (and possibly Monitor External Job), so it's not just disabled, but missing completely. The effect is the same as with a disabled plugin post-1.524. Fix the logged IO root cause (e.g. missing permissions), possibly deleting maven-plugin.jpi and the issue should disappear. More information is needed to investigate this further, like the permissions inside the plugins directory, what kind of file system, etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23383) Console output live feed is broken
Daniel Beck commented on JENKINS-23383 Console output live feed is broken I've seen accumulation of cookies before with parts of Jenkins failing to process the header. Maybe that should be considered the bug. Needs to be filed independently (maybe pointing to this one as one of the negative effects), with more information (e.g. which cookie, what are the values, etc.). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23410) Kill win32 processes from win64 JVMs
dogfood commented on JENKINS-23410 Kill win32 processes from win64 JVMs Integrated in jenkins_main_trunk #3463 FIXED JENKINS-23410 (Revision fad3f7db48e4184221469fbbb0edc2163e26ac0f) Result = SUCCESS kohsuke : fad3f7db48e4184221469fbbb0edc2163e26ac0f Files : core/pom.xml changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-16780) release build fails to deploy new SNAPSHOT pom artifact with 409 error
stevengbrown resolved JENKINS-16780 as Fixed release build fails to deploy new SNAPSHOT pom artifact with 409 error Confirmed that this is fixed in Jenkins Artifactory Plugin 2.2.3. Was fixed under HAP-373 Change By: stevengbrown (12/Jun/14 6:30 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Oleg Nenashev commented on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Partial fix: https://github.com/jenkinsci/jenkins/pull/1275 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Oleg Nenashev started work on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Change By: Oleg Nenashev (12/Jun/14 6:46 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23411) Parallel deletion of jobs from the ListView may lead to NPE errors
Oleg Nenashev
created JENKINS-23411
Parallel deletion of jobs from the ListView may lead to NPE errors
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
core
Created:
12/Jun/14 6:53 AM
Description:
A report from Coverity:
*** CID 1222626: Dereference null return value (NULL_RETURNS)
/src/main/java/hudson/model/ListView.java: 334 in hudson.model.ListView.doRemoveJobFromView(java.lang.String)()
328 @RequirePOST
329 public HttpResponse doRemoveJobFromView(@QueryParameter String name) throws IOException, ServletException {
330 checkPermission(View.CONFIGURE);
331 if(name==null)
332 throw new Failure("Query parameter 'name' is required");
333
CID 1222626: Dereference null return value (NULL_RETURNS)
Assigning: "item" = null return value from "resolveName".
334 TopLevelItem item = resolveName(name);
335 if (remove(item))
336 owner.save();
337
338 return HttpResponses.ok();
339 }
Project:
Jenkins
Priority:
Major
Reporter:
Oleg Nenashev
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23411) Parallel deletion of jobs from the ListView may lead to NPE errors
Oleg Nenashev updated JENKINS-23411 Parallel deletion of jobs from the ListView may lead to NPE errors Change By: Oleg Nenashev (12/Jun/14 6:55 AM) URL: https://scan5.coverity.com:8443/reports.htm#v33873/p10292/fileInstanceId=58237456defectInstanceId=17964666mergedDefectId=1222626 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23369) Unable to check-in using bypass mode
Szymon Michna commented on JENKINS-23369 Unable to check-in using bypass mode I agree that :bypass option is a kind of hack, but you have to have such a permission to do that so you don't use it accidentally. Unfortunately our requirement is to automate the update a version number in the AssemblyInfo files, and check them into MKS before the build. Since the builds are often done many times a day it would be quite time consuming to manually have to accept the change packages and will as such add a manual process into what should be an automated build. I get the point of not having too many options for the plugin on Jenkins so that it's not overly complicated but perhaps my argument can convience you to reconsider adding the bypass option to the check-in plugin. Or perhaps you have other suggestions how can we automate the check-in of AssemblyInfo files changed by the builds in Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23310) Code signing certificate of winp.dll has expired
Daniel Beck commented on JENKINS-23310 Code signing certificate of winp.dll has expired New Winp release was integrated for 1.569 (JENKINS-23410). Maybe the cert issue has been fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23332) No longer able to specify JDK version in Maven 2/3 jobs
Daniel Beck commented on JENKINS-23332 No longer able to specify JDK version in Maven 2/3 jobs jrh3k5: More information is needed to investigate this issue further. Do you have the config.xml from before the update? Is there a warning or error related to loading it logged in jenkins.log from after the 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/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) iframe tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Ramakrishna Bejawar commented on JENKINS-23198 iframe tag not working after upgrading to Jenkins Version 1.559. Doesnt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Hi Roop Vijay I have upgraded to Jenkins 1.559, May be this issue exists in 1.559 + versions. Its not about Jenkins version particularly, Its the plug-in, So need to identify the plug-in name and version and look for resolution. Kind Regards.. Ramakrishna This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) iframe tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Ramakrishna Bejawar edited a comment on JENKINS-23198 iframe tag not working after upgrading to Jenkins Version 1.559. Doesnt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Hi Roop Vijay I have upgraded to Jenkins 1.559, May be this issue exists in 1.559 + versions. Its not about Jenkins version particularly, Its the plug-in, So need to identify the plug-in name and version and look for resolution. Kind Regards.. Ramakrishna Bejawar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression
Daniel Beck updated JENKINS-2 Label display wrong when using operators in _expression_ Not a bug, but I agree this should be changed. Could be done in a plugin though. Change By: Daniel Beck (12/Jun/14 8:54 AM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
Daniel Beck commented on JENKINS-23305 NPE on running some slaves of a matrix build - failure with no explanation … and the constructor takes only a boolean. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23392) Jenkins less responsive after 1.567 update
Daniel Beck commented on JENKINS-23392 Jenkins less responsive after 1.567 update Make sure that you have no loggers configured to log at levels ALL, FINEST, FINER, or FINE at /log/levels. If so, remove custom loggers. Also, while a page is loading, try to get a thread dump either using the jstack tool or the /threadDump page. Attach the result to this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23412) Way to configure description to check in action
Michal Sobczak created JENKINS-23412 Way to configure description to check in action Issue Type: Improvement Assignee: Cletus DSouza Components: integrity-plugin Created: 12/Jun/14 9:19 AM Description: Hi, I want to set description for member revision. Now it use "full build name" (job display name + build name) but I need more information (e.g. build url) It is possible to make it configurable (maybe by some env variable)? Best Regards, Michal Sobczak Project: Jenkins Priority: Minor Reporter: Michal Sobczak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-23413) xunit plugin does not work with XML produced by QTestlib
Mike Melga created JENKINS-23413 xunit plugin does not work with XML produced by QTestlib Issue Type: Bug Assignee: Unassigned Components: xunit Created: 12/Jun/14 9:57 AM Description: xUnit plugin does not work with XML produced by QTestlib, using the xunitxml parameter. The error: "The converted file for the result file '/Users/Shared/Jenkins/Home/jobs/project/workspace/xtestresults.xml' (during conversion process for the metric 'QTestlib') is not valid." I tried to find the corresponding XSL in the usercontent directrory but could not find it. Using version 1.88 of the xUnit Plugin Environment: Mac OS Project: Jenkins Labels: xunit Priority: Minor Reporter: Mike Melga This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Ashok Manji commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Thanks for the update Kohsuke. Looking forward to the resolution This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-20086) Improve the archive artifacts plugin to incude hidden files/directories like .git
Gigi Lentini commented on JENKINS-20086 Improve the archive artifacts plugin to incude hidden files/directories like .git I came across the same issue using Jenkins 1.554.1, and the zip/unzip workaround seems to work for the moment. But I would rather use a clear jenkins config to do so. Do you have any update? Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter] (JENKINS-23414) Add support for build flow job name
Steve Osselton created JENKINS-23414 Add support for build flow job name Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: build-name-setter Created: 12/Jun/14 10:46 AM Description: Would be nice to set build name for a build flow job, currently can't do this as doesn't have it's own build step. Project: Jenkins Priority: Major Reporter: Steve Osselton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Frank Lee
created JENKINS-23415
2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git, git-client, github, github-api, github-oauth
Created:
12/Jun/14 10:58 AM
Description:
Problem:
A job keeps triggering when it should not.
Background:
2 separate jobs are configured to be triggered on the same Github repository depending on branch that pushed to.
When pushing to the 1st branch, "origin/test/branch1", the 1st job is triggered. Good.
When pushing to the 2nd branch, "origin/test/branch2", the 2nd job triggers. Good.
But the 1st job is triggered again. Bad. There's only been 2 pushes.
The repository is very large, so the git clone takes a few minutes for both jobs.
The problem consistently occurs when pushing to the 1st branch, THEN immediately pushing to the 2nd branch. The 1st job is triggered and git cloning. And the 2nd job is triggered and queued. BUT another 1st job is triggered and queued.
Seems to happen when it's still downloading during the clone.
That extra triggered job is causing us grief, because it's used for deployments.
This is reproducible consistently with this script:
#!/bin/bash
pushd mydirectory
git checkout develop
echo ${1}d d.txt
git add .
git commit -m "${1}d"
git push
git checkout test/branch1
git pull --no-edit upstream develop
git push
git checkout test/main
git pull --no-edit upstream test/branch2
git push
popd
And run it as:
./script 1
./script 2
etc...
Jenkins v1.558
Git Client v1.9.0
Git plugin v2.2.1
GitHub API v1.44
Github OAuth v0.14
GitHub Pull Request Builder 1.12
Environment:
CentOS 5, JDK 1.7
Project:
Jenkins
Labels:
jenkins
git
scm
Priority:
Major
Reporter:
Frank Lee
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22193) Add an option to disable the Jar caching
Daniel Beck commented on JENKINS-22193 Add an option to disable the Jar caching IMO this could be resolved as duplicate of JENKINS-18574. A safe location should always be available in the slave home path... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-23416) Configuration LDAP
Christophe Marclay created JENKINS-23416 Configuration LDAP Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Attachments: ORBIUM-LDAP.PNG Components: ldap Created: 12/Jun/14 11:39 AM Description: Hello, We can't configure the security in LDAP with our Active Directory. Can you help us please in this configuration. Thank you. Best regards. Due Date: 13/Jun/14 12:00 AM Environment: Windows 2008 R2 Project: Jenkins Priority: Minor Reporter: Christophe Marclay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22238) IOException archiving artifacts in 1.550
Daniel Beck resolved JENKINS-22238 as Cannot Reproduce IOException archiving artifacts in 1.550 JENKINS-22442 has been resolved in 1.558 and 1.554.1. Based on the comments to this issue, this seems to have the same cause, so closing with the assumption that this issue is obsolete. If this still occurs in the mentioned Jenkins versions or newer, feel free to reopen. Change By: Daniel Beck (12/Jun/14 11:45 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23334) Jenkins Frezees After Windows Security Patches Applied
Murat Gundogdu reopened JENKINS-23334 Jenkins Frezees After Windows Security Patches Applied Actually we couldn't have any workaround to solve this issue and still waiting patches uninstalled until the issue is solved. We contacted with Microsoft, but they said this should be a Jenkins related issue since they've no other feedback from customers. We would be more than happy to assist Jenkins developers by providing any information or log needed. Thanks Change By: Murat Gundogdu (12/Jun/14 11:57 AM) 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/d/optout.
[JIRA] [core] (JENKINS-23334) Jenkins Frezees After Windows Security Patches Applied
Murat Gundogdu edited a comment on JENKINS-23334 Jenkins Frezees After Windows Security Patches Applied Actually we couldn't find any workaround to solve this issue and to be frankly we have no hope to find one in the future. We're still waiting patches uninstalled until the issue is solved. We contacted with Microsoft, but they said this should be a Jenkins related issue since they've no other feedback from customers. We would be more than happy to assist Jenkins developers by providing any information or log needed. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-20086) Improve the archive artifacts plugin to incude hidden files/directories like .git
Daniel Beck
commented on JENKINS-20086
Improve the archive artifacts plugin to incude hidden files/directories like .git
Jenkins uses Ant to archive files. It excludes the following patterns related to various SCM by default (run in Script Console):
org.apache.tools.ant.DirectoryScanner.defaultExcludes.each { println it }
This can be changed globally by running the script below in the Script Console (until the next restart) or by adding a .groovy file with that script in JENKINS_HOME/init.groovy.d/ so this gets loaded upon startup:
org.apache.tools.ant.DirectoryScanner.defaultExcludes.each { org.apache.tools.ant.DirectoryScanner.removeDefaultExclude(it) }
I doubt that this is deserving a per-project preference, given the relative obscurity of the requirement. IMO a cleaner solution would be to extract the relevant data during the build and store it outside the SCM metadata folders.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9192) lastSuccessful and lastStable symbolic links are not being created on Windows
Walter Kacynski resolved JENKINS-9192 as Fixed lastSuccessful and lastStable symbolic links are not being created on Windows This feature works when Jenkins runs as an account that is allowed to create symlinks. Change By: Walter Kacynski (12/Jun/14 12:22 PM) Status: Open Resolved Assignee: tdtappe 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/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-22325) Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build
Shawn Perkins commented on JENKINS-22325 Parameterized Remote Trigger Plugin fails with FATAL: Invalid JSON String after triggering the remote build How long does it typically take for the main repository to pick up the new release? I see that it still shows 2.1 as the version and I could use this fix. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-23416) Configuration LDAP
Daniel Beck resolved JENKINS-23416 as Not A Defect Configuration LDAP This is not a support site, but an issue tracker. Try the mailing lists, or IRC. Change By: Daniel Beck (12/Jun/14 1:23 PM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23392) Jenkins less responsive after 1.567 update
Igor Koyfman resolved JENKINS-23392 as Not A Defect Jenkins less responsive after 1.567 update Looks like it probably isn't this version of Jenkins. I downgraded and still see the issue, so it's more likely the server is being slow. Change By: Igor Koyfman (12/Jun/14 1:39 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23415) 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading
Mark Waite commented on JENKINS-23415 2 Jobs w/same repo. Job triggers twice when first triggered job is Git SCM is still downloading I attempted to duplicate the bug and was unsuccessful. I'll need more information before further investigation is performed. I created an initial repository with the following structure of commits: * 3bcea79 (upstream/test/main, test/main) Adapt README for test/main branch | * b3b7c59 (upstream/test/branch2, test/branch2) Adapt README for test/branch2 |/ | * 4f038d3 (upstream/test/branch1, test/branch1) Adapt README for the test/branch1 branch |/ | * 5ccca9d (HEAD, upstream/develop, develop) Updated README for the develop branch |/ * ea8c87b (upstream/master, master) Add README I created a script in the parent directory as you listed. I created a Jenkins job monitoring upstream/test/branch1, polling every 2 minutes, confirmed it was checking out correct branch I created a Jenkins job monitoring upstream/test/branch2, polling every 2 minutes, confirmed it was checking out correct branch I ran the script with argument 1 I confirmed the Jenkins job on test/branch1 ran and the Jenkins job on test/branch2 did not run After that, I tried further by defining a hook in the git repo which caused the Jenkins jobs to poll each time there was a commit to the repo. The jobs when polled as a result of the hook also behaved as expected. The job monitoring test/branch1 ran each time there was a commit to test/branch1. The job monitoring test/branch2 did not run when there was a commit to test/branch1. Can you provide more details of your configuration (job definitions, etc.) and confirm that the same problem can be duplicated on another Jenkins server? Can you update your git client plugin from 1.9.0 to the currently released 1.9.1, in case there is some relevant difference between the version you're using and the version I'm using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Ireneusz Makowski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Second stack trace: owned by "Executor #-1 for plkrbuilddb : executing FlexNet 10 - TeamAUTO » 2 Database Tests » DBU #97" Id=41963 at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:648) blocked on hudson.model.RunMap@231579 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:381) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:219) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1643) at hudson.model.User.getProjects(User.java:479) at hudson.scm.BlameSubversionMailAddressResolverImpl.findMailAddressFor(BlameSubversionMailAddressResolverImpl.java:23) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:112) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:547) at hudson.plugins.emailext.EmailRecipientUtils.getUserConfiguredEmail(EmailRecipientUtils.java:110) at hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider.addRecipients(CulpritsRecipientProvider.java:41) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:516) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:79) at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:689) at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:403) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1709) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Daniel Beck
commented on JENKINS-23232
SEVERE: I/O error in channel Chunked connection
Ashok: What's the output of
System.getProperty('hudson.diyChunking')
in Manage Jenkins » Script Console?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Thiago Zanetti commented on JENKINS-19994 Unable to delete workspace Mark Waite We are using JGit (git-client-plugin) version 1.9.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Ok, so its the Subversion mail address resolution that is taking a long time. That is not the email-ext plugin's fault. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Thiago Zanetti edited a comment on JENKINS-19994 Unable to delete workspace Mark Waite We are using JGit (git-client-plugin) version 1.9.1 As far as I know there's no other service using git besides Jenkins in this machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-23159) Cron column is forced upon new default views
SCM/JIRA link daemon commented on JENKINS-23159 Cron column is forced upon new default views Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/CronViewColumn.java http://jenkins-ci.org/commit/cron_column-plugin/62ff65c4f4206a046e10129fce7eaeeb0a04829c Log: FIXED JENKINS-23159 Do not show by default. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-23159) Cron column is forced upon new default views
SCM/JIRA link daemon commented on JENKINS-23159 Cron column is forced upon new default views Code changed in jenkins User: Jesse Glick Path: .gitignore pom.xml src/main/java/hudson/plugins/CronViewColumn.java http://jenkins-ci.org/commit/cron_column-plugin/51fb9a28eb45c791aee34e2a948ce68e8fa09c78 Log: Merge pull request #1 from jglick/JENKINS-23159-default JENKINS-23159 Do not show column by default Compare: https://github.com/jenkinsci/cron_column-plugin/compare/b31d6ae66c17...51fb9a28eb45 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) What version of the Mailer plugin do you have installed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-23159) Cron column is forced upon new default views
SCM/JIRA link daemon resolved JENKINS-23159 as Fixed Cron column is forced upon new default views Change By: SCM/JIRA link daemon (12/Jun/14 2:11 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Ireneusz Makowski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) One stack trace: at java.lang.reflect.Method.copy(Unknown Source) at java.lang.reflect.ReflectAccess.copyMethod(Unknown Source) at sun.reflect.ReflectionFactory.copyMethod(Unknown Source) at java.lang.Class.copyMethods(Unknown Source) at java.lang.Class.getMethods(Unknown Source) at org.apache.commons.beanutils.MethodUtils.getMatchingAccessibleMethod(MethodUtils.java:973) at org.apache.commons.beanutils.MappedPropertyDescriptor.getMethod(MappedPropertyDescriptor.java:409) at org.apache.commons.beanutils.MappedPropertyDescriptor.init(MappedPropertyDescriptor.java:111) at org.apache.commons.beanutils.PropertyUtilsBean.getPropertyDescriptor(PropertyUtilsBean.java:934) at org.apache.commons.beanutils.BeanUtilsBean.setProperty(BeanUtilsBean.java:935) at org.apache.commons.beanutils.BeanUtilsBean.populate(BeanUtilsBean.java:830) at org.apache.commons.beanutils.BeanUtils.populate(BeanUtils.java:433) at org.apache.commons.digester.SetPropertiesRule.begin(SetPropertiesRule.java:254) at org.apache.commons.digester.Rule.begin(Rule.java:177) at org.apache.commons.digester.Digester.startElement(Digester.java:1583) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1871) at hudson.scm.BlameSubversionChangeLogParser.parse(BlameSubversionChangeLogParser.java:68) at hudson.scm.BlameSubversionChangeLogParser.parse(BlameSubversionChangeLogParser.java:47) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:922) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:896) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:454) at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1644) at hudson.model.User.getProjects(User.java:479) at hudson.scm.BlameSubversionMailAddressResolverImpl.findMailAddressFor(BlameSubversionMailAddressResolverImpl.java:23) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:112) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:547) at hudson.plugins.emailext.EmailRecipientUtils.getUserConfiguredEmail(EmailRecipientUtils.java:110) at hudson.plugins.emailext.plugins.recipients.CulpritsRecipientProvider.addRecipients(CulpritsRecipientProvider.java:41) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:516) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.access$100(ExtendedEmailPublisher.java:79) at hudson.plugins.emailext.ExtendedEmailPublisher$1.endBuild(ExtendedEmailPublisher.java:689) at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:403) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1709) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at
[JIRA] [scripttrigger] (JENKINS-14076) Would like the ability to create a changelog for jobs triggered by scripttrigger
Steven Owens commented on JENKINS-14076 Would like the ability to create a changelog for jobs triggered by scripttrigger It looks like this has been stagnant for some time. I think the feature would be great also. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Ireneusz Makowski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Mailer plugin is in version 1.8, but I believe i use override section in configuration, then this plugin is not used (Override Global Settings - this setting is used) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Jesse Glick updated JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Change By: Jesse Glick (12/Jun/14 2:34 PM) Labels: jenkins permalinksymlink This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22803) 'JellyTagException: st:include For input string: ' on job view
Jesse Glick resolved JENKINS-22803 as Duplicate JellyTagException: st:include For input string: on job view Change By: Jesse Glick (12/Jun/14 2: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/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Jesse Glick commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand First of all, I doubt this has anything to do with the Maven plugin. Jenkins core creates build number symlinks. Second, what is the actual bug here? That some old Windows backup programs cannot handle symlinks even when the Windows kernel/filesystem can produce them? That is the fault of the backup program, not Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Jesse Glick resolved JENKINS-21459 as Duplicate Jenkins dont run jobs from queue (there are available executors) Change By: Jesse Glick (12/Jun/14 2:40 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/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Jesse Glick updated JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Change By: Jesse Glick (12/Jun/14 2:40 PM) Labels: lts-candidate permalinksymlink This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Jesse Glick commented on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Clearly there is a corrupted build symlink in one of your build directories. But what created it? That is the question. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
SCM/JIRA link daemon resolved JENKINS-21631 as Fixed java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Change By: SCM/JIRA link daemon (12/Jun/14 2:44 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
SCM/JIRA link daemon commented on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/2b89f9d09e3426de8d2d311e059f24cb1c0b0b10 Log: FIXED JENKINS-21631 Noting #1275. Compare: https://github.com/jenkinsci/jenkins/compare/fad3f7db48e4...2b89f9d09e34 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
SCM/JIRA link daemon commented on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Code changed in jenkins User: Jesse Glick Path: core/src/main/java/jenkins/model/PeepholePermalink.java http://jenkins-ci.org/commit/jenkins/74680ca2213255e937df833f956afa821b82a90b Log: Merge branch 'JENKINS-21631' of github.com:synopsys-arc-oss/jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
SCM/JIRA link daemon commented on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/model/PeepholePermalink.java http://jenkins-ci.org/commit/jenkins/5df3f74b4e7700d5f51243ced4c97fdc209c6fb2 Log: JENKINS-21631 - Don't fail with NPE if the PeepholePermalink cache contains the non-numeric value. Actually, the change just prevents symptoms. There should be an error somewhere else. Signed-off-by: Oleg Nenashev o.v.nenas...@gmail.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) iframe tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Roop Vijay Singh commented on JENKINS-23198 iframe tag not working after upgrading to Jenkins Version 1.559. Doesnt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Hi Ramakrishna, I resolved it on my end. you can Install Anything Goes Formatter Plugin. 'Raw HTML', despite it's name, only allows a safe subset of HTML. Iframes are not considered safe. Regards RoopVijay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen commented on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Jesse it is not the build number links. The Maven build includes a section called Module Builds. The plugin seems to create a link for each Module. These module links are the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Ashok Manji commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection @Daniel Beck - Result: true This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) The MailAddressResolver is part of the Mailer plugin. email-ext uses this to resolve an address for a username. MailAddressResolver is an extension point that allows other plugins to provide an address resolver, SCM systems generally will provide one to map a committer username to an email address. In the case of the slowdown you are seeing, the BlameSubversionMailAddressResolverImpl is what is taking a long time, not email-ext itself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
Oleg Nenashev started work on JENKINS-23305 NPE on running some slaves of a matrix build - failure with no explanation Change By: Oleg Nenashev (12/Jun/14 3:31 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
Oleg Nenashev assigned JENKINS-23305 to Oleg Nenashev NPE on running some slaves of a matrix build - failure with no explanation Change By: Oleg Nenashev (12/Jun/14 3:31 PM) Assignee: OlegNenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
Oleg Nenashev commented on JENKINS-23305 NPE on running some slaves of a matrix build - failure with no explanation Sorry, I've missed the previous message... trejkaz is right. The implicit unboxing of null Boolean values throws NPE according to Java specs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Oleg Nenashev commented on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() @Jesse I suppose we should create additional issues for glitches in permalink contents. I'm almost sure that users do not inject garbage (this issue) or empty (JENKINS-21459) strings manually. These glitches may decrease the performance of Jenkins core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Oleg Nenashev edited a comment on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() @Jesse I suppose we should create additional issues for glitches in permalink contents. I'm almost sure that users do not inject garbage (this issue) or empty (JENKINS-21459) strings manually. These cases may decrease the performance of Jenkins core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [visualworks-store] (JENKINS-23389) Unable to check out project on build slave
SCM/JIRA link daemon commented on JENKINS-23389 Unable to check out project on build slave Code changed in jenkins User: Randy Coulman Path: src/main/java/org/jenkinsci/plugins/visualworks_store/StoreSCM.java src/test/java/org/jenkinsci/plugins/visualworks_store/StoreSCMTest.java http://jenkins-ci.org/commit/visualworks-store-plugin/7c63ff058a2fe04b95c2ec7e51eab8fc945d0310 Log: FIXED JENKINS-23389 Support checking out on a build slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [visualworks-store] (JENKINS-23389) Unable to check out project on build slave
SCM/JIRA link daemon resolved JENKINS-23389 as Fixed Unable to check out project on build slave Change By: SCM/JIRA link daemon (12/Jun/14 3:55 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-17235) No error message displayed even on failure if I try to run the same job with same params in parallel
Ying Gan commented on JENKINS-17235 No error message displayed even on failure if I try to run the same job with same params in parallel I have the similar issue. In parallel block I called a job doesn't exist. Build flow failed but log doesn't report anything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve()
Jesse Glick commented on JENKINS-21631 java.lang.NumberFormatException: For input string: !symlink in PeepholePermalink::resolve() @oleg_nenashev: yes I imagine something on Windows caused the bogus contents to appear, and we would like to find what. Also it would be nice if after catching NumberFormatException we deleted the problematic file so the warning only appears once per file. And it would be better to print a one-line warning, since the full stack trace is not really interesting: lots of code can (indirectly) call the resolve method without being at fault, and in the other direction the actual thrower of NumberFormatException is irrelevant if you have the message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite
commented on JENKINS-19994
Unable to delete workspace
I wasn't clear enough with my question. Are you using the default git provider ("Default" - which uses command line git as its back end implementation), or the "JGit" provider ("jgit" - which uses the Eclipse jgit implementation as its "back end provider")?
You can tell which you're using in the job definition. If there is a pick list to choose your git, then read the value of that pick list. If there is no pick list, then you're using the default and have not configured jgit at all.
Also, can you use Windows task manager to search for any processes named "git.exe". If a git process blocks waiting for authentication, it may hold files open so that they cannot be deleted (on Windows).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve()
Oleg Nenashev updated JENKINS-21631 java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve() Change By: Oleg Nenashev (12/Jun/14 4:03 PM) Summary: java.lang.NumberFormatException:Forinputstring: ! symlink variousstuff inPeepholePermalink::resolve() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve()
Oleg Nenashev reopened JENKINS-21631 java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve() Ok. Lets reopen the issue and use it as a master one. Change By: Oleg Nenashev (12/Jun/14 4:04 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22453) Invalid symbolic links get archived but cannot be copied using Copy Artifacts
Ingo Richter commented on JENKINS-22453 Invalid symbolic links get archived but cannot be copied using Copy Artifacts I ran into this issue a couple of days ago, when a job suddenly started to fail. Does anybody know what has changed in this particular area that causes this feature not to work properly anymore? I'm curious how symbolic links have been handled before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve()
Jesse Glick commented on JENKINS-21631 java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve() (Of course any follow-up improvements to the current fix, such as deleting the problematic file, would fall under the scope of this issue.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21631) java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve()
Jesse Glick resolved JENKINS-21631 as Fixed java.lang.NumberFormatException: For input string: various stuff in PeepholePermalink::resolve() I think this issue—that various innocent operations can fail when there is a malformed symlink, causing serious problems—should be closed as fixed, and be immediately eligible for backport. But we should somehow track the root issue, that the malformed symlinks are being produced by something; given this fix, that is much less serious. Change By: Jesse Glick (12/Jun/14 4:13 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/d/optout.
[JIRA] [core] (JENKINS-23405) Proper incorporation of YUI
Tom FENNELLY edited a comment on JENKINS-23405 Proper incorporation of YUI I forked yui2 into my own repo (for starters): https://github.com/tfennelly/yui2 I'm trying to find out how they actually built the full release assembly as this is the easiest path to making sure we are getting the right changes over in Jenkins. the yui2 codebase does not have it's own top level build script. Instead, it relies on a a separate "YUI Builder" project, which typically needs to be checked out separately to a folder parallel to the yui code. I actually checked this into a "builder" folder in my fork. The problem I'm trying to get to the bottom of is the fact that this Builder just builds a single component (e.g. "buttons"). I'm trying to find out where the higher level release scripts are located - they do an aggregated build + apply copyright, version info etc. I was trying to hack this (build.xml in the root of my fork) but it just results in a ton of diffs. Most of the diffs are OK (missing copyrights etc) but I'd like to get rid of them by building it properly if I can. Then I can see the real differences. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23405) Proper incorporation of YUI
Tom FENNELLY commented on JENKINS-23405 Proper incorporation of YUI I forked yui2 into my own repo (for starters): https://github.com/tfennelly/yui2 I'm trying to find out how they actually built the full release assembly as this is the easiest path to making sure we are getting the right changes over in Jenkins. the yui2 codebase does not have it's own top level build script. Instead, it relies on a a separate "YUI Builder" project, which typically needs to be checked out separately to a folder parallel to the yui code. I actually checked this into a "builder" folder in my fork. The problem I'm trying to get to the bottom of is the fact that this Builder just builds a single component (e.g. "buttons"). I'm trying to find out where the higher level release scripts are located - they do an aggregated build + apply copyright, version info etc. I was trying to hack this but it just results in a ton of diffs. Most of the diffs are OK (missing copyrights etc) but I'd like to get rid of them by building it properly if I can. Then I can see the real differences. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23405) Proper incorporation of YUI
Tom FENNELLY commented on JENKINS-23405 Proper incorporation of YUI Here's the google group post I made trying to get this info: https://groups.google.com/forum/#!topic/yui-deprecated/3dfWrEoYOlI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Jakub Czaplicki commented on JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Back to drawing board. Summary from https://github.com/jenkinsci/jenkins/pull/1273 : There's no jQuery available in the core Should use Behaviour.add from within BuildHistoryWidget/entries.jelly rather than modifying the generic layout page. gerrit-trigger-plugin ought to define custom parameter types, with customized presentation, rather than overloading standard textual ones This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen edited a comment on JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Jesse it is not the build number links that are problematic. The Maven build includes a section called Module Builds. The plugin seems to create a link for each Module. These module links are the problem. The Windows OS does not see the links as valid. I believe the links contain a path and the path uses the wrong path separator for Windows. I do not see any impacts in the Jenkins UI. I Jenkins is not impacted because Jenkins uses Java and Java can handle either Windows or Unix file separators. The problem is the Windows OS and backup software see these as corrupted files. Hope this helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-4934) Plot data is retained for deleted builds
Brian Smith commented on JENKINS-4934 Plot data is retained for deleted builds This is interesting... I have the exact opposite problem . It is currently deleting data from my plots even though I have told it to use the data from the last 300 builds... If you set the plot to store the last 300 data points I want it to display the last 300 data points. I don't care if the build the data is built off of is removed. I don't want to waste the space storing the build but I do want to keep the plot data as I am trying to view trends over time. Maybe this should be made an option instead of just doing it one way or the other?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-20086) Improve the archive artifacts plugin to incude hidden files/directories like .git
Nicolas Labrot commented on JENKINS-20086 Improve the archive artifacts plugin to incude hidden files/directories like .git relative obscurity of the requirement why is it obscurs? I have the same issue. First step clean/install the maven project on a private maven repo (to avoid snapshot deps collision between a reentrant pipeline) and archive the workspace. Next steps (test, sonar, deploy on nexus, deploy on tomcat...) reuse this archive instead of rebuilding the project. Sonar steps need the .svn which are not copied by the archive plugin. Is this pipeline wrong? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23272) java.io.IOException: remote file operation failed remote slave Unable to delete
Khaled Janania commented on JENKINS-23272 java.io.IOException: remote file operation failed remote slave Unable to delete Thanks. I'll add that to eliminate the character difference. It was reproducible before I wiped the directories. I'll try to resync everything to reproduce the issue. I also suspect that a sync did not actually cancel when cancelled through the UI, so I'll check whether that was the issue as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Daniel Beck commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Ashok: Check your startup scripts (e.g. /etc/sysconfig/jenkins, /etc/init.d/jenkins, ... when using the RPM installer) for any occurrence of -Dhudson.diyChunking=true and remove it. Restart Jenkins using service restart jenkins (rather than via e.g. /safeRestart) so it picks up the changes. See whether the issue disappears. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23305) NPE on running some slaves of a matrix build - failure with no explanation
Daniel Beck commented on JENKINS-23305 NPE on running some slaves of a matrix build - failure with no explanation It's weird how a job can be scheduled for a node before it could be determined whether it's Unix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22453) Invalid symbolic links get archived but cannot be copied using Copy Artifacts
Daniel Beck commented on JENKINS-22453 Invalid symbolic links get archived but cannot be copied using Copy Artifacts Ingo: Did you recently update to 1.554 or higher, which includes the fix to JENKINS-21958? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Peter Kline edited a comment on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Possibly related JENKINS-23223 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22732) jGit NPE in getShortBranchName with */master branch
Peter Kolínek commented on JENKINS-22732 jGit NPE in getShortBranchName with */master branch Thank you for you feedback. Currently I was not able to reproduce this issue with updated environment: Jenkins ver. 1.554.2 Master on RHEL x64 Jenkins Slave node via JNLP start on Windows 7 x64 Jenkins GIT client plugin 1.9.1 Jenkins GIT plugin 2.2.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Thiago Zanetti updated JENKINS-19994 Unable to delete workspace jgit configuration Change By: Thiago Zanetti (12/Jun/14 7:32 PM) Attachment: jgit_problem.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20086) Improve the archive artifacts plugin to incude hidden files/directories like .git
Daniel Beck updated JENKINS-20086 Improve the archive artifacts plugin to incude hidden files/directories like .git It's not something that can be done out of the box, you need e.g. Copy Artifacts plugin for that. Still, it does seem like a somewhat surprising behavior it's only unsurprising if you know it uses Ant, and that's a build tool. I'm not sure what the best way to introduce an option is though just clearing the default excludes can well be considered a regression. Per-instance option is too heavy-handed. Per-job option seems to be the only sensible one left. Given the apparent reluctance of others to merge my 'archive only if successful' option in 1.567, I'm not looking forward to an argument about this I'm adding this to my list of things I'd like to fix, but anyone feel free to take over. Change By: Daniel Beck (12/Jun/14 7:37 PM) Assignee: DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20086) Allow disabling use of default exclude patterns (.git, .svn, etc.)
Daniel Beck updated JENKINS-20086 Allow disabling use of default exclude patterns (.git, .svn, etc.) Change By: Daniel Beck (12/Jun/14 7:38 PM) Summary: Improvethearchiveartifactsplugintoincudehiddenfiles/directorieslike Allowdisablinguseofdefaultexcludepatterns( .git ,.svn,etc.) Fix Version/s: current Affects Version/s: current Environment: Jenkins1.509.4LTSUbuntu12.04LTS Any Due Date: 31/Oct/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20086) Improve the archive artifacts plugin to incude hidden files/directories like .git
Daniel Beck updated JENKINS-20086 Improve the archive artifacts plugin to incude hidden files/directories like .git Change By: Daniel Beck (12/Jun/14 7:37 PM) Labels: archivingartifact plugin Component/s: core Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Thiago Zanetti edited a comment on JENKINS-19994 Unable to delete workspace Mark Waite I've attached a screenshot from my job configuration. As you can see I'm using jgit. I've followed the steps (which is basically make a build fail by aborting) to reproduce the issue and took a look at Windows Task Manager. There is no git process running when the error occurs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22311) Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history
Daniel Beck updated JENKINS-22311 Large number of build parameters for pending jobs (e.g.gerrit triggered job) can cause unwieldy build history Really more of a Gerrit Trigger plugin issue it seems everyone who's complained so far about the presentation used that plugin. It really should define its own parameter types with their own presentation. Change By: Daniel Beck (12/Jun/14 7:51 PM) Component/s: gerrit-trigger Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-4934) Plot data is retained for deleted builds
Brian Smith edited a comment on JENKINS-4934 Plot data is retained for deleted builds This is interesting... I have the exact opposite problem . It is currently deleting data from my plots even though I have told it to use the data from the last 300 builds... If you set the plot to store the last 300 data points I want it to display the last 300 data points. I don't care if the build the data is built off of is removed. I don't want to waste the space storing the build but I do want to keep the plot data as I am trying to view trends over time. Maybe this should be made an option instead of just doing it one way or the other?? There are also many better ways to handle data that skews the plot (like setting the axis scale) than deleting it. In general terms for my use it is the data that is skewing the plot that I am looking for. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-21811) Support semicolons as CSV delimiters
Brian Smith commented on JENKINS-21811 Support semicolons as CSV delimiters CSV - Comma Separated Values. I think you might have your Excel set incorrectly? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-17235) No error message displayed even on failure if I try to run the same job with same params in parallel
Ying Gan edited a comment on JENKINS-17235 No error message displayed even on failure if I try to run the same job with same params in parallel I have the similar issue. In parallel block I called a job doesn't exist. Build flow failed but log doesn't report anything. Are there anybody working on this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite commented on JENKINS-19994 Unable to delete workspace OK, then one work around is to switch from JGit to command line git. Because command line git runs an external process, it is much less likely to hold files busy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite edited a comment on JENKINS-19994 Unable to delete workspace OK, then one work around is to switch from JGit to command line git. Because command line git runs an external process, it is much less likely to hold files busy. Another work around is to switch from running on Windows to run on Linux, FreeBSD, Solaris or one of the other variants where an open file handle is non-fatal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3] (JENKINS-16025) Allow full path when uploading a file
Giancarlo Martinez commented on JENKINS-16025 Allow full path when uploading a file Not only that, it appears to also upload files incorrectly on Windows slave (regardless of if slave-managed upload is on). It'll take the directory structure and literally write the path to S3 with backslashes, which obviously yields an incorrect result. 301 2014-06-12 17:39:54 Win32/build-slave-with-parameters/287/win\builds\props.txt So the new version has effectively broken uploads on Windows slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
