[JIRA] (JENKINS-55131) CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
Title: Message Title Josh Soref commented on JENKINS-55131 Re: CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty I'm wondering if it makes sense to report the same class multiple times. I understand that it is in fact in the project multiple times, but I question the value of that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55131) CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55131 CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-11 20:51 Priority: Minor Reporter: Josh Soref I ran across a project that looked like this: '1.1' encoding='UTF-8'?> Blah false "disk-usage@0.28"/> "disk-usage@0.28"/> I recently disabled the disk usage plugin which results in: /jenkins/administrativeMonitor/OldData/manage Type Name Error hudson.model.FreeStyleProject blah CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
[JIRA] (JENKINS-55130) Rewrite OldDataMonitor configure text
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55130 Rewrite OldDataMonitor configure text Issue Type: Bug Assignee: Josh Soref Components: core Created: 2018-12-11 20:22 Priority: Minor Reporter: Josh Soref The text implies that there's a "save" button and that there are "files" that will be listed in the table, both of these are absolutely wrong. It also didn't do a good job of noting a common cause of items in the table are plugins (e.g. I disabled the diskspaceusage plugin and got a huge number of rows). Add Comment
[JIRA] (JENKINS-55059) pluginmanager shows Update information obtained: N/A ago
Title: Message Title Josh Soref commented on JENKINS-55059 Re: pluginmanager shows Update information obtained: N/A ago I assume it just hasn't had time to check. My complaint is purely about the display, it should special case N/A and give a distinct string. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55059) pluginmanager shows Update information obtained: N/A ago
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55059 pluginmanager shows Update information obtained: N/A ago Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-06 18:56 Priority: Minor Reporter: Josh Soref Jenkins ver. 2.154 visit /pluginManager/advanced change the update site to https://updates.jenkins.io/experimental/update-center.json Submit change the update site to https://updates.jenkins.io/update-center.json Submit See Update information obtained: N/A ago Expect not to see N/A ago Afaiu, the code starts: https://github.com/jenkinsci/jenkins/blob/7aef24d4542738ce309122ea05a3d194e842c8d8/core/src/main/resources/hudson/PluginManager/check.jelly#L28 https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/resources/hudson/PluginManager/check.properties#L23
[JIRA] (JENKINS-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title Josh Soref assigned an issue to Sam Van Oort Jenkins / JENKINS-36322 NaN execution time may appear if a stage gets terminated incorrectly Change By: Josh Soref Assignee: Josh Soref Sam Van Oort Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title Josh Soref commented on JENKINS-36322 Re: NaN execution time may appear if a stage gets terminated incorrectly The NaNd/NaNy problem will go away with the next release – https://github.com/jenkinsci/pipeline-stage-view-plugin/pull/53 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36322) NaN execution time may appear if a stage gets terminated incorrectly
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-36322 NaN execution time may appear if a stage gets terminated incorrectly Change By: Josh Soref Assignee: Sam Van Oort Josh Soref Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Josh Soref commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace The nested agents do get their own git clones. The ones without a specified agent run on the same node as the main pipeline. I only need to use stash to share build products (omitted because it isn't relevant to the failure). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54947) Add help for anonymizing config
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-54947 Add help for anonymizing config Issue Type: Bug Assignee: Josh Soref Components: support-core-plugin Created: 2018-11-29 14:47 Priority: Minor Reporter: Josh Soref Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49577) delete bundle has no confirmation
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-49577 delete bundle has no confirmation Change By: Josh Soref Summary: delete bundle has no comfirmation confirmation Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53184) Plugins and Core versions are redacted when they have 4 groups of digits
Title: Message Title Josh Soref commented on JENKINS-53184 Re: Plugins and Core versions are redacted when they have 4 groups of digits I think AboutContent could just add/remove the plugin versions as it goes. I might look into doing this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54922) Generated markdown should work in MacDown.app
Title: Message Title Josh Soref commented on JENKINS-54922 Re: Generated markdown should work in MacDown.app jenkinsci/support-core-plugin#155 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54922) Generated markdown should work in MacDown.app
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-54922
Generated markdown should work in MacDown.app
Issue Type:
Bug
Assignee:
Emilio Escobar
Components:
support-core-plugin
Created:
2018-11-28 15:50
Priority:
Minor
Reporter:
Josh Soref
Currently the generated Markdown doesn't do a good enough job of escaping {} characters and the sanitizer loves to generate {} which means that labels and node names have a tendency to generate partially italicized content when rendered in at least MacDown and potentially many other renderers. Sample raw content:
* computer_reliable_bulletin (`user_junior_process.slaves.DumbSlave`)
- Description:_Java 8_
- Executors: 1
- Remote FS root: `/home/jenkins`
- Labels: label_transparent_court label_religious_blood pipeline view_medieval_corn label_mutual_violation label_related_favourite label_easy_insurance
Rendered as:
computer reliable bulletin (user_junior_process.slaves.DumbSlave)
Description: Java 8
Executors: 1
Remote FS root: /home/jenkins
Labels: label_transparent_court label_religious_blood pipeline view_medieval_corn label_mutual_violation label_related_favourite label_easy_insurance
[JIRA] (JENKINS-54920) Refactor AboutJenkins class
Title: Message Title Josh Soref commented on JENKINS-54920 Re: Refactor AboutJenkins class For reference, my current proposal is here: https://github.com/jsoref/support-core-plugin/tree/refactor I won't make a PR for it until jenkinsci/support-core-plugin#155 is merged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54920) Refactor AboutJenkins class
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-54920 Refactor AboutJenkins class Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-11-28 14:55 Priority: Minor Reporter: Josh Soref The AboutJenkins class is huge (>1000 lines) and coverage in AboutJenkinsTest consists of a single function mayBeDateSmokes. I'm trying to improve the output of the AboutJenkins code, and potentially improve the sanitization. But in order to do that (and not be laughed at by my colleagues), I need to be able to write tests for the pieces of code I'm changing. As is, AboutJenkins isn't practically testable in small units because everything is hidden in private class or private static. I understand that people may have pending pull requests (they should get them merged) and they may have code which depends on minute details of how this code works. If they care, they should get their changes merged and then help write tests documenting their expectations which would make it easier for future contributors to understand the constraints the code lives with when they write changes. Add Comment
[JIRA] (JENKINS-45966) " 'Jenkinsfile' not found" due to race condition w/ webhooks and the GH Contents API
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-45966 " 'Jenkinsfile' not found" due to race condition w/ webhooks and the GH Contents API Change By: Josh Soref *The Symptom:*When using an enterprise GHE that is running slow (or I imagine, with a very fast jenkins instance, maybe even on production GH), a check for a Jenkinsfile in the branch events will say that one was not found, even though there is a Jenkinsfile in the PR's origin branch, and in the target branch. This seems to happen if you "slam" GH by creating a commit, branch, and PR all in one go (which people do with automated commits). *What I think is the cause:*As far as I can tell, GitHubSCMProbe is relying on the contents API to determine if a new branch or PR has a Jenkinsfile. When building merge PRs, it uses the merge refs with the contents API, but the merge refs aren't actually ready yet when GH sends out it's its webhooks. To prove this, I spun up a ruby sinatra app that listens for a PR webhook and immediately calls back to GH with the contents API. This reliably fails to find a ref (returns "No commit found for the ref"), unless you put a short sleep between when it receives the webhook, and when it calls out for content. You can find that here: [https://github.com/SpencerMalone/test-repo] if you want to play with it yourself. This is probably something that GH needs to fix, so I've sent them a support ticket, but just incase they are unable to, or in case it takes an exceedingly long time, I've opened this. I think in cases where we get a ref not found from the contents API while responding to branch events, there should be a short delay + retry. Add Comment
[JIRA] (JENKINS-54866) github_branch_source.GitHubSCMSource is ~0 width
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-54866 github_branch_source.GitHubSCMSource is ~0 width Issue Type: Bug Assignee: Unassigned Attachments: image-2018-11-26-14-11-58-378.png, image-2018-11-26-14-14-53-644.png Components: github-branch-source-plugin Created: 2018-11-26 19:15 Environment: github-branch-source-plugin 2.4.1; Jenkins ver. 2.153; Chrome 70.0.3538.102 macOS Mojave Priority: Minor Reporter: Josh Soref Load http://jenkins/configure Scroll down to Global Pipeline Libraries Scroll to Source Code Management See: That tiny blob between GitHub and Credentials is "" nameref="radio-block-15"> "/descriptorByName/org.jenkinsci.plugins.github_branch_source.GitHubSCMSource/fillApiUriItems" name="_.apiUri" class="setting-input select" value="">GitHub
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title
Josh Soref commented on JENKINS-54640
Re: Workspace folders are not unique
So, I think that the plugin is not being careful about whose workspace.txt it's considering... We're using
pipeline {
parallel {
stage {
}
stage {
}
}
}
A quick grep for our project across the various build nodes shows that the hashed directory listed is the one from one build node, but not from the failing build node (which has a different path in the workspaces.txt file).
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title Josh Soref commented on JENKINS-54640 Re: Workspace folders are not unique So, all I've done is rename workspaces.txt I don't really want to have to go to all 10 of my computers and delete entire trees if i can avoid it... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title Josh Soref commented on JENKINS-54640 Re: Workspace folders are not unique ERROR: Unable to launch the agent for somenode java.nio.file.NoSuchFileException: /home/jenkins/workspace/workspaces.txt at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) at java.nio.file.Files.newByteChannel(Files.java:361) at java.nio.file.Files.newByteChannel(Files.java:407) at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384) at java.nio.file.Files.newInputStream(Files.java:152) at hudson.FilePath$Read.invoke(FilePath.java:1991) at hudson.FilePath$Read.invoke(FilePath.java:1983) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3084) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) Caused: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:169) at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284) at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326) at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178) at java.io.InputStreamReader.read(InputStreamReader.java:184) at java.io.BufferedReader.fill(BufferedReader.java:161) at java.io.BufferedReader.readLine(BufferedReader.java:324) at java.io.BufferedReader.readLine(BufferedReader.java:389) at jenkins.branch.WorkspaceLocatorImpl.load(WorkspaceLocatorImpl.java:221) at jenkins.branch.WorkspaceLocatorImpl.access$500(WorkspaceLocatorImpl.java:80) at jenkins.branch.WorkspaceLocatorImpl$Collector.onOnline(WorkspaceLocatorImpl.java:518) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:693) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:432) at hudson.slaves.CommandLauncher.launch(CommandLauncher.java:153) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ERROR: Connection terminated java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2671) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3146) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:858) at java.io.ObjectInputStream.(ObjectInputStream.java:354) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63) Caused:
[JIRA] (JENKINS-54786) Launch command should include an env var for the name of the node
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-54786 Launch command should include an env var for the name of the node Issue Type: Bug Assignee: Unassigned Components: command-launcher-plugin Created: 2018-11-23 01:51 Priority: Minor Reporter: Josh Soref I'd like to be able to do: Launch command: start-agent $NODE_NAME I know there are fancier ways to deal w/ launching nodes, but for now, it would be nice to be able to use the "copy node" and just give it another node whose template includes Launch method includes a variable so that I don't have to do anything other than "OK". Add Comment
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title Josh Soref edited a comment on JENKINS-54640 Re: Workspace folders are not unique Fwiw, this fix doesn't appear to have fixed our flavor of the problem. We tried upgrading to 2.1.1 and that broke things the same way the previous thing did. We're downgrading (to 2.0.20) now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54640) Workspace folders are not unique
Title: Message Title Josh Soref commented on JENKINS-54640 Re: Workspace folders are not unique Fwiw, this fix doesn't appear to have fixed our flavor of the problem. We tried upgrading to 2.1.1 and that broke things the same way the previous thing did. We're downgrading now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title
Josh Soref commented on JENKINS-2111
Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Jesse Glick this commit (https://github.com/jenkinsci/branch-api-plugin/commit/481e4857c9a450c2904ff5188aa9076cf1db1f1c) resulted in a fairly consistent but slightly random and mind boggling build failure. We just upgraded to Jenkins ver. 2.151 today (and upgraded all of our plugins at the same time). We were able to review our plugin update list and then sifted through commits. Eventually we settled on this one and fixed it by downgrading Branch API from 2.0.21 to 2.0.20 which effectively backed this out. We have a declarative Jenkinsfile pipeline file which uses parallel in a stage... It looks approximately like this. Note that We define an agent for the outer job and for Scala Full, but not for Frontend Prod. Frontend Prod builds happily (which means it can find the npm.sh file), Scala Full fails with an error trying to say that it can't find the sbt.sh file (these files all exist in a single git repository). If we pin all stages to a single node, it works. We're using the branch plugin to monitor pull requests from github and it's automagically building our commits based on that...
pipeline {
agent {
label "pipeline"
}
environment {
PIPELINE_SCRIPTS="$WORKSPACE/pipeline/scripts"
SBT_SCRIPT="$PIPELINE_SCRIPTS/sbt.sh"
NPM_SCRIPT="$PIPELINE_SCRIPTS/npm.sh"
}
stages {
stage ("Checkout") {
steps {
script {
result = sh (script: "git log -1 --pretty=format:'%an' | grep 'Jenkins'", returnStatus: true)
if (result != 0) {
echo ("Non jenkins user commit")
}
}
}
}
stage("Compile") {
parallel {
stage("Scala Full") {
agent {
label "pipeline"
}
steps {
sh "$SBT_SCRIPT compile"
}
}
stage("Frontend Prod") {
steps {
sh "$NPM_SCRIPT install"
}
}
}
}
}
}
Add Comment
[JIRA] (JENKINS-51948) ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent
Title: Message Title Josh Soref commented on JENKINS-51948 Re: ExecutorStepExecution.PlaceholderTask getEnclosingLabel/computeEnclosingLabel incorrectly calculate node resulting in mislabeled stages in parallel if they don't have an agent I gave up trying to figure out how to fix this. When I work on things, I tend to post PR requests fairly quickly... Otherwise, I file bugs and hope someone else will fix... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24846) UI Improvement: Update Center
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-24846 UI Improvement: Update Center Change By: Josh Soref Assignee: Josh Soref Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24846) UI Improvement: Update Center
Title: Message Title Josh Soref commented on JENKINS-24846 Re: UI Improvement: Update Center https://github.com/jenkinsci/jenkins/pull/3620 I'm happy to make changes... I think I agree that the check now button should always be present. Maybe tomorrow... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52356) support 64bit files in ZipArchiver
Title: Message Title Josh Soref resolved as Fixed Jenkins / JENKINS-52356 support 64bit files in ZipArchiver Change By: Josh Soref Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53465) ChannelClosedException in Maven channel
Title: Message Title Josh Soref commented on JENKINS-53465 Re: ChannelClosedException in Maven channel That isn't helpful. Please read https://jenkins.io/redirect/serialization-of-anonymous-classes/ it's a short page. It provides a single command that you can run. If you can that for each warning (along with reporting the version of each plugin that triggers the warning) that would be helpful. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53465) Attempt to (de-)serialize anonymous class
Title: Message Title Josh Soref commented on JENKINS-53465 Re: Attempt to (de-)serialize anonymous class JENKINS-53481 JENKINS-53482 JENKINS-53483 I can't deal w/ the global-build-stats-plugin because it's an enum which is its own mess... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53483) Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.jfrog.hudson.maven2.MavenDependenciesRecorder$1
Title: Message Title Josh Soref commented on JENKINS-53483 Re: Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.jfrog.hudson.maven2.MavenDependenciesRecorder$1 https://github.com/jenkinsci/artifactory-plugin/pull/33 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53483) Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.jfrog.hudson.maven2.MavenDependenciesRecorder$1
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-53483 Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.jfrog.hudson.maven2.MavenDependenciesRecorder$1 Issue Type: Bug Assignee: Josh Soref Components: artifactory-plugin Created: 2018-09-07 21:57 Priority: Minor Reporter: Josh Soref WARNING: Attempt to (de-)serialize anonymous class org.jfrog.hudson.maven2.MavenDependenciesRecorder$1 in file:/var/hudson/master/plugins/artifactory/WEB-INF/lib/artifactory.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Add Comment
[JIRA] (JENKINS-53482) Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.whitesource.jenkins.extractor.maven.MavenDependenciesRecorder$1
Title: Message Title Josh Soref commented on JENKINS-53482 Re: Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.whitesource.jenkins.extractor.maven.MavenDependenciesRecorder$1 https://github.com/jenkinsci/whitesource-plugin/pull/4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53482) Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.whitesource.jenkins.extractor.maven.MavenDependenciesRecorder$1
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-53482 Attempt to (de-)serialize anonymous class Attempt to (de-)serialize anonymous class org.whitesource.jenkins.extractor.maven.MavenDependenciesRecorder$1 Issue Type: Bug Assignee: Josh Soref Components: whitesource-plugin Created: 2018-09-07 21:45 Priority: Minor Reporter: Josh Soref Sep 07, 2018 12:23:53 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.whitesource.jenkins.extractor.maven.MavenDependenciesRecorder$1 in file:/var/hudson/master/plugins/whitesource/WEB-INF/lib/whitesource.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Add Comment
[JIRA] (JENKINS-53481) Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2
Title: Message Title Josh Soref commented on JENKINS-53481 Re: Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2 https://github.com/jenkinsci/maven-plugin/pull/120 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53481) Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-53481 Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2 Issue Type: Bug Assignee: Josh Soref Components: maven-plugin Created: 2018-09-07 21:39 Priority: Minor Reporter: Josh Soref Sep 07, 2018 12:23:52 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenArtifactArchiver$2 in file:/var/hudson/master/plugins/maven-plugin/WEB-INF/lib/maven-plugin.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Sep 07, 2018 12:23:54 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 in file:/var/hudson/master/plugins/maven-plugin/WEB-INF/lib/maven-plugin.jar; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
[JIRA] (JENKINS-53465) Attempt to (de-)serialize anonymous class
Title: Message Title Josh Soref commented on JENKINS-53465 Re: Attempt to (de-)serialize anonymous class sakshi sood: Note that some of these have been fixed, but either haven't had released with the fix, or possibly haven't had releases for LTS (about which I know nothing). You can search JIRA for each class, e.g. org.jenkinsci.plugins.gitclient.Git$1 is https://issues.jenkins-ci.org/browse/JENKINS-52948 There are things you could do to help me. The listed URL in the warning includes a command to run in the overview. If you could run that for the items listed here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53454) Attempt to (de-)serialize anonymous class org.jvnet.hudson.plugins.SbtPluginBuilder$SbtInstallation$1
Title: Message Title Josh Soref commented on JENKINS-53454 Re: Attempt to (de-)serialize anonymous class org.jvnet.hudson.plugins.SbtPluginBuilder$SbtInstallation$1 https://github.com/jenkinsci/sbt-plugin/pull/21 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53454) Attempt to (de-)serialize anonymous class org.jvnet.hudson.plugins.SbtPluginBuilder$SbtInstallation$1
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-53454 Attempt to (de-)serialize anonymous class org.jvnet.hudson.plugins.SbtPluginBuilder$SbtInstallation$1 Issue Type: Bug Assignee: Josh Soref Components: sbt-plugin Created: 2018-09-07 05:03 Priority: Minor Reporter: Josh Soref Sep 07, 2018 12:00:53 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jvnet.hudson.plugins.SbtPluginBuilder$SbtInstallation$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Add Comment
[JIRA] (JENKINS-49546) java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed
Title: Message Title Josh Soref commented on JENKINS-49546 Re: java.io.IOException: Remote call on JNLP4-connect connection from /:4028 failed Fwiw, the two warnings in are addressed by JENKINS-50457 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Josh Soref updated JENKINS-52946 Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Josh Soref Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Josh Soref updated JENKINS-52946 https://github.com/jenkinsci/envinject-plugin/pull/131 Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Josh Soref Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Josh Soref resolved as Fixed Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Josh Soref Status: Reopened Resolved Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52947) Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1
Title: Message Title Josh Soref commented on JENKINS-52947 Re: Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1 Jesse Glick? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52947) Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1
Title: Message Title Josh Soref commented on JENKINS-52947 Re: Attempt to (de-)serialize anonymous class com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerParameters$ParameterMode$1 I suspect this is complaining about: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/1ecb59ced215ccc36c97f42eaa35fb6fcdac8146/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerParameters.java#L624 specifically: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/1ecb59ced215ccc36c97f42eaa35fb6fcdac8146/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerParameters.java#L628 and https://github.com/jenkinsci/gerrit-trigger-plugin/blob/1ecb59ced215ccc36c97f42eaa35fb6fcdac8146/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerParameters.java#L640 probably via: https://github.com/jenkinsci/gerrit-trigger-plugin/blob/a3bf98d1d4342900137a2739f3a7333ecf710898/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java#L213-L216 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52509) WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1
Title: Message Title Josh Soref commented on JENKINS-52509 Re: WARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.PluginImpl$1 Fwiw, the warning and the error aren't related. I've tried to fix some instances of the warning. You're welcome to have bugs for both (personally, if I were you, I'd be more interested in the error than the warning...). From an IT/Ops perspective, I'd hope there's more logging to report: the url/host/port/ip that was failing... (and if not, I'd want it added...) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52948) Attempt to (de-)serialize anonymous class in gitclient
Title: Message Title Josh Soref resolved as Fixed Jenkins / JENKINS-52948 Attempt to (de-)serialize anonymous class in gitclient Change By: Josh Soref Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50457) Attempt to (de-)serialize anonymous class
Title: Message Title Josh Soref updated JENKINS-50457 Jenkins / JENKINS-50457 Attempt to (de-)serialize anonymous class Change By: Josh Soref Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50457) Attempt to (de-)serialize anonymous class
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-50457 Attempt to (de-)serialize anonymous class Change By: Josh Soref Assignee: Josh Soref Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53077) Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-53077
Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Change By:
Josh Soref
e:{code:java}TypeError: Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.at onSuccess (hudson-behavior.js:1524)at klass.respondToReadyState (VM283 prototype.js:1657)at klass.onStateChange (VM283 prototype.js:1600)at XMLHttpRequest. (VM283 prototype.js:414) {code}response.responseText: {{""}}[https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1524]I verified that:[https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1523]{code:java}var node = $(div).firstDescendant(); {code}yielded {{null}}.Further investigation shows:{{ rsp response .status}} = : {{0}} . The code for {{this.success()}} used by {{respondToReadyState()}} treats this as a resonse to call {{this.options.onSuccess}}, but I suspect it would be better handled by {{this.options.onFailure}} or by dropping it or something.See [https://stackoverflow.com/questions/36416389/why-does-my-xmlhttprequest-have-readystate-4-but-status-0] for reports of this case.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You
[JIRA] (JENKINS-53077) Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-53077
Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Change By:
Josh Soref
e:{code:java}TypeError: Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.at onSuccess (hudson-behavior.js:1524)at klass.respondToReadyState (VM283 prototype.js:1657)at klass.onStateChange (VM283 prototype.js:1600)at XMLHttpRequest. (VM283 prototype.js:414) {code}response.responseText: {{""}}[https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1524]I 'm pretty sure verified that:[https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1523]{code:java}var node = $(div).firstDescendant(); {code}yielded {{null}}. Further investigation shows:{{rsp.status}} = {{0}}.The code for {{this.success()}} used by {{respondToReadyState()}} treats this as a resonse to call {{this.options.onSuccess}}, but I suspect it would be better handled by {{this.options.onFailure}} or by dropping it or something.See [https://stackoverflow.com/questions/36416389/why-does-my-xmlhttprequest-have-readystate-4-but-status-0] for reports of this case.
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You
[JIRA] (JENKINS-53077) Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'.
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-53077 Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'. Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-08-16 19:57 Priority: Minor Reporter: Josh Soref e: TypeError: Failed to execute 'replaceChild' on 'Node': parameter 1 is not of type 'Node'. at onSuccess (hudson-behavior.js:1524) at klass.respondToReadyState (VM283 prototype.js:1657) at klass.onStateChange (VM283 prototype.js:1600) at XMLHttpRequest. (VM283 prototype.js:414) response.responseText: "" https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1524 I'm pretty sure that: https://github.com/jenkinsci/jenkins/blob/723e5ed8fb1a5289edc31d82bb9ad67e6d97bcd9/war/src/main/webapp/scripts/hudson-behavior.js#L1523 var node = $(div).firstDescendant(); yielded null.
[JIRA] (JENKINS-53054) blueocean should not show branches for non multibranch build
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-53054 blueocean should not show branches for non multibranch build Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2018-08-15 19:01 Priority: Minor Reporter: Josh Soref https://github.com/jenkinsci/blueocean-plugin/blob/1510403599e366d124cce71232cdb3aff5423edd/blueocean-dashboard/src/main/js/components/MultiBranch.jsx#L39 Currently the button is basically an attractive nuisance. When one clicks it, the dialog provides a learn more button That button for reasons I can't determine links to the generic documentation url instead of the specific one that the code is trying to target. It would be much better to just hide the button. Jenkins usually only shows things that are contextually valid. Add
[JIRA] (JENKINS-21383) Restart feature in update center is brittle
Title: Message Title Josh Soref commented on JENKINS-21383 Re: Restart feature in update center is brittle So, I hit a similar problem: I triggered a manual "prepare for shutdown" I went to the plugin update center I selected check all (available updates) I selected the update option I tried to uncheck the restart checkbox When I uncheck the restart checkbox, it temporarily is unchecked and then gets rechecked. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50468) Build Executor Status widget should allow
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-50468 Build Executor Status widget should allow Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-03-28 19:36 Priority: Minor Reporter: Josh Soref Jenkins ver. 2.113 We have a number of nodes that start on demand and stop on idle. If you click on one of the nodes, you can click Launch agent. It would be nice if the drop down for a node from the executor status widget offered (when applicable): Launch agent Mark this node temporarily offline Bring this node back online In addition to the current items: Delete Agent Configure Build History Load Statistics Log Open Blue Ocean (Unrelated, the icon for Delete Agent is pretty confusing. It would be better as a trash can.)
[JIRA] (JENKINS-41327) alerts icons and buttons are randomly placed/aligned
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-41327 alerts icons and buttons are randomly placed/aligned Issue Type: Improvement Assignee: Unassigned Attachments: randomly-placed-buttons.png Components: core Created: 2017/Jan/23 3:30 PM Priority: Minor Reporter: Josh Soref Actual results: Note the random vertical alignment of ⛔ / ⚠ vs the text vs the buttons Note that the buttons are randomly placed (correct is sort of centered in the view – I have no idea to what it applies) Expected results: Pick a single alignment for the icons (probably vertically centered for a a table row) Pick a consistent placement for the buttons (either in their own table column, or on their own line after the problem)
[JIRA] (JENKINS-41302) replace disabled checkbox with descriptive text for plugins that are pending upgrade
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-41302 replace disabled checkbox with descriptive text for plugins that are pending upgrade Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/23 4:06 AM Priority: Minor Reporter: Josh Soref open the plugin manager, and try to update some things that require a restart. either have your jenkins be unable to automatically restart, or disable auto restart The bottom of the plugin manager updates tab shows: > Disabled rows are already upgraded, awaiting restart. Shaded but selectable rows are in progress or failed. And some rows have disabled checkboxes. There's no reason to show humans a disabled textbox, when you can just have actual text that explains "install pending". I'm happy to provide a patch if someone points me in the right direction... Add Comment
[JIRA] (JENKINS-41301) Show cog (⚙) to the right of search/help in the top banner
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-41301 Show cog (⚙) to the right of search/help in the top banner Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/23 4:02 AM Priority: Minor Reporter: Josh Soref If you use jira, and you're an admin, then at the top of jira there's a line that has: = Jira | Dashboards v| Projects v| Issues v| ... [ Create ] ... ( Search :mag: ) ⚙v ☹v If you aren't admin, then the cog (⚙) isn't shown. What I'm suggesting is to do the same for jenkins: = Jenkins | ... [ 2] ( :mag: Search ) ⚙ I'm happy to write the patch, but I can't quite figure out where to put the code. Add Comment
