[JIRA] (JENKINS-40222) 'Transaction summary' and 'Performance report' are unvailable
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-40222 'Transaction summary' and 'Performance report' are unvailable Change By: Yafim Kazak Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40222) 'Transaction summary' / 'Performance report' unavailable when scenarios have underscore in their name
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-40222 'Transaction summary' / 'Performance report' unavailable when scenarios have underscore in their name Change By: Yafim Kazak Summary: 'Transaction summary' and / 'Performance report' are unvailable unavailable when scenarios with have underscore won't work in their name Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40222) 'Transaction summary' and 'Performance report' are unvailable when scenarios with underscore won't work
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-40222 'Transaction summary' and 'Performance report' are unvailable when scenarios with underscore won't work Change By: Yafim Kazak Summary: 'Transaction summary' and 'Performance report' are unvailablewhen scenarios with underscore won't work Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Daniel Spilker commented on JENKINS-40130 Re: Unable to create Jobs using job DSL in pipeline Can someone confirm that the PR fixes the issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title Daniel Beck commented on JENKINS-40130 Re: Unable to create Jobs using job DSL in pipeline I don't have access to an affected instance, so I didn't reference this issue in the PR. I don't know whether this circumvents the problem. But note that the compatibility to class=vector breaking will still remain an issue even with the PR, as it would merely be a workaround. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40373) Agent went offline during the build after configuring NIC teaming
Title: Message Title koma0277 created an issue Jenkins / JENKINS-40373 Agent went offline during the build after configuring NIC teaming Issue Type: Bug Assignee: Unassigned Components: remoting Created: 2016/Dec/12 8:25 AM Environment: Windows 2008 R2 SP1 Jenkins 2.7.3, Tomcat 8, Java 1.8.0_91 64 Bit Priority: Major Reporter: koma0277 After I have configured NIC teaming on the Jenkins server I got serveral issues with Agent went offline during the build ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5a6e25a4[name=Eudekarftps7.8] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) at sun.nio.ch.IOUtil.write(IOUtil.java:65) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java
[JIRA] (JENKINS-40315) Pipeline tests for ALM not works in new version of Jenkins Plugin on Windows Jenkins 2.7.4 server
Title: Message Title Roy Lu commented on JENKINS-40315 Re: Pipeline tests for ALM not works in new version of Jenkins Plugin on Windows Jenkins 2.7.4 server Hi Alex Farion, I check you Jenkins and found many plugins are old version that made much dependency errors. The plugin should be workable after update them. I've already update them. Please test it again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39316) hp-application-automation-tools-plugin: Report not found
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-39316 hp-application-automation-tools-plugin: Report not found Change By: Yafim Kazak Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40071) Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)
Title: Message Title Yafim Kazak assigned an issue to Jacky An Jenkins / JENKINS-40071 Problème intégration JENKINS et ALM 12.21 (upload test result to ALM) Change By: Yafim Kazak Assignee: Ofir Shaked Jacky An Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40213) If scenario folder name started from "n", console log recognizes it as \n
Title: Message Title Yafim Kazak started work on JENKINS-40213 Change By: Yafim Kazak Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40374) stash Notifier not available on Jenkins Plugin-Manager
Title: Message Title Albert V created an issue Jenkins / JENKINS-40374 stash Notifier not available on Jenkins Plugin-Manager Issue Type: Bug Assignee: Unassigned Components: stashnotifier-plugin Created: 2016/Dec/12 9:01 AM Environment: Jenkins ver. 2.35 Priority: Major Reporter: Albert V I can't find the plugin on the Jenkins Plugin-Manager. Add Comment
[JIRA] (JENKINS-40222) 'Transaction summary' / 'Performance report' unavailable when scenarios have underscore in their name
Title: Message Title Yafim Kazak started work on JENKINS-40222 Change By: Yafim Kazak Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40215) Two LR scenarios with identical name causes IOException in performance report generation
Title: Message Title Yafim Kazak started work on JENKINS-40215 Change By: Yafim Kazak Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40315) Pipeline tests for ALM not works in new version of Jenkins Plugin on Windows Jenkins 2.7.4 server
Title: Message Title Yafim Kazak started work on JENKINS-40315 Change By: Yafim Kazak Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40375) SCM Sync configuration plugin authorization, white screen and plugin initialization.
Title: Message Title Kristo Moorits updated an issue Jenkins / JENKINS-40375 SCM Sync configuration plugin authorization, white screen and plugin initialization. Change By: Kristo Moorits Hi,I updated scm-sync configuration to 0.0.10. And experienced a few issues. Firstly, when filling in the subversion repository url then after restart the plugin cannot be initialized. SEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.10 (scm-sync-configuration)java.io.IOException: Failed to initializeat hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521)at hudson.PluginManager$2$1$1.run(PluginManager.java:517)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NullPointerExceptionat sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:54)at sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)at java.lang.reflect.Field.get(Field.java:379)at hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM.extractScmCredentials(ScmSyncSubversionSCM.java:59)at hudson.plugins.scm_sync_configuration.scms.SCM.getConfiguredRepository(SCM.java:66)at hudson.plugins.scm_sync_configuration.SCMManipulator.scmConfigurationSettledUp(SCMManipulator.java:57)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.initializeRepository(ScmSyncConfigurationBusiness.java:72)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.init(ScmSyncConfigurationBusiness.java:67)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.initialInit(ScmSyncConfigurationPlugin.java:174)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.start(ScmSyncConfigurationPlugin.java:157)at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:529)at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:518)I think the reason for that is because when filling in the repository url it says "Unable to access to repository". Which leads us to the next issue. For being able to access the respository would it be possible to add username and password option right where the subversion repository url input is so we could log in just like there's an option in jobs configuration(shown in attachments screenshot).
[JIRA] (JENKINS-40375) SCM Sync configuration plugin authorization, white screen and plugin initialization.
Title: Message Title Kristo Moorits created an issue Jenkins / JENKINS-40375 SCM Sync configuration plugin authorization, white screen and plugin initialization. Issue Type: Improvement Assignee: Frédéric Camblor Attachments: credentials.png Components: scm-sync-configuration-plugin Created: 2016/Dec/12 9:03 AM Priority: Major Reporter: Kristo Moorits Hi, I updated scm-sync configuration to 0.0.10. And experienced a few issues. Firstly, when filling in the subversion repository url then after restart the plugin cannot be initialized. SEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.10 (scm-sync-configuration) java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521) at hudson.PluginManager$2$1$1.run(PluginManager.java:517) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:54) at sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36) at java.lang.reflect.Field.get(Field.java:379) at hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM.extractScmCredentials(ScmSyncSubversionSCM.java:59) at hudson.plugins.scm_sync_configuration.scms.SCM.getConfiguredRepository(SCM.java:6
[JIRA] (JENKINS-39654) HP_RUN_ID not available after Jenkins security change
Title: Message Title Yafim Kazak commented on JENKINS-39654 Re: HP_RUN_ID not available after Jenkins security change Can you please supply more information? Which prudoct is involved? which Step was used? Please upload log and build config. Which jenkins version you used? which OS? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40375) SCM Sync configuration plugin authorization, white screen and plugin initialization.
Title: Message Title Kristo Moorits updated an issue Jenkins / JENKINS-40375 SCM Sync configuration plugin authorization, white screen and plugin initialization. Change By: Kristo Moorits Hi,I updated scm-sync configuration to 0.0.10. And experienced a few issues. Firstly, when filling in the subversion repository url then after restart the plugin cannot be initialized. And due to that we're getting the "white screen of death" and jenkins will start, but shows only white blank page. SEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.10 (scm-sync-configuration)java.io.IOException: Failed to initializeat hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521)at hudson.PluginManager$2$1$1.run(PluginManager.java:517)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NullPointerExceptionat sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:54)at sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)at java.lang.reflect.Field.get(Field.java:379)at hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM.extractScmCredentials(ScmSyncSubversionSCM.java:59)at hudson.plugins.scm_sync_configuration.scms.SCM.getConfiguredRepository(SCM.java:66)at hudson.plugins.scm_sync_configuration.SCMManipulator.scmConfigurationSettledUp(SCMManipulator.java:57)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.initializeRepository(ScmSyncConfigurationBusiness.java:72)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.init(ScmSyncConfigurationBusiness.java:67)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.initialInit(ScmSyncConfigurationPlugin.java:174)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.start(ScmSyncConfigurationPlugin.java:157)at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:529)at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:518)I think the reason for that is because when filling in the repository url it says "Unable to access to repository". Which leads us to the next issue. For being able to access the respository would it be possible to add username and password option right where the subversion repository url input is so we could log in just like there's an option in jobs configuration(shown in attachments screenshot). A quick solution fo
[JIRA] (JENKINS-40071) Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)
Title: Message Title Roy Lu assigned an issue to Roy Lu Jenkins / JENKINS-40071 Problème intégration JENKINS et ALM 12.21 (upload test result to ALM) Change By: Roy Lu Assignee: Jacky An Roy Lu Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40375) SCM Sync configuration plugin authorization, white screen and plugin initialization.
Title: Message Title Kristo Moorits updated an issue Jenkins / JENKINS-40375 SCM Sync configuration plugin authorization, white screen and plugin initialization. Change By: Kristo Moorits Hi,I updated scm-sync configuration to 0.0.10. And experienced a few issues. Firstly, when filling in the subversion repository url then after restart the plugin cannot be initialized. And due to that we're getting the "white screen of death" and jenkins will start, but shows only white blank page.SEVERE: Failed Loading plugin SCM Sync Configuration Plugin v0.0.10 (scm-sync-configuration)java.io.IOException: Failed to initializeat hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:521)at hudson.PluginManager$2$1$1.run(PluginManager.java:517)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:1086)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.NullPointerExceptionat sun.reflect.UnsafeFieldAccessorImpl.ensureObj(UnsafeFieldAccessorImpl.java:54)at sun.reflect.UnsafeObjectFieldAccessorImpl.get(UnsafeObjectFieldAccessorImpl.java:36)at java.lang.reflect.Field.get(Field.java:379)at hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM.extractScmCredentials(ScmSyncSubversionSCM.java:59)at hudson.plugins.scm_sync_configuration.scms.SCM.getConfiguredRepository(SCM.java:66)at hudson.plugins.scm_sync_configuration.SCMManipulator.scmConfigurationSettledUp(SCMManipulator.java:57)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.initializeRepository(ScmSyncConfigurationBusiness.java:72)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.init(ScmSyncConfigurationBusiness.java:67)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.initialInit(ScmSyncConfigurationPlugin.java:174)at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.start(ScmSyncConfigurationPlugin.java:157)at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:529)at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:518)I think the reason for that is because when filling in the repository url it says "Unable to access to repository". Which leads us to the next issue. For being able to access the respository would it be possible to add username and password option right where the subversion repository url input is so we could log in just like there's an option in jobs configuration(shown in attachments screenshot). A quick solution for this
[JIRA] (JENKINS-40375) SCM Sync configuration plugin authorization, white screen and plugin initialization.
Title: Message Title Kristo Moorits updated an issue Jenkins / JENKINS-40375 SCM Sync configuration plugin authorization, white screen and plugin initialization. Change By: Kristo Moorits Attachment: hudson.scm.SubversionSCM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40130) Unable to create Jobs using job DSL in pipeline
Title: Message Title
Allan BURDAJEWICZ commented on JENKINS-40130
Re: Unable to create Jobs using job DSL in pipeline
I found a way to reproduce this conversion error.
Create a freestyle job generator
Add a Job DSL step, make it a Seed job and use a script like:
def gitUrl = 'https://github.com/user/repo.git'
job('generated') {
scm {
git(gitUrl)
}
triggers {
scm('*/30 * * * *')
}
steps {
shell('echo "Hello World!!!"')
}
}
Build the job generator: this creates the job generated at the root level.
Build the job generator again (just to test the update): no error
Move or Copy the Seed job
Create a folder FolderA
Copy or Move the generator job under FolderA
Build the job FolderA/generate
This should display the error message:
Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot convert type java.util.Vector to type hudson.util.DescribableList
Debugging information
class : hudson.model.FreeStyleProject
required-type : hudson.model.FreeStyleProject
converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
path: /project/triggers
line number : 15
version : not available
---
Restart and the error disappears
Restart Jenkins
Build the job FolderA/generate: this creates the job FolderA/generated
[JIRA] (JENKINS-30615) Allow specifying global NMP settings
Title: Message Title Nikolas Falco commented on JENKINS-30615 Re: Allow specifying global NMP settings For portable and secure configuration the config-file-plugin could be useful Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40004) Add description to POM
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40004 Re: Add description to POM Code changed in jenkins User: Evaristo Gutiérrez Path: build.gradle http://jenkins-ci.org/commit/gradle-plugin/141d93ebea58d74080b02276bc808b6fe7391842 Log: JENKINS-40004 Add plugin description to POM (#41) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36539) OK button disabled if project type chosen first
Title: Message Title Manuel Recena Soto commented on JENKINS-36539 Re: OK button disabled if project type chosen first Jesse Glick, the keyboard navigation does not work as I proposed. There is no a JIRA issue for that. I hope to file it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40004) Add description to POM
Title: Message Title Evaristo Gutierrez updated JENKINS-40004 Jenkins / JENKINS-40004 Add description to POM Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36539) OK button disabled if project type chosen first
Title: Message Title
Manuel Recena Soto edited a comment on JENKINS-36539
Re: OK button disabled if project type chosen first
I could not reproduce the issue described here by using Jenkins {{2.19.3}}, the previous version where the fix was delivered.h4. Steps# Click on _New item_ option# Click on _Pipeline_ job / project# Enter the a name for this new job# Change the focus from the form field# The submit button is enableThis introduces a *{color:#d04437}clear regression{color}* related with the keyword keyboard navigation. I was working on it during several days: PR-2250. I invite you to watch the screencast provided there. (flag)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-38956) can't add clover publisher
Title: Message Title Marek Parfianowicz commented on JENKINS-38956 Re: can't add clover publisher I started implementation of the bug fix, see https://issues.jenkins-ci.org/browse/JENKINS-39410?focusedCommentId=279902&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-279902 https://github.com/jenkinsci/clover-plugin/commit/0591eeabb798f2fb656c2c391324216fbae4715f It's not crashing anymore, however I need to test it further on different versions of Jenkins (1.5xx, 1.6xxx and 2.x) different project setups (freestyle and pipelines). I noticed that in some configurations values entered are not persisted, so it'll need extra fix. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39410) Clover-Plugin crash (InvocationTargetException)
Title: Message Title Marek Parfianowicz commented on JENKINS-39410 Re: Clover-Plugin crash (InvocationTargetException) I started implementation of the bug fix, see https://github.com/jenkinsci/clover-plugin/commit/0591eeabb798f2fb656c2c391324216fbae4715f It's not crashing anymore, however I need to test it further on different versions of Jenkins (1.5xx, 1.6xxx and 2.x) different project setups (freestyle and pipelines). I noticed that in some configurations values entered are not persisted, so it requires an additional fix. The fix should solve also JENKINS-38956. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39410) Clover-Plugin crash (InvocationTargetException)
Title: Message Title Marek Parfianowicz edited a comment on JENKINS-39410 Re: Clover-Plugin crash (InvocationTargetException) I started implementation of the bug fix, see[https://github.com/jenkinsci/clover-plugin/commit/0591eeabb798f2fb656c2c391324216fbae4715f] It's not crashing anymore, however I need to test it further on different versions of Jenkins (1.5xx, 1.6xxx and 2.x) different project setups (freestyle and pipelines). I noticed that in some configurations values entered are not persisted, so it requires an additional fix.The fix should solve also JENKINS-38956. A workaround is to use version 4.6.0 of the Clover plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39971) Manual update button hidden if no plugins to update availabe.
Title: Message Title Björn Pedersen commented on JENKINS-39971 Re: Manual update button hidden if no plugins to update availabe. See comment on https://github.com/jenkinsci/jenkins/commit/a51edf7c652c9eaef100ffa94e594ccd2c5b67a3. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40124) missing master polling
Title: Message Title Paul Allen updated JENKINS-40124 Jenkins / JENKINS-40124 missing master polling Change By: Paul Allen Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40124) missing master polling
Title: Message Title Paul Allen started work on JENKINS-40124 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40124) missing master polling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40124 Re: missing master polling Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java http://jenkins-ci.org/commit/p4-plugin/ff3b5dd099977873a404d7b5a29e174732c50830 Log: Prevent NPE on polling if no previous builds. JENKINS-40124 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40124) missing master polling
Title: Message Title Paul Allen updated JENKINS-40124 Ready for release Jenkins / JENKINS-40124 missing master polling Change By: Paul Allen Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40376) Build must fail, if branch spec is an empty string
Title: Message Title Nikolay Ustinov created an issue Jenkins / JENKINS-40376 Build must fail, if branch spec is an empty string Issue Type: Bug Assignee: Mark Waite Attachments: Снимок экрана 2016-12-12 в 17.49.52.png, Снимок экрана 2016-12-12 в 17.50.10.png, Снимок экрана 2016-12-12 в 17.51.42.png Components: git-plugin Created: 2016/Dec/12 10:52 AM Environment: git-plugin version 3.0.1 jenkins 2.7.4 Priority: Major Reporter: Nikolay Ustinov Use case: Create a freestyle build project with the following settings: This build is parameterized Name = BRANCH_SPECIFIER Default Value = Source Code Management Git Branch Specifier (blank for default): = $BRANCH_SPECIFIER Expected: The build must fail with ERROR because of $BRANCH_SPECIFIER was set as empty and explicit better then implicit. If you want branch spec as "*", then you should set $BRANCH_SPECIFIER was set as "*". Actually: $BRANCH_SPECIFIER was set as "**" and job will start in an infinite loop. Build for the build. Changes inserted in JENKINS-8656 need to be rolled back because they is non logical and misleading.
[JIRA] (JENKINS-40124) missing master polling
Title: Message Title Paul Allen commented on JENKINS-40124 Re: missing master polling Sorry that was supposed to be JENKINS-40356. I'll Close this one any way as FilterPollMasterImpl is no longer used. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40124) missing master polling
Title: Message Title Paul Allen closed an issue as Fixed Jenkins / JENKINS-40124 missing master polling Change By: Paul Allen Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40356) NPE on p4 polling
Title: Message Title Paul Allen commented on JENKINS-40356 Re: NPE on p4 polling Code fixed in change: https://swarm.workshop.perforce.com/changes/21270 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40356) NPE on p4 polling
Title: Message Title Paul Allen updated JENKINS-40356 Ready for release Jenkins / JENKINS-40356 NPE on p4 polling Change By: Paul Allen Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40356) NPE on p4 polling
Title: Message Title Paul Allen started work on JENKINS-40356 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40356) NPE on p4 polling
Title: Message Title Paul Allen updated JENKINS-40356 Jenkins / JENKINS-40356 NPE on p4 polling Change By: Paul Allen Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40356) NPE on p4 polling
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40356 Re: NPE on p4 polling Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java http://jenkins-ci.org/commit/p4-plugin/bb7a23cdf5056ffa1c89645141e1c2b749c547a9 Log: Prevent NPE on polling if no previous builds. JENKINS-40356 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39278) new pipeline build not started by p4 trigger if existing pipeline already running
Title: Message Title Paul Allen started work on JENKINS-39278 Change By: Paul Allen Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39278) new pipeline build not started by p4 trigger if existing pipeline already running
Title: Message Title Paul Allen updated JENKINS-39278 Jenkins / JENKINS-39278 new pipeline build not started by p4 trigger if existing pipeline already running Change By: Paul Allen Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39152) Reduce submit delay caused by Perforce triggered build endpoint
Title: Message Title Paul Allen started work on JENKINS-39152 Change By: Paul Allen Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39152) Reduce submit delay caused by Perforce triggered build endpoint
Title: Message Title Paul Allen updated JENKINS-39152 Jenkins / JENKINS-39152 Reduce submit delay caused by Perforce triggered build endpoint Change By: Paul Allen Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40376) Build must fail, if branch spec is an empty string
Title: Message Title
Nikolay Ustinov updated an issue
Jenkins / JENKINS-40376
Build must fail, if branch spec is an empty string
Change By:
Nikolay Ustinov
Use case:{quote}Create a freestyle build project with the following settings:- This build is parameterizedName = BRANCH_SPECIFIERDefault Value = Source Code ManagementGit- Branch Specifier (blank for default): = $BRANCH_SPECIFIER{quote}Expected: The build must fail with ERROR because of $BRANCH_SPECIFIER was set as empty and *explicit better then implicit*. If you want branch spec as "**", then you should set $BRANCH_SPECIFIER was set as "**". Actually:$BRANCH_SPECIFIER was set as "**" and job will start in an infinite loop. Build for the build. Changes inserted in JENKINS-8656 need to be rolled back because they is non logical and misleading.Commit https://github.com/jenkinsci/git-plugin/commit/dc575dce269020afe79bf0224c906b2520c5438d
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you
[JIRA] (JENKINS-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar reopened an issue Jenkins / JENKINS-38228 Incorrect implementation of `loadUserByUsename`, Users are added on demand Change By: Denys Digtiar Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Denys Digtiar commented on JENKINS-38228 Re: Incorrect implementation of `loadUserByUsename`, Users are added on demand It is still an issue I believe. Linking a fix which should make it more clear. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40377) Jenkins sometime does not record build information on disk
Title: Message Title Viktor Pal created an issue Jenkins / JENKINS-40377 Jenkins sometime does not record build information on disk Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2016/Dec/12 11:54 AM Priority: Major Reporter: Viktor Pal This happens with Jenkins ver. 2.19.3. Some builds just disappear from the build history. It looks like as the thread just died and nothing recorded this. The build log is missing the end of the build output and also the SUCCESS/FAILED strings. The build directory is missing the "injectedEnvVars.txt" and "build.xml" files and only has the "changelog.xml" the "log" file. This also causes other builds for the same job to start as the build is not blocking any more as it is supposed to. Jenkins is running in Docker using the official Jenkins image. This issue is very similar or the same as: https://issues.jenkins-ci.org/browse/JENKINS-19476 No related entries in the logs that I could identify to be related to this. This happens sporadically but frequent enough to cause issues. Add Comment
[JIRA] (JENKINS-19476) Jenkins sometime does not record build information on disk
Title: Message Title Viktor Pal commented on JENKINS-19476 Re: Jenkins sometime does not record build information on disk Daniel Beck New issue opened here: https://issues.jenkins-ci.org/browse/JENKINS-40377 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40378) ValidatorException: PKIX path building failed: SunCertPathBuilderException: unable to find valid certification path to requested target
Title: Message Title Vladimir Vitkov created an issue Jenkins / JENKINS-40378 ValidatorException: PKIX path building failed: SunCertPathBuilderException: unable to find valid certification path to requested target Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Dec/12 12:12 PM Environment: Jenkins: 1.650 S3-plugin: 0.10.10 AWS-SDK: 1.11.37 Priority: Major Reporter: Vladimir Vitkov Currently we are observing the following: Job runs fine Job Finishes successfully Upload to S3 fails with: Publish artifacts to S3 Bucket Build is still running Publish artifacts to S3 Bucket Using S3 profile: Production Publish artifacts to S3 Bucket bucket=xxx-archive/yyy/zzz/test1, file=xxx-yyy-20161212113849-5f2ac7573246b7cfea067aff1043926589b2d8b5.zip region=eu-west-1, will be uploaded from slave=true managed=false , server encryption false ERROR: Build step failed with exception com.amazonaws.AmazonClientException: Unable to execute HTTP request: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:747) at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:489) at com.amazonaws.http.Amazon
[JIRA] (JENKINS-40320) No page found 'config.jelly' for class hudson.model.User
Title: Message Title Michael Clarke closed an issue as Duplicate Jenkins / JENKINS-40320 No page found 'config.jelly' for class hudson.model.User Change By: Michael Clarke Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39278) new pipeline build not started by p4 trigger if existing pipeline already running
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39278 Re: new pipeline build not started by p4 trigger if existing pipeline already running Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java http://jenkins-ci.org/commit/p4-plugin/57f3947a38fbc35f5debeec30701f44b026a43ec Log: Use ExecutorService to prevent blocking during polling task. JENKINS-39278 JENKINS-39152 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39152) Reduce submit delay caused by Perforce triggered build endpoint
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39152 Re: Reduce submit delay caused by Perforce triggered build endpoint Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java http://jenkins-ci.org/commit/p4-plugin/57f3947a38fbc35f5debeec30701f44b026a43ec Log: Use ExecutorService to prevent blocking during polling task. JENKINS-39278 JENKINS-39152 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39152) Reduce submit delay caused by Perforce triggered build endpoint
Title: Message Title Paul Allen updated JENKINS-39152 Ready for release Jenkins / JENKINS-39152 Reduce submit delay caused by Perforce triggered build endpoint Change By: Paul Allen Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39278) new pipeline build not started by p4 trigger if existing pipeline already running
Title: Message Title Paul Allen updated JENKINS-39278 Ready for release Jenkins / JENKINS-39278 new pipeline build not started by p4 trigger if existing pipeline already running Change By: Paul Allen Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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/op
[JIRA] (JENKINS-40313) Exception when display view plugins
Title: Message Title Michael Clarke commented on JENKINS-40313 Re: Exception when display view plugins You updated to the latest version of what? It looks like this is an issue with the version of the testswarm-plugin you have installed. Have you tried removing or updating that? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40379) Option for 'Select All' against imported jobs
Title: Message Title Lajish Lakshmanan created an issue Jenkins / JENKINS-40379 Option for 'Select All' against imported jobs Issue Type: Improvement Assignee: Unassigned Components: job-import-plugin Created: 2016/Dec/12 1:06 PM Environment: Windows(where I've used) Priority: Minor Reporter: Lajish Lakshmanan HI there, It would be very helpful for any user who is using this plugin to import jobs from remote server. There should be a checkbox for select all jobs. In my scenario, I am importing more than 10,000 jobs. Add Comment
[JIRA] (JENKINS-40379) Option for 'Select All' against imported jobs
Title: Message Title Lajish Lakshmanan updated an issue Jenkins / JENKINS-40379 Option for 'Select All' against imported jobs Change By: Lajish Lakshmanan Environment: Windows (where I've used) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38228) Incorrect implementation of `loadUserByUsename`, Users are added on demand
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-38228 Re: Incorrect implementation of `loadUserByUsename`, Users are added on demand Denys Digtiar Did you set the setting "Username Attribute" in configuration and it does not work? when you set this setting the name of the user is taken from this attribute it is not more random generated. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40380) AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Title: Message Title
Greg Harvey created an issue
Jenkins / JENKINS-40380
AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Issue Type:
Bug
Assignee:
Evan Van Dyke
Components:
core, dashboard-view-plugin
Created:
2016/Dec/12 1:18 PM
Environment:
Jenkins 2.35 Dashboard View 2.9.2
Labels:
user-experience robustness 2.0 jenkins
Priority:
Minor
Reporter:
Greg Harvey
Hi, I kept getting locked out of company systems and we eventually tracked it down to our intrusion protection system, OSSEC, blocking me due to these calls on a Jenkins server: {{"POST /ajaxExecutors HTTP/1.1" 403 }} Turns out if you leave a Jenkins tab open in a browser and the session times out, Jenkins goes right on polling for build information with AJAX (I've tagged core and the Dashboard View Plugin, because this happens on dashboard pages I think, but I'm not 100% on that). The consequence of this is a continuous string of 403 response codes which, after a little while, will trigger an IPS worth its salts to block the IP address - which is exactly what happens to me. Why Jenkins bug? Because most applications I've come across handle this by redirecting folk to the login page if they get a 403 from an AJAX call, not keeping on hammering on those 403s. If Jenkins did that, there'd be one 403, a redirect to login and there the browser tab would sit, showing a login screen. And an IPS would not be triggered. Hope that makes sense! Thanks, Greg
[JIRA] (JENKINS-40380) AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Title: Message Title
Greg Harvey updated an issue
Jenkins / JENKINS-40380
AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Change By:
Greg Harvey
Hi,I kept getting locked out of company systems and we eventually tracked it down to our intrusion protection system, OSSEC, blocking me due to these calls on a Jenkins server:{{"POST /ajaxExecutors HTTP/1.1" 403 }}Turns out if you leave a Jenkins tab open in a browser and the session times out, Jenkins goes right on polling for build information with AJAX (I've tagged core and the Dashboard View Plugin, because this happens on dashboard pages I _think_, but I'm not 100% on that). The consequence of this is a continuous string of 403 response codes which, after a little while, will trigger an IPS worth its salts to block the IP address - which is exactly what happens to me.Why Jenkins bug? Because most applications I've come across handle this by redirecting folk to the login page if they get a 403 from an AJAX call, not keeping on hammering on those 403s. If Jenkins did that, there'd be one 403, a redirect to login and there the browser tab would sit, showing a login screen. And an IPS would not be triggered.Hope that makes sense!Thanks,Greg
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40380) AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Title: Message Title
Greg Harvey updated an issue
Jenkins / JENKINS-40380
AJAX callbacks generate 403s for expired sessions which can trigger an IPS
Change By:
Greg Harvey
Hi,I kept getting locked out of company systems and we eventually tracked it down to our intrusion protection system, OSSEC, blocking me due to these calls on a Jenkins server:{{"POST /ajaxExecutors HTTP/1.1" 403}}Turns out if you leave a Jenkins tab open in a browser and the session times out, Jenkins goes right on polling for build information with AJAX (I've tagged core and the Dashboard View Plugin, because this happens on dashboard pages I _think_, but I'm not 100% on that). The consequence of this is a continuous string of 403 response codes which, after a little while, will trigger an any IPS worth its salts to block the IP address - which is exactly what happens to me.Why Jenkins bug? Because most applications I've come across handle this by redirecting folk to the login page if they get a 403 from an AJAX call, not keeping on hammering on those 403s. If Jenkins did that, there'd be one 403, a redirect to login and there the browser tab would sit, showing a login screen. And an IPS would not be triggered.Hope that makes sense!Thanks,Greg
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40381) PreBuildMerge --ff-only fails to send notification mails for non-ff branches
Title: Message Title tsondergaard created an issue Jenkins / JENKINS-40381 PreBuildMerge --ff-only fails to send notification mails for non-ff branches Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Dec/12 1:21 PM Priority: Minor Reporter: tsondergaard Consider a job is configured with Branches to build: Branch specifier: for-master/** Additional Behaviours Merge before build Branch to merge to: master Fast-forward mode: --ff-only Calculate changelog against a specific branch Name of branch: master It is clearly possible, with this configuration, to calculate the changelog and thus identify who should receive failure notifications, even if the branch to build is not a fast-forward. This isn't done, though, so if someone pushes a branch for-master/foo that is not a fast-forward of master, then the job will fail with a message like this:
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Andrei Troie commented on JENKINS-35132
Re: Pipeline: GitHub webhook received but nothing happens
+1 Josh Chandler I am also in the same situation. I have a jenkins server with mostly freestyle jobs and we've recently decided to migrate to using pipelines. For testing, I set up a multibranch pipeline that builds the same repo as one of my freestyle jobs. The freestyle jobs get triggered just fine when the Github webhook gets received, the items under the multibranch pipeline do not. Just as Josh Chandler says, the log indicates that a POST has been receieved (as per the code here) but then nothing happens. As far as I can tell the problem occurs slightly further down, here, which is called from here. As you can see, the code in triggerFrom does the following check: if (item instanceof ParameterizedJobMixIn.ParameterizedJob), so only items that somehow end up implementing the correct I then verified this by using my jenkins script console and running the following script:
jenkinsInstance = jenkins.model.Jenkins.instance
parametrizedJobMixinItems = jenkinsInstance.getItems(ParameterizedJobMixIn.ParameterizedJob.class)
parametrizedJobMixinItems.each { println(it) }
and sure enough, I only see my freestyle jobs there, not my multibranch items as well. You could say that ultimately the responsibility lies with the creators of the multibranch pipeline, that they didn't respect the correct inheritance hierarchy, but the fact remains that as it stands, the code in the github plugin cannot trigger multibranch pipeline items.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Andrei Troie edited a comment on JENKINS-35132
Re: Pipeline: GitHub webhook received but nothing happens
+1 [~jachandler] I am also in the same situation. I have a jenkins server with mostly freestyle jobs and we've recently decided to migrate to using pipelines. For testing, I set up a multibranch pipeline that builds the same repo as one of my freestyle jobs. The freestyle jobs get triggered just fine when the Github webhook gets received, the items under the multibranch pipeline do not. Just as [~jachandler] says, the log indicates that a POST has been receieved (as per the code [here|https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L68]) but then nothing happens. As far as I can tell the problem occurs slightly further down, [here|https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/util/JobInfoHelpers.java#L110], which is called from [here|https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L79]. As you can see, the code in {{triggerFrom}} does the following check: {{if (item instanceof ParameterizedJobMixIn.ParameterizedJob)}}, so only items that somehow end up implementing having the correctinheritance hierarchy can get triggered by this code. I then verified this by using my jenkins script console and running the following script:{code:java}jenkinsInstance = jenkins.model.Jenkins.instanceparametrizedJobMixinItems = jenkinsInstance.getItems(ParameterizedJobMixIn.ParameterizedJob.class)parametrizedJobMixinItems.each { println(it) } {code}and sure enough, I could only see my freestyle jobs there, not my multibranch pipeline items as well.You could say that ultimately the responsibility lies with the creators of the multibranch pipeline, that they didn't respect the correct inheritance hierarchy, but the fact remains that as it stands, the code in the github plugin cannot trigger multibranch pipeline items.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title
Andrei Troie edited a comment on JENKINS-35132
Re: Pipeline: GitHub webhook received but nothing happens
+1 [~jachandler] I am also in the same situation. I have a jenkins server with mostly freestyle jobs and we've recently decided to migrate to using pipelines. For testing, I set up a multibranch pipeline that builds the same repo as one of my freestyle jobs. The freestyle jobs get triggered just fine when the Github webhook gets received, the items under the multibranch pipeline do not. Just as [~jachandler] says, the log indicates that a POST has been receieved (as per the code [here|https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L68]) but then nothing happens. As far as I can tell the problem occurs slightly further down, [here|https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/util/JobInfoHelpers.java#L110], which is called from [here|https://github.com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L79]. As you can see, the code in {{triggerFrom}} does the following check: {{if (item instanceof ParameterizedJobMixIn.ParameterizedJob)}}, so only items that end up having the correct inheritance hierarchy can get triggered by this code , because otherwise they'll end up failing this [null check|https://github . com/jenkinsci/github-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github/webhook/subscriber/DefaultPushGHEventSubscriber.java#L80]. I then verified this by using my jenkins script console and running the following script:{code:java}jenkinsInstance = jenkins.model.Jenkins.instanceparametrizedJobMixinItems = jenkinsInstance.getItems(ParameterizedJobMixIn.ParameterizedJob.class)parametrizedJobMixinItems.each { println(it) } {code}and sure enough, I could only see my freestyle jobs there, not my multibranch pipeline items as well.You could say that ultimately the responsibility lies with the creators of the multibranch pipeline, that they didn't respect the correct inheritance hierarchy, but the fact remains that as it stands, the code in the github plugin cannot trigger multibranch pipeline items.
Add Comment
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Kanstantsin Shautsou commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens MultibranchPipepline doesn't use gitscm, it totally separate code that works on their own triggers/plugins. Please fill issues to workflow. Github-plugin provides generic API for plugins, but nobody uses it and implements their own bicycles. Starting from this time there is no sense to make one powerful plugin as we thought before. If you don't like this triggering algorithm - don't use it. You can implement one more trigger way by using eventing APIs. Hint: on screenshot https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Integration+Plugin that triggers jobs as i wanted without sticking to gitscm at all and in theory it should work with "worfklow" (again mutlibranch is totally different APIs, if somebody exposed not suitable types in workflow-multibranch for not siutable triggers, then it their bugs) and workflow was known to be broken because they did hacks for triggers - fix was in one of latest releases. But again there is no any useful information in this issue or in comments. Please follow https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40382) Git implementation of SCMFileSystem
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-40382 Git implementation of SCMFileSystem Issue Type: New Feature Assignee: Stephen Connolly Components: git-plugin Created: 2016/Dec/12 1:58 PM Priority: Minor Reporter: Stephen Connolly Need an implementation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler updated an issue Jenkins / JENKINS-35132 Pipeline: GitHub webhook received but nothing happens Change By: Josh Chandler Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Josh Chandler commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens The word "generic" doesn't even occur on this page until you get to the comments: https://wiki.jenkins-ci.org/display/JENKINS/Github+Plugin I take issue with the sentiment that "nobody uses [the generic APIs]" because, in fact, the plugin documentation explicitly states that it does, in that it is able to trigger webhooks. If that is not the case, the plugin needs to be deprecated for end-user consumption and the documentation changed. There is nothing on the github-plugin page to indicate that an installable plugin is just an abstraction that I shouldn't be using for the purpose stated by the documentation. This functionality was guaranteed up until workflow. Kirill did not protest the use of the plugin in the way I have specified, leading me to believe this was expected behavior until now. If that was not the case, I would love to know why no one said anything to the contrary for seven months until you jumped on this thread. The very fact that of 19 watchers of this issue, that no one but you knew about this, is pretty incredible. In fact, if you ask google "jenkins github push trigger": guess what comes up as the very first result?:"Starting from this time" does not magically reconcile the fact that this bug was filed under completely different auspices seven months ago. If I am totally incorrect and this is the direction that the authors are taking with respect to their plugins, there is still a bug in that the documentation for the github-plugin needs to be changed to tell us we shouldn't be using it this way, and to point us to the appropriate plugins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
Title: Message Title Jesse Glick resolved as Cannot Reproduce Sounds obsolete. Jenkins / JENKINS-15552 envinject plugin v1.72 might be incompatible with Jenkins v.1486 Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-14332) Repeated channel/timeout errors from Jenkins slave
Title: Message Title Jesse Glick commented on JENKINS-14332 Re: Repeated channel/timeout errors from Jenkins slave Related to JENKINS-1948 perhaps? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Kanstantsin Shautsou commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens Because jenkins INFRA is not suitable for maintaining. I switched assign to Kirill Merkushev but i can't have notifications for issues. So after making review and releases i decided to check issues. I provided hints and description, i don't want discuss this issue anymore because issue complain is about not github-plugin. Trigger description will be updated as it seems that people still confused and doesn't read documentation that describes that this pushtrigger works only with gitscm. Most of jenkins plugins documentation is pure because done by developers for developers. Last year documentation was updated. Will review and update when i will have time. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40383) Update Wiki page for latest release
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-40383 Update Wiki page for latest release Issue Type: Task Assignee: Sam Van Oort Components: pipeline-graph-analysis-plugin Created: 2016/Dec/12 2:48 PM Labels: documentation wiki Priority: Minor Reporter: Nick Jones The Jenkins Wiki page for this plugin, linked to from the Jenkins plugin manager (/pluginManager) does not describe or link to the 1.3 release that the plugin manager shows as being available. I can manually craft a GitHub release comparison between 1.2 and 1.3 but this Wiki page should have a change log entry for 1.3, and links to the same comparison. Add Comment
[JIRA] (JENKINS-37575) Jenkins node keeps sending the same logs indefinitely
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37575 Jenkins node keeps sending the same logs indefinitely Change By: Jesse Glick Component/s: remoting Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Title: Message Title Jesse Glick commented on JENKINS-6817 Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel JENKINS-1948? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37575 Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely Change By: Jesse Glick Summary: Delays in FileMonitoringTask. WriteLog cancause process output to be resent indefinitely Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37575 Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely Change By: Jesse Glick Labels: robustness Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37575) Delays in WriteLog can
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37575 Delays in WriteLog can Change By: Jesse Glick Summary: Jenkins node keeps sending the same logs indefinitely Delays in WriteLog can Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40313) Exception when display view plugins
Title: Message Title Emiliano m commented on JENKINS-40313 Re: Exception when display view plugins mm... I'm haven't that plugin, I have jenkins updated and all plugins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37575) Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely
Title: Message Title Jesse Glick commented on JENKINS-37575 Re: Delays in FileMonitoringTask.WriteLog can cause process output to be resent indefinitely JENKINS-38381 does use a different code path. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40313) Exception when display view plugins
Title: Message Title Emiliano m edited a comment on JENKINS-40313 Re: Exception when display view plugins mm... I 'm haven't that plugin, I have jenkins updated and all plugins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40383) Update Wiki page for 1.3 Pipeline Graph Analysis release
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-40383 Update Wiki page for 1.3 Pipeline Graph Analysis release Change By: Nick Jones Summary: Update Wiki page for latest 1.3 Pipeline Graph Analysis release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35132) Pipeline: GitHub webhook received but nothing happens
Title: Message Title Kanstantsin Shautsou commented on JENKINS-35132 Re: Pipeline: GitHub webhook received but nothing happens Checked wiki page - everything described right. UI text will be changed later. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40376) Build must fail, if branch spec is an empty string
Title: Message Title Mark Waite resolved as Won't Fix We don't change default behaviors of the git plugin, even if one or more users feel they are non logical and misleading Too many users and installations depend on the default behaviors, and too little benefit would be gained by requiring them to change their parameterized jobs or their automation which launches jobs. Jenkins / JENKINS-40376 Build must fail, if branch spec is an empty string Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40381) PreBuildMerge --ff-only fails to send notification mails for non-ff branches
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-40381 PreBuildMerge --ff-only fails to send notification mails for non-ff branches Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40121) Wrong .gitconfig parsed (Local system instead of jenkins service account)
Title: Message Title Mark Waite closed an issue as Won't Fix This is a command line git behavior, not something that the git plugin can or should fix. Jenkins / JENKINS-40121 Wrong .gitconfig parsed (Local system instead of jenkins service account) Change By: Mark Waite Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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...@googl
[JIRA] (JENKINS-39300) View.getDisplayName() is ignored when rendering tabs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39300 Re: View.getDisplayName() is ignored when rendering tabs Code changed in jenkins User: Stephen Connolly Path: core/src/main/resources/hudson/views/DefaultMyViewsTabBar/myViewTabs.jelly core/src/main/resources/hudson/views/DefaultViewsTabBar/viewTabs.jelly core/src/main/resources/lib/layout/tab.jelly http://jenkins-ci.org/commit/jenkins/0763ffd0e928eeb7b2411701f03a165139902f54 Log: [FIXED JENKINS-39300] Use View.getDisplayName() when rendering the view tabs Also fix the stapler documentation for the tag Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Mark Waite resolved as Not A Defect The plugin is known to work with bitbucket hosted private repositories. It is regularly tested with those private repositories. This is unlikely to be a plugin bug, but rather an authentication or configuration error. Jenkins / JENKINS-39728 Jenkins not able to clone private bitbucket repo Change By: Mark Waite Status: In Progress Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To uns
[JIRA] (JENKINS-37295) Redesign the empty states
Title: Message Title Cliff Meyers commented on JENKINS-37295 Re: Redesign the empty states Looks good to me. If each empty state standardizes on the format of some "header" text, body text, and an action button then we can probably dump the use of Markdown for i18n which Michael Neale and I have been eyeing for a while now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37295) Redesign the empty states
Title: Message Title Cliff Meyers edited a comment on JENKINS-37295 Re: Redesign the empty states Looks good to me. If each empty state standardizes on the format of some "header" text, body text, and an action button then we can probably dump the use of Markdown ( for i18n ) in empty states which [~michaelneale] and I have been eyeing for a while now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-40369) rerun button in rundetails sometimes redirects to the wrong url
Title: Message Title Cliff Meyers commented on JENKINS-40369 Re: rerun button in rundetails sometimes redirects to the wrong url Will have to debug it, but we are relying on the "expectedBuildNumber" that's returned from the REST API when we execute the run. We should start there and make sure the value is correct. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38277) The webhook registration didn't register the push hook
Title: Message Title Kirill Merkushev assigned an issue to Kohsuke Kawaguchi Jenkins / JENKINS-38277 The webhook registration didn't register the push hook Change By: Kirill Merkushev Assignee: Kirill Merkushev Kohsuke Kawaguchi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-37087) Label expressions and multiple labels per pod aren't handled properly
Title: Message Title Bruno Bieth commented on JENKINS-37087 Re: Label expressions and multiple labels per pod aren't handled properly Is this still open? I took a glance at the PR and couldn't find any test, am I missing something? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39632) Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins
Title: Message Title Kirill Merkushev commented on JENKINS-39632 Re: Unselecting "Build when a change is pushed to GitHub" results in NullPointerException and breaks all builds in Jenkins Unmarshalling for job which contains null tag Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38721 Re: Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/workflow/steps/CatchErrorStepTest.java http://jenkins-ci.org/commit/workflow-basic-steps-plugin/a1073f63461efa41b97d038191610c9dcbd60327 Log: Adjust test to work against -Djenkins.version=2.19.4 after JENKINS-36594 & JENKINS-38721. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36594) CauseOfInterruption.UserInterruption#print() may cause creation of previously deleted users
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36594 Re: CauseOfInterruption.UserInterruption#print() may cause creation of previously deleted users Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/workflow/steps/CatchErrorStepTest.java http://jenkins-ci.org/commit/workflow-basic-steps-plugin/a1073f63461efa41b97d038191610c9dcbd60327 Log: Adjust test to work against -Djenkins.version=2.19.4 after JENKINS-36594 & JENKINS-38721. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
