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

Orchestrate inter-build triggers #19127

Closed
nickboldt opened this issue Feb 22, 2021 · 1 comment
Closed

Orchestrate inter-build triggers #19127

nickboldt opened this issue Feb 22, 2021 · 1 comment
Assignees
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues kind/enhancement A feature request - must adhere to the feature request template. sprint/next

Comments

@nickboldt
Copy link
Contributor

nickboldt commented Feb 22, 2021

Is your enhancement related to a problem? Please describe.

Based on a conversation last week ~ Feb 10 w/ Florent, Mykhailo and Nick, we've decided to set up inter-build triggers to better orchestrate and automate the Che releases.

See https://docs.google.com/spreadsheets/d/1BtmO2hLWwFUejstnP6eBDEImE1LvUDK1pUP8rYDPkdA/edit#gid=0

Describe the solution you'd like

Sample code snippet:

jobs:
  - machine-exec:
      - steps:
        - id: release-machine-exec
          uses: che-incubator/release-action@next
          with:
            - repository : eclipse/che-machine-exec
            - token: ${{secrets.TOKEN }}

  - che-theia:
      - steps:
        - id: release-che-theia
          uses: che-incubator/release-action@next
          with:
            - repository : eclipse/che-theia
            - token: ${{secrets.TOKEN }}

  - che-plugin-registry:
      needs: [che-theia, che-machine-exec]
      - steps:
        - id: release-che-plugin-registry
          uses: che-incubator/release-action@next
          with:
            - repository : eclipse/che-plugin-registry
            - token: ${{secrets.TOKEN }}

WIP also involves moving from tried-and-true bash scripts to typescript so that more tests can be written.

@nickboldt nickboldt added the kind/enhancement A feature request - must adhere to the feature request template. label Feb 22, 2021
@nickboldt nickboldt assigned nickboldt and mkuznyetsov and unassigned nickboldt Feb 22, 2021
@nickboldt nickboldt added this to the 7.27 milestone Feb 22, 2021
@nickboldt nickboldt added area/ci CI build and releases, PR testing, & whitelabel/productization issues area/productization labels Feb 22, 2021
@nickboldt nickboldt modified the milestones: 7.27, 7.28 Mar 12, 2021
@nickboldt nickboldt modified the milestones: 7.28, 7.29 Mar 29, 2021
@nickboldt
Copy link
Contributor Author

5 months later, no progress on this, so closing as won't do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues kind/enhancement A feature request - must adhere to the feature request template. sprint/next
Projects
None yet
Development

No branches or pull requests

2 participants