[JIRA] (JENKINS-43826) Exclude skipped stages from estimated duration calculation
Title: Message Title jessebs commented on JENKINS-43826 Re: Exclude skipped stages from estimated duration calculation When only works if the stage was skipped because of a foreseen reason. If the stage is skipped because a previous stage failed, then the skipped stages are on the order of a few milliseconds and are considered during the average stage time calculation. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181344.1493132114000.5844.1583964422246%40Atlassian.JIRA.
[JIRA] (JENKINS-61359) Shared Library Polling does not work with Multibranch Projects
Title: Message Title jessebs created an issue Jenkins / JENKINS-61359 Shared Library Polling does not work with Multibranch Projects Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2020-03-05 23:25 Priority: Minor Reporter: jessebs I have a multibranch project configured that's using a Jenkinsfile pointing to a shared library. When the shared library changes, builds are not triggered. Looking at the 'Scan Multibranch Pipeline Log' I see that only the project's repository is pulled, not the pipeline's Add Comment
[JIRA] [campfire-plugin] (JENKINS-34184) Campfire plugin fails to send notification when using Folder or Multi-Branch project
Title: Message Title Jesse Bowes created an issue Jenkins / JENKINS-34184 Campfire plugin fails to send notification when using Folder or Multi-Branch project Issue Type: Bug Assignee: jenslukowski Components: campfire-plugin Created: 2016/Apr/12 8:42 PM Environment: Jenkins 1.642.4, Campfire Plugin 2.7, Folders Plugin 6.7 Priority: Minor Reporter: Jesse Bowes To replicate: Install the Folders Plugin Install the Campfire Notification plugin and configure Create a new folder Within the folder, create a freestyle job Add Campfire notification as a post build action
[JIRA] [multi-branch-project-plugin] (JENKINS-33906) Icon based on status of single branch
Title: Message Title Jesse Bowes created an issue Jenkins / JENKINS-33906 Icon based on status of single branch Issue Type: Improvement Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Mar/30 2:55 PM Priority: Minor Reporter: Jesse Bowes Currently, we are able to configure a ball status icon for the Jenkins Project containing all the branches, but if a branch has a failure, this icon is red. It would be nice to be able to configure this to use the status of a specific branch (like default or release). Add Comment
[JIRA] [rake-plugin] (JENKINS-26436) Rake Plugin Does Not Find All RVM Installed Ruby Instances
Jesse Bowes created JENKINS-26436 Rake Plugin Does Not Find All RVM Installed Ruby Instances Issue Type: Bug Assignee: david_calavera Components: rake-plugin Created: 15/Jan/15 2:26 AM Description: When RVM looks for rubies, it searches in the specifications. It appears that sometimes, ruby adds a 'default' subdirectory to specifications that holds the rake specifications. I don't know what causes RVM to do this, but it happens. Pull request on the way. Project: Jenkins Priority: Minor Reporter: Jesse Bowes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path
Jesse Bowes created JENKINS-26326 Boot up Vagrant VM not using relative path Issue Type: Bug Assignee: Unassigned Components: vagrant-plugin Created: 07/Jan/15 8:00 PM Description: Under the Boot Up Vagrant VM task, specifying a relative path to the Vagrantfile doesnt work. Tried: ./Vagrantfile and Vagrantfile It appears as though 'vagrant up' tries to execute in / I can fix this by using the full path (/var/lib/jenkins/jobs/project/workspace/Vagrantfile), but it's not ideal Project: Jenkins Priority: Minor Reporter: Jesse Bowes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path
Jesse Bowes updated JENKINS-26326 Boot up Vagrant VM not using relative path Change By: Jesse Bowes (07/Jan/15 8:08 PM) Description: UndertheBootUpVagrantVMtask,specifyingarelativepathtotheVagrantfiledoesntwork.Tried:./VagrantfileandVagrantfileItappearsasthoughvagrantuptriestoexecutein/ leavingthefieldemptygivesastacktrace:java.lang.NullPointerException atjava.util.regex.Matcher.getTextLength(Matcher.java:1234) atjava.util.regex.Matcher.reset(Matcher.java:308) atjava.util.regex.Matcher.init(Matcher.java:228) atjava.util.regex.Pattern.matcher(Pattern.java:1088) athudson.FilePath.normalize(FilePath.java:285) athudson.FilePath.init(FilePath.java:230) atorg.jenkinsci.plugins.vagrant.VagrantWrapper.parseVagrantEnvironment(VagrantWrapper.java:107) atorg.jenkinsci.plugins.vagrant.VagrantWrapper.validate(VagrantWrapper.java:184) atorg.jenkinsci.plugins.vagrant.VagrantWrapper.executeCommand(VagrantWrapper.java:133) atorg.jenkinsci.plugins.vagrant.VagrantUpCommand.perform(VagrantUpCommand.java:101) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) athudson.model.Run.execute(Run.java:1745) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240) Icanfixthisbyusingthefullpath(/var/lib/jenkins/jobs/project/workspace/Vagrantfile),butitsnotideal This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vagrant-plugin] (JENKINS-26326) Boot up Vagrant VM not using relative path
Jesse Bowes
updated JENKINS-26326
Boot up Vagrant VM not using relative path
Change By:
Jesse Bowes
(07/Jan/15 8:17 PM)
Description:
UndertheBootUpVagrantVMtask,specifyingarelativepathtotheVagrantfiledoesntwork.Tried:./VagrantfileandVagrantfileItappearsasthoughvagrantuptriestoexecutein/leavingthefieldemptygivesastacktrace:
{noformat}
java.lang.NullPointerException atjava.util.regex.Matcher.getTextLength(Matcher.java:1234) atjava.util.regex.Matcher.reset(Matcher.java:308) atjava.util.regex.Matcher.init(Matcher.java:228) atjava.util.regex.Pattern.matcher(Pattern.java:1088) athudson.FilePath.normalize(FilePath.java:285) athudson.FilePath.init(FilePath.java:230) atorg.jenkinsci.plugins.vagrant.VagrantWrapper.parseVagrantEnvironment(VagrantWrapper.java:107) atorg.jenkinsci.plugins.vagrant.VagrantWrapper.validate(VagrantWrapper.java:184) atorg.jenkinsci.plugins.vagrant.VagrantWrapper.executeCommand(VagrantWrapper.java:133) atorg.jenkinsci.plugins.vagrant.VagrantUpCommand.perform(VagrantUpCommand.java:101) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) athudson.model.Run.execute(Run.java:1745) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240)
{noformat}
Icanfixthisbyusingthefullpath(/var/lib/jenkins/jobs/project/workspace/Vagrantfile),butitsnotideal
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-15828) JDK Install fails with SSL Handshake Exception
Jesse Bowes created JENKINS-15828 JDK Install fails with SSL Handshake Exception Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Nov/12 7:18 PM Description: When I set up a JDK to automatically install, build fails with: Installing JDK jdk-7u6-oth-JPR Downloading JDK from http://download.oracle.com/otn/java/jdk/7u6-b24/jdk-7u6-linux-x64.tar.gz FATAL: Remote host closed connection during handshake javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:849) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:637) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:89) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:828) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2116) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) at hudson.tools.JDKInstaller.locate(JDKInstaller.java:381) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:125) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:203) at hudson.model.JDK.forNode(JDK.java:122) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:943) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:59) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:154) at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.init(MavenExtractorEnvironment.java:85) at org.jfrog.hudson.maven3.Maven3ExtractorListener.setUpEnvironment(Maven3ExtractorListener.java:64) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:642) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1516) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.EOFException: SSL peer shut down incorrectly at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:830) ... 29 more Project: Jenkins Priority: Major Reporter: Jesse Bowes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13405) JDK Automatic install fails on Debian
Jesse Bowes created JENKINS-13405: - Summary: JDK Automatic install fails on Debian Key: JENKINS-13405 URL: https://issues.jenkins-ci.org/browse/JENKINS-13405 Project: Jenkins Issue Type: Bug Components: javanet Reporter: Jesse Bowes I have my Jenkins system set up to automatically install Java 7. When I add a new project and try to build, I see errors saying: Started by an SCM change Building in workspace /var/lib/jenkins/jobs/FeedWatcher/workspace Installing /var/lib/jenkins/tools/Java_SE_7/jdk.sh [Java_SE_7] $ /var/lib/jenkins/tools/Java_SE_7/jdk.sh -noregister /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 1: cannot open html: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 2: cannot open head: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: cannot open title: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: Request: not found /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 4: cannot open META: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 5: cannot open link: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 6: cannot open link: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 7: : not found /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 8: cannot open body: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 9: cannot open div: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 10: cannot open table: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 11: cannot open tr: No such file /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 12: Syntax error: redirection unexpected ERROR: Failed to install JDK. Exit code=2 Finished: FAILURE Looking at /var/lib/jenkins/tools/Java_SE_7/jdk.sh, I see it's HTML generated from an Oracle site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
