Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-14

Allow concurrent execution of sibling tasks if possible

    Details

    • Type: New Feature
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None

      Description

      Potential issues:

      • concurrent download of JARs by Ivy

      Other requirements:

      • allow to disable concurrent build in user settings, gradle.groovy of gradlesettings.xml
      • concurrency settings like number of simultaneous builds in user settings

        Activity

        devijvers Steven Devijver created issue -
        hans_d Hans Dockter made changes -
        Field Original Value New Value
        Fix Version/s someday [ 14076 ]
        adammurdoch Adam Murdoch made changes -
        Assignee Hans Dockter [ hans_d ]
        contegix Contegix Support made changes -
        Project Import Sat Mar 19 09:23:24 CDT 2011 [ 1300544604020 ]
        daz Daz DeBoer made changes -
        Workflow jira [ 12072 ] jira with pivotal tracker [ 13965 ]
        adammurdoch Adam Murdoch made changes -
        Fix Version/s someday [ 10053 ]
        ldaley Luke Daley made changes -
        Workflow jira with pivotal tracker [ 13965 ] jira with pivotal tracker (no resolved, only closed) [ 17058 ]
        ldaley Luke Daley made changes -
        Workflow jira with pivotal tracker (no resolved, only closed) [ 17058 ] Copy of jira with pivotal tracker (no closed, only resolved) [ 19764 ]
        Hide
        bmuschko Benjamin Muschko added a comment -

        As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

        We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

        Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

        • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
        • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

        We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

        Show
        bmuschko Benjamin Muschko added a comment - As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by: Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines . Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete. We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

          People

          • Assignee:
            Unassigned
            Reporter:
            devijvers Steven Devijver
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development