[JIRA] [p4-plugin] (JENKINS-32616) Add support for multibranch pipelines
Title: Message Title Frederik Wallner created an issue Jenkins / JENKINS-32616 Add support for multibranch pipelines Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 26/Jan/16 7:58 AM Labels: p4 pipeline multibranch Priority: Major Reporter: Frederik Wallner Add support for multibranch pipelines (https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md#creating-multibranch-projects). Add Comment
[JIRA] [jira-plugin] (JENKINS-32602) jira-plugin missing License
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-32602 jira-plugin missing License Change By: Radek Antoniuk Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-31958) Pipeline doesn't update when manual steps are retriggered
Title: Message Title Leigh Anderson commented on JENKINS-31958 Re: Pipeline doesn't update when manual steps are retriggered Tracked this down to an incompatibility with parameterized-trigger 2..25. Seems that the warnings about deprecated support really mean "Doesn't work at all" Please close this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-32615) com.sonyericsson.jenkins.plugins.bfa.model.dbf.ParameterizedTriggerDBF uses wrong ClassLoader to detect hudson.plugins.parameterizedtrigger.Build
Title: Message Title Frédéric Chuong created an issue Jenkins / JENKINS-32615 com.sonyericsson.jenkins.plugins.bfa.model.dbf.ParameterizedTriggerDBF uses wrong ClassLoader to detect hudson.plugins.parameterizedtrigger.BuildInfoExporterAction Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 26/Jan/16 7:18 AM Environment: Jenkins 1.625.3 Build Failure Analyzer 1.13.3 Parameterized Trigger plugin 2.30 Labels: parameterized-trigger Priority: Major Reporter: Frédéric Chuong com.sonyericsson.jenkins.plugins.bfa.model.dbf.ParameterizedTriggerDBF mentions We want to avoid having dependencies to other plugins thus using reflection., that means checking for hudson.plugins.parameterizedtrigger.BuildInfoExporterAction using the current classloader (Class.forName(className)) will never return anything since Jenkins isolate plugins classloaders. This causes the feature (extract failure from downstream) not to work and produces the following error to be logged:
[JIRA] [subversion-plugin] (JENKINS-29237) Version 2.5 requires access to repository root
Title: Message Title Jon Sten closed an issue as Fixed Just updated to 2.5.7 and everything works. After some binary searching I concluded that 2.5.5 resolved this issue. Most likely it was the update of SVNKIT to 1.8.11! Jenkins / JENKINS-29237 Version 2.5 requires access to repository root Change By: Jon Sten Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title Francis Upton commented on JENKINS-32584 Re: ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap Just released 1.31, it should be available in the next day or so. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Francis Upton commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus Can you try this with version 1.29 of the ec2 plugin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-32590) Inline CSS is ignored in published HTML reports
Title: Message Title Marius Gedminas commented on JENKINS-32590 Re: Inline CSS is ignored in published HTML reports What's the difference, security-wise, between user-generated HTML files in the workspace embedding inline CSS (which is forbidden) versus user-generated HTML files in the workspace linking to user-generated CSS files in the workspace (which is allowed)? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28649) ExportedBean error with Workflow and AfterRestartTask
Title: Message Title Daniel Weber updated an issue Jenkins / JENKINS-28649 ExportedBean error with Workflow and AfterRestartTask Change By: Daniel Weber Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin "If nothing is defined, your code will be assumed to fall under the MIT license terms." Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title Erik Trimble commented on JENKINS-32604 Re: join-pluging missing licensing information This is a problem specific to this particular plugin, not the Jenkins project as a whole. Other plugins have similar LICENSE files and/or describe the license in the pom.xml file in their respective GitHub repos. I can't make any decision or push for anything on this issue - there's literally nothing for me to consult on. This problem specifically has to be handled by the people who are responsible for writing/maintaining the Join Plugin code; they own the copyright on the code, and need to decide (and publish) what license they want to make it available under. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29762) Make inclusion of build and environment variables configurable
Title: Message Title
Rusty Gerard commented on JENKINS-29762
Re: Make inclusion of build and environment variables configurable
>The mask passwords plugin only masked passwords in the build consoles,
I'm aware of that. What I meant was implement the solution in a similar fashion to the Mask-Passwords plugin, rather than omit all environment variables.
What might be simplest for users is to include the Mask-Passwords plugin as a dependency. If Mask-Passwords is enabled in the job, then delete those environment variables from the payload, or replace the value in the payload with the same static string constant that Mask-Passwords prints to the console ("").
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus Please provide similar plugin details which works similarly like ec2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus Sorry,i am also doing on first time checking this plugin.As explained in "Description" I have followed to update plugin.On fresh Jenkins dashboard i have put ec2 plugin and needed dependent plugin and configured cloud details .It has failed to launch slaves when tried to test job with slave name. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information Please consult with the overall project on this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Francis Upton commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus I'm not familiar with how to use Eucalyptus, nor can I find the offending source code to help me to understand this problem. Can you either point me to the source code or give me steps about how I might be able to reproduce this problem so I can fix it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus Yes.Same issue.attached jenkins_1.31.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Murali Phani updated an issue Jenkins / JENKINS-32588 Unable to launch linux slaves using ec2 plugin using Eucalyptus Change By: Murali Phani Attachment: jenkins_1.31.log Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title Erik Trimble commented on JENKINS-32604 Re: join-pluging missing licensing information I'm a commercial user. The plugin needs to be licensed - without licensing the code explicitly, it can't be (legally) used by anyone. Someone needs to put a LICENSE.txt file or similar holding the proper license (e.g. MIT, GPL, BSD, etc.) for the plugin into the GitHub repo. Legally, since this code has no explicit license attached to it, it's licensed solely to the authors, with no rights to copy or use it granted. It needs a license doc. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Francis Upton commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus So the same problem then? Can you attach the log again just to be sure? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Francis Upton commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus I don't see what the problem is from this log entry. And the original problem does seem to be fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title
Murali Phani edited a comment on JENKINS-32588
Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus
Thanks.I have updated new plugin .but below isssue is there in log {color:#33}---clip-- INFO IWARNING : Jenkins is fully up and running Exception during provisioning Launching emi-7050735e for template BtsmancompileJan 26, 2016 7 com.amazonaws.AmazonServiceException : 46:49 AM hudson com . plugins eucalyptus . ec2 ws . SlaveTemplate logProvisionInfoINFO WebServicesException : Launching emi-7050735e for template BtsmancompileLooking for existing instances with describe-instance Missing required object (Service : {InstanceIds AmazonEC2; Status Code : [],Filters 500; Error Code : [{Name InternalFailure; Request ID : image 6d8b0b9b - id,Values: [emi dc77 - 7050735e]}, {Name: availability 4695 - zone,Values: [bhcloc55_2]}, {Name: instance.group 9ada - name,Values 55383235fe0c)at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java : [btscompilemans]}, {Name: key-name,Values: [btsman]}, {Name: instance-type,Values: [m1 1181)at com . small]}],} amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:766) Jan 26, 2016 7 at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java : 48:15 AM hudson 485)at com . model amazonaws . AsyncPeriodicWork$1 run http.AmazonHttpClient.execute(AmazonHttpClient.java:306) INFO at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java : Finished Download metadata 11901)at com . 189,519 ms amazonaws.services.ec2.AmazonEC2Client.describeSpotInstanceRequests(AmazonEC2Client.java:6437) ---clip--{color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title
Murali Phani commented on JENKINS-32588
Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus
Thanks.I have updated new plugin .but below isssue is there in log
--
clip
- INFO: Jenkins is fully up and running Launching emi-7050735e for template Btsmancompile Jan 26, 2016 7:46:49 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Launching emi-7050735e for template Btsmancompile Looking for existing instances with describe-instance: {InstanceIds: [],Filters: [{Name: image-id,Values: [emi-7050735e]}, {Name: availability-zone,Values: [bhcloc55_2]}, {Name: instance.group-name,Values: [btscompilemans]}, {Name: key-name,Values: [btsman]}, {Name: instance-type,Values: [m1.small]}],} Jan 26, 2016 7:48:15 AM hudson.model.AsyncPeriodicWork$1 run INFO: Finished Download metadata. 189,519 ms --
clip
-
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-reports-plugin] (JENKINS-32614) Cannot parse Scenario Outlines from Calabash Cucumber
Title: Message Title Brad M commented on JENKINS-32614 Re: Cannot parse Scenario Outlines from Calabash Cucumber Some defects, like JENKINS-21835 refer to dead link https://github.com/cucumber/gherkin/issues/165 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-reports-plugin] (JENKINS-32614) Cannot parse Scenario Outlines from Calabash Cucumber
Title: Message Title
Brad M created an issue
Jenkins / JENKINS-32614
Cannot parse Scenario Outlines from Calabash Cucumber
Issue Type:
Bug
Assignee:
Damian Szczepanik
Components:
cucumber-reports-plugin
Created:
26/Jan/16 2:06 AM
Labels:
plugin
Priority:
Major
Reporter:
Brad M
Error message during cucumber.json parsing:
[Cucumber Tests] Parsing results.
[Cucumber Tests] parsing cucumber.json
ERROR: Step: {When } name: {I search on the code ""} received before previous step: {When } name: {I search on the code ""} handled! Maybe caused by broken JSON, see #JENKINS-21835
Failed to parse Cucumber JSON: Step: {When } name: {I search on the code ""} received before previous step: {When } name: {I search on the code ""} handled! Maybe caused by broken JSON, see #JENKINS-21835
Build step 'Publish Cucumber test result report' changed build result to FAILURE
(Note the above logs the new step twice, instead of currentStep)
The unit tests in the plugin code show Scenario Outlines with format like:
[JIRA] [translation-plugin] (JENKINS-32613) Translation Assistance plugin missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32613 Translation Assistance plugin missing Licensing Information Issue Type: Bug Assignee: Unassigned Components: translation-plugin Created: 26/Jan/16 1:32 AM Labels: license Priority: Major Reporter: Erik Trimble There is no LICENSE.txt or similar file at the top level of the GitHub project, nor is there any mention of a license in the pom.xml file therein. This code must be explicitly licensed before it can be used. Add Comment
[JIRA] [port-allocator-plugin] (JENKINS-32612) Port Allocator plugin - missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32612 Port Allocator plugin - missing Licensing Information Issue Type: Bug Assignee: Andres Rodriguez Components: port-allocator-plugin Created: 26/Jan/16 1:28 AM Labels: license Priority: Minor Reporter: Erik Trimble There is no LICENSE.txt or similar file at the top level of the GitHub project, nor is there any mention of licensing in the pom.xml file therein. This code must be explicitly licensed before it can be used. Add Comment
[JIRA] [repository-connector-plugin] (JENKINS-32611) Repository Connector plugin - missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32611 Repository Connector plugin - missing Licensing Information Issue Type: Bug Assignee: Unassigned Components: repository-connector-plugin Created: 26/Jan/16 1:27 AM Labels: license Priority: Major Reporter: Erik Trimble There is no LICENSE.txt or similar file at the top level of the GitHut project, nor is there any mention of a license in the pom.xml file. This code must be explicitly licensed before it can be used. Add Comment
[JIRA] [ssh-slaves-plugin] (JENKINS-32610) SSH Slaves - missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32610 SSH Slaves - missing Licensing Information Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ssh-slaves-plugin Created: 26/Jan/16 1:21 AM Labels: license Priority: Major Reporter: Erik Trimble There is no LICENSE.txt or similar file at the top level of the GitHub project, nor is there any mention of a license in the pom.xml file therein. This code MUST be explicitly licensed before it can be used. Add Comment
[JIRA] [maven-info-plugin] (JENKINS-32609) Maven Info - missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32609 Maven Info - missing Licensing Information Issue Type: Bug Assignee: olamy Components: maven-info-plugin Created: 26/Jan/16 1:17 AM Labels: license Priority: Major Reporter: Erik Trimble There is no LICENSE.txt or similar file at the top level of the GitHub Project, nor is there any license info in the pom.xml file. This code MUST be licensed before it can be used. Add Comment
[JIRA] [maven-repo-cleaner-plugin] (JENKINS-32608) Maven Repo Cleaner - missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32608 Maven Repo Cleaner - missing Licensing Information Issue Type: Bug Assignee: Unassigned Components: maven-repo-cleaner-plugin Created: 26/Jan/16 1:14 AM Labels: license Priority: Major Reporter: Erik Trimble There is no LICENSE.txt or similar file at the top level of the GitHub project, nor is there any licensing information in the pom.xml file there. This code requires a license before it can be used. Add Comment
[JIRA] [build-pipeline-plugin] (JENKINS-32607) Build Pipeline - missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32607 Build Pipeline - missing Licensing Information Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 26/Jan/16 1:03 AM Labels: license Priority: Major Reporter: Erik Trimble There is no LICENSE.txt or similar file at the top level of the GitHub project, nor is any license mentioned in the pom.xml file therein. This code must be properly and explicitly licensed before it can be useful. Add Comment
[JIRA] [cvs-plugin] (JENKINS-32606) CVS plugin missing explicit Licensing information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32606 CVS plugin missing explicit Licensing information Issue Type: Bug Assignee: Unassigned Components: cvs-plugin Created: 26/Jan/16 12:58 AM Labels: license Priority: Major Reporter: Erik Trimble There's no LICENSE.txt or similar file at the top level of the GitHub project, nor is there a license mentioned in the pom.xml Some (but not all) of the files have a MIT license header, but most don't. The whole project needs to be explicitly licensed before it can be used. Add Comment
[JIRA] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title mdonohue commented on JENKINS-32604 Re: join-pluging missing licensing information who are you, and what is this in reference to? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emotional-jenkins-plugin] (JENKINS-32605) emotional-jenkins missing Licensing information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32605 emotional-jenkins missing Licensing information Issue Type: Bug Assignee: Unassigned Components: emotional-jenkins-plugin Created: 26/Jan/16 12:53 AM Labels: license Priority: Major Reporter: Erik Trimble There's no LICENSE.txt or similar file at the top level of the GitHub project, nor is there any mention of a license in the pom.xml file therein. The code is unusable until it's been properly licensed. Add Comment
[JIRA] [join-plugin] (JENKINS-32604) join-pluging missing licensing information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32604 join-pluging missing licensing information Issue Type: Bug Assignee: mdonohue Components: join-plugin Created: 26/Jan/16 12:46 AM Labels: license Priority: Major Reporter: Erik Trimble There's no LICENSE.txt or similar file at the top-level of the GitHub project, nor is there a entry in the pom.xml Without either, the code is unusable. Add Comment
[JIRA] [jira-issue-updater-plugin] (JENKINS-32603) Jira Issue Updater - Missing Licensing Information
Title: Message Title Erik Trimble updated an issue Jenkins / JENKINS-32603 Jira Issue Updater - Missing Licensing Information Change By: Erik Trimble Summary: Jira Issue Updater - Missing Licensing Information Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3-plugin] (JENKINS-31556) Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off
Title: Message Title Adam Housman commented on JENKINS-31556 Re: Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off I have the same issue Jenkins 1.609.3 S3 Plugin 0.8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-issue-updater-plugin] (JENKINS-32603) Missing Licensing Information
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32603 Missing Licensing Information Issue Type: Bug Assignee: Unassigned Components: jira-issue-updater-plugin Created: 26/Jan/16 12:13 AM Labels: license Priority: Major Reporter: Erik Trimble There's no licensing information for the plugin. It should either be in a file "LICENSE" or similar at the top of the GitHub project, or referenced in the pom.xml file therein. The code can't be used until it has an explicit license. Add Comment
[JIRA] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Tony Bridges commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Does the pull request conclusively correct the issue ? If so, maybe we can get it rolled into a new plugin release ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-32602) jira-plugin missing License
Title: Message Title Erik Trimble created an issue Jenkins / JENKINS-32602 jira-plugin missing License Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 26/Jan/16 12:10 AM Environment: all Labels: license Priority: Major Reporter: Erik Trimble The jira-plugin has neither a LICENSE file at the top level of the GitHub project, nor does it mention a license in the pom.xml file. This should be explicitly stated in either place. It's not usable until it's licensed.
[JIRA] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Tony Bridges commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type We've seen this a few times, most recently in a MultiJob run calling a maven job, but previously in a Freestyle job calling maven jobs. We are running 1.609.3.1, CBE. I've opened a ticket with CB Support and cited this defect. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title James Sandlin edited a comment on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace This should definitely be part of Jenkins Jenkin's GIT plugin itself. With CI gaining popularity, more and more companies use multiple repos. Unfortunately, with Jenkins not supporting it natively, the multi-scm plugin breaks other plugins' CI functionality.We've seen problems with:* github pull request builder* github plugin's push functionalityThis also caused us to checkout with the multi-scm plugin in a specific order to ensure Jenkins has the correct version in its variables.When using Build Forge 10 years ago, a single repo was normal. Not so much any more. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title James Sandlin edited a comment on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace This should definitely be part of Jenkins itself. With CI gaining popularity, more and more companies use multiple repos. Unfortunately, with Jenkins not supporting it natively, the multi-scm plugin breaks other plugins' CI functionality.We've seen problems with:*github pull request builder*github plugin's push functionalityThis also caused us to checkout with the multi-scm plugin in a specific order to ensure Jenkins has the correct version in its variables.When using Build Forge 10 years ago, a single repo was normal. Not so much any more. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title James Sandlin commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace This should definitely be part of Jenkins itself. With CI gaining popularity, more and more companies use multiple repos. Unfortunately, with Jenkins not supporting it natively, the multi-scm plugin breaks other plugins' CI functionality. We've seen problems with: *github pull request builder *github plugin's push functionality This also caused us to checkout with the multi-scm plugin in a specific order to ensure Jenkins has the correct version in its variables. When using Build Forge 10 years ago, a single repo was normal. Not so much any more. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26104) Custom Workflow step for sending mail
Title: Message Title Craig Rodrigues commented on JENKINS-26104 Re: Custom Workflow step for sending mail I'm having problems with pipeline plugin (formerly named workflow plugin). I described the problem here: https://groups.google.com/d/msg/jenkinsci-users/vziPhYZQcPI/tY2FPK1oEgAJ Can someone help? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM
Title: Message Title Kris Ravenscroft commented on JENKINS-27514 Re: Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM Has any silent progress been made on this issue? I currently have to reboot weekly due to this issue. Currently running Jenkins 1.645 and SSH Plugin 1.10. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-4709) Add exclusion regions in TFS polling and checkout
Title: Message Title Olivier Dagenais resolved as Fixed Fixed via pull request #68. Jenkins / JENKINS-4709 Add exclusion regions in TFS polling and checkout Change By: Olivier Dagenais Status: Open Resolved Assignee: redsolo renarj Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-32504) Make JiraEnvironmentVariableBuilder compatible with pipeline
Title: Message Title Jan Zajíc updated an issue Jenkins / JENKINS-32504 Make JiraEnvironmentVariableBuilder compatible with pipeline Change By: Jan Zajíc Summary: Make JiraEnvironmentVariableBuilder compatible with workflow pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32601) Connection timeout behind a proxy
Title: Message Title Sylvain Deschenes created an issue Jenkins / JENKINS-32601 Connection timeout behind a proxy Issue Type: Bug Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 25/Jan/16 9:07 PM Environment: Jenkins v.1.625.3 Runs directly Is in a private network, access with a proxy. Priority: Major Reporter: Sylvain Deschenes I've got this error: Bitbucket notify on start failed: There was a problem while creating a connection to the remote service. org.scribe.exceptions.OAuthConnectionException: There was a problem while creating a connection to the remote service. at org.scribe.model.Request.send(Request.java:69) at org.scribe.model.Request.send(Request.java:75) at org.jenkinsci.plugins.bitbucket.api.BitbucketApiService.getAccessToken(BitbucketApiService.java:27) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.notifyBuildStatus(BitbucketBuildStatusNotifier.java:216) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:79) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835) at hudson.maven.MavenModu
[JIRA] [git-plugin] (JENKINS-32218) buildsByBranchName is not set anymore
Title: Message Title Jey Saba commented on JENKINS-32218 Re: buildsByBranchName is not set anymore I'm also experiencing the issue of commit changes not being set for each build. Like others here, I am seeing the problem only in some of the jobs on my server. I've narrowed down the issue to the inclusion of the Prune stale remote-tracking branches option in Additional Behaviours. I can also confirm that I started seeing this symptom after upgrading from 2.4.0 to 2.4.1, running Jenkins 1.625.3 LTS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-32583) Predefined parameters do not expand variables properly
Title: Message Title vlad morav stopped work on JENKINS-32583 Change By: vlad morav Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-32600) Move to 1.10.49 version of AWS SDK
Title: Message Title Francis Upton assigned an issue to Nicolas De Loof Jenkins / JENKINS-32600 Move to 1.10.49 version of AWS SDK Change By: Francis Upton Assignee: Francis Upton Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [aws-java-sdk-plugin] (JENKINS-32600) Move to 1.10.49 version of AWS SDK
Title: Message Title Francis Upton updated an issue Jenkins / JENKINS-32600 Move to 1.10.49 version of AWS SDK Please move this back to ec2-plugin once you have released your plugin with this version. Change By: Francis Upton Component/s: aws-java-sdk-plugin Component/s: ec2-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32600) Move to 1.10.49 version of AWS SDK
Title: Message Title Francis Upton created an issue Jenkins / JENKINS-32600 Move to 1.10.49 version of AWS SDK Issue Type: Task Assignee: Francis Upton Components: ec2-plugin Created: 25/Jan/16 8:18 PM Priority: Minor Reporter: Francis Upton Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issu
[JIRA] [ec2-plugin] (JENKINS-32588) Unable to launch linux slaves using ec2 plugin using Eucalyptus
Title: Message Title Francis Upton commented on JENKINS-32588 Re: Unable to launch linux slaves using ec2 plugin using Eucalyptus Can you try this HPI and see if this resolves your problem? https://jenkins.ci.cloudbees.com/job/plugins/job/ec2-plugin/373/org.jenkins-ci.plugins$ec2/artifact/org.jenkins-ci.plugins/ec2/1.31-SNAPSHOT/ec2-1.31-SNAPSHOT.hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32595) Schedule the next stage after I approved a pipeline
Title: Message Title Jesse Glick resolved as Not A Defect You can use the sleep step with a calculated time (the relevant methods are already whitelisted AFAIK). Jenkins / JENKINS-32595 Schedule the next stage after I approved a pipeline Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-32491) Rename Workflow Plugin to Pipeline
Title: Message Title Jan Zajíc assigned an issue to Jan Zajíc Jenkins / JENKINS-32491 Rename Workflow Plugin to Pipeline Change By: Jan Zajíc Assignee: Jan Zajíc Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-32504) Make JiraEnvironmentVariableBuilder compatible with workflow
Title: Message Title Jan Zajíc assigned an issue to Jan Zajíc Jenkins / JENKINS-32504 Make JiraEnvironmentVariableBuilder compatible with workflow Change By: Jan Zajíc Assignee: Jan Zajíc Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rundeck-plugin] (JENKINS-27892) Rundeck - Could not find a job with the identifier
Title: Message Title Evan Powell commented on JENKINS-27892 Re: Rundeck - Could not find a job with the identifier I have this issue on v3.5.1 as well. My Jenkins jobs are simple freestyle jobs, and the Rundeck jobs are all in uniquely named groups (job names are not unique however). I have a suspicion that it may have to do with Jenkins' authenticated session with Rundeck expiring. Occasionally, my Jenkins job that triggers and tails a Rundeck job execution will fail with the error message "Rundeck is not running !". This occurs even when I am interacting with Rundeck directly in another tab. Our session expiration setting on Rundeck is 30 minutes. We're updating it to 12 hours, but if my theory is correct this will only mitigate the issue and not solve it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32599) JENKINS_HOME/users/config.xml Results in Nameless User
Title: Message Title
Kenneth Baltrinic updated an issue
Jenkins / JENKINS-32599
JENKINS_HOME/users/config.xml Results in Nameless User
Change By:
Kenneth Baltrinic
If a valid config.xml file for a user is placed in the root user folder, i.e. {{JENKINS_HOME/users/config.xml}}, it causes a nameless user to be created that does not appear anywhere in the UI and generally can't be managed. (You can access it via groovy script or by editing the xml but that seems to be about it).In our case this file was created by a bug in a Chef recipe, but Chef bugs asside, it seems incorrect behavior for Jenkins pick up such a misplaced config file and created a nameless user from of it. Or is this intended behavior? If so this ticket should be used to document it somewhere and if not, it should be used to fix it.For some background: This turns out to be the rood root cause of the issue reported in JENKINS-29860. The initial AD error reported there was caused by having a nameless user with the same SSH key as a named user. (This lead to JENKINS-32534 being opened as well.) The nameless user was created because of a bug in the Chef recipe such that it created a config.xml file for our admin user in the root user folder {{JENKINS_HOME/users/config.xml}} instead of updating the intended existing file {{JENKINS_HOME/users//config.xml}}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send
[JIRA] [core] (JENKINS-32599) JENKINS_HOME/users/config.xml Results in Nameless User
Title: Message Title Kenneth Baltrinic created an issue Jenkins / JENKINS-32599 JENKINS_HOME/users/config.xml Results in Nameless User Issue Type: Bug Assignee: Unassigned Components: core Created: 25/Jan/16 6:51 PM Environment: 1.625.2 LTS (and prior) Labels: security user config.xml Priority: Minor Reporter: Kenneth Baltrinic If a valid config.xml file for a user is placed in the root user folder, i.e. JENKINS_HOME/users/config.xml, it causes a nameless user to be created that does not appear anywhere in the UI and generally can't be managed. (You can access it via groovy script or by editing the xml but that seems to be about it). In our case this file was created by a bug in a Chef recipe, but Chef bugs asside, it seems incorrect behavior for Jenkins pick up such a misplaced config file and created a nameless user from of it. Or is this intended behavior? If so this ticket should be used to document it somewhere and if not, it should be used to fix it.
[JIRA] [job-dsl-plugin] (JENKINS-32598) Folder authorization permission NPE
Title: Message Title
Thomas Wabner created an issue
Jenkins / JENKINS-32598
Folder authorization permission NPE
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
25/Jan/16 6:28 PM
Environment:
job-dsl-plugin 1.42
Priority:
Blocker
Reporter:
Thomas Wabner
The folder currently does not support authorization/permission elements because the variable availablePermissions seems to be null (not declared/initializes).
https://jenkinsci.github.io/job-dsl-plugin/#path/folder-authorization
You can also check this in the API browser:
http://job-dsl.herokuapp.com/
{{folder('example-2') { authorization { permission('hudson.model.Item.Discover', 'anonymous') }
}}}
Exception: {{java.lang.NullPointerException: Cannot invoke method contains() on null object at java_util_Set$contains$2.call(Unknown Source) at javaposse.jobdsl.dsl.helpers.AuthorizationContext.permission(AuthorizationContext.groovy:49)}}
I guess, a simple variable declaration should be enough. But I'am not that groovy aware to create pull requests for this.
[JIRA] [repo-plugin] (JENKINS-26836) Repo support for Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26836 Re: Repo support for Workflow Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/d77a777f217b79a6617063408f79e239b74dc0f8 Log: Merge pull request #326 from Typz/patch-1 JENKINS-26836 Update COMPATIBILITY.md for repo plugin Compare: https://github.com/jenkinsci/workflow-plugin/compare/10b3bc8154c1...d77a777f217b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30759) NPE from PlaceholderTask.finish
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30759 Re: NPE from PlaceholderTask.finish Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ExecutorStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/10b3bc8154c156a08b1eb5ad3f60d79eae8902bc Log: Merge pull request #323 from jglick/quick-node- JENKINS-30759 JENKINS-30759 Race condition initializing fields in RunningTask Compare: https://github.com/jenkinsci/workflow-plugin/compare/0bf6742cd3b8...10b3bc8154c1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30759) NPE from PlaceholderTask.finish
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30759 NPE from PlaceholderTask.finish Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30759) NPE from PlaceholderTask.finish
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30759 Re: NPE from PlaceholderTask.finish Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ExecutorStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/e0fe19d80ad3478780d8f4246f63d398358e7437 Log: [FIXED JENKINS-30759] Race condition initializing fields in RunningTask. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32598) Folder authorization permission NPE
Title: Message Title
Thomas Wabner updated an issue
Jenkins / JENKINS-32598
Folder authorization permission NPE
Change By:
Thomas Wabner
The folder currently does not support authorization/permission elements because the variable availablePermissions seems to be null (not declared/initializes).https://jenkinsci.github.io/job-dsl-plugin/#path/folder-authorizationYou can also check this in the API browser:http://job-dsl.herokuapp.com/ {{ {quote} folder('example-2') {authorization {permission('hudson.model.Item.Discover', 'anonymous')}} {quote } } Exception:{{java.lang.NullPointerException: Cannot invoke method contains() on null object at java_util_Set$contains$2.call(Unknown Source) at javaposse.jobdsl.dsl.helpers.AuthorizationContext.permission(AuthorizationContext.groovy:49)}}I guess, a simple variable declaration should be enough. But I'am not that groovy aware to create pull requests for this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32598) Folder authorization permission NPE
Title: Message Title
Thomas Wabner updated an issue
Jenkins / JENKINS-32598
Folder authorization permission NPE
Change By:
Thomas Wabner
The folder currently does not support authorization/permission elements because the variable availablePermissions seems to be null (not declared/initializes).https://jenkinsci.github.io/job-dsl-plugin/#path/folder-authorizationYou can also check this in the API browser:http://job-dsl.herokuapp.com/{quote}folder('example-2') {authorization {permission('hudson.model.Item.Discover', 'anonymous')}}{quote}Exception:{ { quote} java.lang.NullPointerException: Cannot invoke method contains() on null object at java_util_Set$contains$2.call(Unknown Source) at javaposse.jobdsl.dsl.helpers.AuthorizationContext.permission(AuthorizationContext.groovy:49) {quote } } I guess, a simple variable declaration should be enough. But I'am not that groovy aware to create pull requests for this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-32598) Folder authorization permission NPE
Title: Message Title
Thomas Wabner updated an issue
Jenkins / JENKINS-32598
Folder authorization permission NPE
Change By:
Thomas Wabner
The folder currently does not support authorization/permission elements because the variable availablePermissions seems to be null (not declared/initializes).https://jenkinsci.github.io/job-dsl-plugin/#path/folder-authorizationYou can also check this in the API browser:http://job-dsl.herokuapp.com/{{ folder('example-2') {authorization {permission('hudson.model.Item.Discover', 'anonymous')}} }}Exception:{{java.lang.NullPointerException: Cannot invoke method contains() on null object at java_util_Set$contains$2.call(Unknown Source) at javaposse.jobdsl.dsl.helpers.AuthorizationContext.permission(AuthorizationContext.groovy:49)}}I guess, a simple variable declaration should be enough. But I'am not that groovy aware to create pull requests for this.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-29762) Make inclusion of build and environment variables configurable
Title: Message Title gabe cee commented on JENKINS-29762 Re: Make inclusion of build and environment variables configurable The mask passwords plugin only masked passwords in the build consoles, for example if you are using an api key which gets injected as a EnvVar then it wont echo out in the console but the logstash plugin just see's it as a EnvVar and publishes the data. Optional inclusion of env vars would be useful for those who dont want to publish this information as well Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title Francis Upton closed an issue as Fixed Will be in 1.31 to be released shortly. Jenkins / JENKINS-32584 ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap Change By: Francis Upton Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30685) Hide core dependencies in plugin classpath
Title: Message Title Spike Washburn updated an issue Jenkins / JENKINS-30685 Hide core dependencies in plugin classpath Change By: Spike Washburn Summary: Hide core dependencies in plugin classapth classpath Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32257) GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes
Title: Message Title rsandell updated an issue Jenkins / JENKINS-32257 GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes Change By: rsandell Component/s: core Component/s: gerrit-trigger-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32257) GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes
Title: Message Title rsandell commented on JENKINS-32257 Re: GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes I changed component to core because it required me to set some component, but I don't know if the issue is actually in core. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32257) GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes
Title: Message Title rsandell assigned an issue to Unassigned Jenkins / JENKINS-32257 GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes Change By: rsandell Assignee: rsandell Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-32257) GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes
Title: Message Title rsandell commented on JENKINS-32257 Re: GERRIT_CHANGE_SUBJECT truncation can leave unbalanced quotes This is not a Gerrit Trigger issue, the Gerrit Trigger doesn't do any trucation. There is a mitigation of this issue released in 2.18.0 that enables the user to remove or encode that parameter. But the underlying truncation is somewhere else. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22767) AbstractLazyLoadRunMap.getById subject to race condition with .load
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22767 Re: AbstractLazyLoadRunMap.getById subject to race condition with .load Code changed in jenkins User: Jesse Glick Path: job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/a8073443b901b0cde63dacec2f82f9691833744b Log: JENKINS-22767 Noting symptom. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30395) ClosedByInterruptException in JenkinsRule setup
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30395 Re: ClosedByInterruptException in JenkinsRule setup Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/BuildQueueTasksTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsScmFlowDefinitionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/DSLTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/DynamicEnvironmentExpanderTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/EnvWorkflowTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/JenkinsRuleExt.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/ScalabilityTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/SingleJobTestBase.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDumpTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/global/WorkflowLibRepositoryTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/steps/LoadStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/steps/RestartingLoadStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ArtifactArchiverStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CatchErrorStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/DeleteDirStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/EchoStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/EnvStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/IsUnixStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/MailStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PwdStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ReadWriteFileStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/SleepStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/StageTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/SynchronousNonBlockingStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/TimeoutStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ToolStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WorkspaceStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/RunWrapperTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/durable_task/ShellStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/input/InputStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/GitStepRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/GitStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/MercurialStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/SubversionStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/stash/StashTest.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/AbstractCpsFlowTest.java htt
[JIRA] [core] (JENKINS-30395) ClosedByInterruptException in JenkinsRule setup
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30395 Re: ClosedByInterruptException in JenkinsRule setup Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/BuildQueueTasksTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsScmFlowDefinitionTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/DSLTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/DynamicEnvironmentExpanderTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/EnvWorkflowTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/JenkinsRuleExt.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/ScalabilityTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/SingleJobTestBase.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDumpTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/global/WorkflowLibRepositoryTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/steps/LoadStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/cps/steps/RestartingLoadStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ArtifactArchiverStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CatchErrorStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/CoreWrapperStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/DeleteDirStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/EchoStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/EnvStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/IsUnixStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/MailStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PwdStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ReadWriteFileStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/SleepStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/StageTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/SynchronousNonBlockingStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/TimeoutStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ToolStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WorkspaceStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/RunWrapperTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/durable_task/ShellStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/input/InputStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/GitStepRestartTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/GitStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/MercurialStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/scm/SubversionStepTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/stash/StashTest.java cps/src/test/java/org/jenkinsci/plugins/workflow/cps/AbstractCpsFlowTest.java htt
[JIRA] [ws-cleanup-plugin] (JENKINS-22696) Delete workspace with sudo doesn't work
Title: Message Title Harry Flink resolved as Fixed Resolving this issue as cleaning the workspace containing root-owned files seems to work with newer versions of Jenkins and ws-cleanup plugin. Jenkins / JENKINS-22696 Delete workspace with sudo doesn't work Change By: Harry Flink Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup-plugin] (JENKINS-22696) Delete workspace with sudo doesn't work
Title: Message Title Harry Flink commented on JENKINS-22696 Re: Delete workspace with sudo doesn't work St. John Johnson: Thanks for the tip! I hadn't checked that out, but now that I test it, the ws-cleanup just works. I don't even have to give it any advanced parameters to explicitly tell it to use sudo. The requireTTY is not set to sudoers, or at least grep doesn't find it anywhere from /etc. Now when I just select the checkout "Delete workspace before build starts", the workspace is cleared correctly, even if there are files owned by root. We are currently using Jenkins v1.632 with Workspace Cleanup Plugin 0.28 (the latest version). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chucknorris-plugin] (JENKINS-32594) Bend the pipeline-plugin to Chuck's will
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32594 Re: Bend the pipeline-plugin to Chuck's will Code changed in jenkins User: Baptiste Mathus Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/a5d62d2cde0f10c34d9b9685d2e7ad05665f0841 Log: Noting chucknorris compatibility cf. JENKINS-32594 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [radiatorview-plugin] (JENKINS-32549) Support the pipeline-plugin (apka workflow)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32549 Re: Support the pipeline-plugin (apka workflow) Code changed in jenkins User: Baptiste Mathus Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/774cee1947cf7e43bcefabe4469eb39c6341160a Log: Noting radiatorview compatibility Cf. JENKINS-32549 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chucknorris-plugin] (JENKINS-32594) Bend the pipeline-plugin to Chuck's will
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32594 Bend the pipeline-plugin to Chuck's will Change By: Jesse Glick Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32596) ACLDecorator
Title: Message Title stephenconnolly commented on JENKINS-32596 Re: ACLDecorator I don't remember discussing this with you, but the design sounds like something I would discuss... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32597) Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace
Title: Message Title Magnus Jacobsson created an issue Jenkins / JENKINS-32597 Log fills up with messages like: WARNING: Executor #4 for HOST : executing JOBNAME #171005 termination trace Issue Type: Bug Assignee: Unassigned Attachments: jenkins_tail_1.log Components: core Created: 25/Jan/16 4:23 PM Environment: Jenkins 1.645 Linux metaria 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14 21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Priority: Major Reporter: Magnus Jacobsson The Jenkins log fills up with messages of this type and the log files become HUGE, making it very hard to diagnose other problems. It seems like something is continuously trying to terminate something, but fails over and over again. The log items seem to come every time a job terminates on that slave and the number of logged items at a given time seems to accumulate underlying errors. I tried to disconnect and reconnect the slave, but this just results in even more log items (the doDisconnect me
[JIRA] [core] (JENKINS-32596) ACLDecorator
Title: Message Title
Jesse Glick created an issue
Jenkins / JENKINS-32596
ACLDecorator
Issue Type:
New Feature
Assignee:
Unassigned
Components:
core
Created:
25/Jan/16 4:02 PM
Labels:
multibranch workflow api permission authorization
Priority:
Major
Reporter:
Jesse Glick
Currently workflow-multibranch uses WorkflowJobProperty.decorateACL to customize ACL behavior but this is a hack. Discussed with stephenconnolly:
Suggest a new core interface
package jenkins.security;
/** Permits {@link ACL} decisions to be overridden by extensions outside the control of either an {@link AccessControlled} or an {@link AuthorizationStrategy}. */
public abstract class ACLDecorator implements ExtensionPoint {
/**
* May be used to override {@link ACL#hasPermission(Authentication, Permission)} decisions.
* @param object the object of a permission check
* @param a some authentication (not {@link ACL#SYSTEM}, which is always granted everything)
* @param permission some permission
* @return true to grant the permission, false to deny it, or null to allow another extension and finally the base logic to apply
*/
public abstract Boolean ha
[JIRA] [htmlpublisher-plugin] (JENKINS-32590) Inline CSS is ignored in published HTML reports
Title: Message Title Daniel Beck resolved as Not A Defect Not actually a defect, works as intended. JENKINS-32296 may help a bit here, but otherwise https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy stands. Jenkins / JENKINS-32590 Inline CSS is ignored in published HTML reports Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31753) Fields are aligned at the bottom in the view of the parameters of a job
Title: Message Title Daniel Beck assigned an issue to Frederic bonerandi Jenkins / JENKINS-31753 Fields are aligned at the bottom in the view of the parameters of a job Change By: Daniel Beck Assignee: Daniel Beck Frederic bonerandi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-32584) ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap
Title: Message Title Michael Barrientos commented on JENKINS-32584 Re: ec2-plugin counts *every* instance (not just Jenkins slave instances) when counting slaves; incorrectly hits slave cap Your build #371 snapshot worked for me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-32595) Schedule the next stage after I approved a pipeline
Title: Message Title Adrien Lecharpentier created an issue Jenkins / JENKINS-32595 Schedule the next stage after I approved a pipeline Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 25/Jan/16 3:25 PM Priority: Minor Reporter: Adrien Lecharpentier When I approve a step, let say the QA deployment, I'd like to be able to say "process the next stage at 2pm" even if it's 10am when I approve the current pipeline. This would be nice to have to be able to organize and schedule production deployment or in case the resource used after the input step requires to be allocated based on time. Add Comment
[JIRA] [branch-api-plugin] (JENKINS-30252) Provide easy access to git branch name in multibranch workflow scripts
Title: Message Title
Marcus Sjölin edited a comment on JENKINS-30252
Re: Provide easy access to git branch name in multibranch workflow scripts
This feature seem to have gone into 1.11, however I cannot get this to work in 1.13 {code}node {// Mark the code checkout 'stage'stage 'Checkout'// Get some code from a GitHub repositorycheckout([$class: 'GitSCM', branches: [[name: 'develop'], [name: 'feature/*']], doGenerateSubmoduleConfigurations: false, submoduleCfg: [], userRemoteConfigs: [[credentialsId: '...', url: 'ssh://git@giturl']]])echo "${BRANCH_NAME} ${env.BRANCH_NAME}"}{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mesos-plugin] (JENKINS-27670) Deadlock when calling supervise()
Title: Message Title Carlos Sanchez resolved as Fixed This issue is fixed with PR https://github.com/jenkinsci/mesos-plugin/pull/196 Jenkins / JENKINS-27670 Deadlock when calling supervise() Change By: Carlos Sanchez Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-15931) Build is hanging in xUnit plugin processing
Title: Message Title Francis Upton updated an issue Jenkins / JENKINS-15931 Build is hanging in xUnit plugin processing Change By: Francis Upton Summary: Build is hanging on newly created EC2 slaves in xUnit plugin processing Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-15931) Build is hanging on newly created EC2 slaves
Title: Message Title Eckhard Völlm edited a comment on JENKINS-15931 Re: Build is hanging on newly created EC2 slaves Yes, we do not have ec2 plugin in use, i can confirm that.And we decided to try an upgrade of Java version now, using oracle 1.8.0_66-b17 since last week,Since we did that, there was no hanging, but time is too short to say something, not many test were running since snowzilla hit eastcost. Propose to switch Subject, to "Build is hanging in xUnit plugin processing" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-15931) Build is hanging on newly created EC2 slaves
Title: Message Title Eckhard Völlm commented on JENKINS-15931 Re: Build is hanging on newly created EC2 slaves Yes, we do not have ec2 plugin in use, i can confirm that. And we decided to try an upgrade of Java version now, using oracle 1.8.0_66-b17 since last week, Since we did that, there was no hanging, but time is too short to say something, not many test were running since snowzilla hit eastcost. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32328) A custom update center is not consulted for Tool installer metadata
Title: Message Title dogfood commented on JENKINS-32328 Re: A custom update center is not consulted for Tool installer metadata Integrated in jenkins_main_trunk #4430 JENKINS-32328 process multiple update-centers for ToolInstallers (Revision 80a6a9e7cbc1f2c7ecbf7c1161c55dae8c0233e0) JENKINS-32328 handling tool Installers which do not have the default (Revision e7f88146baf87dc96d723255e522bf51471f6701) Result = SUCCESS valentina.armenise : 80a6a9e7cbc1f2c7ecbf7c1161c55dae8c0233e0 Files : core/src/main/java/hudson/model/DownloadService.java test/src/test/resources/hudson/model/hudson.tasks.Maven.MavenInstaller1.json test/src/test/resources/hudson/model/hudson.tools.JDKInstallerResult.json core/src/main/java/hudson/tools/ToolInstaller.java test/src/test/resources/hudson/model/hudson.tasks.Ant.AntInstaller3.json test/src/test/resources/hudson/model/hudson.tasks.Ant.AntInstallerResult.json test/src/test/resources/hudson/model/hudson.tools.JDKInstaller3.json test/src/test/resources/hudson/model/hudson.tasks.Ant.AntInstaller2.json test/src/test/resources/hudson/model/hudson.tasks.Maven.MavenInstallerResult.json test/src/test/resources/hudson/model/hudson.tasks.Maven.MavenInstaller2.json test/src/test/resources/hudson/model/hudson.tools.JDKInstaller2.json test/src/test/resources/hudson/model/hudson.tasks.Ant.AntInstaller1.json core/src/main/java/hudson/tools/JDKInstaller.java test/src/test/resources/hudson/model/hudson.tools.JDKInstaller1.
[JIRA] [xunit-plugin] (JENKINS-15931) Build is hanging on newly created EC2 slaves
Title: Message Title Francis Upton updated an issue Jenkins / JENKINS-15931 Build is hanging on newly created EC2 slaves Change By: Francis Upton Component/s: ec2-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-15931) Build is hanging on newly created EC2 slaves
Title: Message Title Francis Upton commented on JENKINS-15931 Re: Build is hanging on newly created EC2 slaves Does not appear to be an ec2 plugin issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
