[JIRA] (JENKINS-14990) Allow to specify per-package thresholds
Title: Message Title Share Cheng assigned an issue to Share Cheng Jenkins / JENKINS-14990 Allow to specify per-package thresholds Change By: Share Cheng Assignee: Share Cheng 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-8958) Code coverage color scheme not suited for color blind users
Title: Message Title Share Cheng assigned an issue to Share Cheng Jenkins / JENKINS-8958 Code coverage color scheme not suited for color blind users Change By: Share Cheng Assignee: Share Cheng 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Share Cheng resolved as Fixed Jenkins / JENKINS-43866 Don't round up 99.x% coverage to 100% Change By: Share Cheng 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Share Cheng stopped work on JENKINS-43866 Change By: Share Cheng Status: In Progress Open 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-49820) 'Do not allow concurrent builds' in pipeline sometimes fails
Title: Message Title Mathias De Maré updated an issue Jenkins / JENKINS-49820 'Do not allow concurrent builds' in pipeline sometimes fails Change By: Mathias De Maré Priority: Minor 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43866 Re: Don't round up 99.x% coverage to 100% Code changed in jenkins User: ShenYu Zheng Path: src/main/java/hudson/plugins/cobertura/Ratio.java src/test/java/hudson/plugins/cobertura/RatioTest.java http://jenkins-ci.org/commit/cobertura-plugin/c612ade943ca91ea43eb2d07d02607ece8666245 Log: JENKINS-43866 Don't round up 99.x% coverage to 100% (#94) 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-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title ikedam closed an issue as Fixed 1.3.0 with this fix is released. It will be available in the update center in a day. Jenkins / JENKINS-49573 Matrix Configuration Parameter Plugin is affected by JEP-200 Change By: ikedam Status: Resolved Closed 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-49850) Run pre-release ATH against Jenkins Essentials bill-of-materials
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49850 Run pre-release ATH against Jenkins Essentials bill-of-materials Change By: Jesse Glick Summary: Run pre-release ATH against Jenkins Essentials bil bill -of-materials 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-49866) Automatically configure Docker Cloud if the docker.sock is available
Title: Message Title Jesse Glick commented on JENKINS-49866 Re: Automatically configure Docker Cloud if the docker.sock is available I thought there was agreement to move cloud preconfiguration into dedicated plugins selected according to “flavor”? 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-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title R. Tyler Croy commented on JENKINS-49892 Re: Evaluate options for collecting "method instrumentation" telemetry I've also taken a look at InspectIT which doesn't seem to really have a good server-side component and makes me worry about potential security implications using it across a wide-area network 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-49893) Declarative directive snippet generator
Title: Message Title Andrew Bayer commented on JENKINS-49893 Re: Declarative directive snippet generator Work in progress PR is up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/250 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-49893) Declarative directive snippet generator
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-49893 Declarative directive snippet generator Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-03-02 22:14 Priority: Minor Reporter: Andrew Bayer I've been asked a few times for a snippet generator specifically for Declarative's directives - while some of the contents can just be copy-pasted from the normal snippet generator, some are a bit confusing (i.e., you have to use the properties step to get a trigger, job property, or parameter, and then you have to extract just the relevant bit of the resulting snippet to copy into the directive) and others aren't in the snippet generator at all (like agent and when). So...let's write a Declarative directive snippet generator. =) Add Comment
[JIRA] (JENKINS-49893) Declarative directive snippet generator
Title: Message Title Andrew Bayer started work on JENKINS-49893 Change By: Andrew Bayer 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-44292) Jcloud GCP network error
Title: Message Title Fritz Elfert commented on JENKINS-44292 Re: Jcloud GCP network error Already working on upgrade to 2.1.0 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-49488) Document that all promotion conditions have to be met to start the promotion
Title: Message Title Rick Liu commented on JENKINS-49488 Re: Document that all promotion conditions have to be met to start the promotion ok I agree with you ~ In addition to document improvement, maybe add a new feature to choose AND or OR for promote conditions. 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-49488) Document that all promotion conditions have to be met to start the promotion
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 Document that all promotion conditions have to be met to start the promotion Change By: Rick Liu Issue Type: Improvement New Feature 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-17434) Allow to call parsers without jenkins (standalone)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-17434 Re: Allow to call parsers without jenkins (standalone) Code changed in jenkins User: Ulli Hafner Path: src/main/java/io/jenkins/plugins/analysis/warnings/AndroidLint.java src/main/java/io/jenkins/plugins/analysis/warnings/CodeNArc.java src/main/java/io/jenkins/plugins/analysis/warnings/CppCheck.java src/main/java/io/jenkins/plugins/analysis/warnings/DocFx.java src/main/java/io/jenkins/plugins/analysis/warnings/ErrorProne.java src/main/java/io/jenkins/plugins/analysis/warnings/Flake8.java src/main/java/io/jenkins/plugins/analysis/warnings/JsHint.java src/main/java/io/jenkins/plugins/analysis/warnings/KlocWork.java src/main/java/io/jenkins/plugins/analysis/warnings/MyPy.java src/main/java/io/jenkins/plugins/analysis/warnings/Pit.java src/main/java/io/jenkins/plugins/analysis/warnings/PyDocStyle.java src/main/java/io/jenkins/plugins/analysis/warnings/ResharperInspectCode.java src/main/java/io/jenkins/plugins/analysis/warnings/Xlc.java src/main/java/io/jenkins/plugins/analysis/warnings/XmlLint.java src/main/java/io/jenkins/plugins/analysis/warnings/ZptLint.java src/main/resources/io/jenkins/plugins/analysis/warnings/Messages.properties src/test/java/hudson/plugins/warnings/parser/ResharperInspectCodeAdapterTest.java src/test/java/hudson/plugins/warnings/parser/ResharperInspectCodeParserTest.java src/test/java/io/jenkins/plugins/analysis/warnings/ParsersITest.java src/test/resources/io/jenkins/plugins/analysis/warnings/android-lint.xml src/test/resources/io/jenkins/plugins/analysis/warnings/codeNarc.xml src/test/resources/io/jenkins/plugins/analysis/warnings/cppcheck.xml src/test/resources/io/jenkins/plugins/analysis/warnings/docfx.json src/test/resources/io/jenkins/plugins/analysis/warnings/error-prone.log src/test/resources/io/jenkins/plugins/analysis/warnings/flake8.txt src/test/resources/io/jenkins/plugins/analysis/warnings/jshint.xml src/test/resources/io/jenkins/plugins/analysis/warnings/klocwork.xml src/test/resources/io/jenkins/plugins/analysis/warnings/mypy.txt src/test/resources/io/jenkins/plugins/analysis/warnings/pit.xml src/test/resources/io/jenkins/plugins/analysis/warnings/pydocstyle.txt src/test/resources/io/jenkins/plugins/analysis/warnings/spotbugsXml.xml src/test/resources/io/jenkins/plugins/analysis/warnings/xmllint.txt src/test/resources/io/jenkins/plugins/analysis/warnings/zptlint.log http://jenkins-ci.org/commit/warnings-plugin/dcbd8e1b3b660ffa3764486557491849e77d63d9 Log: Let all parsers not depend on Jenkins anymore. Integrated all parsers into new module analysis-model. Added adapter classes for parsers of violations-lib. [FIXED JENKINS-17434] [FIXED JENKINS-40439] Compare: https://github.com/jenkinsci/warnings-plugin/compare/3f29bdbcfac9...dcbd8e1b3b66
[JIRA] (JENKINS-40439) Move parsers into external library
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40439 Re: Move parsers into external library Code changed in jenkins User: Ulli Hafner Path: src/main/java/io/jenkins/plugins/analysis/warnings/AndroidLint.java src/main/java/io/jenkins/plugins/analysis/warnings/CodeNArc.java src/main/java/io/jenkins/plugins/analysis/warnings/CppCheck.java src/main/java/io/jenkins/plugins/analysis/warnings/DocFx.java src/main/java/io/jenkins/plugins/analysis/warnings/ErrorProne.java src/main/java/io/jenkins/plugins/analysis/warnings/Flake8.java src/main/java/io/jenkins/plugins/analysis/warnings/JsHint.java src/main/java/io/jenkins/plugins/analysis/warnings/KlocWork.java src/main/java/io/jenkins/plugins/analysis/warnings/MyPy.java src/main/java/io/jenkins/plugins/analysis/warnings/Pit.java src/main/java/io/jenkins/plugins/analysis/warnings/PyDocStyle.java src/main/java/io/jenkins/plugins/analysis/warnings/ResharperInspectCode.java src/main/java/io/jenkins/plugins/analysis/warnings/Xlc.java src/main/java/io/jenkins/plugins/analysis/warnings/XmlLint.java src/main/java/io/jenkins/plugins/analysis/warnings/ZptLint.java src/main/resources/io/jenkins/plugins/analysis/warnings/Messages.properties src/test/java/hudson/plugins/warnings/parser/ResharperInspectCodeAdapterTest.java src/test/java/hudson/plugins/warnings/parser/ResharperInspectCodeParserTest.java src/test/java/io/jenkins/plugins/analysis/warnings/ParsersITest.java src/test/resources/io/jenkins/plugins/analysis/warnings/android-lint.xml src/test/resources/io/jenkins/plugins/analysis/warnings/codeNarc.xml src/test/resources/io/jenkins/plugins/analysis/warnings/cppcheck.xml src/test/resources/io/jenkins/plugins/analysis/warnings/docfx.json src/test/resources/io/jenkins/plugins/analysis/warnings/error-prone.log src/test/resources/io/jenkins/plugins/analysis/warnings/flake8.txt src/test/resources/io/jenkins/plugins/analysis/warnings/jshint.xml src/test/resources/io/jenkins/plugins/analysis/warnings/klocwork.xml src/test/resources/io/jenkins/plugins/analysis/warnings/mypy.txt src/test/resources/io/jenkins/plugins/analysis/warnings/pit.xml src/test/resources/io/jenkins/plugins/analysis/warnings/pydocstyle.txt src/test/resources/io/jenkins/plugins/analysis/warnings/spotbugsXml.xml src/test/resources/io/jenkins/plugins/analysis/warnings/xmllint.txt src/test/resources/io/jenkins/plugins/analysis/warnings/zptlint.log http://jenkins-ci.org/commit/warnings-plugin/dcbd8e1b3b660ffa3764486557491849e77d63d9 Log: Let all parsers not depend on Jenkins anymore. Integrated all parsers into new module analysis-model. Added adapter classes for parsers of violations-lib. [FIXED JENKINS-17434] [FIXED JENKINS-40439] Compare: https://github.com/jenkinsci/warnings-plugin/compare/3f29bdbcfac9...dcbd8e1b3b66
[JIRA] (JENKINS-40439) Move parsers into external library
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40439 Re: Move parsers into external library Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/edu/hm/hafner/analysis/parser/ResharperInspectCodeParser.java src/main/java/edu/hm/hafner/analysis/parser/violations/AbstractViolationAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/AndroidLintParserAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/CodeNarcAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/CppCheckAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/DocFxAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/ErrorProneAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/Flake8Adapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/JsHintAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/KlocWorkAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/MyPyAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/PitAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/PyDocStyleAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/ResharperInspectCodeAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/XmlLintAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/ZptLintAdapter.java src/test/java/edu/hm/hafner/analysis/parser/ResharperInspectCodeParserTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/AndroidLintParserAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/CodeNarcAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/CppCheckAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/DocFxAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/ErrorProneAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/Flake8AdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/JsHintAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/KlocWorkAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/MyPyAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/PitAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/PyDocStyleAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/ResharperInspectCodeAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/XmlLintAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/ZptLintAdapterTest.java src/test/resources/edu/hm/hafner/analysis/parser/ResharperInspectCode.xml src/test/resources/edu/hm/hafner/analysis/parser/codenarc/CodeNarcReport2.xml src/test/resources/edu/hm/hafner/analysis/parser/codenarc/CodeNarcXmlReport.xml src/test/resources/edu/hm/hafner/analysis/parser/findbugs/spotbugsXml.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/ResharperInspectCode.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/android-lint.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/codeNarc.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/cppcheck.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/docfx.json src/test/resources/edu/hm/hafner/analysis/parser/violations/error-prone.log src/test/resources/edu/hm/hafner/analysis/parser/violations/flake8.txt src/test/resources/edu/hm/hafner/analysis/parser/violations/jshint.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/klocwork.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/mypy.txt src/test/resources/edu/hm/hafner/analysis/p
[JIRA] (JENKINS-49803) Connection with Testlink-Problem
Title: Message Title Douglas Velho updated an issue Jenkins / JENKINS-49803 Connection with Testlink-Problem Change By: Douglas Velho Environment: Windows/64 bits- Jenkins ver. 2.89.4 TestLink 1.9.16/ TestLink Plugin 3.13jdk1.8.0_161-jre1.8.0_161Chrome. 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-17434) Allow to call parsers without jenkins (standalone)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-17434 Re: Allow to call parsers without jenkins (standalone) Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/edu/hm/hafner/analysis/parser/ResharperInspectCodeParser.java src/main/java/edu/hm/hafner/analysis/parser/violations/AbstractViolationAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/AndroidLintParserAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/CodeNarcAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/CppCheckAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/DocFxAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/ErrorProneAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/Flake8Adapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/JsHintAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/KlocWorkAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/MyPyAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/PitAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/PyDocStyleAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/ResharperInspectCodeAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/XmlLintAdapter.java src/main/java/edu/hm/hafner/analysis/parser/violations/ZptLintAdapter.java src/test/java/edu/hm/hafner/analysis/parser/ResharperInspectCodeParserTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/AndroidLintParserAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/CodeNarcAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/CppCheckAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/DocFxAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/ErrorProneAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/Flake8AdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/JsHintAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/KlocWorkAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/MyPyAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/PitAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/PyDocStyleAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/ResharperInspectCodeAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/XmlLintAdapterTest.java src/test/java/edu/hm/hafner/analysis/parser/violations/ZptLintAdapterTest.java src/test/resources/edu/hm/hafner/analysis/parser/ResharperInspectCode.xml src/test/resources/edu/hm/hafner/analysis/parser/codenarc/CodeNarcReport2.xml src/test/resources/edu/hm/hafner/analysis/parser/codenarc/CodeNarcXmlReport.xml src/test/resources/edu/hm/hafner/analysis/parser/findbugs/spotbugsXml.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/ResharperInspectCode.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/android-lint.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/codeNarc.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/cppcheck.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/docfx.json src/test/resources/edu/hm/hafner/analysis/parser/violations/error-prone.log src/test/resources/edu/hm/hafner/analysis/parser/violations/flake8.txt src/test/resources/edu/hm/hafner/analysis/parser/violations/jshint.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/klocwork.xml src/test/resources/edu/hm/hafner/analysis/parser/violations/mypy.txt src/test/resources/edu/hm/h
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49892 Evaluate options for collecting "method instrumentation" telemetry Change By: R. Tyler Croy To support some of the work that [~csanchez] is doing, we will need to find some way of selectively collecting method instrumentation telemetry. This will help us identify stale and unused code paths.Some options might include using off-the-shelf tools such as: * New Relic * Dynatrace * AppDynamics * Datadog APM * ??? Or rolling some combination of our own? Not sure. 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-49803) Connection with Testlink-Problem
Title: Message Title Douglas Velho commented on JENKINS-49803 Re: Connection with Testlink-Problem There is an attachment when i try to 'build now' with the configuration on this link https://www.ranorex.com/blog/integrating-ranorex-automation-in-jenkins-continuous-integration-process/ 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-49803) Connection with Testlink-Problem
Title: Message Title Douglas Velho updated an issue Jenkins / JENKINS-49803 Connection with Testlink-Problem Change By: Douglas Velho Attachment: ao_tentar_gerar_build.JPG 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-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title R. Tyler Croy started work on JENKINS-49892 Change By: R. Tyler Croy 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-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49892 Evaluate options for collecting "method instrumentation" telemetry Change By: R. Tyler Croy To support some of the work that [~csanchez] is doing, we will need to find some way of selectively collecting method instrumentation telemetry. This will help us identify stale and unused code paths.Some options might include using off-the-shelf tools such as: * New Relic * AppDynamics * Datadog APM * ??? Or rolling some combination of our own? Not sure. 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-49186) non exportable objects exported causing errors in api/xml?depth=2
Title: Message Title Jimmy Praet commented on JENKINS-49186 Re: non exportable objects exported causing errors in api/xml?depth=2 I am also running into this issue with the JSON API. org.kohsuke.stapler.export.NotExportableException: class jenkins.scm.api.SCMHeadOrigin$Default doesn't have @ExportedBean 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-46642) Logs can grow without bound when using ansiColor plugin
Title: Message Title Jesse Glick commented on JENKINS-46642 Re: Logs can grow without bound when using ansiColor plugin Or might be a dupe of JENKINS-37575, not sure offhand. 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-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49892 Evaluate options for collecting "method instrumentation" telemetry Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 18:38 Priority: Minor Reporter: R. Tyler Croy To support some of the work that Carlos Sanchez is doing, we will need to find some way of selectively collecting method instrumentation telemetry. This will help us identify stale and unused code paths. Some options might include using off-the-shelf tools such as: New Relic Datadog APM ??? Or rolling some combination of our own? Not sure. Add Comment
[JIRA] (JENKINS-49737) Extras Executable WAR should warn everybody that Java 9 is not supported
Title: Message Title Amit Magar commented on JENKINS-49737 Re: Extras Executable WAR should warn everybody that Java 9 is not supported Hi Oleg, Thanks for your input. I made the requested changes. Amit 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-48862) softlinks in build for lastSuccessful and lastStable failing
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-48862
Re: softlinks in build for lastSuccessful and lastStable failing
This sounds like a duplicate of JENKINS-21330 (I do not think it is related to my recent changes). My guess is that {{/var/jenkins_home/jobs/Redmine3-DB-Copy/lastSuccessful}} and {{/var/jenkins_home/jobs/Redmine3-DB-Copy/lastStable}} are actual directories instead of symlinks (maybe because of a faulty backup/restore that converted the symlinks into directories).A workaround would be to delete those directories manually so that the next build can create the symlinks correctly.We could prevent the issue by using `Util.deleteRecursive` instead of `File.deleteIfExists` [here|https://github.com/jenkinsci/jenkins/blob/852ecdc5f2a7802fa74f425bd17ba028f787b2c1/core/src/main/java/hudson/Util.java#L1334] to prevent this kind of issue , but maybe that is too risky in case someone cares about the contents of the directory.
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-49757) Git plugin calls fetch twice for a single job
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-49757 Git plugin calls fetch twice for a single job Change By: Mark Waite Summary: Git clone plugin calls fetch twice for a single job 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-49757) Git clone calls fetch twice for a single job
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-49757 Git clone calls fetch twice for a single job Change By: Mark Waite Summary: Git clone triggers calls fetch twice for a single job 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-48862) softlinks in build for lastSuccessful and lastStable failing
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-48862
Re: softlinks in build for lastSuccessful and lastStable failing
This sounds like a duplicate of JENKINS-21330 (I do not think it is related to my recent changes) . My guess is that {{/var/jenkins_home/jobs/Redmine3-DB-Copy/lastSuccessful}} and {{/var/jenkins_home/jobs/Redmine3-DB-Copy/lastStable}} are actual directories instead of symlinks (maybe because of a faulty backup/restore that converted the symlinks into directories).A workaround would be to delete those directories manually so that the next build can create the symlinks correctly.We could prevent the issue by using `Util.deleteRecursive` instead of `File.deleteIfExists` [here|https://github.com/jenkinsci/jenkins/blob/852ecdc5f2a7802fa74f425bd17ba028f787b2c1/core/src/main/java/hudson/Util.java#L1334] to prevent this kind of issue, but maybe that is too risky in case someone cares about the contents of the directory.
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-49757) Git clone triggers fetch twice
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-49757 Git clone triggers fetch twice Change By: Mark Waite Priority: Major Minor 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-49840) When Wipe out repository & force clone is selected, single branch checkout does not happen
Title: Message Title
Mark Waite edited a comment on JENKINS-49840
Re: When Wipe out repository & force clone is selected, single branch checkout does not happen
Please provide more details about the use case you're describing. Based on your description, I would guess that you:# Create a Freestyle job# Add Git as the SCM for that Freestyle job with a repository (like https://github.com/jenkinsci/git-client-plugin)# Set the "Branches to build" using a non-default branch (like '1.21.x')# Use the "Advanced" button to add a narrower refspec ( , like : {noformat}+refs/heads/1.21.x:refs/remotes/origin/1.21.x{noformat} ) # Add "Wipe out repository & force clone" as an "Additional Behaviours"# Run the job# Review the refspec used in the job, and see that the initial clone did not honor the configured refspec. Instead, the first fetch uses {noformat}git fetch --tags --progress https://github.com/jenkinsci/git-client-plugin +refs/heads/*:refs/remotes/origin/*{noformat}That is the expected behavior. The git plugin initial defaults ignored the refspec on first clone. Many users unknowingly depended on that default behavior of the git plugin.Rather than break those users, the git plugin added a configuration option to "Honor refspec on initial clone" to the "Advanced clone options". Refer to JENKINS-28516, JENKINS-31393, JENKINS-33140, JENKINS-35162, JENKINS-36507, and JENKINS-36563.If that is not the problem you're describing, please provide more details.
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 f
[JIRA] (JENKINS-49840) When Wipe out repository & force clone is selected, single branch checkout does not happen
Title: Message Title Mark Waite commented on JENKINS-49840 Re: When Wipe out repository & force clone is selected, single branch checkout does not happen Please provide more details about the use case you're describing. Based on your description, I would guess that you: Create a Freestyle job Add Git as the SCM for that Freestyle job with a repository (like https://github.com/jenkinsci/git-client-plugin) Set the "Branches to build" using a non-default branch (like '1.21.x') Use the "Advanced" button to add a narrower refspec (like +refs/heads/1.21.x:refs/remotes/origin/1.21.x ) Add "Wipe out repository & force clone" as an "Additional Behaviours" Run the job Review the refspec used in the job, and see that the initial clone did not honor the configured refspec. Instead, the first fetch uses git fetch --tags --progress https://github.com/jenkinsci/git-client-plugin +refs/heads/*:refs/remotes/origin/* That is the expected behavior. The git plugin initial defaults ignored the refspec on first clone. Many users unknowingly depended on that default behavior of the git plugin. Rather than break those users, the git plugin added a configuration option to "Honor refspec on initial clone" to the "Advanced clone options". Refer to JENKINS-28516, JENKINS-31393, JENKINS-33140, JENKINS-35162, JENKINS-36507, and JENKINS-36563. If that is not the problem you're describing, please provide more details. Add Comment
[JIRA] (JENKINS-48862) softlinks in build for lastSuccessful and lastStable failing
Title: Message Title Devin Nusbaum commented on JENKINS-48862 Re: softlinks in build for lastSuccessful and lastStable failing This sounds like a duplicate of JENKINS-21330. My guess is that /var/jenkins_home/jobs/Redmine3-DB-Copy/lastSuccessful and /var/jenkins_home/jobs/Redmine3-DB-Copy/lastStable are actual directories instead of symlinks (maybe because of a backup/restore that converted the symlinks into directories). A workaround would be to delete those directories manually so that the next build can create the symlinks correctly. We could prevent the issue by using `Util.deleteRecursive` instead of `File.deleteIfExists` here to prevent this kind of issue, but maybe that is too risky in case someone cares about the contents of the directory. 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-48862) softlinks in build for lastSuccessful and lastStable failing
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-48862
Re: softlinks in build for lastSuccessful and lastStable failing
This sounds like a duplicate of JENKINS-21330. My guess is that {{/var/jenkins_home/jobs/Redmine3-DB-Copy/lastSuccessful}} and {{/var/jenkins_home/jobs/Redmine3-DB-Copy/lastStable}} are actual directories instead of symlinks (maybe because of a faulty backup/restore that converted the symlinks into directories).A workaround would be to delete those directories manually so that the next build can create the symlinks correctly.We could prevent the issue by using `Util.deleteRecursive` instead of `File.deleteIfExists` [here|https://github.com/jenkinsci/jenkins/blob/852ecdc5f2a7802fa74f425bd17ba028f787b2c1/core/src/main/java/hudson/Util.java#L1334] to prevent this kind of issue, but maybe that is too risky in case someone cares about the contents of the directory.
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-27341) Shallow clone fetches all tags and ignores refspec
Title: Message Title Mark Waite resolved as Fixed Fixed in git plugin that added support for honoring refspec on initial clone. Jenkins / JENKINS-27341 Shallow clone fetches all tags and ignores refspec Change By: Mark Waite 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://gro
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Oleg Nenashev updated JENKINS-39674 Jenkins / JENKINS-39674 Build name file path file gets locked by Jenkins process 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Oleg Nenashev started work on JENKINS-39674 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-39674 Build name file path file gets locked by Jenkins process Change By: Oleg Nenashev Assignee: Lev Mishin 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-49840) When Wipe out repository & force clone is selected, single branch checkout does not happen
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49840 When Wipe out repository & force clone is selected, single branch checkout does not happen Change By: Mark Waite Assignee: Mark Waite 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-49269) Upgrade Jenkins core flow to run the ath test defined in 49263
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49269 Upgrade Jenkins core flow to run the ath test defined in 49263 Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49524) JenkinsDatabaseSecurityRealmTest#login_and_logout is flaky
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49524 JenkinsDatabaseSecurityRealmTest#login_and_logout is flaky Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-48852) Build name file cannot immediately be deleted from workspace after build
Title: Message Title Oleg Nenashev resolved as Duplicate Jenkins / JENKINS-48852 Build name file cannot immediately be deleted from workspace after build Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate 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-49265) Investigate incorporating the Metrics plugin into Essentials for metrics/instrumentation
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49265 Investigate incorporating the Metrics plugin into Essentials for metrics/instrumentation Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-48862) softlinks in build for lastSuccessful and lastStable failing
Title: Message Title Oleg Nenashev commented on JENKINS-48862 Re: softlinks in build for lastSuccessful and lastStable failing Sounds like a core bug. CC Devin Nusbaum who was working on the symlinks in Jenkins recently 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-48862) softlinks in build for lastSuccessful and lastStable failing
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-48862 softlinks in build for lastSuccessful and lastStable failing Change By: Oleg Nenashev Component/s: core 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Oleg Nenashev commented on JENKINS-48900 Re: Show "Full Name" on Assign Roles page? It would make sense to do that. Seems to be a quick win 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Oleg Nenashev Labels: newbie-friendly 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Jeff Pearce commented on JENKINS-43866 Re: Don't round up 99.x% coverage to 100% 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-49008) java.nio.file.AccessDeniedException: /var/lib/jenkins/config.xml
Title: Message Title Oleg Nenashev resolved as Not A Defect No response from the reporter. Closing as "Not a defect" Jenkins / JENKINS-49008 java.nio.file.AccessDeniedException: /var/lib/jenkins/config.xml Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect 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, visi
[JIRA] (JENKINS-49840) When Wipe out repository & force clone is selected, single branch checkout does not happen
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49840 When Wipe out repository & force clone is selected, single branch checkout does not happen Change By: Oleg Nenashev Component/s: git-plugin Component/s: core 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-49836) Cannot view Console logs
Title: Message Title Oleg Nenashev commented on JENKINS-49836 Re: Cannot view Console logs It seems that the data on the disk has been corrupted somehow. Would it be possible to get a sample of the corrupted file? 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-49840) When Wipe out repository & force clone is selected, single branch checkout does not happen
Title: Message Title Oleg Nenashev assigned an issue to Mark Waite Jenkins / JENKINS-49840 When Wipe out repository & force clone is selected, single branch checkout does not happen Change By: Oleg Nenashev Assignee: Mark Waite 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-49838) Failed to download from http://updates.jenkins-ci.org/download/war/2.109/jenkins.war (redirected to: http://ftp-chi.osuosl.org/pub/jenkins/war/2.109/jenkins.war).
Title: Message Title Oleg Nenashev commented on JENKINS-49838 Re: Failed to download from http://updates.jenkins-ci.org/download/war/2.109/jenkins.war (redirected to: http://ftp-chi.osuosl.org/pub/jenkins/war/2.109/jenkins.war). I cannot say anything without an error code. Jenkins WAR is available on the osuosl mirror 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Pieter-Jan Busschaert commented on JENKINS-43866 Re: Don't round up 99.x% coverage to 100% Probably should be 99 <= pct < 100 ? (100% should stay 100%) 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-49737) Extras Executable WAR should warn everybody that Java 9 is not supported
Title: Message Title Oleg Nenashev started work on JENKINS-49737 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-49737) Extras Executable WAR should warn everybody that Java 9 is not supported
Title: Message Title Oleg Nenashev updated JENKINS-49737 Jenkins / JENKINS-49737 Extras Executable WAR should warn everybody that Java 9 is not supported 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Jeff Pearce edited a comment on JENKINS-43866 Re: Don't round up 99.x% coverage to 100% Sorry - that was a typo. I meant did indeed mean to type round 99 < pct <= 100 to 99. 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Jeff Pearce commented on JENKINS-43866 Re: Don't round up 99.x% coverage to 100% Sorry - that was a typo. I meant round 99 < pct <= 100 to 99. 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-43866) Don't round up 99.x% coverage to 100%
Title: Message Title Pieter-Jan Busschaert commented on JENKINS-43866 Re: Don't round up 99.x% coverage to 100% Thanks for looking into this, but your proposal is worse than the current problem I think it would be OK if you round everything between 99% and 100% down to 99%, but certainly don't change 98, 97... to 90% 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-49857) Provide easy single-sign-on by default with GitHub integration
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49857 Provide easy single-sign-on by default with GitHub integration Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49883) Pre-bake an Examples folder with functional tutorial Pipelines
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49883 Pre-bake an Examples folder with functional tutorial Pipelines Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49891) pitmutation report barfs at "Kill ratio is NaN% (0 0)" with pitest 1.3.2
Title: Message Title Martin Schröder created an issue Jenkins / JENKINS-49891 pitmutation report barfs at "Kill ratio is NaN% (0 0)" with pitest 1.3.2 Issue Type: Bug Assignee: Benjamin Sproule Attachments: index.html, mutations.xml Components: pitmutation-plugin Created: 2018-03-02 15:54 Environment: jenkins is 2.109, pitmuation plugin is 1.0-16, pitest is 1.3.2 Priority: Minor Reporter: Martin Schröder When I set the used pitest version to 1.3.2, the resulting xml files can not be parsed by the plugin; it allways breaks the build with "Kill ratio is NaN% (0 0)". The generated reports are attached. Add Comment
[JIRA] (JENKINS-49869) Disable non-Pipeline/Folder items in the new item view
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49869 Disable non-Pipeline/Folder items in the new item view Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49808) Define user telemetry/analytics requirements
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49808 Define user telemetry/analytics requirements Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49868) Disable tool installers entirely
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49868 Disable tool installers entirely Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49863) Include a Pipeline Shared Library to provide additional useful (community managed) Pipeline steps
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49863 Include a Pipeline Shared Library to provide additional useful (community managed) Pipeline steps Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49449) Author basic smoke tests of the jenkins/evergreen container
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49449 Author basic smoke tests of the jenkins/evergreen container Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49875) Provide a GitHub webhooks relay
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49875 Provide a GitHub webhooks relay Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49856) Support server-side manipulated feature flagging
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49856 Support server-side manipulated feature flagging Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 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-49864) Include the Docker CLI binaries in the jenkins/evergreen image by default
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49864 Include the Docker CLI binaries in the jenkins/evergreen image by default Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 2 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-49866) Automatically configure Docker Cloud if the docker.sock is available
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49866 Automatically configure Docker Cloud if the docker.sock is available Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 1 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-49860) Auto-configure AWS agent provisioning when the instance has IAM credentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49860 Auto-configure AWS agent provisioning when the instance has IAM credentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 2 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-49861) Disable master executors by default
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49861 Disable master executors by default Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 2 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-49860) Auto-configure AWS agent provisioning when the instance has IAM credentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49860 Auto-configure AWS agent provisioning when the instance has IAM credentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 2 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-49860) Auto-configure AWS agent provisioning when the instance has IAM credentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49860 Auto-configure AWS agent provisioning when the instance has IAM credentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 1 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-49853) Provide a cloud-friendly installation for AWS
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49853 Provide a cloud-friendly installation for AWS Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 1 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-49866) Automatically configure Docker Cloud if the docker.sock is available
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49866 Automatically configure Docker Cloud if the docker.sock is available Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 2 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-49861) Disable master executors by default
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49861 Disable master executors by default Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 1 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-49853) Provide a cloud-friendly installation for AWS
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49853 Provide a cloud-friendly installation for AWS Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 2 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-49864) Include the Docker CLI binaries in the jenkins/evergreen image by default
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49864 Include the Docker CLI binaries in the jenkins/evergreen image by default Change By: R. Tyler Croy Sprint: Essentials - Milestone 2 1 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-49861) Disable master executors by default
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49861 Disable master executors by default Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49866) Automatically configure Docker Cloud if the docker.sock is available
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49866 Automatically configure Docker Cloud if the docker.sock is available Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49853) Provide a cloud-friendly installation for AWS
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49853 Provide a cloud-friendly installation for AWS Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49860) Auto-configure AWS agent provisioning when the instance has IAM credentials
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49860 Auto-configure AWS agent provisioning when the instance has IAM credentials Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49864) Include the Docker CLI binaries in the jenkins/evergreen image by default
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49864 Include the Docker CLI binaries in the jenkins/evergreen image by default Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-49852 Collect Pipeline usage telemetry Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 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-49890) Allow inline script approvals for admins when looking at Pipeline logs
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49890 Allow inline script approvals for admins when looking at Pipeline logs Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:47 Priority: Minor Reporter: R. Tyler Croy Rather than throwing a big ugly exception, the Pipeline log in the Classic UI should allow admins to inline approve scripts and retrigger the Pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1
[JIRA] (JENKINS-49889) Provide outbound webhooks from Jenkins to integrate into other services
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49889 Provide outbound webhooks from Jenkins to integrate into other services Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:46 Priority: Minor Reporter: R. Tyler Croy Jenkins Essentials should behave nicely in a connected internet of stuff. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49886) Add simply log analysis code to detect common exceptions
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49886 Add simply log analysis code to detect common exceptions Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:45 Priority: Minor Reporter: R. Tyler Croy Just a wild idea of a series of regexes which map to a document on jenkins.io "This is a commonly broken thing, read this article to learn more" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49888) Detect whether the instance is on the public internet and suggest security practices
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49888 Detect whether the instance is on the public internet and suggest security practices Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:45 Priority: Minor Reporter: R. Tyler Croy Prevent pwnage Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49887) Highlight "essential" plugins on plugins.jenkins.io
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49887 Highlight "essential" plugins on plugins.jenkins.io Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:45 Priority: Minor Reporter: R. Tyler Croy 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 "Jenk
[JIRA] (JENKINS-49885) Embed a /doc site
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49885 Embed a /doc site Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:44 Priority: Minor Reporter: R. Tyler Croy Perhaps embedding the jenkins.io/doc/book content in the application directly in some way. This could be just a link, or a full embed, not sure Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49884) Avoid common configuration errors in "essential" plugins
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49884 Avoid common configuration errors in "essential" plugins Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:43 Priority: Minor Reporter: R. Tyler Croy This is super vague, but there's some ambiguous text and fields in lots of key plugins, we should provide upstream patches for those. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49883) Pre-bake an Examples folder with functional tutorial Pipelines
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-49883 Pre-bake an Examples folder with functional tutorial Pipelines Issue Type: Story Assignee: R. Tyler Croy Components: essentials Created: 2018-03-02 15:43 Priority: Minor Reporter: R. Tyler Croy These should all be easily copied and pasted by an end user, e.g. somebody can take a conventional "nodejs Pipeline" and fork it, then tweak it themselves. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c
