[JIRA] (JENKINS-37130) Could not initialize class JavaLibCHelper - ERROR: Error cloning remote repo 'origin'
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-37130 Could not initialize class JavaLibCHelper - ERROR: Error cloning remote repo 'origin' Change By: Mark Waite Summary: Could not initialize class JavaLibCHelper - ERROR: Error cloning remote repo 'origin' 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-37794) JGit filters tags with "/" in their name, CliGit does not
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-37794 JGit filters tags with "/" in their name, CliGit does not Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30896) Unoptimized node & log storage
Title: Message Title Sam Van Oort commented on JENKINS-30896 Re: Unoptimized node & log storage Note for later implementation of log consolidation: WorkflowRun.copyLogs + logNodeMessage (writing to a WorkflowConsoleLogger) IIUC there's a StreamBuildListener attached to the WorkflowRun which gets log outputs, this is sliced and copied into a new log file for each FlowNode periodically (at the least upon completion, via copyLogs), which becomes part of a LogActionImpl. If we wanted we could write directly to an output file, and then use an alternate LogAction version that gives offsets within this file. Interleaved streams from parallels are an issue though (probably we need to keep separate log streams for each, numbered by parallel # or iota and branch order, I.E. 1-1.log, 1-2.log, 2-1.log, 2-2.log). Would need to create new StreamBuildListeners in this case. Possible case also for something like NIO w/ channels (since we're basically redirecting inputs from one channel into multiplexing (reactor pattern?). 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-38290) Make available a System Property to change Context.REFERRAL to IGNORE
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38290 Re: Make available a System Property to change Context.REFERRAL to IGNORE Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/eca9c9e2421acf7b9acb2be3fe328bcd03f15fb7 Log: Merge pull request #42 from fbelzunc/JENKINS-38290 JENKINS-38290 System Property to be able to ignore referrals Compare: https://github.com/jenkinsci/active-directory-plugin/compare/d6f2723e98ca...eca9c9e2421a 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-38290) Make available a System Property to change Context.REFERRAL to IGNORE
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38290 Re: Make available a System Property to change Context.REFERRAL to IGNORE Code changed in jenkins User: Félix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/2f48cd2f5a818664b4f424e5a6a2873babf58605 Log: JENKINS-38290 System Property to be able to ignore referrals 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-35385) Findbug issue - Not able to see list of committers.
Title: Message Title David van Laatum closed an issue as Incomplete no response Jenkins / JENKINS-35385 Findbug issue - Not able to see list of committers. Change By: David van Laatum Status: Open Closed Resolution: Incomplete 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-37494) Health Report publishing wrong result if you have running concurrent jobs
Title: Message Title David van Laatum commented on JENKINS-37494 Re: Health Report publishing wrong result if you have running concurrent jobs Depending on what you're including in the email ie is it build stats, unit tests or files from the workspace if you use the same workspace for concurrent builds that is going to happen as they will interfere with each other. 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-37594) email-ext plugin can't recognize content file in workspace
Title: Message Title David van Laatum commented on JENKINS-37594 Re: email-ext plugin can't recognize content file in workspace Works for me on osx. see screen shots 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-37594) email-ext plugin can't recognize content file in workspace
Title: Message Title David van Laatum updated an issue Jenkins / JENKINS-37594 email-ext plugin can't recognize content file in workspace Change By: David van Laatum Attachment: Screen Shot 2016-09-17 at 12.04.21 PM.png Attachment: Screen Shot 2016-09-17 at 12.04.57 PM.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37774) Adding attachments causes duplicate attachments to be added
Title: Message Title David van Laatum commented on JENKINS-37774 Re: Adding attachments causes duplicate attachments to be added I assume you meant Email Ext Plugin: 2.47 not 2.4.7 I have just tried to reproduce without success so going to need more details such as exact job config 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-27396) Elastic timeout
Title: Message Title ikedam commented on JENKINS-27396 Re: Elastic timeout pipeline-graph-analysis-plugin::StatusAndTiming#computeChunkTiming is available for get execution durations. 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-35367) EMail-Ext Extended Pipeline Support - Templates
Title: Message Title David van Laatum commented on JENKINS-35367 Re: EMail-Ext Extended Pipeline Support - Templates The only option at the moment is to build the contents of the email programmatically in the groovy script. I have sent a email to the token macro plugin's maintainer asking for an update 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-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Jesse Glick updated JENKINS-28447 Jenkins / JENKINS-28447 CpsScmFlowDefinition does not resolve variables Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title Jesse Glick updated JENKINS-27295 Jenkins / JENKINS-27295 Boolean parameters injected as String Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29952) Allow access to environment variables as Groovy variables
Title: Message Title Jesse Glick updated JENKINS-29952 Jenkins / JENKINS-29952 Allow access to environment variables as Groovy variables Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30910) Job parameters should be exposed as environment variables
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30910 Job parameters should be exposed as environment variables Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: workflow-cps-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-30910) Job parameters should be exposed as environment variables
Title: Message Title Jesse Glick updated JENKINS-30910 Jenkins / JENKINS-30910 Job parameters should be exposed as environment variables Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38297) assertEqualDataBoundBeans should support DataBoundSetter for members
Title: Message Title ikedam commented on JENKINS-38297 Re: assertEqualDataBoundBeans should support DataBoundSetter for members https://github.com/jenkinsci/jenkins-test-harness/pull/34 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-38297) assertEqualDataBoundBeans should support DataBoundSetter for members
Title: Message Title ikedam started work on JENKINS-38297 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38297) assertEqualDataBoundBeans should support DataBoundSetter for members
Title: Message Title ikedam updated JENKINS-38297 Jenkins / JENKINS-38297 assertEqualDataBoundBeans should support DataBoundSetter for members Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title Jesse Glick started work on JENKINS-27295 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38297) assertEqualDataBoundBeans should support DataBoundSetter for members
Title: Message Title ikedam commented on JENKINS-38297 Re: assertEqualDataBoundBeans should support DataBoundSetter for members @DataBoundSetter support for members looks starts from stapler-1.220 https://github.com/stapler/stapler/commit/425314ba247ab90791ca3ba0507ab5b8e25d2a2d 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-38297) assertEqualDataBoundBeans should support DataBoundSetter for members
Title: Message Title
ikedam created an issue
Jenkins / JENKINS-38297
assertEqualDataBoundBeans should support DataBoundSetter for members
Issue Type:
Improvement
Assignee:
ikedam
Components:
jenkins-test-harness
Created:
2016/Sep/17 1:28 AM
Environment:
jenkins-test-harnes-2.14
Priority:
Minor
Reporter:
ikedam
JENKINS-36398 added the feature to support setters with @DataBoundStter
private String field;
@DataBoundSetter
public void setField(String field) {...}
public String getField() {...}
But it doesn't work with members with @DataBoundSetter.
@DataBoundSetter
public String field;
[JIRA] (JENKINS-37568) Email Ext Plugin broke the Jenkins
Title: Message Title David van Laatum closed an issue as Not A Defect Jenkins / JENKINS-37568 Email Ext Plugin broke the Jenkins Change By: David van Laatum Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-36398) assertEqualDataBoundBeans for classes with DataBoundSetter
Title: Message Title ikedam closed an issue as Fixed Jenkins / JENKINS-36398 assertEqualDataBoundBeans for classes with DataBoundSetter Change By: ikedam 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-36398) assertEqualDataBoundBeans for classes with DataBoundSetter
Title: Message Title ikedam resolved as Fixed Fixed in jenkins-test-harness 2.11 Jenkins / JENKINS-36398 assertEqualDataBoundBeans for classes with DataBoundSetter Change By: ikedam Status: In Progress 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-37959) Failed to send out e-mail javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful
Title: Message Title David van Laatum closed an issue as Incomplete Insufficient details Jenkins / JENKINS-37959 Failed to send out e-mail javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful Change By: David van Laatum Status: Open Closed Resolution: Incomplete 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
[JIRA] (JENKINS-37961) Failed to send out e-mail com.sun.mail.smtp.SMTPSendFailedException: [EOF]
Title: Message Title David van Laatum closed an issue as Incomplete Insufficient details Jenkins / JENKINS-37961 Failed to send out e-mail com.sun.mail.smtp.SMTPSendFailedException: [EOF] Change By: David van Laatum Status: Open Closed Resolution: Incomplete 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-38063) An attempt to send an e-mail to empty list of recipients, ignored.
Title: Message Title David van Laatum commented on JENKINS-38063 Re: An attempt to send an e-mail to empty list of recipients, ignored. Adding recipients from trigger recipient list This tells me you are using the default config of using a recipient list have you entered recipients into the list? If you have other triggers then they are not being triggered 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-38063) An attempt to send an e-mail to empty list of recipients, ignored.
Title: Message Title David van Laatum closed an issue as Not A Defect Jenkins / JENKINS-38063 An attempt to send an e-mail to empty list of recipients, ignored. Change By: David van Laatum Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title ikedam updated JENKINS-26521 Jenkins / JENKINS-26521 timeout step should support breaking on inactivity, not just a fixed duration Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title ikedam commented on JENKINS-26521 Re: timeout step should support breaking on inactivity, not just a fixed duration Pipeline now supports ConsoleLogFilter (JENKINS-27392) ! https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/18 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-38225) TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD)
Title: Message Title Félix Belzunce Arcos commented on JENKINS-38225 Re: TokenGroups-lookup is filtered/limited to user-domain (in Forest/Multi-Domain AD) Hello, what bindName are you using? Is it in format CN="", ... or you are using the displayedName? 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-29952) Allow access to environment variables as Groovy variables
Title: Message Title Jesse Glick started work on JENKINS-29952 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title ikedam started work on JENKINS-26521 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-26521 timeout step should support breaking on inactivity, not just a fixed duration Change By: ikedam Assignee: Andrew Bayer ikedam 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-30910) Job parameters should be exposed as environment variables
Title: Message Title Jesse Glick started work on JENKINS-30910 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30910) Job parameters should be exposed as environment variables
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-30910 Job parameters should be exposed as environment variables Change By: Jesse Glick Assignee: Andrew Bayer Jesse Glick 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-38290) Make available a System Property to change Context.REFERRAL to IGNORE
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-38290 Make available a System Property to change Context.REFERRAL to IGNORE Change By: Félix Belzunce Arcos Make available a System Property to change Context.REFERRAL to IGNOREBy default we use FOLLOWhttps://github.com/jenkinsci/active-directory-plugin/blob/d6bb427d070f35acf376f73de041d02df3be2996/src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java#L517http://docs.oracle.com/javase/jndi/tutorial/ldap/referral/jndi.html This will be done through the Java Argument -Dhudson.plugins.active_directory.referral.ignore=true in case you want to set-up 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-38296) Cannot hpi:run Folders Plugin
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-38296 Cannot hpi:run Folders Plugin Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 2016/Sep/17 12:07 AM Priority: Minor Reporter: Daniel Beck Due to the test-scoped dependency on matrix-auth, hpi:run will detect a cycle and disable both. Workaround: Remove the dependency and delete src/test. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title
Joshua Spiewak commented on JENKINS-2111
Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace
FWIW, I wrote this today:
Closure cleanMultiBranchWorkspaces
cleanMultiBranchWorkspaces = { item ->
if (item instanceof com.cloudbees.hudson.plugins.folder.Folder) {
if (item.name == 'archive') {
println "Skipping $item"
} else {
println "Found folder $item, checking its items"
item.items.each { cleanMultiBranchWorkspaces(it) }
}
} else if (item instanceof org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject) {
println "Found a multi-branch workflow $item"
workspaces = jenkins.model.Jenkins.instance.nodes.collect { it.getWorkspaceFor(item).listDirectories() }.flatten().findAll { it != null }
def activeBranches = item.items.name
println "Active branches = $activeBranches"
if (workspaces) {
workspaces.removeAll { workspace ->
activeBranches.any { workspace.name.startsWith(it) }
}
workspaces.each {
println "Removing workspace $it.name on ${it.toComputer().name} without active branch"
}
}
}
}
jenkins.model.Jenkins.instance.items.each { cleanMultiBranchWorkspaces(it) }
Need to switch the startsWith to a regex for more exact matching. Created a job with the Groovy plugin executing this as a system script.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Andrew Bayer commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace Also, blergh, finding all the workspaces for a Pipeline job is...hard. node.getWorkspaceFor isn't useful here. I think we'd need to look for all FlowNode on a WorkflowRun for a given WorkflowJob to see if they've got a WorkspaceAction and then act on those WorkspaceAction...which is demented. Oy. 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-38295) Let users know that displayedName should be used with several domains
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38295 Re: Let users know that displayedName should be used with several domains Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/50db0a024404daa8189751851cac94c60555d3a6 Log: Merge pull request #44 from fbelzunc/JENKINS-38295 JENKINS-38294 Add a warning when displayed name is not used with several domains Compare: https://github.com/jenkinsci/active-directory-plugin/compare/3163157ce6a6...50db0a024404 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-28222) Thread labels in console output don't persist after a node block
Title: Message Title Jesse Glick updated JENKINS-28222 Jenkins / JENKINS-28222 Thread labels in console output don't persist after a node block Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38294) When validating the ad set-up with several domains the check fails due a space after the comma
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38294 Re: When validating the ad set-up with several domains the check fails due a space after the comma Code changed in jenkins User: Félix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/c76d69179ba72dad4633e18e7a014f99892ad2c3 Log: JENKINS-38294 Add a warning when displayed name is not used with several domains 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-28222) Thread labels in console output don't persist after a node block
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28222 Re: Thread labels in console output don't persist after a node block Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java src/test/java/org/jenkinsci/plugins/workflow/job/WorkflowRunTest.java http://jenkins-ci.org/commit/workflow-job-plugin/1f24b2e61d865bdbb1ab9b2023a61074537e74e1 Log: [FIXED JENKINS-28222] Branch labels were being incorrectly skipped after an end block node. 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-38294) When validating the ad set-up with several domains the check fails due a space after the comma
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38294 Re: When validating the ad set-up with several domains the check fails due a space after the comma Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/50db0a024404daa8189751851cac94c60555d3a6 Log: Merge pull request #44 from fbelzunc/JENKINS-38295 JENKINS-38294 Add a warning when displayed name is not used with several domains Compare: https://github.com/jenkinsci/active-directory-plugin/compare/3163157ce6a6...50db0a024404 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-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title
Jesse Glick commented on JENKINS-28447
Re: CpsScmFlowDefinition does not resolve variables
I think I have finally reproduced this in a test, the build ending with something like
…
> git rev-parse origin/${VERSION}^{commit} # timeout=10
> git rev-parse ${VERSION}^{commit} # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Finished: FAILURE
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-28447) CpsScmFlowDefinition does not resolve variables
Title: Message Title Jesse Glick started work on JENKINS-28447 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Andrew Bayer commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace Jesse Glick Feels to me like Job.performDelete may be more of the right place to do this? 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-35081) Separate authorization configuration page
Title: Message Title stephenconnolly assigned an issue to stephenconnolly Jenkins / JENKINS-35081 Separate authorization configuration page Change By: stephenconnolly Assignee: stephenconnolly 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-38295) Let users know that displayedName should be used with several domains
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-38295 Let users know that displayedName should be used with several domains Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: Screen Shot 2016-09-17 at 01.40.01.png Components: active-directory-plugin Created: 2016/Sep/16 11:40 PM Priority: Minor Reporter: Félix Belzunce Arcos Let users know that displayedName should be used with several domains Add Comment
[JIRA] (JENKINS-30910) Job parameters should be exposed as environment variables
Title: Message Title Andrew Bayer commented on JENKINS-30910 Re: Job parameters should be exposed as environment variables Jesse Glick Why don't we have an equivalent to this in WorkflowRun? If we did, we'd pick up ParameterAction contributions automatically... 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-38246) Enable viewing current github API rate status in UI
Title: Message Title CloudBees Inc. commented on JENKINS-38246 Re: Enable viewing current github API rate status in UI Are you using anonymous access for scanning the organization? 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-30910) Job parameters should be exposed as environment variables
Title: Message Title Andrew Bayer commented on JENKINS-30910 Re: Job parameters should be exposed as environment variables Patrick Wolf So I think input step return values are a different thing than ParameterValue... 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-38294) When validating the ad set-up with several domains the check fails due a space after the comma
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38294 When validating the ad set-up with several domains the check fails due a space after the comma Change By: SCM/JIRA link daemon 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-38294) When validating the ad set-up with several domains the check fails due a space after the comma
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38294 Re: When validating the ad set-up with several domains the check fails due a space after the comma Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/3163157ce6a68abbfff89a9e1c2d06ad0435b2aa Log: Merge pull request #43 from fbelzunc/JENKINS-38294 [FIXED JENKINS-38294] Trim the domains so a space after comma does not get introduced Compare: https://github.com/jenkinsci/active-directory-plugin/compare/d6bb427d070f...3163157ce6a6 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-38294) When validating the ad set-up with several domains the check fails due a space after the comma
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38294 Re: When validating the ad set-up with several domains the check fails due a space after the comma Code changed in jenkins User: Félix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/936986143c17f4f8d43a93d8dde21f74d3ca06d8 Log: JENKINS-38294 Trim the domains so a space after comma does not get affected 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-38227) Allow letting CMake choose the generator
Title: Message Title Craig Scott commented on JENKINS-38227 Re: Allow letting CMake choose the generator As a workaround in the meantime, the Ninja generator should be supported on all major platforms. 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-37782) Pipeline Config: Unable to refer to environment var in input string
Title: Message Title Andrew Bayer resolved as Not A Defect Jenkins / JENKINS-37782 Pipeline Config: Unable to refer to environment var in input string Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-38294) When validating the ad set-up with several domains the check fails due a space after the comma
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-38294 When validating the ad set-up with several domains the check fails due a space after the comma Change By: Félix Belzunce Arcos Attachment: Screen Shot 2016-09-17 at 00.25.08.png Attachment: Screen Shot 2016-09-17 at 00.25.19.png As showed in the images, there is a false error when checking the ad set-up - when it is working properly. !Screen Shot 2016-09-17 at 00.25.08.png|thumbnail! !Screen Shot 2016-09-17 at 00.25.19.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You
[JIRA] (JENKINS-38294) When validating the ad set-up with several domains the check fails due a space after the comma
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-38294 When validating the ad set-up with several domains the check fails due a space after the comma Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Sep/16 10:51 PM Priority: Minor Reporter: Félix Belzunce Arcos Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) --
[JIRA] (JENKINS-31801) Using Throttle Concurrent Builds in a Pipeline
Title: Message Title Andrew Bayer commented on JENKINS-31801 Re: Using Throttle Concurrent Builds in a Pipeline fwiw, I'm going to try to take another look at this soon. 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-38259) "IllegalArgumentException: folder must not be null" when cloning vm
Title: Message Title Greg Smith commented on JENKINS-38259 Re: "IllegalArgumentException: folder must not be null" when cloning vm It turned out that this problem was related to permissions – the user in question did not have the correct permissions to the folder, so the "getParent()" was null – thus the error message. It would be nice to have a better error, but as this problem was resolved by changing the user permissions, setting to minor. Hopefully someone else find this helpful in the future. 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-37839) Many users are getting error while opening jenkins
Title: Message Title Janario Oliveira commented on JENKINS-37839 Re: Many users are getting error while opening jenkins Is this in the right component? https://github.com/jenkinsci/http-request-plugin > A plugin to make request as a job step. If it is, can you give more information? Can you copy the entire exception? If it is not in the right component, can you move to the right one. 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-38286) NPE in snippet generator
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38286 NPE in snippet generator Change By: SCM/JIRA link daemon 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-38286) NPE in snippet generator
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38286 Re: NPE in snippet generator Code changed in jenkins User: James Nord Path: src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java http://jenkins-ci.org/commit/cucumber-testresult-plugin/edd718966bbb7023d7be69d65b99d438757b9808 Log: [FIXED JENKINS-38286] prevent NPE in snippet generator 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-37109) Ability to use Credentials for Basic/Digest Authentications
Title: Message Title Janario Oliveira closed an issue as Duplicate Jenkins / JENKINS-37109 Ability to use Credentials for Basic/Digest Authentications Change By: Janario Oliveira 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-37109) Ability to use Credentials for Basic/Digest Authentications
Title: Message Title Janario Oliveira resolved as Duplicate Jenkins / JENKINS-37109 Ability to use Credentials for Basic/Digest Authentications Change By: Janario Oliveira Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38293) Unable to create Jira issue using Jira plugin for jenkins
Title: Message Title Prabhu Manisekar created an issue Jenkins / JENKINS-38293 Unable to create Jira issue using Jira plugin for jenkins Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2016/Sep/16 10:13 PM Priority: Major Reporter: Prabhu Manisekar I have set up the 2.2.1 version of Jira plugin for jenkins with my jenkins instance. I am having issue with "Create jira issue" upon job failure. The update relevant jira issue part is working fine. The job faile ar create jira issue step Below is the error that i am getting (from console output) ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.jira.JiraCreateIssueNotifier.getStatus(JiraCreateIssueNotifier.java:186) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:332) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:133) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Build step 'Create Jira Issue' marked build as failure Need help fixing it.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Code changed in jenkins User: Thorsten Scherler Path: src/test/js/log-karaoke/parallelStages.js http://jenkins-ci.org/commit/blueocean-acceptance-test/bacaf455453a65ab50b0797e681007f46fe26ba3 Log: JENKINS-37962 better documentation of the steps 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-38292) Sauce Connect 4.3.16: Error launching Sauce Connect
Title: Message Title Akshar Panchal created an issue Jenkins / JENKINS-38292 Sauce Connect 4.3.16: Error launching Sauce Connect Issue Type: Bug Assignee: Gavin Mogan Components: sauce-ondemand-plugin Created: 2016/Sep/16 9:59 PM Environment: Jenkins Version: 2.7.4 OS: Debian Linux XXX 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux Java: 1.8 Priority: Major Reporter: Akshar Panchal This is issue seems to intermittent. We have down stream job which kicks off 2 Jenkins job that starts sauce connect with different tunnel identifier, scproxy-port and se-port. We have been experience this issue quite oftenStack Trace: Launching Sauce Connect on 172.17.0.1 /data/jenkins/sc-4.3.16-linux/bin/sc already exists, so not extracting Error launching Sauce Connect Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process ERROR: Failed to parse POMs com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Error launching Sauce Connect at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:335) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:918) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:373) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:655) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1741)
[JIRA] (JENKINS-38256) Merged branches are still processed
Title: Message Title Dominik Bartholdi edited a comment on JENKINS-38256 Re: Merged branches are still processed I opened a request to enhance the REST api on bitbucket: https:// jira bitbucket . atlassian.com org / browse site / BSERV-9167 master/issues/13311/ 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-38291) Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name
Title: Message Title
Oleg Nenashev created an issue
Jenkins / JENKINS-38291
Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name
Issue Type:
Bug
Assignee:
Unassigned
Components:
logstash-plugin
Created:
2016/Sep/16 9:38 PM
Priority:
Major
Reporter:
Oleg Nenashev
Elasticsearch 2 does not support dots in field names. However, it's a perfectly valid case on Windows. Java system properties also may contain dots. If such variable appears in the logstash plugin, it just fails to report the entire build. In my case it is "com.apple.java.jvmTask" on Mac
{
"data": {
"id": "40",
"projectName": "TestLogstash",
"displayName": "#40",
"fullDisplayName": "TestLogstash #40",
"url": "job/TestLogstash/40/",
"buildHost": "remoteSlave",
"buildLabel": "master",
"buildNum": 40,
"buildDuration": 33,
"rootProjectName": "TestLogstash",
"rootProjectDisplayName": "#40",
"rootBuildNum": 40,
"buildVariables": {
"PATH": "/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin",
"JAVA_ARCH": "x86_64",
.
"__CF_USER_TEXT_ENCODING": "0x1F6:0x0:0x0",
"com.apple.java.jvmTask": "CommandLine",
"LC_CTYPE": "UTF-8",
"HOME": "/Users/nenashev",
"SHLVL": "1"
},
"sensitiveBuildVariables": [
"FOO"
]
},
"message": [
"+ echo 'Hello, world! Password is BAR'"
],
"source": "jenkins",
"source_host": "http://localhost:8080/jenkins/",
"@timestamp": "2016-09-16T14:29:01-0700",
"@version": 1
}
[JIRA] (JENKINS-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38152 Re: Jenkinsfile schema Java API as WorkflowRun action Code changed in jenkins User: Andrew Bayer Path: src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/Utils.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTAgent.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTBranch.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTBuildCondition.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTElement.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTEnvironment.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTNamedArgumentList.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTNotifications.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPipelineDef.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPositionalArgumentList.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPostBuild.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTSingleArgument.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStages.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStep.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTTools.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTTreeStep.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Converter.groovy src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/actions/ExecutionModelAction.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/f4899b814f15f8dadf153c70f0c3a103f2d757f1 Log: First work on JENKINS-38152 - action/stripped stages Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38256) Merged branches are still processed
Title: Message Title Dominik Bartholdi commented on JENKINS-38256 Re: Merged branches are still processed I opened a request to enhance the REST api on bitbucket: https://jira.atlassian.com/browse/BSERV-9167 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-38290) Make available a System Property to change Context.REFERRAL to IGNORE
Title: Message Title Félix Belzunce Arcos started work on JENKINS-38290 Change By: Félix Belzunce Arcos Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38290) Make available a System Property to change Context.REFERRAL to IGNORE
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-38290 Make available a System Property to change Context.REFERRAL to IGNORE Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Sep/16 9:29 PM Priority: Minor Reporter: Félix Belzunce Arcos Make available a System Property to change Context.REFERRAL to IGNORE By default we use FOLLOW https://github.com/jenkinsci/active-directory-plugin/blob/d6bb427d070f35acf376f73de041d02df3be2996/src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java#L517 http://docs.oracle.com/javase/jndi/tutorial/ldap/referral/jndi.html Add Comment
[JIRA] (JENKINS-32033) Support for multiple domain controllers
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32033 Re: Support for multiple domain controllers Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/d6bb427d070f35acf376f73de041d02df3be2996 Log: Merge pull request #41 from fbelzunc/JENKINS-32033 [FIXED JENKINS-32033] Support for multiple domain controllers Compare: https://github.com/jenkinsci/active-directory-plugin/compare/2e79649b3119...d6bb427d070f 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-32033) Support for multiple domain controllers
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32033 Support for multiple domain controllers Change By: SCM/JIRA link daemon Status: In Progress 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-32033) Support for multiple domain controllers
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32033 Re: Support for multiple domain controllers Code changed in jenkins User: Félix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/fbbb85c066db5d0a976d37349176c586ea67d0f9 Log: JENKINS-32033 Support for multiple domain controllers 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-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Code changed in jenkins User: Thorsten Scherler Path: src/test/js/log-karaoke/parallelStages.js http://jenkins-ci.org/commit/blueocean-acceptance-test/f093dfbac61d82b8a6b2b506f9205bd2b82ae5d0 Log: JENKINS-37962 Update comment to describe test case 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-38289) ansiblePlaybook pipeline step does not respect environment
Title: Message Title
Andrew Gunnerson created an issue
Jenkins / JENKINS-38289
ansiblePlaybook pipeline step does not respect environment
Issue Type:
Bug
Assignee:
Jean-Christophe Sirot
Components:
ansible-plugin, pipeline
Created:
2016/Sep/16 9:15 PM
Environment:
Jenkins 2.7.3 Pipeline plugin 2.3 Ansible plugin 0.5
Priority:
Minor
Reporter:
Andrew Gunnerson
The "ansiblePlaybook" step doesn't seem to respect variables set with "env.NAME = VALUE" or with "withEnv([NAME: VALUE]) {...}". In my particular case, ANSIBLE_CONFIG needs to be set so that a custom Ansible configuration file can be used. I've created a simple pipeline job to illustrate the issue (linked below). Despite ANSIBLE_CONFIG being set, it is not present in the ansible-playbook process's environment (confirmed by looking at /proc/ANSIBLE_PID/environ). Pipeline job: https://gist.github.com/agunnerson-ibm/dd065a950269d68fbb84e64425bad08e#file-pipeline-groovy Job log: https://gist.github.com/agunnerson-ibm/dd065a950269d68fbb84e64425bad08e#file-job-log (Note how it loads /etc/ansible/ansible.cfg instead of the custom config)
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineActivity.js src/test/js/smoke.js http://jenkins-ci.org/commit/blueocean-acceptance-test/1f77a931ec5579632046d9616470fb832913d939 Log: Merge remote-tracking branch 'origin/master' into JENKINS-37962 Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/0255dc1c1dfc...1f77a931ec55 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-36615) Unable to run multibranch pipeline with '/' the name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-36615 Re: Unable to run multibranch pipeline with '/' the name Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineActivity.js src/test/js/smoke.js http://jenkins-ci.org/commit/blueocean-acceptance-test/8d50b41ab0288bf38257d471d6ce6e9fb1d89983 Log: JENKINS-36615 Add test for clicking on run button then on the emerging toast the open (#41) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/log-karaoke/noStages.js src/test/js/log-karaoke/parallelStages.js src/test/resources/test_scripts/parallel-stages.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/0255dc1c1dfc9d33396b22418dfa73a0ff643fc5 Log: JENKINS-37962 Add test for clicking on run button then on the emerging toast the open 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-27396) Elastic timeout
Title: Message Title Jesse Glick assigned an issue to ikedam Jenkins / JENKINS-27396 Elastic timeout Change By: Jesse Glick Assignee: Andrew Bayer ikedam 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-37701) Manual trigger not running in build pipeline
Title: Message Title John Lozano commented on JENKINS-37701 Re: Manual trigger not running in build pipeline Same issue here with jenkins 2.21 and Build Pipeline 1.5.4 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-18464) Build Pipeline and Join plugin do not play nicely together
Title: Message Title John McGehee edited a comment on JENKINS-18464 Re: Build Pipeline and Join plugin do not play nicely together After attending At the Jenkins World conference over the past two days, I think it might be better saw the community moving to use the new _Pipeline_ functionality in place of the mashup of plugins that we have historically had to use. With _Pipeline_ I see dim prospects for further development on the scene these plugins , I suspect that piecemeal solutions like the _Build Pipeline_ and _Join_ plugin will become obsolete which have been superseded by _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-38288) cucumber trend graph does not show up in a pipeline job
Title: Message Title James Nord created an issue Jenkins / JENKINS-38288 cucumber trend graph does not show up in a pipeline job Issue Type: Bug Assignee: James Nord Components: cucumber-testresult-plugin Created: 2016/Sep/16 8:28 PM Environment: cucmber 0.9.6 Priority: Minor Reporter: James Nord cucumber test report trend does not show up in a pipeline job Add Comment
[JIRA] (JENKINS-38287) test history not working in pipeline
Title: Message Title James Nord created an issue Jenkins / JENKINS-38287 test history not working in pipeline Issue Type: Bug Assignee: James Nord Components: cucumber-testresult-plugin Created: 2016/Sep/16 8:27 PM Environment: cucumber-t-r-p 0.9.6 Priority: Minor Reporter: James Nord look at a test in a pipeline using c-t-r-p It does not work. WARNING: owner is null when trying to getTestResultAction. Sep 16, 2016 1:24:43 PM hudson.tasks.test.TestObject getTestResultAction WARNING: owner is null when trying to getTestResultAction. Sep 16, 2016 1:24:43 PM hudson.tasks.test.TestObject getTestResultAction WARNING: owner is null when trying to getTestResultAction. Sep 16, 2016 1:24:43 PM hudson.tasks.test.TestObject getTestResultAction WARNING: owner is null when trying to getTestResultAction. Sep 16, 2016 1:25:23 PM hudson.tasks.test.TestObject getTestResultAction WARNING: owner is null when trying to getTestResultAction. Sep 16, 2016 1:25:23 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.historyAvailable() in /jenkins/job/cucumber-1/3/cucumberTestReport/dates-with-different-date-formats/determine-past-date/history/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.tasks.junit.History.historyAvailable(History.java:72) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at
[JIRA] (JENKINS-35677) build-timeout-plugin cannot be used with pipelines (workflows)
Title: Message Title ikedam commented on JENKINS-35677 Re: build-timeout-plugin cannot be used with pipelines (workflows) Added a note to the Wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin (You might not see that in a day for the server-side caching) 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-35677) build-timeout-plugin cannot be used with pipelines (workflows)
Title: Message Title ikedam resolved as Won't Fix I found it's really difficult to make build-timeout to pipeline, as the mechanism of pipeline is completely different from that of legacy projects (Freestyle, Multiconfiguration, and so on). I thinks it's better to extend timeout feature of pipelines so that it supports same features of build-timeout. There are JIRA issues for that, and I close this issue as "Won't Fix". Elastic timeout: JENKINS-27396 Timeout operations: JENKINS-32228 No activity timeout: JENKINS-26521 Jenkins / JENKINS-35677 build-timeout-plugin cannot be used with pipelines (workflows) Change By: ikedam Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-32033) Support for multiple domain controllers
Title: Message Title Félix Belzunce Arcos started work on JENKINS-32033 Change By: Félix Belzunce Arcos Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32033) Support for multiple domain controllers
Title: Message Title Félix Belzunce Arcos assigned an issue to Félix Belzunce Arcos Jenkins / JENKINS-32033 Support for multiple domain controllers Change By: Félix Belzunce Arcos Assignee: Félix Belzunce Arcos 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-38286) NPE in snippet generator
Title: Message Title James Nord created an issue Jenkins / JENKINS-38286 NPE in snippet generator Issue Type: Bug Assignee: James Nord Components: cucumber-testresult-plugin Created: 2016/Sep/16 8:18 PM Priority: Minor Reporter: James Nord cucumber 0.9.6 [WARNING] Error while serving http://localhost:8080/jenkins/job/cucumber-1/pipeline-syntax/descriptorByName/org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver/checkTestResults java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at
[JIRA] (JENKINS-35677) build-timeout-plugin cannot be used with pipelines (workflows)
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-35677 build-timeout-plugin cannot be used with pipelines (workflows) Change By: ikedam Assignee: ikedam 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-37597) ECS nodes not removed from build executor list
Title: Message Title Ruslan Vlasyuk commented on JENKINS-37597 Re: ECS nodes not removed from build executor list Me too. But I'm using docker swarm plus docker registry and it works like ecs. I've found a script for Jenkins, it could be useful for deleting offline nodes, but it's not a right way. Waiting for this feature for Jenkins 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-25804) Whitelisted signature presets for Java standard APIs and Jenkins core APIs
Title: Message Title Christian Höltje commented on JENKINS-25804 Re: Whitelisted signature presets for Java standard APIs and Jenkins core APIs This ticket is a bit open-ended. What's the conditions that needed to be satisfied to mark this ticket closed? The plugin already ships with a small static whitelist. On a clean 2.7.4 Jenkins instance the "In-process Script Approval" is empty. 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-27396) Elastic timeout
Title: Message Title
Jesse Glick commented on JENKINS-27396
Re: Elastic timeout
stage('Build') {
node {
checkout scm
timeout(id: 'main', initial: 10, percentage: 150) {
sh 'make'
}
stash name: 'bin', includes: 'a.out'
}
}
stage('Test') {
node {
unstash 'bin'
timeout(id: 'test', initial: 60, percentage: 150) {
sh 'make test'
}
}
}
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.
