Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Composite commands label and id #18

Closed
l0rd opened this issue Feb 6, 2020 · 5 comments · Fixed by #35
Closed

Composite commands label and id #18

l0rd opened this issue Feb 6, 2020 · 5 comments · Fixed by #35
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented Feb 6, 2020

Composite currently only has a label. But that appears to be something that would be visible in the Che UI. It should have an id as well so that tools like odo can reference composite commands with the following requirements:

  • 2 distincts attributes: label and id
  • both can coexist
  • id is mandatory
  • id used to reference parent devfiles commands (not label)

Sample devfile snippet to show example of usage/format:

projects:
 - name: "devworkspace-spec"
   git:
       location: "https://github.com/che-incubator/devworkspace-api"
       branch: "master"
commands:
 - exec:
     commandLine: "./buildSchema.sh"
     component: build-tools
     id: buildSchema
 - vscodeTask:
     id: openDevfile
     inlined:
       json       
 - composite:
     id: buildAndOpen
     label: Build schema and open devfile
     commands:
       - buildSchema
       - openDevfile
     parallel: false
components:
 - container:
     image: some container image with required build tools
     name: "build-tools"
@l0rd l0rd mentioned this issue Feb 6, 2020
28 tasks
@l0rd
Copy link
Contributor Author

l0rd commented Feb 6, 2020

cc @johnmcollier @elsony

@l0rd
Copy link
Contributor Author

l0rd commented Feb 18, 2020

Proposal reviewed and approved with the following requirements:

  • 2 distincts attributes: label and id
  • both can coexist
  • id is mandatory
  • id used to reference parent devfiles commands (not label)

@l0rd l0rd changed the title Alias for Composite commands Id for Composite commands Feb 18, 2020
@groeges
Copy link

groeges commented Mar 19, 2020

@l0rd Looking at this issue alongside #27 will the composite element define the group or will each of the individual exec elements define a group. My thoughts are the composite would define the group but wanted to check.

@l0rd
Copy link
Contributor Author

l0rd commented Mar 20, 2020

@groeges I would say that the group can be specified for a composite and its commands can belong to distinct groups:

commands:
 - exec:
     id: build
     commandLine: "./build.sh"
     component: tooling
     group: 
        kind: build
 - exec:
     id: run
     commandLine: "./run.sh"
     component: tooling
     group: 
        kind: run
 - composite:
     id: buildAndRun
     label: Build and Run
     commands:
       - build
       - run
     parallel: false
     group: 
        kind: run

davidfestal added a commit that referenced this issue Apr 3, 2020
Signed-off-by: David Festal <dfestal@redhat.com>
@l0rd l0rd changed the title Id for Composite commands Composite commands label and id Apr 7, 2020
davidfestal added a commit that referenced this issue Apr 22, 2020
* Implement agreement on issue #18
* Implement agreement on issue #17
* Implement agreement on issue #21
* Implement agreement on issue #22
* Implement agreement on issue #27
* Implement agreement on issue #9
* Implement agreement on issue #10
* Fix PR comments about issue #9 PR comment #35 (comment)
* Fix PR comments about issue #17 PR comment #35 (comment)
* Implement agreement on issue #14 and  #19
* Add the spring boot example
* Implement agreement on issue #32
* Fix last PR comments

Signed-off-by: David Festal <dfestal@redhat.com>

Co-Authored-By: Sergii Leshchenko <sleshche@redhat.com>
@l0rd l0rd added this to the 2.0.0 milestone Jun 16, 2020
@davidfestal davidfestal linked a pull request Jun 23, 2020 that will close this issue
@davidfestal
Copy link
Collaborator

Implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants