[JIRA] [git-plugin] (JENKINS-31954) Fail to set GIT Source Code Management
Title: Message Title Nico Bollen updated an issue Jenkins / JENKINS-31954 Fail to set GIT Source Code Management Change By: Nico Bollen Environment: Debian, Jenkins 1.640 , gitlab-plugin 1.1.28, git-plugin 2.4.0 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-31954) Fail to set GIT Source Code Management
Title: Message Title Nico Bollen created an issue Jenkins / JENKINS-31954 Fail to set GIT Source Code Management Issue Type: Bug Assignee: Mark Waite Components: git-plugin, gitlab-plugin Created: 08/Dec/15 7:55 AM Environment: Debian, Jenkins 1.640 Labels: exception Priority: Minor Reporter: Nico Bollen After upgrading to v1.640 I get error reports after enabling the GIT Source Code Management and trying to save a job. Add Comment
[JIRA] [memegen-plugin] (JENKINS-31943) Meme generator plugin is broken
Title: Message Title Jon Cairns commented on JENKINS-31943 Re: Meme generator plugin is broken Thanks for reporting this. It's been a long time since I've done anything on the plugin, so I'll familiarise myself with the code again and try and get the API call 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-3195) Cannot update from 1.286 to 1.287 with update center
Title: Message Title SCM/JIRA link daemon commented on JENKINS-3195 Re: Cannot update from 1.286 to 1.287 with update center Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/67c13dab316130468f101a300a3f0f388b8d6736 Log: Noting JENKINS-30304 and JENKINS-3195 from https://github.com/jenkinsci/jenkins/pull/1908 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] [cli] (JENKINS-31776) Extract online-node CLI command from Core to CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31776 Re: Extract online-node CLI command from Core to CLI Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/d3e3c57af098ad337ef7fc26aa45ce99372f10bc Log: Noting JENKINS-31776 from https://github.com/jenkinsci/jenkins/pull/1938 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-30304) Footer hides trend graph links
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30304 Re: Footer hides trend graph links Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/67c13dab316130468f101a300a3f0f388b8d6736 Log: Noting JENKINS-30304 and JENKINS-3195 from https://github.com/jenkinsci/jenkins/pull/1908 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-29059) Always display example build times in Build Periodically section
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29059 Re: Always display example build times in Build Periodically section Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/1fa120197155be439f72f765fca49d3cc8f6d7a1 Log: Noting JENKINS-29059 from https://github.com/jenkinsci/jenkins/pull/1941 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-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node (rather than editing), an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400. I'd propose reusing throwing this same error message upon trying to rename a node over another existing node.Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. 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-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node (rather than editing) , an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400. I'd propose rendering the reusing this same error message upon trying to rename a node over another existing node.Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. 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-29014) REST API Footer Link Doesn't Work from Subpages
Title: Message Title Christopher Simons edited a comment on JENKINS-29014 Re: REST API Footer Link Doesn't Work from Subpages I have submitted a fix for this: Fixed in [ Pull Request PR #1850|https://github.com/jenkinsci/jenkins/pull/1850]. 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-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again (through the UI). Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because job names are trimmed when first created. It seems a sensible solution would be simply to trim the given job for rename operations as well, so that the name-setting behavior is consistent across create/update operations and inadvertent leading/trailing whitespace is removed before it can cause problems. I have submitted a fix for this: Fixed in [ Pull Request PR #1855|https://github.com/jenkinsci/jenkins/pull/1855]. 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-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons edited a comment on JENKINS-31235 Re: /createItem?mode=copy shouldn't require Content-Type header I have submitted a fix for this: Fixed in [ Pull Request PR #1892|https://github.com/jenkinsci/jenkins/pull/1892]. 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-30569) JS error triggered by collapsing build history
Title: Message Title Christopher Simons edited a comment on JENKINS-30569 Re: JS error triggered by collapsing build history I have submitted a fix for this: Fixed in [ Pull Request PR #1856|https://github.com/jenkinsci/jenkins/pull/1856]. 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-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node, an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400 . I'd propose rendering the same error message upon trying to rename a node over another existing node. Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. 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-9346) Improve layout of help text for parameters of git tokens
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-9346 Improve layout of help text for parameters of git tokens Change By: Mark Waite Assignee: Mark Waite 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] [throttle-concurrent-builds-plugin] (JENKINS-31801) Using Throttle Concurrent Builds in a WorkFlow
Title: Message Title Oleg Nenashev edited a comment on JENKINS-31801 Re: Using Throttle Concurrent Builds in a WorkFlow [~daveml]. Yes, this is a known case (was also a blocker at my previous company). Actually I would say that workflow's implementation is not very suitable to remote hardware management due to the failover robustness (which cannot be disabled IIRC). If Jenkins or its node restarts, WF will continue the execution and will restore *ONLY* it's own state. Currently the state of the remote stuff cannot be restored from Workflow => jobs may behave unreliably. > I've seen a presentation by CloudBees that appears to indicate that a WorkFlow can be used with any pluginI doubt it's correct. Could you refer this presentation? If it is misguiding, we will need to 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] [core] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title
Rob Winch edited a comment on JENKINS-5303
Re: Upgrade Acegi Security to the latest Spring Security release
[~integer] Thank you for the response.{quote}Rob Winch will it be possible to create Proxy or backward compatible migration?{quote}Unfortunately, I don't think there is a way to make the transition completely seamless (i.e. using a Proxy). There may be steps we can provide to make the transition easier. However, this is difficult to determine at this point since I'm not familiar with the Jenkins code base.{quote}If not, could you provide some PR to core (there is a spring-security branch but with 0 work).{quote}Although not clear, my initial intention was to answer any concrete questions that arose when someone else put the PR together.I put together a branch at [rwinch/jeknins/tree/security|https://github.com/rwinch/jenkins/tree/security] that updates to the latest Spring and Spring Security. At the moment, {{mvn -Plight-test test}} passes, but a full build fails. One of the issues appears to be that there are external libraries that will need updating as well (i.e. matrix-auth). There is also some clean up that needs to be done (i.e. whitespace changes that should be removed, etc).I'm not certain I will get time to spend on this again in the near future. Perhaps someone can take what I have put together and polish it?Cheers,Rob PS: At this point I'm fully relying on the tests to catch any errors. it is possible there are logic errors in my changes as I went through them rather abruptly
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-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Rob Winch commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release Kanstantsin Shautsou Thank you for the response. Rob Winch will it be possible to create Proxy or backward compatible migration? Unfortunately, I don't think there is a way to make the transition completely seamless (i.e. using a Proxy). There may be steps we can provide to make the transition easier. However, this is difficult to determine at this point since I'm not familiar with the Jenkins code base. If not, could you provide some PR to core (there is a spring-security branch but with 0 work). Although not clear, my initial intention was to answer any concrete questions that arose when someone else put the PR together. I put together a branch at rwinch/jeknins/tree/security that updates to the latest Spring and Spring Security. At the moment, mvn -Plight-test test passes, but a full build fails. One of the issues appears to be that there are external libraries that will need updating as well (i.e. matrix-auth). There is also some clean up that needs to be done (i.e. whitespace changes that should be removed, etc). I'm not certain I will get time to spend on this again in the near future. Perhaps someone can take what I have put together and polish it? Cheers, Rob 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] [throttle-concurrent-builds-plugin] (JENKINS-31801) Using Throttle Concurrent Builds in a WorkFlow
Title: Message Title Oleg Nenashev commented on JENKINS-31801 Re: Using Throttle Concurrent Builds in a WorkFlow Dave Lawrence. Yes, this is a known case (was also a blocker at my previous company). Actually I would say that workflow's implementation is not very suitable to remote hardware management due to the failover robustness (which cannot be disabled IIRC). > I've seen a presentation by CloudBees that appears to indicate that a WorkFlow can be used with any plugin I doubt it's correct. Could you refer this presentation? If it is misguiding, we will need to 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] [git-plugin] (JENKINS-9346) Improve layout of help text for parameters of git tokens
Title: Message Title Oleg Nenashev commented on JENKINS-9346 Re: Improve layout of help text for parameters of git tokens Andrew Bayer, The comment above is related to this merge: https://github.com/jenkinsci/jenkins/commit/0597f3c4c6f24db9352e8e19ec0b89ed7194697d . I suppose the committer's branch was just misnamed. I'm not working on this 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] [git-plugin] (JENKINS-9346) Improve layout of help text for parameters of git tokens
Title: Message Title Oleg Nenashev assigned an issue to Mark Waite Jenkins / JENKINS-9346 Improve layout of help text for parameters of git tokens Change By: Oleg Nenashev Assignee: Oleg Nenashev Mark Waite 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] [_unsorted] (JENKINS-30793) Build process not completed
Title: Message Title Oleg Nenashev resolved as Incomplete The issue is incomplete. Closing it, because there was no response from the requester Jenkins / JENKINS-30793 Build process not completed Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Incomplete 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] [other] (JENKINS-31872) How can I use a pluging(developed in higher version) in a lower version of Jenkins.
Title: Message Title Oleg Nenashev resolved as Won't Do Jenkins / JENKINS-31872 How can I use a pluging(developed in higher version) in a lower version of Jenkins. Change By: Oleg Nenashev Status: Open Resolved Resolution: Won't Do 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] [other] (JENKINS-31872) How can I use a pluging(developed in higher version) in a lower version of Jenkins.
Title: Message Title Oleg Nenashev commented on JENKINS-31872 Re: How can I use a pluging(developed in higher version) in a lower version of Jenkins. In your code logStream is not being initialized from what I see. Closing the issue as it's not related to Jenkins open-source plugins 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] [other] (JENKINS-31442) Jenkins Wrong Build History (Dec 31, 1969)
Title: Message Title Oleg Nenashev commented on JENKINS-31442 Re: Jenkins Wrong Build History (Dec 31, 1969) I cannot give any details, because there is no plugin code. Most likely CxScanResult's index.jelly explicitly includes sidepanel.jelly, which is not available for the class. It causes the stacktrace, but I doubt it's related to the issue with Build History visualization 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-27092) create a step to abort the build with a NOT_BUILT status
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27092 Re: create a step to abort the build with a NOT_BUILT status Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitStatus.java src/test/java/hudson/plugins/git/GitStatusTest.java http://jenkins-ci.org/commit/git-plugin/2dfd86d27a7cd4089349fd012d7d70a5e827ed81 Log: Test JENKINS-30178 using GitStatus.toString Asserts that job parameter default values are available when a job is started by a notifyCommit. If the notifyCommit includes a sha1 parameter, then the changes for JENKINS-27092 fail to assign parameters their default values. Modifying the GitStatus object to be more easily tested was simpler than using a TestExtension. Should eventually replace the testing misuse of the GitStatus.toString() method with a TestExtension of GitStatus.Listener. 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-30178) Regression: parameters are not set on commit notification
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30178 Re: Regression: parameters are not set on commit notification Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/GitStatus.java src/test/java/hudson/plugins/git/GitStatusTest.java http://jenkins-ci.org/commit/git-plugin/2dfd86d27a7cd4089349fd012d7d70a5e827ed81 Log: Test JENKINS-30178 using GitStatus.toString Asserts that job parameter default values are available when a job is started by a notifyCommit. If the notifyCommit includes a sha1 parameter, then the changes for JENKINS-27092 fail to assign parameters their default values. Modifying the GitStatus object to be more easily tested was simpler than using a TestExtension. Should eventually replace the testing misuse of the GitStatus.toString() method with a TestExtension of GitStatus.Listener. 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-30178) Regression: parameters are not set on commit notification
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30178 Re: Regression: parameters are not set on commit notification Code changed in jenkins User: fbelzunc Path: src/main/java/hudson/plugins/git/GitStatus.java http://jenkins-ci.org/commit/git-plugin/0a661ceaa5da94e92df97a2220a792d1eaa34317 Log: [Fix JENKINS-30178] Add default parameters defined in the job 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-31878) False warning on no sense parameters in the build a job snippet generator
Title: Message Title Jesse Glick commented on JENKINS-31878 Re: False warning on no sense parameters in the build a job snippet generator Something like that, yeah. 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] [credentials-binding-plugin] (JENKINS-31946) Parameter expression may only resolve to a credentials ID
Title: Message Title Jesse Glick commented on JENKINS-31946 Re: Parameter _expression_ may only resolve to a credentials ID When creating new credentials, use the Advanced section to specify a mnemonic ID. 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-31953) Stopping build running parallel branches can doubly deliver stop
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-31953 Stopping build running parallel branches can doubly deliver stop Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: workflow-plugin Created: 08/Dec/15 3:10 AM Priority: Minor Reporter: Jesse Glick Noticed as part of JENKINS-31769: If you run a build with parallel branches, some of which have already completed but others of which are still running, and you abort the build, StepExecution.stop will be run twice on the leaf steps in at least some of the live branches: once directly from CpsFlowExecution.interrupt, once indirectly via ParallelStepExecution.stop. This despite the fact that (as per JENKINS-26148) stop is only supposed to be delivered to the innermost executions. ParallelStepExecution is incorrectly listed as one of these (along with its living children). Reproducible in a test as follows: diff --git a/aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java b/aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java index bfa48b3..57ee251 100644 --- a/aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java +++ b/aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsFlowExecutionTest.java @@ -34,6 +34,7 @@ import java.util.List; import java.util.ListIterator; import org.codehaus.groovy.transform.ASTTransformationVisitor; import org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition; +import org.jenkinsci.plug
[JIRA] [core] (JENKINS-28676) Viewing archived files with UTF8 text shows garbled output
Title: Message Title Jun Gu commented on JENKINS-28676 Re: Viewing archived files with UTF8 text shows garbled output Hi Leon Blakey, did you resolve this issue? I find a same issue like this. Could you provide some solutions? 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] [support-core-plugin] (JENKINS-31952) Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise
Title: Message Title
Owen Wood created an issue
Jenkins / JENKINS-31952
Dockerfile: cloudbees/jenkins needs to be cloudbees/jenkins-enterprise
Issue Type:
Bug
Assignee:
Owen Wood
Components:
support-core-plugin
Created:
08/Dec/15 2:23 AM
Priority:
Minor
Reporter:
Owen Wood
out.println("FROM cloudbees/jenkins:" + fullVersion.substring(0, s));
needs to be
out.println("FROM cloudbees/jenkins-enterprise:" + fullVersion.substring(0, s));
Example of current error:
Pulling repository docker.io/cloudbees/jenkins
Error: image cloudbees/jenkins:1.609.1.1 not found
[JIRA] [core] (JENKINS-27268) "dumb" slave?
Title: Message Title Daniel Beck commented on JENKINS-27268 Re: "dumb" slave? This is currently scheduled for the 2.0 release next year as part of the more general terminology cleanup JENKINS-21095. It's just nicer that way with the required coordinated doc changes etc. Learn more: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0 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-14269) Archive the artifacts does not preserve file exec permissions
Title: Message Title Andrew Barnish commented on JENKINS-14269 Re: Archive the artifacts does not preserve file exec permissions Any chance of a fix to 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] [sloccount-plugin] (JENKINS-31893) Sloccount plugin can not publish cloc result(cloc.xml) when there are 'robotframework' language files(.robot)
Title: Message Title huang zhizhong closed an issue as Won't Fix Jenkins / JENKINS-31893 Sloccount plugin can not publish cloc result(cloc.xml) when there are 'robotframework' language files(.robot) Change By: huang zhizhong Status: Open Closed Resolution: Won't Fix 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] [sloccount-plugin] (JENKINS-31893) Sloccount plugin can not publish cloc result(cloc.xml) when there are 'robotframework' language files(.robot)
Title: Message Title huang zhizhong commented on JENKINS-31893 Re: Sloccount plugin can not publish cloc result(cloc.xml) when there are 'robotframework' language files(.robot) i found this is because cloc.xml not encode as UTF-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] [branch-api-plugin] (JENKINS-31949) CustomOrganizationFolderDescriptor.HideGeneric not working inside folders
Title: Message Title Jesse Glick started work on JENKINS-31949 Change By: Jesse Glick Status: Open In Progress 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-27251) windows slaves disconnect during build
Title: Message Title Antek Baranski commented on JENKINS-27251 Re: windows slaves disconnect during build I am seeing the very same error on Windows slaves, no OS X or Linux slave shows this. The weird thing is that the next build runs fine on the node, right after the 'apparently' failure. Failure on remote 10:46:52 java.io.IOException: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@4af9aab0[name=X] 10:46:52 at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:169) 10:46:52 at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:151) 10:46:52 at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) 10:46:52 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@4af9aab0[name=uup-winasset02] 10:46:52 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) 10:46:52 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) 10:46:52 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 10:46:52 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 10:46:52 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 10:46:52 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 10:46:52 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 10:46:52 at java.lang.Thread.run(Thread.java:745) 10:46:52 Caused by: java.io.IOException: Connection timed out 10:46:52 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) 10:46:52 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) 10:46:52 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) 10:46:52 at sun.nio.ch.IOUtil.read(IOUtil.java:197) 10:46:52 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:384) 10:46:52 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) 10:46:52 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) 10:46:52 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) 10:46:52 ... 6 more 10:46:52 Slave went offline during the build 10:46:52 ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@4af9aab0[name=] 10:46:52 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) 10:46:52 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:628) 10:46:52 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 10:46:52 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) 10:46:52 at java.util.concurrent.FutureTask.run(FutureTask.java:262) 10:46:52 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 10:46:52 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 10:46:52 at java.lang.Thread.run(Thread.java:745) 10:46:52 Caused by: java.io.IOException: Connection timed out 10:46:52 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) 10:46:52 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) 10:46:52 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) 10:46:52 at sun.nio.ch.IOUtil.read(IOUtil.java:197) 10:46:52 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:384) 10:46:52 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) 10:46:52 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) 10:46:52 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) 10:46:52 ... 6 more
[JIRA] [aws-lambda-plugin] (JENKINS-28648) allow lambda s3 artifact location
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28648 Re: allow lambda s3 artifact location Code changed in jenkins User: Michael Willemse Path: blogpost/lambda.md pom.xml src/main/java/com/xti/jenkins/plugin/awslambda/exception/AWSLambdaPluginException.java src/main/java/com/xti/jenkins/plugin/awslambda/exception/LambdaDeployException.java src/main/java/com/xti/jenkins/plugin/awslambda/service/LambdaDeployService.java src/main/java/com/xti/jenkins/plugin/awslambda/service/WorkSpaceZipper.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploader.java src/main/java/com/xti/jenkins/plugin/awslambda/util/LambdaClientConfig.java src/test/java/com/xti/jenkins/plugin/awslambda/service/LambdaDeployServiceTest.java src/test/java/com/xti/jenkins/plugin/awslambda/service/WorkSpaceZipperTest.java src/test/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploaderTest.java http://jenkins-ci.org/commit/aws-lambda-plugin/755d4a735d8fabeec116ca38423362387db20553 Log: Merge pull request #7 from jenkinsci/master JENKINS-28648 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] [credentials-binding-plugin] (JENKINS-31946) Parameter expression may only resolve to a credentials ID
Title: Message Title
Nick Irvine edited a comment on JENKINS-31946
Re: Parameter _expression_ may only resolve to a credentials ID
Some more testing reveals that it looks like Parameter _expression_ doesn't actually expand parameters? Just keep getting the following:{code}FATAL: ${CREDS_ID}16:14:03 org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${CREDS_ID}{code} I'm definitely setting CREDS_ID; it works with an Environment Script that executes earlier.
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] [credentials-binding-plugin] (JENKINS-31946) Parameter expression may only resolve to a credentials ID
Title: Message Title
Nick Irvine commented on JENKINS-31946
Re: Parameter _expression_ may only resolve to a credentials ID
Some more testing reveals that it looks like Parameter _expression_ doesn't actually expand parameters? Just keep getting the following:
FATAL: ${CREDS_ID}
16:14:03 org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: ${CREDS_ID}
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] [cloudbees-folder-plugin] (JENKINS-27269) Credentials not usable in 'subfolders'
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-27269 Credentials not usable in 'subfolders' Change By: Jesse Glick Labels: credentials folder subfolders 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] [cloudbees-folder-plugin] (JENKINS-25595) After copying a Folder, all jobs within it are disabled
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-25595 After copying a Folder, all jobs within it are disabled Change By: Jesse Glick Labels: folder 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] [branch-api-plugin] (JENKINS-31949) CustomOrganizationFolderDescriptor.HideGeneric not working inside folders
Title: Message Title Jesse Glick commented on JENKINS-31949 Re: CustomOrganizationFolderDescriptor.HideGeneric not working inside folders (If you install an appropriate provider like the CloudBees GitHub Branch Source plugin, then you will get a GitHub Organization option, but you should never see this generic entry.) 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] [branch-api-plugin] (JENKINS-31949) CustomOrganizationFolderDescriptor.HideGeneric not working inside folders
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31949 CustomOrganizationFolderDescriptor.HideGeneric not working inside folders It is not supposed to appear, ever. Change By: Jesse Glick Component/s: branch-api-plugin Component/s: workflow-plugin Labels: folders multibranch 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] [branch-api-plugin] (JENKINS-31949) CustomOrganizationFolderDescriptor.HideGeneric not working inside folders
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31949 CustomOrganizationFolderDescriptor.HideGeneric not working inside folders Change By: Jesse Glick Summary: Duplicate project type name (functionality is different) CustomOrganizationFolderDescriptor.HideGeneric not working inside folders 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-31949) Duplicate project type name (functionality is different)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-31949 Duplicate project type name (functionality is different) Change By: Jesse Glick Labels: multibranch 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-27268) "dumb" slave?
Title: Message Title Mike Wood commented on JENKINS-27268 Re: "dumb" slave? Any chance this could be broken down into what the action items are? I'd be interested in picking up a task or two and putting in a PR if that helps! I'm sure I could get a few others to help out too and make this an easier transition. Thanks for bringing this up and discussing it. It's important and I'm glad action is being taken! 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-31951) Team Foundation Server Polling didn't work
Title: Message Title YI Mei Cai created an issue Jenkins / JENKINS-31951 Team Foundation Server Polling didn't work Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 07/Dec/15 11:34 PM Environment: Jenkins: 1.609.1 Team Foundation Server Plug-in 4.0.0 Priority: Major Reporter: YI Mei Cai Hi, I have a job which configured with "Poll SCM" . The Source Code Management is using Team Foundation Server with "Use update" Even I have changes, the Polling keeps saying. For example. The polling started 11:11:00 pm Dec 7, 2015 and it indicates "No changes" Then I manually execute the job and it shows I have 7 changes. Please let me know How I can get it working. thanks Yi Mei
[JIRA] [swarm-plugin] (JENKINS-31950) Unable to add toollocations to the swarm slave command line
Title: Message Title Petrik van der Velde created an issue Jenkins / JENKINS-31950 Unable to add toollocations to the swarm slave command line Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 07/Dec/15 11:03 PM Environment: Master:Windows 2012R2 Slave: Windows 2012R2 Priority: Minor Reporter: Petrik van der Velde When I try to add a tool location to the swarm slave command line my slave doesn't want to connect to jenkins anymore. The following command line is fine: java -Xrs -jar "%JENKINS_HOME%\swarm-client-2.0.jar" -executors 1 -labels ".NET AzureSDK AzureUpload TFS Vmware" -master "http://myjenkinsmaster" -fsroot "C:\ci" -mode "exclusive" -showHostName -username "MyUser" -password "@C:\my\key\file\location.txt" And the following command line fails: java -Xrs -jar "%JENKINS_HOME%\swarm-client-2.0.jar" -executors 1 -labels ".NET AzureSDK AzureUpload TFS Vmware" -t NuGet="c:\tools\nuget" -t powershell="c:\windows\system32\WindowsPowershell\v1.0" -master "http://myjenkinsmaster" -fsroot "C:\ci" -mode "exclusive" -showHostName -username "MyUser" -password "@C:\my\key\file\location.txt" If if using only a single tool it still fails. The error that shows up in the log is:
[JIRA] [other] (JENKINS-31442) Jenkins Wrong Build History (Dec 31, 1969)
Title: Message Title Lamin Faty commented on JENKINS-31442 Re: Jenkins Wrong Build History (Dec 31, 1969) Oleg Nenashev Thanks for the update. But can you be more specific, in other words, can you give me more details. Thanks 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-31150) Support Multiple SCM tags for rundeck notifier
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31150 Re: Support Multiple SCM tags for rundeck notifier Code changed in jenkins User: joel.ringuette Path: src/main/java/org/jenkinsci/plugins/rundeck/RundeckNotifier.java http://jenkins-ci.org/commit/rundeck-plugin/abf6f1dd9c6f4a7907cc47f43fb35ce8bf9ff7f1 Log: Fix issues caused by JENKINS-31150 not being backward compatible. 1 - NPE thrown when tags are stored under the old format. 2 - Tags are not displayed in job configuration when reloaded under the new format. 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-31949) Duplicate project type name (functionality is different)
Title: Message Title suresh nallamilli updated an issue Jenkins / JENKINS-31949 Duplicate project type name (functionality is different) Change By: suresh nallamilli After upgrading to latest workflow plugns (also installed workflow-multibranch) , am seeing that two options for creating Folder. See below image. Its May be It is better to rename the new project type to something else may b like "multibranch folder".Also an explanation about how it is different from project type "Multibranch workflow" helps Please note that you can see this only from within a nested folder , not at top level!DuplicateProjectType.png|thumbnail! 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-31949) Duplicate project type name (functionality is different)
Title: Message Title suresh nallamilli updated an issue Jenkins / JENKINS-31949 Duplicate project type name (functionality is different) Change By: suresh nallamilli Summary: Duplicate project type name (functionality is diferent different ) 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-31949) Duplicate project type name (functionality is diferent)
Title: Message Title suresh nallamilli created an issue Jenkins / JENKINS-31949 Duplicate project type name (functionality is diferent) Issue Type: Bug Assignee: Jesse Glick Attachments: DuplicateProjectType.png Components: workflow-plugin Created: 07/Dec/15 10:12 PM Priority: Minor Reporter: suresh nallamilli After upgrading to latest workflow plugns (also installed workflow-multibranch) , am seeing that two options for creating Folder. See below image. Its is better to rename the new project type to something else may b "multibranch folder". Also an explanation about how it is different from project type "Multibranch workflow" helps Please note that you can see this only from within a nested folder , not at top level
[JIRA] [workflow-plugin] (JENKINS-31878) False warning on no sense parameters in the build a job snippet generator
Title: Message Title Jens Wilke commented on JENKINS-31878 Re: False warning on no sense parameters in the build a job snippet generator What about rewording: "Disabled propagate is redundant if waiting is disabled, because the propagate parameter setting gets ignored. For brevity, keep propagate at its default value." 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] [acceptance-test-harness] (JENKINS-31948) plugins.TaskScannerPluginTest & plugins.FindBugsPluginTest take 30 minutes each
Title: Message Title recampbell created an issue Jenkins / JENKINS-31948 plugins.TaskScannerPluginTest & plugins.FindBugsPluginTest take 30 minutes each Issue Type: Bug Assignee: Oliver Gondža Components: acceptance-test-harness Created: 07/Dec/15 9:32 PM Environment: Linux/CloudBees Priority: Minor Reporter: recampbell These two tests take 30 minutes each, which accounts for 1 out of the 6 hours it takes for the ATH to run. ath-oss-split-3] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,713.746 sec - in plugins.FindBugsPluginTest [ath-oss-split-4] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2,034.433 sec - in plugins.TaskScannerPluginTest
[JIRA] [workflow-plugin] (JENKINS-31878) False warning on no sense parameters in the build a job snippet generator
Title: Message Title Jens Wilke commented on JENKINS-31878 Re: False warning on no sense parameters in the build a job snippet generator Consider the following: First, I disable "propagate", since I don't want my build to fail because of a downstream job result. This is legal, isn't it? Now, I have two options left: 1. Wait, because, for example I want to send a mail for build completion after everything is done including the downstream jobs 2. Don't wait, because, the downstream jobs do notification of their own Both two potions are legal. However, when I disable waiting, I get a warning, that this is a senseless option. To get the warning away, I have to enable 'propagate' again, but, I don't want anything to propagate! 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-31769) sh steps on slaves randomly hang when complete
Title: Message Title Jesse Glick started work on JENKINS-31769 Change By: Jesse Glick Status: Open In Progress 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-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29881 Re: WorkflowRun.getChangeSets should skip empty changesets Code changed in jenkins User: Andrew Bayer Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsScmFlowDefinitionTest.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/1b9c1ef6d327684097103b47da591acd92e61aee Log: [FIXED JENKINS-29881] Don't include empty changesets in getChangeSets() 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-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29881 WorkflowRun.getChangeSets should skip empty changesets 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-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29881 Re: WorkflowRun.getChangeSets should skip empty changesets Code changed in jenkins User: Andrew Bayer Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/CpsScmFlowDefinitionTest.java job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java http://jenkins-ci.org/commit/workflow-plugin/e1a94f081bda7732b74b0abcb4affa6f4dae1725 Log: Merge pull request #267 from abayer/jenkins-29881 JENKINS-29881 Don't include empty changesets in getChangeSets() Compare: https://github.com/jenkinsci/workflow-plugin/compare/e3f21bc2b3e3...e1a94f081bda 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] [credentials-binding-plugin] (JENKINS-31946) Parameter expression may only resolve to a credentials ID
Title: Message Title Nick Irvine commented on JENKINS-31946 Re: Parameter _expression_ may only resolve to a credentials ID To clarify, the property names I'm using come from the Credentials > page: ID: part of the URL when I click on a cred: http:///credential-store/domain///, e.g., e297bca6-4aa0-4fae-a625-2a6b996373d4 name: for username/password type, it is autogenerated: "/* ()" Maybe there is a way to use the name that I'm not aware of. 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] [_unsorted] (JENKINS-31525) Build history date
Title: Message Title Oleg Nenashev commented on JENKINS-31525 Re: Build history date The screenshot is similar to JENKINS-31525. I suspect it's a duplicate 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] [other] (JENKINS-31442) Jenkins Wrong Build History (Dec 31, 1969)
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-31442 Jenkins Wrong Build History (Dec 31, 1969) Change By: Oleg Nenashev Component/s: other Component/s: _unsorted 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] [other] (JENKINS-31442) Jenkins Wrong Build History (Dec 31, 1969)
Title: Message Title Oleg Nenashev commented on JENKINS-31442 Re: Jenkins Wrong Build History (Dec 31, 1969) Hi Lamin, It seems to be an issue in a plugin, which is not being hosted on jenkinsci org or anywhere else on GitHub. I doubt this bugtracker is a relevant place for such 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] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy edited a comment on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
Got a new one hang , this time with the control directory It's job team_agility_dev #1, started Dec 7, 2015 6:00 PM which hangs aftre running a simple shell script (calling "rm"). {noformat}Started by upstream project "nightly" build number 1originally caused by: Started by timerRunning: Print MessagerunmeRunning: run_stageEntering stage run_stage... (146/148) Setup dialog* (147/148) Setup gui/qigui * (148/148) Setup life/usersession New qisrc worktree initialized in /home/jenkins/w/team_agility_devRunning: Shell Script[team_agility_dev] Running shell script+ rm -f snapshot.json{noformat}on the qisrc slave{noformat}$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`$ ls -ld jenkins/workspace/team_agility_dev/.e7972254/drwxrwxr-x 2 jenkins jenkins 4096 Dec 7 19:12 jenkins/workspace/team_agility_dev/.e7972254/$ ls -l jenkins/workspace/team_agility_dev/.e7972254/total 16-rw-rw-r-- 1 jenkins jenkins 22 Dec 7 19:12 jenkins-log.txt-rw-rw-r-- 1 jenkins jenkins 2 Dec 7 19:12 jenkins-result.txt-rw-rw-r-- 1 jenkins jenkins 6 Dec 7 19:12 pid-rwxr-xr-x 1 jenkins jenkins 33 Dec 7 19:12 script.sh$ cat jenkins/workspace/team_agility_dev/.e7972254/jenkins-log.txt+ rm -f snapshot.json$ cat jenkins/workspace/team_agility_dev/.e7972254/jenkins-result.txt 0$ cat jenkins/workspace/team_agility_dev/.e7972254/pid26868$ cat jenkins/workspace/team_agility_dev/.e7972254/script.sh #!/bin/sh -xerm -f snapshot.json{noformat}Also {{Jenkins.instance.getNode('qisrc').createPath('/home/jenkins/jenkins/workspace/team_agility_dev/.e7972254/jenkins-result.txt').exists()}} return trueHere is the durable task log, it starts from the previous test_workflow" hang at 16:13:47.220+ then jumps to the new job a 18:58:58.789+ when I cancelled the hung one (which was blocking team_agility_dev since they compete for the same executor).I skipped some parts with ellipsis.At the very end you'll see that it reads from {{.e7972254/jenkins-log.txt}}{noformat}2015-12-07 16:13:47.220+ [id=63]FINEo.j.p.w.s.d.DurableTaskStep$Execution#check: could not check /home/jenkins/jenkins/workspace/test_workflowjava.lang.InterruptedExceptionat java.lang.Object.wait(Native Method)at hudson.remoting.Request.call(Request.java:147)at hudson.remoting.Channel.call(Channel.java:777)at hudson.FilePath.act(FilePath.java:980)at hudson.FilePath.act(FilePath.java:969)at hudson.FilePath.deleteRecursive(FilePath.java:1171)at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.cleanup(FileMonitoringTask.java:155)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:199)at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:154)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745)2015-12-07 18:58:58.789+ [id=51]FINEo.j.p.d.FileMonitoringTask$FileMonitoringController#writeLog: copied 170 bytes from /home/jenkins/jenkins/workspace/test_workflow/.3bdc0065/jenkins-log.txt2
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy commented on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
Got a new one, with the control directory
job team_agility_dev #1, started Dec 7, 2015 6:00 PM
Started by upstream project "nightly" build number 1
originally caused by:
Started by timer
Running: Print Message
runme
Running: run_stage
Entering stage run_stage
...
(146/148) Setup dialog
* (147/148) Setup gui/qigui
* (148/148) Setup life/usersession
New qisrc worktree initialized in /home/jenkins/w/team_agility_dev
Running: Shell Script
[team_agility_dev] Running shell script
+ rm -f snapshot.json
on the qisrc slave
$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`
$ ls -ld jenkins/workspace/team_agility_dev/.e7972254/
drwxrwxr-x 2 jenkins jenkins 4096 Dec 7 19:12 jenkins/workspace/team_agility_dev/.e7972254/
$ ls -l jenkins/workspace/team_agility_dev/.e7972254/
total 16
-rw-rw-r-- 1 jenkins jenkins 22 Dec 7 19:12 jenkins-log.txt
-rw-rw-r-- 1 jenkins jenkins 2 Dec 7 19:12 jenkins-result.txt
-rw-rw-r-- 1 jenkins jenkins 6 Dec 7 19:12 pid
-rwxr-xr-x 1 jenkins jenkins 33 Dec 7 19:12 script.sh
$ cat jenkins/workspace/team_agility_dev/.e7972254/jenkins-log.txt
+ rm -f snapshot.json
$ cat jenkins/workspace/team_agility_dev/.e7972254/jenkins-result.txt
0
$ cat jenkins/workspace/team_agility_dev/.e7972254/pid
26868
$ cat jenkins/workspace/team_agility_dev/.e7972254/script.sh
#!/bin/sh -xe
rm -f snapshot.json
Also Jenkins.instance.getNode('qisrc').createPath('/home/jenkins/jenkins/workspace/team_agility_dev/.e7972254/jenkins-result.txt').exists() return true
Here is the durable task log, it starts from the previous test_workflow" hang at 16:13:47.220+ then jumps to the new job a 18:58:58.789+ when I cancelled the hung one (which was blocking team_agility_dev since they compete for the same executor).
I skipped some parts with ellipsis. At the very you'll see that it reads from .e7972254/jenkins-log.txt
2015-12-07 16:13:47.220+ [id=63]FINEo.j.p.w.s.d.DurableTaskStep$Execution#check: could not check /home/jenkins/jenkins/workspace/test_workflow
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at hudson.remoting.Request.call(Request.java:147)
at hudson.remoting.Channel.call(Channel.java:777)
at hudson.FilePath.act(FilePath.java:980)
at hudson.FilePath.act(FilePath.java:969)
at hudson.FilePath.deleteRecursive(FilePath.java:1171)
at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.cleanup(FileMonitoringTask.java:155)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:199)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:154)
at java.util.concurrent.E
[JIRA] [_unsorted] (JENKINS-31550) Configure System Page shows Oops page (/configure)
Title: Message Title Oleg Nenashev commented on JENKINS-31550 Re: Configure System Page shows Oops page (/configure) Please provide a stacktrace displayed in the Window. It's not possible to analyze the issue without it: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+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] [_unsorted] (JENKINS-31764) Credentials
Title: Message Title Oleg Nenashev commented on JENKINS-31764 Re: Credentials Please follow these guidelines: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Why do you think it's an issue? Have you logged in? 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] [_test] (JENKINS-31947) Jobs hanging in Build Executor even if it is finished
Title: Message Title Oleg Nenashev commented on JENKINS-31947 Re: Jobs hanging in Build Executor even if it is finished This issue does not provide enough info. Please follow the guidelines here: https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue In particular, it would be useful to get a report from JENKINS_URL/queue/api . With the right depth specification it should provide the scheduling cause 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] [sitemonitor-plugin] (JENKINS-31540) SiteMonitor plugin doesn't support TLS1.2 encryption
Title: Message Title Francisco Hernandez Suarez commented on JENKINS-31540 Re: SiteMonitor plugin doesn't support TLS1.2 encryption Could you please post a URL that use that algorithm in order to test the issue? is the site that your are trying to monitor public? 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-28759) Batch steps on slaves randomly hang when complete
Title: Message Title Jesse Glick commented on JENKINS-28759 Re: Batch steps on slaves randomly hang when complete I discovered a potential bug in platform-independent code which might explain at least certain cases of this issue. Some other observations like Jeremy Riley’s do not sound related. 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] [_test] (JENKINS-31947) Jobs hanging in Build Executor even if it is finished
Title: Message Title Prabhu Pilli updated an issue Jenkins / JENKINS-31947 Jobs hanging in Build Executor even if it is finished Change By: Prabhu Pilli I am seeing about 70 jobs in the build queue. All these jobs are completed long ago.I can remove them by deleting the project but why are these getting rescheduled. 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] [credentials-binding-plugin] (JENKINS-31946) Parameter expression may only resolve to a credentials ID
Title: Message Title Jesse Glick commented on JENKINS-31946 Re: Parameter _expression_ may only resolve to a credentials ID Inline help probably needs to be created. I am not following why you think you need to search by name. Specify custom, meaningful IDs when creating the credentials. 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] [_test] (JENKINS-31947) Jobs hanging in Build Executor even if it is finished
Title: Message Title Prabhu Pilli created an issue Jenkins / JENKINS-31947 Jobs hanging in Build Executor even if it is finished Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 07/Dec/15 7:56 PM Priority: Critical Reporter: Prabhu Pilli 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
[JIRA] [credentials-binding-plugin] (JENKINS-31946) Parameter expression may only resolve to a credentials ID
Title: Message Title Nick Irvine created an issue Jenkins / JENKINS-31946 Parameter _expression_ may only resolve to a credentials ID Issue Type: Bug Assignee: Jesse Glick Components: credentials-binding-plugin Created: 07/Dec/15 7:54 PM Priority: Minor Reporter: Nick Irvine When using the Parameter _expression_ option, it's unclear what the _expression_ needs to resolve to. After some guessing, I figured out it likes credentials IDs. First, the fact that I had to figure this out by trial and error is annoying (it's undocumented AFAICT). Second, it would be nice if you could search by name/description. Otherwise, for this parameter to be used, I have to maintain a table of name to ID mappings somewhere in the job's parameters, and that's fragile and redundant. Add Comment
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title Jesse Glick commented on JENKINS-31769 Re: sh steps on slaves randomly hang when complete My suspicion falls on … FINE o.j.p.w.s.d.DurableTaskStep$Execution#check: could not check /home/jenkins/jenkins/workspace/test_workflow java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:147) at hudson.remoting.Channel.call(Channel.java:777) at hudson.FilePath.act(FilePath.java:980) at hudson.FilePath.act(FilePath.java:969) at hudson.FilePath.deleteRecursive(FilePath.java:1171) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.cleanup(FileMonitoringTask.java:155) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:199) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:154) at … There is a three-second timeout on rounds of checking, to prevent hung slave connections from stalling everything. So in the latest case it sounds like if the slave is heavily enough loaded that about three seconds elapse between the start of the first check round after the process has exited and when cleanup is called, there could be a race condition whereby the control directory is actually deleted but the step does not exit. I think the sequence of operations needs to be reordered a bit. That does not explain the original hangs, in which case the control dir was there. 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.
[JIRA] [workflow-plugin] (JENKINS-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title Jesse Glick started work on JENKINS-29881 Change By: Jesse Glick Status: Open In Progress 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-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy commented on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
And this does not reproduce consistently enough to inspect logs during a workday I suppose?
The normal jobs take hours, which make the probabilty to see a hang quite low. I'm trying to reproduce the issue on smaller purpose-less jobs.
I'm making progress: I got a new hang, with logs!
I'm not sure it is the exact same problem since this is the first time that 1/ I notice unexpected console logs and 2/ the control directory is not there.
The setup is: a workflow job called test_nightly is run every 4 minutes. It starts another workflow job called test_workflow, two times is a row. I expect at least half of the test_nightly jobs will get superseded. The sources are at the end.
It worked as expected until test_nightly #91, which started at Dec 7, 2015 4:04 PM
Started by timer
Running: run_stage
Entering stage run_stage
Canceling older #90
Waiting for builds [89]
Unblocked since #89 finished
Running: Building test_workflow
Starting building project: test_workflow
which started test_workflow #75 at Dec 7, 2015 4:06 PM, which never returned The console logs below are quite surprising, the line + file /home/jenkins/w/team_romeo_dev/.qi appears too many times, as if several threads fetched the log in parallel.
started by upstream project "test_nightly" build number 91
originally caused by:
Started by timer
Running: Print Message
runme
Running: run_stage
Entering stage run_stage
Proceeding
Running: Allocate node : Start
Running on qisrc in /home/jenkins/jenkins/workspace/test_workflow
Running: Allocate node : Body : Start
Running: Print Message
i: 0
Running: Shell Script
[test_workflow] Running shell script
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
Running: Print Message
i: 1
...
i: 648
Running: Shell Script
[test_workflow] Running shell script
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
Running: Print Message
i: 649
Running: Shell Script
[test_workflow] Running shell script
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
full console log here: http://pastebin.com/6cWTbNF4 durable task log: http://pastebin.com/DKZCNEna default log: http://pastebin.com/LUXUYERM
On the slave, there is no control directory (contrary to others occurrences of the hang)
$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`
$ ls -la jenkins/wo
[JIRA] [workflow-plugin] (JENKINS-31902) Interrupting upstream flow build will not interrupt downstream flow build
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31902 Interrupting upstream flow build will not interrupt downstream flow build 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-31902) Interrupting upstream flow build will not interrupt downstream flow build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31902 Re: Interrupting upstream flow build will not interrupt downstream flow build Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildQueueListener.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerListener.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/e3f21bc2b3e389075c84b2d0be9cebeacebd2d89 Log: JENKINS-31902 Merging #263. Compare: https://github.com/jenkinsci/workflow-plugin/compare/c91ed6500713...e3f21bc2b3e3 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-31902) Interrupting upstream flow build will not interrupt downstream flow build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31902 Re: Interrupting upstream flow build will not interrupt downstream flow build Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java support/src/main/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/19c6aa50869d18f96ab60ef6051b8efc32c860f2 Log: [FIXED JENKINS-31902] Interrupt also downstream flyweight executors, hosting a WorkflowRun. 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-31386) "checkout scm" does not work in standalone jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31386 Re: "checkout scm" does not work in standalone jobs Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/help-scriptPath.html multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/SCMVar.java multibranch/src/main/resources/org/jenkinsci/plugins/workflow/multibranch/SCMVar/help.jelly multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/SCMVarTest.java http://jenkins-ci.org/commit/workflow-plugin/fe22dc9fa39267239e6ca16001bd9cd97b0ee48c Log: [FIXED JENKINS-31386] Define the scm var in standalone projects using CpsScmFlowDefinition. 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-31386) "checkout scm" does not work in standalone jobs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31386 Re: "checkout scm" does not work in standalone jobs Code changed in jenkins User: Jesse Glick Path: CHANGES.md cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/config.jelly cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsScmFlowDefinition/help-scriptPath.html multibranch/src/main/java/org/jenkinsci/plugins/workflow/multibranch/SCMVar.java multibranch/src/main/resources/org/jenkinsci/plugins/workflow/multibranch/SCMVar/help.jelly multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/SCMBinderTest.java multibranch/src/test/java/org/jenkinsci/plugins/workflow/multibranch/SCMVarTest.java http://jenkins-ci.org/commit/workflow-plugin/c91ed650071362d9949da5fbffd13a9262c1fb1e Log: JENKINS-31386 Merging #264. Compare: https://github.com/jenkinsci/workflow-plugin/compare/85330f60060d...c91ed6500713 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-31386) "checkout scm" does not work in standalone jobs
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31386 "checkout scm" does not work in standalone jobs 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] [sitemonitor-plugin] (JENKINS-31540) SiteMonitor plugin doesn't support TLS1.2 encryption
Title: Message Title Pavel Saab commented on JENKINS-31540 Re: SiteMonitor plugin doesn't support TLS1.2 encryption This is error I am getting in the build log: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake - Remote host closed connection during handshake It looks like we are using RSA algorithm instead of ECDH_P256 that is used by GitHub.com 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-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons started work on JENKINS-31321 Change By: Christopher Simons Status: Open In Progress 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-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title
Christopher Simons updated an issue
Jenkins / JENKINS-31321
Renaming a node over another is possible and destroys both configurations
Change By:
Christopher Simons
When performing a node name rework, I was able to it is possible (partially?) overwrite a node with another one simply by renaming (which is a bit strange) but, apparently, the configuration of the "new" an existing node was broken so it was necessary to delete it and create it from scratch .Steps to reproduce:# Create a node named {{foo}}# Make {{foo}} node as temporarily offline# Create another node named {{bar}}# Go to the {{bar}} node configuration# Rename it to {{foo}} and press _Save_Expected results:* A prompt asking if that's what the user really intends: An error message. ** _Yes_ would be the equivalent to deleting {{foo}} node and replacing its configuration contents with the one from {{bar}} (now named {{foo}}) ** _No_ would cause the operation to be aborted Actual results:* Node {{bar}} replaces {{foo}} without any notice* Things start to behave wacky: build starts to fail without a reason (see attached edited log, {{Jenkins-BuildBreakageAfterNodeRename.txt}} Disclaimer: I wasn't able to validate the exact steps to reproduce procedure *nor* if making the node temporarily offline is really necessary as a Jenkins test instance was not available (procedure was compiled from memory).Workaround:* Delete a node before renaming another one over it* If such an undesired node rename was made, delete and reconfigure the affected node againPriority set to "major" as loss of information (node configuration) is involved. Build breakage (until the problem is understood and fixed) is also triggered, although that's not as serious and could be considered "minor".
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node, an error page is rendered with the message "Error: Slave called ‘foo’ already exists". I'd propose rendering the same error message is rendered upon trying to rename a node over another existing node. 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-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons commented on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node, an error page is rendered with the message "Error: Slave called ‘foo’ already exists". I'd propose rendering the same error message is rendered upon trying to rename a node over another existing node. 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-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-31321 Renaming a node over another is possible and destroys both configurations Change By: Christopher Simons Assignee: Christopher Simons 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] [docker-custom-build-environment-plugin] (JENKINS-31944) Docker commandline passed wrong user id when executing.
Title: Message Title Stephen Leary created an issue Jenkins / JENKINS-31944 Docker commandline passed wrong user id when executing. Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 07/Dec/15 5:44 PM Priority: Minor Reporter: Stephen Leary When docker is invoked it is passed the userid of the jenkins user on the host machine. This breaks things because the local user doesnt actually exist (PAM module checks fail for example) and doesnt match the environment variables for the username. It would be better to use the username (easymode) or explicitly create the jenkins user with the userid of the host. Add Comment
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title
Andrew Bayer commented on JENKINS-29780
Re: unarchive should support "Flatten directories"
PR up - https://github.com/jenkinsci/jenkins/pull/1948 - as I said on the PR, I'm a bit wary of the DirScanner.FlattenGlob logic - more specifically, I'm not sure how best to test it. The {{relativePath}}s are definitely coming in right, though.
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] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title hannes schluchtmann commented on JENKINS-29077 Re: No selector is shown for installing NodeJS from nodejs.org Haha, all fine with me. I can wait for now. But all your replies helped me a lot to understand the general situation. Thanks for that! 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] [memegen-plugin] (JENKINS-31943) Meme generator plugin is broken
Title: Message Title Andrew a updated an issue Jenkins / JENKINS-31943 Meme generator plugin is broken Change By: Andrew a Priority: Minor Major 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-29780) unarchive should support "Flatten directories"
Title: Message Title
Andrew Bayer edited a comment on JENKINS-29780
Re: unarchive should support "Flatten directories"
Debating whether to put that ` {{ DirScanner ` }} in core - that feels right to me, since it could be useful elsewhere...
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] [memegen-plugin] (JENKINS-31943) Meme generator plugin is broken
Title: Message Title
Andrew a created an issue
Jenkins / JENKINS-31943
Meme generator plugin is broken
Issue Type:
Bug
Assignee:
Jon Cairns
Components:
memegen-plugin
Created:
07/Dec/15 4:57 PM
Priority:
Minor
Reporter:
Andrew a
Something changed in memegenerator API, no meme is generated and you can see the following in the jenkins log:
Memegenerator API failure: Procedure or function 'Instance_Create' expects parameter '@Created', which was not supplied., full response: {"errorMessage":"Procedure or function 'Instance_Create' expects parameter '@Created', which was not supplied.","success":false}
Add Comment
[JIRA] [windows-slaves-plugin] (JENKINS-31928) Little/No documentation on windows slave "No tty allocated failure"
Title: Message Title
Amrish R updated an issue
Jenkins / JENKINS-31928
Little/No documentation on windows slave "No tty allocated failure"
Change By:
Amrish R
I am not able to find much documentation/help on resolving an issue with building a Jenkins job on a windows slave. I am not sure what needs to be done to fix the following issue. Here are the logs. It will be nice if the wiki is updated with some information on solving this issue{code:java}Building remotely on Windows Slave (windows) in workspacec:\Builds\workspace\windows-nuget-push> C:\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository> C:\Git\cmd\git.exe config remote.origin.url g...@github.com:SDK-NewGen/sdk.git # timeout=10Fetching upstream changes from g...@github.com:NewGen/sdk.git> C:\Git\cmd\git.exe --version # timeout=10using GIT_SSH to set credentials > C:\Git\cmd\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:NewGen/sdk.git +refs/heads/*:refs/remotes/origin/*> C:\Git\cmd\git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10> C:\Git\cmd\git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10Checking out Revision e1feb68bcc21e8801a5bcaf087bda5041370fbf7 (refs/remotes/origin/develop)> C:\Git\cmd\git.exe config core.sparsecheckout # timeout=10> C:\Git\cmd\git.exe checkout -f e1feb68bcc21e8801a5bcaf087bda5041370fbf7> C:\Git\cmd\git.exe rev-list e1feb68bcc21e8801a5bcaf087bda5041370fbf7 # timeout=10[windows-nuget-push] $ sh -xe C:\WINDOWS\TEMP\hudson8489555376979916245.sh 2 [main] sh 140924 tty_list::allocate_tty: No tty allocated+ ./update-repo.shC:\WINDOWS\TEMP\hudson8489555376979916245.sh: ./update-repo.sh: not foundBuild step 'Execute shell' marked build as failureFinished: FAILURE{code}I think the failure is indicated by the following log message and I am not sure how to fix it.2 [main] sh 140924 tty_list::allocate_tty: No tty allocated, A quick google search pointed me to this [link][https://git.wiki.kernel.org/index.php/GitFaq#Why_does_gitk_on_Cygwin_display_.22git_1316_tty_list::allocate:_No_tty_allocated.22.3F], but I am not able to resolve this issue by removing tty from the CYGWIN environmental variable. Here is the shell command that is configured to be executed{code:java}./update-repo.sh./node_modules/.bin/gulp dev{code}
Add Comment
