[JIRA] [groovy-plugin] (JENKINS-28653) Install from URL is broken
Title: Message Title Ingo Richter created an issue Jenkins / JENKINS-28653 Install from URL is broken Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 31/May/15 7:02 AM Environment: OSX 10.10.3, Jenkins 1.615 Priority: Major Reporter: Ingo Richter Since the groovy installation from codehaus is broken right now, a possible workaround could be to specify a download URL to an zip/tar.gz file. This seems to be broken too, since nothing will be downloaded and installed when I use the groovy version in my job. The download URL that I've used is http://dl.bintray.com/groovy/maven/groovy-binary-2.4.3.zip. I'm able to download with a browser. Using wget/curl, shows that there is a redirect response, that might not be properly handled by the groovy plugin at the moment.
[JIRA] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title nir h commented on JENKINS-28594 Re: Leading underscore added to committers email address. Deleted, still the same... May 31, 2015 11:52:50 AM FINE hudson.plugins.tfs.model.TfsUserLookup Looking up Jenkins user for TFS account '%s'. May 31, 2015 11:52:50 AM FINE hudson.tasks.MailAddressResolver Resolving e-mail address for "domain_user" ID=domain_user May 31, 2015 11:52:50 AM FINE hudson.plugins.active_directory.ActiveDirectoryMailAddressResolverImpl Failed to look up Active Directory for e-mail address org.acegisecurity.userdetails.UsernameNotFoundException: No such user or group: domain_user at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.getDnOfUserOrGroup(ActiveDirectoryAuthenticationProvider.java:220) at hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:107) at hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:53) at hudson.plugins.active_directory.ActiveDirectoryMailAddressResolverImpl.findMailAddressFor(ActiveDirectoryMailAddressResolverImpl.java:54) at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:122) at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:560) at hudson.plugins.tfs.model.TfsUserLookup.find(TfsUserLookup.java:32) at hudson.plugins.tfs.model.Project.convertServerChangeset(Project.java:63) at hudson.plugins.tfs.model.Project.getVCCHistory(Project.java:110) at hudson.plugins.tfs.model.Project.getDetailedHistory(Project.java:130) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:38) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:214) at hudson.model.AbstractProject.checkout(AbstractProject.java:1276) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28654) NPE in Abstract
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28654 NPE in Abstract Issue Type: Bug Assignee: Oleg Nenashev Components: core Created: 31/May/15 12:05 PM Priority: Minor Reporter: Oleg Nenashev I got into the error during my experiments with automatic job creation on the plugin startup. NPE may happen if... Jenkins instance has been already initialized Nodes have not been loaded yet SEVERE: Failed Initializing plugin docker-traceability java.lang.NullPointerException at hudson.model.AbstractProject.(AbstractProject.java:269) at org.jenkinsci.plugins.docker.traceability.model.jobs.DockerBuildReferenceJob.(DockerBuildReferenceJob.java:65) at org.jenkinsci.plugins.docker.traceability.model.jobs.DockerBuildReferenceJob.loadJob(DockerBuildReferenceJob.java:134) at org.jenkinsci.plugins.docker.traceability.model.jobs.DockerBuildReferenceFactory.onStart(DockerBuildReferenceFactory.java:55) at org.jenkinsci.plugins.docker.traceability.DockerTraceabilityPlugin.postInitialize(DockerTraceabilityPlugin.java:66) at hudson.PluginManager$2$1$2.run(PluginManager.java:376)
[JIRA] [core] (JENKINS-28654) NPE in AbstractProject constructor if Jenkins instance has not been completely initialized
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-28654 NPE in AbstractProject constructor if Jenkins instance has not been completely initialized Change By: Oleg Nenashev Summary: NPE in Abstract AbstractProject constructor if Jenkins instance has not been completely initialized Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-28654) NPE in Abstract
Title: Message Title Oleg Nenashev started work on JENKINS-28654 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-28654) NPE in AbstractProject constructor if Jenkins instance has not been completely initialized
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-28654
NPE in AbstractProject constructor if Jenkins instance has not been completely initialized
Change By:
Oleg Nenashev
I got into the error during my experiments with automatic job creation on the plugin startup.NPE may happen if...* Jenkins instance has been already initialized* Nodes have not been loaded yet Stacktrace example (the code has not been committed yet): {quote}SEVERE: Failed Initializing plugin docker-traceabilityjava.lang.NullPointerException at hudson.model.AbstractProject.(AbstractProject.java:269) at org.jenkinsci.plugins.docker.traceability.model.jobs.DockerBuildReferenceJob.(DockerBuildReferenceJob.java:65) at org.jenkinsci.plugins.docker.traceability.model.jobs.DockerBuildReferenceJob.loadJob(DockerBuildReferenceJob.java:134) at org.jenkinsci.plugins.docker.traceability.model.jobs.DockerBuildReferenceFactory.onStart(DockerBuildReferenceFactory.java:55) at org.jenkinsci.plugins.docker.traceability.DockerTraceabilityPlugin.postInitialize(DockerTraceabilityPlugin.java:66) at hudson.PluginManager$2$1$2.run(PluginManager.java:376){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title Oleg Nenashev started work on JENKINS-28655 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-traceability-plugin] (JENKINS-28655) Make Docker Traceability tolerant against FingerprintCleanupThread
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28655 Make Docker Traceability tolerant against FingerprintCleanupThread Issue Type: Improvement Assignee: Oleg Nenashev Components: docker-traceability-plugin Created: 31/May/15 1:03 PM Priority: Critical Reporter: Oleg Nenashev FingerprintCleanupThread may delete fingerprints if there is no references to jobs. For old cores it is required to create an artificial project, which would reference builds on-demand. Such project would also allow to manage fingerprints from its interface. Add Comment
[JIRA] [docker-traceability-plugin] (JENKINS-28656) Docker Traceability should support the creation of image fingerprints on-demand
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28656 Docker Traceability should support the creation of image fingerprints on-demand Issue Type: New Feature Assignee: Oleg Nenashev Components: docker-traceability-plugin Created: 31/May/15 1:06 PM Priority: Minor Reporter: Oleg Nenashev Currently the plugin presumes that the parent's image fingerprint is somehow created by other plugins (e.g. docker-workflow or docker-build-publish). If there's no such plugins, Docker Traceability won't create container fingerprints. It would be great to have an option, which would allow the creation of parent image fingerprints in any case. Add Comment
[JIRA] [docker-commons-plugin] (JENKINS-28657) Support creation of named fingerprints in DockerFingerprints
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28657 Support creation of named fingerprints in DockerFingerprints Issue Type: New Feature Assignee: Unassigned Components: docker-commons-plugin Created: 31/May/15 2:21 PM Priority: Minor Reporter: Oleg Nenashev Currently docker-commons assigns filename to any created fingerprint. It would be better to display image IDs or names in the filename. APIs should be extended to support such feature Add Comment
[JIRA] [docker-commons-plugin] (JENKINS-28658) CLONE - Support creation of named fingerprints in DockerFingerprints
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-28658 CLONE - Support creation of named fingerprints in DockerFingerprints Issue Type: New Feature Assignee: Unassigned Components: docker-commons-plugin Created: 31/May/15 2:24 PM Priority: Minor Reporter: Oleg Nenashev Currently docker-commons assigns filename to any created fingerprint. It would be better to display image IDs or names in the filename. APIs should be extended to support such feature Add Comment
[JIRA] [docker-traceability-plugin] (JENKINS-28658) Support creation of named container fingerprints
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-28658 Support creation of named container fingerprints Change By: Oleg Nenashev Summary: CLONE - Support creation of named container fingerprints in DockerFingerprints Component/s: docker-traceability-plugin Component/s: docker-commons-plugin Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-17290) Category titles in Available Plugins list appear wrong in reverse sort order
Title: Message Title Daniel Beck commented on JENKINS-17290 Re: Category titles in Available Plugins list appear wrong in reverse sort order Isn't that a session cookie or something from the last time you reordered the list? What happens when you open Jenkins in private browsing mode? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25370) H in schedule does not work properly for minutes
Title: Message Title Daniel Beck commented on JENKINS-25370 Re: H in schedule does not work properly for minutes Looks like there is something strange broken with scedules ... It would help if you'd mention the Jenkins version affected. Also, it's not clear how this is related to the reported issue. There's no 'H/1' anywhere in the report. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-20697) API wrong number of arguments on build specific endpoints
Title: Message Title Daniel Beck resolved as Duplicate Duplicates some issue with older releases of Static Analysis Plugins that @Exported a getter with parameter. Has been fixed long ago. Jenkins / JENKINS-20697 API wrong number of arguments on build specific endpoints Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [klaros-testmanagement-plugin] (JENKINS-28659) Add proper migration of test result path settings for existing projects
Title: Message Title stolp updated an issue Jenkins / JENKINS-28659 Add proper migration of test result path settings for existing projects Change By: stolp Summary: Add proper migration of singletest test result path settings for existing projects Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [klaros-testmanagement-plugin] (JENKINS-28659) Add proper migration of singletest result path settings for existing projects
Title: Message Title stolp created an issue Jenkins / JENKINS-28659 Add proper migration of singletest result path settings for existing projects Issue Type: Improvement Assignee: stolp Components: klaros-testmanagement-plugin Created: 31/May/15 8:58 PM Priority: Minor Reporter: stolp Existing projects should be properly migrated instead of showing empty result paths. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265
[JIRA] [configurationslicing-plugin] (JENKINS-20319) Configuration slicing resets send separate emails... for Email notification
Title: Message Title Ninian resolved as Fixed fixed in v1.41 Jenkins / JENKINS-20319 Configuration slicing resets send separate emails... for Email notification Change By: Ninian Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-16490) New versions of slave.jar not reliably pushed via JNLP
Title: Message Title Christoph Obexer commented on JENKINS-16490 Re: New versions of slave.jar not reliably pushed via JNLP I remember reading in another thread that jenkins-slave.exe is updated automatically, couldn't it take care of updating the slave.jar too? Another idea: would a redirect of the /jnlpJars/slave.jar to /jnlpJars/slave-vx.xxx.x.jar help? Last time the slave.jar had to be updated i had to learn powershell and write a script that deployed the new slave.jar across all our windows slaves - that was frustrating and took way too long for something that ought to be built in. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-28660) Remove the header that allows downloading as a zip because that uses needless space and hides the window title
Title: Message Title Christoph Obexer created an issue Jenkins / JENKINS-28660 Remove the header that allows downloading as a zip because that uses needless space and hides the window title Issue Type: Improvement Assignee: mcrooney Components: htmlpublisher-plugin Created: 31/May/15 10:30 PM Priority: Minor Reporter: Christoph Obexer Viewing a html page obscures the page title because the html report is displayed inside an iframe. this also hides the report URL which interests me often when viewing test report because the URL then provides a quick way to discover the test name without scrolling to the top of the report every time. (I need the test name to discover which file I need to look at to fix/change the test.) In contrast I never needed the download as zip option. If I wanted to download the report I would simply press Ctrl+S probably. An option to remove the header would be nice. Add Comment
[JIRA] [performance-plugin] (JENKINS-28266) JMeter sampler error count isn't checked against error thresholds
Title: Message Title Andri Purmawinata commented on JENKINS-28266 Re: JMeter sampler error count isn't checked against error thresholds Hi, I found similar issue with JmeterSummarizer as the report. It works when using relative threshold but not error threshold. And seems the average response time is not the same with the cumulative summary average response time. Below is the log. Thanks. summary + 2 in 6s = 0.3/s Avg: 186 Min: 169 Max: 203 Err: 0 (0.00%) Active: 0 Started: 5 Finished: 5 summary = 65 in 95s = 0.7/s Avg: 163 Min: 134 Max: 285 Err: 55 (84.62%) Tidying up ... @ Mon Jun 01 11:11:39 AEST 2015 (1433121099509) ... end of run Performance: Percentage of errors greater or equal than 0% sets the build as unstable Performance: Percentage of errors greater or equal than 0% sets the build as failure Performance: Recording JmeterSummarizer reports '/root/apache-jmeter-2.13/bin/jmeter.log' Performance: Parsing JMeter report file '/var/lib/jenkins/jobs/performance-tests/builds/2015-06-01_11-10-00/performance-reports/JmeterSummarizer/jmeter.log'. jmeter.log has an average of: 174 Performance: File jmeter.log reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-28661) Docker builds do not work with matrix project plugin
Title: Message Title Sam Gleske created an issue Jenkins / JENKINS-28661 Docker builds do not work with matrix project plugin Issue Type: Bug Assignee: Kanstantsin Shautsou Components: docker-plugin, matrix-project-plugin Created: 01/Jun/15 1:45 AM Environment: Ubuntu 14.04.2 LTS Linux 3.13.0-53-generic x86_64 GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu) java version "1.7.0_79" Labels: docker matrix Priority: Major Reporter: Sam Gleske When launching a build for a matrix project the job stays infinitely waiting on slaves and the docker plugin does not spin up any containers. I have published scripts which automatically generate a matrix build job if you wish to test this. https://github.com/samrocketman/jenkins-bootstrap-jervis export a GitHub API token.
[JIRA] [docker-plugin] (JENKINS-28661) Docker builds do not work with matrix project plugin
Title: Message Title Sam Gleske commented on JENKINS-28661 Re: Docker builds do not work with matrix project plugin https://github.com/jenkinsci/docker-plugin/issues/242 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ansicolor-plugin] (JENKINS-11752) ANSI color plugin adds garbage to log
Title: Message Title Jan Vansteenkiste commented on JENKINS-11752 Re: ANSI color plugin adds garbage to log Still true for ansicolor 0.4.1 :/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-28662) abrupt close of down stream job and child job is missing from the build panel
Title: Message Title Jagadeesh R created an issue Jenkins / JENKINS-28662 abrupt close of down stream job and child job is missing from the build panel Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 01/Jun/15 5:18 AM Priority: Critical Reporter: Jagadeesh R we have a single parent job, we are using multi job plugin to call 3 downstream jobs, we call multiple instances of same job(parent job) at a time and when we do this for some jobs(20% of all jobs), down stream job is closed abruptly and missing from the build panel Add Comment
[JIRA] [subversion-plugin] (JENKINS-18414) Jenkins Subversion plugin checkouts in something NON-UTF-8
Title: Message Title Jonny Bergstrom commented on JENKINS-18414 Re: Jenkins Subversion plugin checkouts in something NON-UTF-8 Many years later... I just updated to latest Jenkins (1.615) and the Subversion plugin is 2.5, however: The checkout process does not properly checkout a file which has a unicode(ish) cahracter in it, specifically: "bigletter_人.png" comes out as "bigletter_?.png". I think this is related to the problem in this issue. I'm running on OS X Yosemite, installed through Homebrew (afaik). I think I did setup utf8 in the startup parameters like below, but it does not fix the problem: "1.0" encoding="UTF-8"?> "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> "1.0"> Label homebrew.mxcl.jenkins ProgramArguments /usr/bin/java -Dmail.smtp.starttls.enable=true -Dfile.encoding=utf-8 -Dsun.jnu.encoding=UTF-8 -jar /usr/local/opt/jenkins/libexec/jenkins.war --httpListenAddress=127.0.0.1 --httpPort=8088 RunAtLoad Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ansicolor-plugin] (JENKINS-11752) ANSI color plugin adds garbage to log
Title: Message Title Patrick Byrne commented on JENKINS-11752 Re: ANSI color plugin adds garbage to log Yes, these appear to be ~2Kb (7-zip) compressed files embedded in each line of output. This has to be one of the most egregious examples of 'bloat' which I have seen. I would love to hear an explanation of why this was ever thought to be a good idea. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
