[JIRA] (JENKINS-50476) RestartableJenkinsRule should allow steps where Jenkins is not expected to start correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50476 Re: RestartableJenkinsRule should allow steps where Jenkins is not expected to start correctly Code changed in jenkins User: Baptiste Mathus Path: src/main/java/org/jvnet/hudson/test/RestartableJenkinsRule.java http://jenkins-ci.org/commit/jenkins-test-harness/61a2b959388ed584ce327ff77ff057f6a6fd61de Log: JENKINS-50476 offer a way to assert that Jenkins won't start Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50476) RestartableJenkinsRule should allow steps where Jenkins is not expected to start correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50476 Re: RestartableJenkinsRule should allow steps where Jenkins is not expected to start correctly Code changed in jenkins User: Baptiste Mathus Path: src/main/java/org/jvnet/hudson/test/RestartableJenkinsRule.java http://jenkins-ci.org/commit/jenkins-test-harness/15a06ecccdcd996df444db6a2e08bd3a28607c45 Log: Merge pull request #96 from batmat/JENKINS-50476 JENKINS-50476 offer a way to assert that Jenkins won't start Compare: https://github.com/jenkinsci/jenkins-test-harness/compare/2e8d1af86c7f...15a06ecccdcd Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50500) Jenkins with HP ALM to set status "Closed" or " Resolved"
Title: Message Title Sameer Mohammad commented on JENKINS-50500 Re: Jenkins with HP ALM to set status "Closed" or " Resolved" Hello, It should be a part of test harness. I am trying to change the defect status to resolved or pending or something else from jenkins. Let me know if you have any questions. Also if you could share any integration details for test harness would be great Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45982) Calling super to CPS-transformed methods fails with CpsCallableInvocation
Title: Message Title Mor L commented on JENKINS-45982 Re: Calling super to CPS-transformed methods fails with CpsCallableInvocation Hi, when is workflow-cps 2.46 going to be released? As it stands all my inheritance trials in Shared Libraries ended in failures due to this and similar errors. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title
Antonio Muñiz commented on JENKINS-48510
Re: Pipeline Milestone step: Adding parameter for milestone classification
The proposed ordinalGroup feature would be a workaround for a good practice: one branch, one job. Having 2 projects/branches been built by the same job is not desirable. Avoiding this is the whole point of multibranch projects. Each project should have its own multibranch job. If projects live in branches of the same repository, then use specific {{Jenkinsfile}}s in branches.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-47844) Repeatable intermittent svn update failures due to NPE
Title: Message Title Vassilena Treneva commented on JENKINS-47844 Re: Repeatable intermittent svn update failures due to NPE We often see the same issue in our environments. Running on Jenkins ver. 2.113 and Subversion Plug-in 2.10.5 05:46:48 java.lang.NullPointerException*05:46:48* at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:123)05:46:48 at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757)05:46:48 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:892)05:46:48 at hudson.scm.SCM.checkout(SCM.java:504)05:46:48 at hudson.model.AbstractProject.checkout(AbstractProject.java:1208)05:46:48 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)05:46:48 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)05:46:48 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)05:46:48 at hudson.model.Run.execute(Run.java:1727)05:46:48 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)05:46:48 at hudson.model.ResourceController.execute(ResourceController.java:97)05:46:48 at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47844) Repeatable intermittent svn update failures due to NPE
Title: Message Title Vassilena Treneva edited a comment on JENKINS-47844 Re: Repeatable intermittent svn update failures due to NPE We often see the same issue in our environments.Running on Jenkins ver. 2.113 and Subversion Plug-in 2.10.5 *05:46:48* java.lang.NullPointerException *05:46:48* at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:123) *05:46:48* at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) *05:46:48* at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:892) *05:46:48* at hudson.scm.SCM.checkout(SCM.java:504) *05:46:48* at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) *05:46:48* at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) *05:46:48* at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) *05:46:48* at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) *05:46:48* at hudson.model.Run.execute(Run.java:1727) *05:46:48* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) *05:46:48* at hudson.model.ResourceController.execute(ResourceController.java:97) *05:46:48* at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50500) Jenkins with HP ALM to set status "Closed" or " Resolved"
Title: Message Title Oleg Nenashev commented on JENKINS-50500 Re: Jenkins with HP ALM to set status "Closed" or " Resolved" Sorry, I still do not understand the question. The original component was "Jenkins Test Harness". It is a Jenkins-internal testing framework: https://github.com/jenkinsci/jenkins-test-harness/ . Do you expect changes in it in order to track tests for your plugin? If no, is it a feature request or question to an existing plugin? E.g. https://wiki.jenkins.io/display/JENKINS/HP+ALM+Quality+Center+Plugin or https://wiki.jenkins.io/display/JENKINS/HP+Application+Automation+Tools Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title Raul Arabaolaza commented on JENKINS-50405 Re: runATH leads to deadlock of resource consumption for core PR builds In the meanwhile, I can just make the ensureInNode accept a list of labels and check that all are present in the current node Andrew Bayer Do you believe an ensureInNode step able to deal with label expressions could be an interesting addition for workflow.durable-task-step plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50508) NPE on withMaven step after upgrade to Pipeline Maven Integration 3.5.0
Title: Message Title Andreya Kostov created an issue Jenkins / JENKINS-50508 NPE on withMaven step after upgrade to Pipeline Maven Integration 3.5.0 Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-04-02 09:07 Environment: OS: Debian Linux (Docker) Jenkins: 2.107.1 (LTS) Pipeline Maven Integration Plugin: 3.5.0 Priority: Minor Reporter: Andreya Kostov After upgrading Pipeline Maven Integration Plugin from 3.4.3 to 3.5.0, a scripted pipeline fails on withMaven step with the following error: java.lang.NullPointerException: while trying to read the field 'clazz' of a null object loaded from local variable 'd' at org.jenkinsci.plugins.structs.SymbolLookup.findDescriptor(SymbolLookup.java:147) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:155) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultC
[JIRA] (JENKINS-50484) The Groovy Postbuild 2.4 Broken links using manager.addShortText in pipeline and freestyle
Title: Message Title Mallikarjun Halburgi updated an issue Jenkins / JENKINS-50484 The Groovy Postbuild 2.4 Broken links using manager.addShortText in pipeline and freestyle Change By: Mallikarjun Halburgi Attachment: Groovy_Postbuild_Plugin_issue_2_24_0.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50484) The Groovy Postbuild 2.4 Broken links using manager.addShortText in pipeline and freestyle
Title: Message Title Mallikarjun Halburgi commented on JENKINS-50484 Re: The Groovy Postbuild 2.4 Broken links using manager.addShortText in pipeline and freestyle Please fix it. PFA on issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50480) UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.*
Title: Message Title Oleg Nenashev commented on JENKINS-50480 Re: UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.* > The docker-java library is not a direct dependency of the docker plugin but is pulled in transitively through the docker-java-api plugin. Would it make more sense to whitelist the classes in that plugin instead if they can be safely serialized? This library is generally a risky thing, because it does not consistently retain binary compatibility. That's why it has been originally shaded in plugins like Docker, Yet Another Docker Plugin, Docker Traceability, etc. So a user of such API library may find his plugin broken by a library update. Maybe the situation became better over years, Kanstantsin Shautsou improved Docker Java's lifecycle a lot Apart from that, +1 for moving whitelist to a library in the current state. > I think that whitelisting the classes in the com.github.dockerjava.api.model package is probably ok I have reviewed all classes, and yes they are OK in the current version. OTOH the whitelist does not seem to be enough. com.github.dockerjava.api.command.InspectContainerResponse$Node is not whitelisted. The serialization of InspectContainerResponse may fail if the field is not null > but serializing the 2 commands in the com.github.dockerjava.api.command package seem like an accident where an inner class picks up a parameter or local variable Yes, InspectContainerResponse$ContainerState and InspectContainerResponse$Node inner classes are not static. Making them static would break binary compatibility. It may be acceptable for Docker Java tho. Probably it's fine to keep it whitelisted. E.g. InspectContainerResponse is also explicitly persisted in the Docker Traceability plugin (within https://github.com/jenkinsci/docker-traceability-plugin/blob/49141a86d41269799e00161a02ac72e9aa9a3a15/docker-traceability-api/src/main/java/org/jenkinsci/plugins/docker/traceability/api/DockerTraceabilityReport.java#L51). This does seem to be a valid use-case for serialization though it makes the plugin affected by JEP-200 for sure. I will create a ticket Add Comment This message was sent by Atlassian JIRA (v7.
[JIRA] (JENKINS-50509) Docket Traceability plugin is affected by JEP-200
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50509 Docket Traceability plugin is affected by JEP-200 Issue Type: Bug Assignee: Alex Taylor Components: docker-traceability-plugin Created: 2018-04-02 09:52 Priority: Minor Reporter: Oleg Nenashev It is a follow-up to the investigation of JENKINS-50480... 1) Docker Traceability API library has no Whitelist manifest entry, so the classes in it will be likely rejected. There is a critical class for fingerprinting: https://github.com/jenkinsci/docker-traceability-plugin/blob/49141a86d41269799e00161a02ac72e9aa9a3a15/docker-traceability-api/src/main/java/org/jenkinsci/plugins/docker/traceability/api/DockerTraceabilityReport.java#L51 2) Docker Traceability includes shaded versions of Docker Java classes. Since shading happens in a separate JAR, it likely also needs whittelisting Add Comment
[JIRA] (JENKINS-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50483 AWS Device Farm plugin affected by JEP-200 Change By: Oleg Nenashev Assignee: Chandra Bommas Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Oleg Nenashev started work on JENKINS-50483 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50508) NPE on withMaven step after upgrade to Pipeline Maven Integration 3.5.0
Title: Message Title Andreya Kostov updated an issue Jenkins / JENKINS-50508 NPE on withMaven step after upgrade to Pipeline Maven Integration 3.5.0 Change By: Andreya Kostov Attachment: jenkins_log_error.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49548) Add a BO test for the ATH
Title: Message Title Raul Arabaolaza closed an issue as Won't Do BO already has a decent ATH, so it makes no sense to duplicate tests between BO ATH and the standard ATH If there is a need to run acceptance tests for BO the standard ATH is not the way to go Jenkins / JENKINS-49548 Add a BO test for the ATH Change By: Raul Arabaolaza Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emai
[JIRA] (JENKINS-50508) NPE on withMaven step after upgrade to Pipeline Maven Integration 3.5.0
Title: Message Title Andreya Kostov commented on JENKINS-50508 Re: NPE on withMaven step after upgrade to Pipeline Maven Integration 3.5.0 Attached a part of the Jenkins logs, which is probably related - instantiating org.jenkinsci.plugins.pipeline.maven.publishers.TasksScannerPublisher.DescriptorImpl fails. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Oleg Nenashev commented on JENKINS-50483 Re: AWS Device Farm plugin affected by JEP-200 The plugin stores Build logs on the project level. Such approach is clearly a bug, it may cause collisions between jobs running in parallel Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Oleg Nenashev updated JENKINS-50483 Jenkins / JENKINS-50483 AWS Device Farm plugin affected by JEP-200 Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Oleg Nenashev commented on JENKINS-50483 Re: AWS Device Farm plugin affected by JEP-200 I have created https://github.com/jenkinsci/aws-device-farm-plugin/pull/3 with a patch. Dustin Kerber would you be able to try the build from CI and report testing results? I have no proper test environment, so I cannot guarantee the patch solves all JEP-200 issues in the plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50480) UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.*
Title: Message Title Oleg Nenashev updated JENKINS-50480 Jenkins / JENKINS-50480 UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.* Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50480) UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.*
Title: Message Title Oleg Nenashev started work on JENKINS-50480 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Oleg Nenashev commented on JENKINS-50216 Re: Google Auth Plugin is incompatible with Jenkins 2.102+ I have got a response from plugin maintainers regarding this issue. They are ready to help with reviews, and CLA is not longer required according to them. So I have created https://github.com/jenkinsci/google-oauth-plugin/pull/16. Once it is merged, we can proceed with the fix (if prioritized) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50475) Scope import dependencies
Title: Message Title Cyrille Le Clerc commented on JENKINS-50475 Re: Scope import dependencies Scope "import" is missing here https://github.com/jenkinsci/pipeline-maven-plugin/blob/1729e64250c10213ca428141092540bdeeaba97a/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java#L67 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50492) Thread blocked
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50492 Thread blocked Change By: Oleg Nenashev Component/s: multijob-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50492) Thread blocked
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-50492 Thread blocked Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50492) Thread blocked
Title: Message Title Oleg Nenashev commented on JENKINS-50492 Re: Thread blocked I assume it is one of the known issues in the MultiJob plugin. The attached file is not formatted as a standard thread dump, so it's hard to read it. Would be nice if you could resubmit the file in a proper format Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49932) Add editor ATH coverage for changing an existing stage in a Jenkinsfile
Title: Message Title Karl Shultz closed an issue as Duplicate I took care of both of these tickets at the same time. Jenkins / JENKINS-49932 Add editor ATH coverage for changing an existing stage in a Jenkinsfile Change By: Karl Shultz Status: Open Closed Assignee: Karl Shultz Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this me
[JIRA] (JENKINS-46330) Users cannot cancel builds of non-AbstractProject jobs from build history
Title: Message Title Nathan Vahrenberg updated an issue Jenkins / JENKINS-46330 Users cannot cancel builds of non-AbstractProject jobs from build history Change By: Nathan Vahrenberg Attachment: build.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-17693) Confluence Publisher for Confluence 5x
Title: Message Title mingxing long commented on JENKINS-17693 Re: Confluence Publisher for Confluence 5x i use this plugin to upload an file to a confluence page. I want to update this file every build, so chose an option which is named "relaced attachment". plugin is version2.0, confluence is version6.2.1, and I get the error as follow: [confluence] Upload attachment to Confluence page: Evaluating file(s) pattern: Found 1 workspace artifact(s) to upload to Confluence Upload 1 file(s) to Confluence ERROR: Build step failed with exception java.lang.UnsuporttedOperationException at java.util.AbstractList.remove(AbstractList.java:161) at java.util.AbstractList$Itr.remove(AbstractList.java:374) at java.util.AbstractCollection.remove(AbstractCollection.java:293) at com.myyearbook.hudson.plugins.ConfluencePblisher.performAttachments(ConfluencePblisher.java:442) at com.myyearbook.hudson.plugins.ConfluencePblisher.perform(ConfluencePblisher.java:321) at hudson.tasks.BuildStepcomptibilityLayer.perform(BuildStepcomptibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildException.perform(AbstractBuildException.java:779) at hudson.model.AbstractBuild$AbstractBuildException.performAllBuild(AbstractBuild.java:720) at hudson.model.Build$BuildException.post2(Build.java:486) at hudson.model.AbstractBuild$AbstractBuildException.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at hudson.model.freeStyleBuildRun.run(freeStyleBuildRun.java:43) at hudson.ResourceController.execute(ResourceController.java:98) at hudson.Executor.run(Executor.java:405) Build step publish Confluence marked build as failed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title thiyagachudar perumal updated an issue Jenkins / JENKINS-39154 Can not edit Pipeline script - text not visible on Configure Page Change By: thiyagachudar perumal Attachment: jenkins.pdf Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title thiyagachudar perumal commented on JENKINS-39154 Re: Can not edit Pipeline script - text not visible on Configure Page This is happening again for version 2.41 ,can any one help us , jenkins.pdf Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-17693) Confluence Publisher for Confluence 5x
Title: Message Title mingxing long commented on JENKINS-17693 Re: Confluence Publisher for Confluence 5x i use this plugin to upload a file which not exist is ok, but upload a file which already exist get the error above Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-17693) Confluence Publisher for Confluence 5x
Title: Message Title mingxing long edited a comment on JENKINS-17693 Re: Confluence Publisher for Confluence 5x i use this plugin to upload an file to a confluence page. I want to update this file every successful build, so chose an option which is named "relaced attachment". plugin is version2.0, confluence is version6.2.1, and I get the error as follow:[confluence] Upload attachment to Confluence page: Evaluating file(s) pattern: Found 1 workspace artifact(s) to upload to Confluence Upload 1 file(s) to ConfluenceERROR: Build step failed with exceptionjava.lang.UnsuporttedOperationException at java.util.AbstractList.remove(AbstractList.java:161) at java.util.AbstractList$Itr.remove(AbstractList.java:374) at java.util.AbstractCollection.remove(AbstractCollection.java:293) at com.myyearbook.hudson.plugins.ConfluencePblisher.performAttachments(ConfluencePblisher.java:442) at com.myyearbook.hudson.plugins.ConfluencePblisher.perform(ConfluencePblisher.java:321) at hudson.tasks.BuildStepcomptibilityLayer.perform(BuildStepcomptibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildException.perform(AbstractBuildException.java:779) at hudson.model.AbstractBuild$AbstractBuildException.performAllBuild(AbstractBuild.java:720) at hudson.model.Build$BuildException.post2(Build.java:486) at hudson.model.AbstractBuild$AbstractBuildException.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at hudson.model.freeStyleBuildRun.run(freeStyleBuildRun.java:43) at hudson.ResourceController.execute(ResourceController.java:98) at hudson.Executor.run(Executor.java:405) Build step publish Confluence marked build as failed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-17693) Confluence Publisher for Confluence 5x
Title: Message Title mingxing long edited a comment on JENKINS-17693 Re: Confluence Publisher for Confluence 5x i use this plugin to upload an file to a confluence page. I want to update this file every successful build, so chose an option which is named "relaced attachment". plugin Plugin is version2.0, and confluence is version6.2.1 .In this case , and I get uploading a file which not exist is ok, but uploading a file which already exist gets the error which is as follow:[confluence] Upload attachment to Confluence page: Evaluating file(s) pattern: Found 1 workspace artifact(s) to upload to Confluence Upload 1 file(s) to ConfluenceERROR: Build step failed with exceptionjava.lang.UnsuporttedOperationException at java.util.AbstractList.remove(AbstractList.java:161) at java.util.AbstractList$Itr.remove(AbstractList.java:374) at java.util.AbstractCollection.remove(AbstractCollection.java:293) at com.myyearbook.hudson.plugins.ConfluencePblisher.performAttachments(ConfluencePblisher.java:442) at com.myyearbook.hudson.plugins.ConfluencePblisher.perform(ConfluencePblisher.java:321) at hudson.tasks.BuildStepcomptibilityLayer.perform(BuildStepcomptibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildException.perform(AbstractBuildException.java:779) at hudson.model.AbstractBuild$AbstractBuildException.performAllBuild(AbstractBuild.java:720) at hudson.model.Build$BuildException.post2(Build.java:486) at hudson.model.AbstractBuild$AbstractBuildException.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at hudson.model.freeStyleBuildRun.run(freeStyleBuildRun.java:43) at hudson.ResourceController.execute(ResourceController.java:98) at hudson.Executor.run(Executor.java:405) Build step publish Confluence marked build as failed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-17693) Confluence Publisher for Confluence 5x
Title: Message Title mingxing long updated an issue Jenkins / JENKINS-17693 Confluence Publisher for Confluence 5x Change By: mingxing long Comment: i use this plugin to upload a file which not exist is ok, but upload a file which already exist get the error above Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-17693) Confluence Publisher for Confluence 5x
Title: Message Title mingxing long edited a comment on JENKINS-17693 Re: Confluence Publisher for Confluence 5x i use this plugin to upload an file to a confluence page. I want to update this file every successful build, so chose an option which is named "relaced attachment". Plugin is version2.0, and confluence is version6.2.1.In this case, uploading a file which not exist is ok, but uploading a the file which already exist exists gets the error which is as follow:[confluence] Upload attachment to Confluence page: Evaluating file(s) pattern: Found 1 workspace artifact(s) to upload to Confluence Upload 1 file(s) to ConfluenceERROR: Build step failed with exceptionjava.lang.UnsuporttedOperationException at java.util.AbstractList.remove(AbstractList.java:161) at java.util.AbstractList$Itr.remove(AbstractList.java:374) at java.util.AbstractCollection.remove(AbstractCollection.java:293) at com.myyearbook.hudson.plugins.ConfluencePblisher.performAttachments(ConfluencePblisher.java:442) at com.myyearbook.hudson.plugins.ConfluencePblisher.perform(ConfluencePblisher.java:321) at hudson.tasks.BuildStepcomptibilityLayer.perform(BuildStepcomptibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildException.perform(AbstractBuildException.java:779) at hudson.model.AbstractBuild$AbstractBuildException.performAllBuild(AbstractBuild.java:720) at hudson.model.Build$BuildException.post2(Build.java:486) at hudson.model.AbstractBuild$AbstractBuildException.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1753) at hudson.model.freeStyleBuildRun.run(freeStyleBuildRun.java:43) at hudson.ResourceController.execute(ResourceController.java:98) at hudson.Executor.run(Executor.java:405) Build step publish Confluence marked build as failed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title thiyagachudar perumal reopened an issue The Pipeline Script editor is not showing up again when i upgraded the Jenkins API and Groovy to the latest version . Also the nodes are not showing up other than Master jenkins.pdf Jenkins / JENKINS-39154 Can not edit Pipeline script - text not visible on Configure Page Change By: thiyagachudar perumal Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe fr
[JIRA] (JENKINS-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Viktor Utkin edited a comment on JENKINS-45419 Re: 'Use Repository' setting does not find other remote urls if multiple repos are added to job Now it shows duplicates for first repo if I enter filled it in field "Use repository" !image-2018-04-02-17-59-17-394.png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Viktor Utkin reopened an issue Now it shows duplicates for first repo if I enter it in field "Use repository" Unable to render embedded object: File (image-2018-04-02-17-59-17-394.png) not found. Jenkins / JENKINS-45419 'Use Repository' setting does not find other remote urls if multiple repos are added to job Change By: Viktor Utkin Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Viktor Utkin edited a comment on JENKINS-45419 Re: 'Use Repository' setting does not find other remote urls if multiple repos are added to job Now it shows duplicates for first repo if I filled it in field "Use repository" !image-2018-04-02- 17 18 - 59 03 - 17 15 - 394 586 .png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Viktor Utkin edited a comment on JENKINS-45419 Re: 'Use Repository' setting does not find other remote urls if multiple repos are added to job Now it shows duplicates for first repo (I have two in one pipeline) if I filled it in field "Use repository" !image-2018-04-02-18-03-15-586.png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48170) BlackDuck Hub Plugin does not terminate scan-cli when job is cancelled
Title: Message Title Ari Kamen updated an issue Jenkins / JENKINS-48170 BlackDuck Hub Plugin does not terminate scan-cli when job is cancelled Change By: Ari Kamen Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50502) JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons
Title: Message Title Ari Kamen commented on JENKINS-50502 Re: JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons Linda Springsteen we will look into this issue, but we have also announced an EOL for this product. We recommend that users transition to our Detect product, we also have a Detect for Jenkins if interested. https://wiki.jenkins.io/display/JENKINS/Black+Duck+Detect+Plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48170) BlackDuck Hub Plugin does not terminate scan-cli when job is cancelled
Title: Message Title Ari Kamen commented on JENKINS-48170 Re: BlackDuck Hub Plugin does not terminate scan-cli when job is cancelled Rob Petti we will look into this issue, but we have also announced an EOL for this product. We recommend that users transition to our Detect product, we also have a Detect for Jenkins if interested. https://wiki.jenkins.io/display/JENKINS/Black+Duck+Detect+Plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50502) JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50502 Re: JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons Ari Kamen Thanks for the response! BTW, it may make sense to verify the compatibility of the new plugin with JEP-200. I do not see code which is obviously impacted, but I may be missing sosmething. The new plugin is based on Gradle, so we cannot run plugin compatibility tester against it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50491) NOT EVERY commit triggers (start) jenkins job by webhook (gitlab)
Title: Message Title
val v updated an issue
Jenkins / JENKINS-50491
NOT EVERY commit triggers (start) jenkins job by webhook (gitlab)
Change By:
val v
For jenkins job is configured pipeline.There are stable connection and all works but,SOMETIMES without visible reason gitlab webhook does not start (trigger) jenkins job. Bug was reproduced when this job is already running and after more than hour of inactivity (it also passed more than 1 hour from last commit to git - as trigger to job). Gitlab does not repeated this trigger which means that gitlab received accept ("200") from jenkins server OR does not send webhook at all. Detail of process flow is on attached screen.example: first commit - 98a913 - 18.39 28.03.2018 - trigger OKsecond commit - 02ebc1 - 12.49 29.03.2018 - no webhookthird commit - be8d57 - 13.40 29.03.2018 - no webhookfourth commit - 87ea5d - 29.03.2018 - trigger OK Job is configured to starts on every changes to source or target branches. These commits are commits to source branch. (looks like https://issues.jenkins-ci.org/browse/JENKINS-34727 with little difference but not depends on time)***addition:received in jenkins log next note with such situation (webhook received, job did not start): Apr 02, 2018 5:39:18 PM INFO com.dabsquared.gitlabjenkins.webhook.GitLabWebHook getDynamicWebHook called with url: /project/autograder_main_FeatureBranchBuildApr 02, 2018 5:39:40 PM INFO org.eclipse.jetty.server.session.Session beginInvalidateSession node01use5jw2vbywv16e45jtsmcxcc2420 already being invalidated
Add Comment
[JIRA] (JENKINS-50502) JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons
Title: Message Title Ari Kamen commented on JENKINS-50502 Re: JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons Oleg Nenashev indeed we have switched to gradle as all of our plugins are now gradle based with a common gradle plugin for consistency and ease of deployment. Want to thank you for bringing this to our attention, the list of compatibility issues does seem rather substantial, I assume you are referring to this: https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50491) NOT EVERY commit triggers (start) jenkins job by webhook (gitlab)
Title: Message Title
val v updated an issue
Jenkins / JENKINS-50491
NOT EVERY commit triggers (start) jenkins job by webhook (gitlab)
Change By:
val v
For jenkins job is configured pipeline.There are stable connection and all works but,SOMETIMES without visible reason gitlab webhook does not start (trigger) jenkins job. Bug was reproduced when this job is already running and after more than hour of inactivity (it also passed more than 1 hour from last commit to git - as trigger to job). Gitlab does not repeated this trigger which means that gitlab received accept ("200") from jenkins server OR does not send webhook at all. Detail of process flow is on attached screen.example: first commit - 98a913 - 18.39 28.03.2018 - trigger OKsecond commit - 02ebc1 - 12.49 29.03.2018 - no webhookthird commit - be8d57 - 13.40 29.03.2018 - no webhookfourth commit - 87ea5d - 29.03.2018 - trigger OK Job is configured to starts on every changes to source or target branches. These commits are commits to source branch. (looks like https://issues.jenkins-ci.org/browse/JENKINS-34727 with little difference but not depends on time) ***addition:received in jenkins log next note with such situation (webhook received, job did not start):Apr 02, 2018 5:39:18 PM INFO com.dabsquared.gitlabjenkins.webhook.GitLabWebHook getDynamicWebHook called with url: /project/autograder_main_FeatureBranchBuildApr 02, 2018 5:39:40 PM INFO org.eclipse.jetty.server.session.Session beginInvalidateSession node01use5jw2vbywv16e45jtsmcxcc2420 already being invalidated
Add Comment
[JIRA] (JENKINS-46248) Deadlock in queue maintenance + node removal
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-46248 Deadlock in queue maintenance + node removal Change By: Jesse Glick Labels: deadlock pipeline threads Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46248) Deadlock in queue maintenance + node removal
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-46248 Deadlock in queue maintenance + node removal Change By: Jesse Glick Labels: deadlock pipeline queue threads Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50502) JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons
Title: Message Title Linda Springsteen commented on JENKINS-50502 Re: JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons I hope this can be fixed as we have contractual agreements to black duck scan all source code we deliver. Thanks, Linda Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50502) JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50502 Re: JEP-200: Refusing to marshal com.blackducksoftware.integration.hub.report.api.ReportData for security reasons OK, as JEP-200 maintainers we will assume that the ticket is going to be handled by the vendor. Please do not hesitate to ping me and Jesse Glick if any reviews/expertise are required > Want to thank you for bringing this to our attention, the list of compatibility issues does seem rather substantial, I assume you are referring to this: https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200 Yes. JEP-200 is pretty big. https://jenkins.io/blog/2018/03/15/jep-200-lts/ includes overview of the change from the User PoV. Regarding the plugin maintainer side, see the embedded presentation and links (unfortunately not really applicable to Gradle, manual testing steps are required). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50509) Docket Traceability plugin is affected by JEP-200
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50509 Docket Traceability plugin is affected by JEP-200 Change By: Jesse Glick Labels: JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50476) RestartableJenkinsRule should allow steps where Jenkins is not expected to start correctly
Title: Message Title Baptiste Mathus updated JENKINS-50476 Released in 2.36 Jenkins / JENKINS-50476 RestartableJenkinsRule should allow steps where Jenkins is not expected to start correctly Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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://grou
[JIRA] (JENKINS-50510) use repository settings dublicates branch listing
Title: Message Title sergey vanin created an issue Jenkins / JENKINS-50510 use repository settings dublicates branch listing Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2018-04-02 15:49 Priority: Minor Reporter: sergey vanin If I add 2 git repositories to my job, and then add two git parameter instances (to list the branches from each repo) and set the 'Use Repository' setting to regex to identify each repo, all branches from 2 repos are shown, while only one should. I am not using the multi scm plugin, I just added two repos to the job. This had been working before I upgraded to the latest version, I think because "continue" instead of break. Add Comment
[JIRA] (JENKINS-50511) BlueOcean quality audit for essentials
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-50511 BlueOcean quality audit for essentials Issue Type: Epic Assignee: Isa Vilacides Components: blueocean-plugin Created: 2018-04-02 15:52 Labels: essentials Priority: Minor Reporter: Isa Vilacides As part of the essentials effort we need to make sure that the plugins included in it have a quality level that allows us to contribute changes in a confident way. This epic contains all the tasks to audit and harden BO and its dependencies Add Comment
[JIRA] (JENKINS-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title
Raul Arabaolaza commented on JENKINS-50405
Re: runATH leads to deadlock of resource consumption for core PR builds
PR#34 should fix the issue, basically what I have done is change ensureInNode so it takes a comma-separated list of labels and checks that all of those labels are present individually in the current node, if not it allocates a new node with the labels joined by "&&". Caveats, is still unable to deal with complex labels, but that functionality is not needed to run on the current infra as you can simply enclose the entire runATH call in a node("docker&&highmem") as the Jenkinsfile for core does, whith the changes in #34 no node allocation will be done at all and no node will be blocked waiting for another one
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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-50512) BlueOcean code coverage analysis
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-50512 BlueOcean code coverage analysis Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-02 15:54 Priority: Minor Reporter: Isa Vilacides Acceptance criteria Analyse the code coverage reports and identify areas with poor coverage Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50512) BlueOcean code coverage analysis
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50512 BlueOcean code coverage analysis Change By: Isa Vilacides *Acceptance criteria* * Analyse the code coverage reports and identify areas with poor coverage * Create tickets to improve the coverage with the specific gaps to improve Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50513) BO P1 cases definition
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-50513 BO P1 cases definition Issue Type: Task Assignee: Karl Shultz Components: blueocean-plugin Created: 2018-04-02 15:55 Priority: Minor Reporter: Isa Vilacides Acceptance criteria For the BO suite of plugins define the list of P1 cases Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50514) BO ATH audit
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-50514 BO ATH audit Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-02 15:57 Priority: Minor Reporter: Isa Vilacides Acceptance criteria All the P1 cases are either covered by unit, integration or acceptance tests If there are missing acceptance tests, there are corresponding tickets created Add Comment
[JIRA] (JENKINS-50515) BO tests stability
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-50515 BO tests stability Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2018-04-02 15:57 Priority: Minor Reporter: Isa Vilacides Acceptance criteria We have a list of flakey tests (if any) We have a ticket to deflaky them Add Comment
[JIRA] (JENKINS-50480) UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.*
Title: Message Title Jesse Glick commented on JENKINS-50480 Re: UnsupportedOperationException: Refusing to marshal com.github.dockerjava.api.* BTW DockerComputerJNLPConnector$1#val$inspect sounds like it will trigger some anonymous inner class warning in new cores, too (and rightly). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run PCT in BO with its dependencies on a PR basis
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-50516 Add the run PCT step to run PCT in BO with its dependencies on a PR basis Issue Type: Task Assignee: Raul Arabaolaza Components: blueocean-plugin Created: 2018-04-02 16:00 Priority: Minor Reporter: Isa Vilacides Acceptance criteria Analyse first and second level dependencies of BO and decide which ones to include in BO's run Incorporate the runPCT step to run PCT with BO's dependencies on a PR basis Add Comment
[JIRA] (JENKINS-50511) BlueOcean quality audit for essentials
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50511 BlueOcean quality audit for essentials Change By: Isa Vilacides As part of the essentials effort we need to make sure that the plugins included in it have a quality level that allows us to contribute changes in a confident way. This epic contains all the tasks to audit and harden BO and its dependencies so that we can incorporate to this workflow https://docs.google.com/document/d/1LFLxuwbdChNFLNs9ETGZi4lDsq7QaCtcwcXSA24RrDs/edit#heading=h.d2wp7cux0ig5 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50283) TestInProgress Plugin broken by JEP-200
Title: Message Title Oleg Nenashev commented on JENKINS-50283 Re: TestInProgress Plugin broken by JEP-200 No response from the maintainers so far. I would recommend usage of https://plugins.jenkins.io/junit-realtime-test-reporter as a workaround. This plugin is in the better state && it does not require custom configurations to get it running in Jenkins Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50050) junit realtime plugin does not support test result sets
Title: Message Title Oleg Nenashev started work on JENKINS-50050 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50050) junit realtime plugin does not support test result sets
Title: Message Title Oleg Nenashev updated JENKINS-50050 Jenkins / JENKINS-50050 junit realtime plugin does not support test result sets Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50050) junit realtime plugin does not support test result sets
Title: Message Title Oleg Nenashev assigned an issue to Daniel Beland Jenkins / JENKINS-50050 junit realtime plugin does not support test result sets Change By: Oleg Nenashev Assignee: Daniel Beland Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run PCT in BO with its dependencies on a PR basis
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50516 Add the run PCT step to run PCT in BO with its dependencies on a PR basis Change By: Isa Vilacides *Acceptance criteria* * Analyse first and second level dependencies of BO and decide which ones to include in BO's run * Incorporate the runPCT step to run PCT with BO's dependencies on a PR basis and run the essentials plugins tests Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50516 Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials Change By: Isa Vilacides Labels: essentials Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50516 Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials Change By: Isa Vilacides Summary: Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50516 Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials Change By: Isa Vilacides *Acceptance criteria* * Incorporate the runPCT step to run PCT of the essentials plugins to run the PCT on an essentials PR basis Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49639) Sonar Gerrit plugin not posting comments when changedLinesOnly == true
Title: Message Title Tatiana Didik commented on JENKINS-49639 Re: Sonar Gerrit plugin not posting comments when changedLinesOnly == true v. 2.3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49561) FSSCM Does Not Update File Modifiers
Title: Message Title Jens Rogalli commented on JENKINS-49561 Re: FSSCM Does Not Update File Modifiers This is the Mergerequest which should resolve this issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49639) Sonar Gerrit plugin not posting comments when changedLinesOnly == true
Title: Message Title Tatiana Didik resolved as Fixed Jenkins / JENKINS-49639 Sonar Gerrit plugin not posting comments when changedLinesOnly == true Change By: Tatiana Didik Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50516 Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials Change By: Isa Vilacides *Acceptance criteria* * Analyse first and second level dependencies of BO and decide which ones to include in BO's run * Incorporate the runPCT step to run PCT and run of the essentials plugins tests Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run on a PR basis to essentials
Title: Message Title Isa Vilacides commented on JENKINS-50516 Re: Add the run PCT step to run on a PR basis to essentials This requires clarification of the flow by R. Tyler Croy and Raul Arabaolaza Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run on a PR basis to essentials
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50516 Add the run PCT step to run on a PR basis to essentials Change By: Isa Vilacides Summary: Add the run PCT step to run PCT in BO with its dependencies on a PR basis to essentials Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48170) BlackDuck Hub Plugin does not terminate scan-cli when job is cancelled
Title: Message Title Rob Petti commented on JENKINS-48170 Re: BlackDuck Hub Plugin does not terminate scan-cli when job is cancelled Yes, I've been discussing that with BlackDuck management. I would still appreciate if you supported the existing plugin, even if that means migrating it over to using Detect. There is no need to have two separate plugins for this. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49561) FSSCM Does Not Update File Modifiers
Title: Message Title Jens Rogalli edited a comment on JENKINS-49561 Re: FSSCM Does Not Update File Modifiers This is the [ Mergerequest |https://github.com/jenkinsci/filesystem_scm-plugin/pull/9] which should resolve this issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49561) FSSCM Does Not Update File Modifiers
Title: Message Title Jens Rogalli edited a comment on JENKINS-49561 Re: FSSCM Does Not Update File Modifiers This is the [Mergerequest|https://github.com/jenkinsci/filesystem_scm-plugin/pull/9] which should resolve this issue .Ernst can you check it out and test it? Thank you. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50512) BlueOcean unit and integration coverage analysis
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50512 BlueOcean unit and integration coverage analysis Change By: Isa Vilacides Summary: BlueOcean code unit and integration coverage analysis Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50512) BlueOcean code coverage analysis
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-50512 BlueOcean code coverage analysis Change By: Isa Vilacides *Acceptance criteria* * Analyse the code coverage reports and identify areas with poor coverage of unit and integration tests * Create tickets to improve the coverage with the specific gaps to improve Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50516) Add the run PCT step to run on a PR basis to essentials
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-50516 Add the run PCT step to run on a PR basis to essentials Change By: Raul Arabaolaza *Acceptance criteria* * Incorporate the runPCT step to run PCT of the essentials plugins to run the PCT on an essentials PR basis ** The PCT should be run for all plugins that form the essentials program and the jenkins core version used by essentials Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50517) git-plugin quality audit for essentials
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-50517 git-plugin quality audit for essentials Issue Type: Epic Assignee: Isa Vilacides Components: essentials Created: 2018-04-02 16:21 Priority: Minor Reporter: Isa Vilacides As part of the essentials effort we need to make sure that the plugins included in it have a quality level that allows us to contribute changes in a confident way. This epic contains all the tasks to audit and harden git and its dependencies so that we can incorporate to this workflow https://docs.google.com/document/d/1LFLxuwbdChNFLNs9ETGZi4lDsq7QaCtcwcXSA24RrDs/edit#heading=h.d2wp7cux0ig5 Add Comment
[JIRA] (JENKINS-50518) Use presigned URLs for upload
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50518 Use presigned URLs for upload Issue Type: New Feature Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2018-04-02 16:29 Priority: Critical Reporter: Jesse Glick Since we do not want to trust agent JVMs with S3 credentials, all BlobCallable implementations should be given a set of presigned URLs for PUT method and not use S3 code at all. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-
[JIRA] (JENKINS-50519) Preconfigure in Essentials
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50519 Preconfigure in Essentials Issue Type: New Feature Assignee: Jesse Glick Components: artifact-manager-s3-plugin Created: 2018-04-02 16:34 Labels: essentials Priority: Major Reporter: Jesse Glick This plugin should be preconfigured somehow TBD if included in Essentials running on AWS. Add Comment
[JIRA] (JENKINS-50520) Remove jClouds shading
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-50520 Remove jClouds shading Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50520) Remove jClouds shading
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50520 Remove jClouds shading Issue Type: Improvement Assignee: Jesse Glick Components: artifact-manager-s3-plugin Created: 2018-04-02 16:35 Priority: Minor Reporter: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" g
[JIRA] (JENKINS-50519) Preconfigure in Essentials
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-50519 Preconfigure in Essentials Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50521) Add a new field for custom Github context at the global Jenkins level
Title: Message Title Gennady Feldman created an issue Jenkins / JENKINS-50521 Add a new field for custom Github context at the global Jenkins level Issue Type: New Feature Assignee: Raul Arabaolaza Components: pipeline-githubnotify-step-plugin Created: 2018-04-02 16:55 Priority: Minor Reporter: Gennady Feldman Please provide a way to provide a custom github context at the Global Jenkins level. Right now if you run multiple Jenkins they conflict with each other and override the PR status among other things. Looks like context is already available as a parameter inside Jenkinsfile. This would be a way to customize the default value at the Jenkins level. Add Comment
[JIRA] (JENKINS-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-50507 withMaven must not trigger its own project Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50507) withMaven must not trigger its own project
Title: Message Title Cyrille Le Clerc commented on JENKINS-50507 Re: withMaven must not trigger its own project Is this a regression? Is WithMaven triggering the same branch or a different branch? > My pipeline has 2 OS specific stages: > Linux and Windows, where the windows stage requires an artifact built by Linux stage via withMaven. > This causes withMaven to trigger its very own pipeline I am surprised that calling twice withMaven in the same pipeline could cause this problem. I don't exclude the problem to be elsewhere. See code fragment below and "// Don't trigger myself". https://github.com/jenkinsci/pipeline-maven-plugin/blob/d68ce7bba62f6881ca1ada84ee1cf8d5a851f7a8/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/listeners/DownstreamPipelineTriggerRunListener.java#L62 ListdownstreamPipelines = GlobalPipelineMavenConfig.getDao().listDownstreamJobs(upstreamPipeline.getFullName(), upstreamBuild.getNumber()); // Don't trigger myself downstreamPipelines.remove(upstreamPipeline.getFullName()); ... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50522) New jobs not validating github webhook filters
Title: Message Title Byron Kim created an issue Jenkins / JENKINS-50522 New jobs not validating github webhook filters Issue Type: Bug Assignee: Kirill Merkushev Components: github-branch-source-plugin, github-plugin Created: 2018-04-02 17:21 Environment: Jenkins ver. 2.89.4 Github Branch Source Plugin: 2.3.3 Github Plugin: 1.29.0 Labels: scm plugin jenkins Priority: Major Reporter: Byron Kim We have a Github repo that can trigger multiple builds based on certain filters. The most obvious one is the branch and then some are filtered down based on the Included Regions filter (ie Jenkins is triggered based on which path files are committed to). As an example: App-AuthAPI App-LookupAPI App-DBAPI Each one is from the same repo however, App-DBAPI was added recently and is triggered no matter what happens (random branch is deleted, a commit to a completely different branch). I have a test build that I modified and that worked fine based on filters. When I created anything new, none of the filters are respected. I restarted Jenkins and the filters are fine for about 10 minutes before it goes back to triggering for every event in the repo. I've tested cloning projects, to recreating from scratch, to doing the most basic thing (ie random string branch that doesn't actual
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Jesse Glick commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification I do not see a clear use case for this. The example given in the issue description is artificial so that does not help give context. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50481) Unable to check updates for plugins
Title: Message Title Brian Pham updated an issue Jenkins / JENKINS-50481 Unable to check updates for plugins Change By: Brian Pham Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
