[JIRA] (JENKINS-37356) OWASP checker can't update on slave
Title: Message Title Steve Springett closed an issue as Fixed Closing issue Jenkins / JENKINS-37356 OWASP checker can't update on slave Change By: Steve Springett Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title Steve Springett commented on JENKINS-37478 Re: OWASP does not release files from scan Chad Schwieterman A fix should be available in the next release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37478) OWASP does not release files from scan
Title: Message Title Steve Springett commented on JENKINS-37478 Re: OWASP does not release files from scan Email from Jeremy Long: I was finally able to track down why files were not able to be deleted. The method used to generate the SHA1 and MD5 Checksums was creating a lock on files extracted from archives (the unreleased resource was present until GC, but deletion of files was being attempted prior to GC so files could not be deleted). This was resolved in a patch earlier today: https://github.com/jeremylong/DependencyCheck/commit/7fc2be6a0a805c7d7d923509f7cfeb9b7de9d2f7#diff-bf75b3a9add9ae32e03f642a675c7f63 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36450) Unable to inject HP Application AUtomation Tools properties with attributes/environment variables
Title: Message Title Roy Lu commented on JENKINS-36450 Re: Unable to inject HP Application AUtomation Tools properties with attributes/environment variables Hi Alex, Thank you for you suggestion. We're working on supporting credentials. Maybe in next release you'll see the credential chooser instead of username/password fields. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37193) inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x
Title: Message Title Andrew Sumner commented on JENKINS-37193 Re: inedo-buildmaster-plugin is Not compatible with BuildMaster 5.x Thanks for the report, I'm looking into this now Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37972) EZ-Templates support Multijob plugin
Title: Message Title Ebrahim Moshaya commented on JENKINS-37972 Re: EZ-Templates support Multijob plugin This will be a great plugin to support. You'd need to allow the jobs implementing the multijob template to retain local multijob phases. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38808) Jenkins fails to parse Maven poms with version ranges in parent elements
Title: Message Title Mark Lehky closed an issue as Duplicate should have done better search Jenkins / JENKINS-38808 Jenkins fails to parse Maven poms with version ranges in parent elements Change By: Mark Lehky Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-23846) Jenkins Maven support doesn't handle version ranges in parent definitions
Title: Message Title Mark Lehky commented on JENKINS-23846 Re: Jenkins Maven support doesn't handle version ranges in parent definitions I can replicate this using latest Jenkins. See JENKINS-38808 for additional info. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38808) Jenkins fails to parse Maven poms with version ranges in parent elements
Title: Message Title Mark Lehky commented on JENKINS-38808 Re: Jenkins fails to parse Maven poms with version ranges in parent elements Just tried the same thing from latest Jenkins ver. 2.19.1, running in Docker. Still same problem, although the error is little more verbose: Parsing POMs Failed to transfer Could not find artifact ::pom:(1.0,99.0) in central (http://repo.maven.apache.org/maven2) ERROR: Failed to parse POMs org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact ::pom:(1.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1301) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1098) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:960) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:679) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1720) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38808) Jenkins fails to parse Maven poms with version ranges in parent elements
Title: Message Title
Mark Lehky updated an issue
Jenkins / JENKINS-38808
Jenkins fails to parse Maven poms with version ranges in parent elements
Change By:
Mark Lehky
I am running Jenkins 1.651.3, Linux, OracleJava8.From within Jenkins I installed Maven 3.3.9 "from Apache".In our poms, we are using version ranges in parent elements, as described [here|https://maven.apache.org/docs/3.2.2/release-notes.html#Support_version_ranges_in_parent_elements_MNG-2199]. This all builds fine from command line.In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine.If in the main build phase I specify target "clean install", the build fails with:{ code noformat }Parsing POMsFailed to transfer Could not find artifact ::pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2)ERROR: Failed to parse POMsorg.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-resolvable parent POM: Could not find artifact ::pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10{ code noformat }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38808) Jenkins fails to parse Maven poms with version ranges in parent elements
Title: Message Title
Mark Lehky updated an issue
Jenkins / JENKINS-38808
Jenkins fails to parse Maven poms with version ranges in parent elements
Change By:
Mark Lehky
I am running Jenkins 1.651.3, Linux, OracleJava8.From within Jenkins I installed Maven 3.3.9 "from Apache".In our poms, we are using version ranges in parent elements, as described [here | https://maven.apache.org/docs/3.2.2/release-notes.html#Support_version_ranges_in_parent_elements_MNG-2199]. This all builds fine from command line. In my Maven build project, if I specify a Pre-Build step that uses the installed Maven, with target "clean install", everything builds fine.If in the main build phase I specify target "clean install", the build fails with:{code}Parsing POMsFailed to transfer Could not find artifact ::pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2)ERROR: Failed to parse POMsorg.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:[FATAL] Non-resolvable parent POM: Could not find artifact ::pom:(1.3.0,99.0) in central (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 10, column 10{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Now able to start new pipeline builds from view and to configure the number of pipeline instances per pipeline. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Ebrahim Moshaya commented on JENKINS-38755 Re: Merge Choice Parameter values more intelligently I meant I don't I want the default to be rows 2 reordering_is_retained and 4 child_additions_are_retained Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Ebrahim Moshaya edited a comment on JENKINS-38755 Re: Merge Choice Parameter values more intelligently I meant I don't I want the default to be rows 2 reordering_is_retained and 4 child_additions_are_retained Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Marc Carter commented on JENKINS-38755 Re: Merge Choice Parameter values more intelligently I don't understand your last request. If these rules would work for your setup why do you want default to be no sync at all. It's been a bit bumpy but this is "the way it's going to work". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Ebrahim Moshaya commented on JENKINS-38755 Re: Merge Choice Parameter values more intelligently Marc Carter Yes your example would work with our setup. Meaning, we would be using row 2 reordering_is_retained and row 4 child_additions_are_retained. I would be grateful if the default behavior is to exempt choice parameter from syncing with template so that our current configurations and setup is safe from upgrading to this. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Marc Carter commented on JENKINS-38755 Re: Merge Choice Parameter values more intelligently Given that ABC represents a param with three choices and that the default choice is the first one (this is how they work internally), here's my plan: Template Child Result Comment ABC ABC ABC no_change ABC CAB CAB reordering_is_retained ABCD ABC ABCD template_additions_are_added ABC ABCD DACB child_additions_are_retained ABC AB AB child_removals_are_ignored_wrongly AB ABC ABC
[JIRA] (JENKINS-37399) Updates to a Choice Parameter are not synchronised
Title: Message Title Ebrahim Moshaya commented on JENKINS-37399 Re: Updates to a Choice Parameter are not synchronised @drekbour This change kind of broke all our configurations seeing as we had difference choices for different use cases in the implementing jobs. Could you please update to allow us to exclude the choice parameters all together from syncing the choices? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38695) Adding promotions needs to exclude .svn directories
Title: Message Title Marc Carter commented on JENKINS-38695 Re: Adding promotions needs to exclude .svn directories I made a further change to this as I can't believe it was actually working. Could you check the trunk behaviour is correct (in lieu of automated tests which are in the process of being written)? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37399) Updates to a Choice Parameter are not synchronised
Title: Message Title Ebrahim Moshaya edited a comment on JENKINS-37399 Re: Updates to a Choice Parameter are not synchronised [~drekbour] I fully agree. For example, we We have an ez template deploy job using the choice parameter "DEPLOY_ENVIRONMENT", that is available for developers, support and operations. The Choice parameter for some jobs implementing the template allow deploying artifacts to developer environments. However, I also have some jobs implementing the template that is hidden away and only available to support and operations that have production environments in the list of choice parameters. Ideally, we don't want every job inheriting the template to sync the choice parameters list or the order. Is there a way to exclude the choice parameters from syncing up with the parent template? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38695) Adding promotions needs to exclude .svn directories
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38695 Re: Adding promotions needs to exclude .svn directories Code changed in jenkins User: Marc Carter Path: src/main/java/com/joelj/jenkins/eztemplates/promotedbuilds/PromotedBuildsTemplateUtils.java http://jenkins-ci.org/commit/ez-templates-plugin/a55b62d78c1044323c981de67d3120064cbc8a54 Log: Bugfix: JENKINS-38695 Adding promotions needs to exclude .svn directories Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37399) Updates to a Choice Parameter are not synchronised
Title: Message Title Ebrahim Moshaya commented on JENKINS-37399 Re: Updates to a Choice Parameter are not synchronised Marc Carter I fully agree. For example, we have an ez template deploy job using the choice parameter "DEPLOY_ENVIRONMENT", that is available for developers, support and operations. The Choice parameter for some jobs implementing the template allow deploying artifacts to developer environments. However, I also have some jobs implementing the template that is hidden away and only available to support and operations that have production environments in the list of choice parameters. Ideally, we don't want every job inheriting the template to sync the choice parameters list or the order. Is there a way to exclude the choice parameters from syncing up with the parent template? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38755) Merge Choice Parameter values more intelligently
Title: Message Title Ebrahim Moshaya commented on JENKINS-38755 Re: Merge Choice Parameter values more intelligently I fully agree. For example, we have an ez template deploy job using the choice parameter "DEPLOY_ENVIRONMENT", that is available for developers. The Choice parameter for some jobs implementing the template allow deploying artifacts to developer environments. However, I also have some jobs implementing the template that is hidden away and only available to support and operations that have production environments in the list of choice parameters. Ideally, we don't want every job inheriting the template to sync the choice parameters list or the order. Is there a way to exclude the choice parameters from syncing up with the parent template? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28386) Workflow support for Copy to Slave plugin
Title: Message Title mcrooney commented on JENKINS-28386 Re: Workflow support for Copy to Slave plugin That makes sense for public Jenkins; I don't see anything inherently dangerous about this in a Jenkins with authentication inside an intranet/VPC (though I agree it is less secure). Regardless, you can also accomplish a similar thing by running a separate agent on the master with a different user or in a container, and thus having the unix security model to isolate things as desired. This would allow you to Stash world-readable files on the master without exposing secrets, unless there are other concerns I'm not aware of, which I fully admit there might be. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Failed builds now properly showing time and duration of last run. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin There has been development done here: https://github.com/tommysdk/delivery-pipeline-plugin/tree/JENKINS-34040 It provides basic support but there are some identified issues which would be nice to have: [ ] Last run on failed builds [ ] Progress bar timing corresponding to actual stages/tasks [ ] Build failure should not mark all tasks as failed (mimic DPP behaviour) [ ] Number of pipeline instances per pipeline [ ] Enable start of new pipeline build? [ ] Show commit message It could be argued that the currently provided functionality is enough to satisfy this ticket and move the identified issues to separate tickets in JIRA. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38841) Fix erroneous commas in triggered by
Title: Message Title Tommy Tynjä commented on JENKINS-38841 Re: Fix erroneous commas in triggered by Fixed in 95bf6fa8184f598bbdf95a5196d36cd87eca97d3. Will be part of next release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38841) Fix erroneous commas in triggered by
Title: Message Title Tommy Tynjä resolved as Fixed Jenkins / JENKINS-38841 Fix erroneous commas in triggered by Change By: Tommy Tynjä Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38841) Fix erroneous commas in triggered by
Title: Message Title Tommy Tynjä created an issue Jenkins / JENKINS-38841 Fix erroneous commas in triggered by Issue Type: Bug Assignee: Tommy Tynjä Components: delivery-pipeline-plugin Created: 2016/Oct/08 11:38 AM Priority: Trivial Reporter: Tommy Tynjä Issue for fixing erroneous triggeredBy commas in pipe.js. Corresponding PR: https://github.com/Diabol/delivery-pipeline-plugin/pull/207 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38701) HTTP 413 when using kerberos to authenticate
Title: Message Title Bryson Gibbons commented on JENKINS-38701 Re: HTTP 413 when using kerberos to authenticate I'll dig into this when I get some time; I may not be able to easily duplicate what you are seeing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Valentijn Scholten edited a comment on JENKINS-32087 Re: Configure JIRA credentials at the Job configuration level I agree this would make the plugin more usable for bigger/enterprise environments. We don't want to people to be able to know credentials to view other departments projects/issues. It could be beneficials to start using the Jenkins Credentials Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Valentijn Scholten commented on JENKINS-32087 Re: Configure JIRA credentials at the Job configuration level I agree this would make the plugin more usable for bigger/enterprise environments. We don't want to people to be able to know credentials to view other departments projects/issues. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38840) log parser plugin fails on slave node
Title: Message Title Stephan van der Merwe created an issue Jenkins / JENKINS-38840 log parser plugin fails on slave node Issue Type: Bug Assignee: Manuel Recena Soto Attachments: Selection_006.jpg, Selection_007.jpg, Selection_008.jpg Components: log-parser-plugin Created: 2016/Oct/08 9:49 AM Environment: Operating system: Ubuntu 16.04 java version "9-ea" Java(TM) SE Runtime Environment (build 9-ea+134) Java HotSpot(TM) 64-Bit Server VM (build 9-ea+134, mixed mode) Jenkins ver. 2.7.4 Log parser plugin 2.0 Labels: plugin log-parser log parser Priority: Major Reporter: Stephan van der Merwe Steps taken: 1. I installed the log parser plugin, 2. Setup my rules file on the master. 3. created a job/build to run on a slave 4. For this job, setup post-build actions with console output log parsing 5. mark build failed on error 6. Use global rules 7. selected my rule file. When I execute the job, the job runs successfully however the log parsing failed. Clicking on the Parsed Console Output option, I get the following. ERROR: Failed to parse console log java.io.IOException: Remote call on centos7 failed So it looks like the log parser plugin cannot communicate with the slave node to get log output. Please help, this is so frustrating when things don't work as they should. Below is the output of the error in the jenkins.log Oct 08, 2016 11:13:36 AM
[JIRA] (JENKINS-37479) Unclassified staticMethod java.nio.file.Paths get java.lang.String
Title: Message Title Gabriel Konat commented on JENKINS-37479 Re: Unclassified staticMethod java.nio.file.Paths get java.lang.String I see. The following pipeline script triggers the exception: echo Math.round(currentBuild.duration / 1000) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38839) Run Always tick box to run even if build fails
Title: Message Title Dell Green created an issue Jenkins / JENKINS-38839 Run Always tick box to run even if build fails Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2016/Oct/08 6:56 AM Priority: Minor Reporter: Dell Green Other plugins like Pmd, Findbugs, Checkstyle etc have a tick box in advanced section on build config to run even if build fails. Cant seem to find this option in Jacoco plugin. Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38813) NullPointerException accessing params variable with Subversion tag
Title: Message Title Christopher Head updated an issue Jenkins / JENKINS-38813 NullPointerException accessing params variable with Subversion tag Change By: Christopher Head After upgrading to 2.18, the Pipeline: Groovy plugin claims that build parameters can be accessed through a variable called “params”, in addition to how they used to be accessible as global variables.If I create a pipeline job with a parameter of type “List Subversion tags (and more)”, and in the job’s Groovy code I refer to the “params” variable, a NullPointerException occurs. No Here is the backtrace I was able to obtain (seems that sometimes a backtrace is given ; only a single line of text in the console output stating and sometimes it isn’t):java.lang. NullPointerException is printed at org . jenkinsci.plugins.workflow.cps.persistence.IteratorHack.writeReplace(IteratorHack.java:52) at org.jenkinsci.plugins.workflow.cps.ParamsVariable.getValue(ParamsVariable.java:70) at org.jenkinsci.plugins.workflow.cps.CpsScript.getProperty(CpsScript.java:119) at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:172) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:456) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:243) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onGetProperty(GroovyInterceptor.java:52) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:308) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:24) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:1) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) 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 com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at
[JIRA] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Yibin Sheng edited a comment on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin I use HTML Publisher to take the place of Cobertura publish coverage report now, but it is far from satisfactory. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Yibin Sheng commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin I use HTML Publisher to take the place of Cobertura now, but it is far from satisfactory. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
