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

SPIKE: Review and test options for multi workflow pipelines #8

Open
jonathan-winn-geo opened this issue Jul 29, 2020 · 4 comments
Open
Assignees
Labels
cmascience cmascience related rep documentation Improvements or additions to documentation pipelines/workflows Automated pipelines / workflows / actions via GitHub question Further information is requested S.Slow (> 2 days) sprint ready Issue is ready to work on testing Testing code - automated pipeline or within app tests

Comments

@jonathan-winn-geo
Copy link
Collaborator

jonathan-winn-geo commented Jul 29, 2020

As a system user I want to record the system design options and pipeline / workflow functionality in the wiki so that it can be referred to during maintenance or be used by others when designing other systems

What are the options to create several workflows in the repo, to allow

  • different levels of tests on master, dev or test branches (e.g. more detailed tests via Test, simple via Master)
  • to allow some workflows to only run after previous workflows have completed
  • to allow a full CI / CD
  • to publish to package after successful build to master, or on schedule
@jonathan-winn-geo jonathan-winn-geo added this to the Backlog milestone Jul 29, 2020
@jonathan-winn-geo jonathan-winn-geo self-assigned this Jul 29, 2020
@jonathan-winn-geo
Copy link
Collaborator Author

jonathan-winn-geo commented Jul 29, 2020

https://docs.github.com/en/actions/reference/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token

If you would like to trigger a workflow from a workflow run, you can trigger the event using a personal access token.
You'll need to create a personal access token and store it as a secret.
To minimize your GitHub Actions usage costs, ensure that you don't create recursive or unintended workflow runs.
For more information, see "Creating and storing encrypted secrets."

  • this approach is limited, as it is linked to one developer,by the personal access token, it would not be suitable for team use by an organisation
  • another method is needed
  • leaving this here for reference

@jonathan-winn-geo
Copy link
Collaborator Author

Tasks

  • create personal access token, store as secret =

@jonathan-winn-geo
Copy link
Collaborator Author

@jonathan-winn-geo
Copy link
Collaborator Author

jonathan-winn-geo commented Jul 29, 2020

workflows and events

You can configure your workflows to run when specific activity on GitHub happens, at a scheduled time, or when an event outside of GitHub occurs.

https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch

"The workflow files for that commit SHA and Git ref are inspected,
and a new workflow run is triggered for any workflows that have
on: values that match the triggering event."

To trigger specific workflows in a repository, use the workflow_dispatch event. To trigger more than one workflow in a repository and create custom events and event types, use the repository_dispatch event.

You can manually trigger a workflow run using the GitHub API and from GitHub. To trigger the custom workflow_dispatch webhook event using the REST API, you must send a POST request to a GitHub API endpoint and provide the ref and any required inputs. For more information, see the "Create a workflow dispatch event" REST API endpoint.

@jonathan-winn-geo jonathan-winn-geo changed the title Review and test options for multi workflow pipelines SPIKE: Review and test options for multi workflow pipelines Jul 29, 2020
@jonathan-winn-geo jonathan-winn-geo added cmascience cmascience related rep documentation Improvements or additions to documentation pipelines/workflows Automated pipelines / workflows / actions via GitHub question Further information is requested S.Slow (> 2 days) sprint ready Issue is ready to work on testing Testing code - automated pipeline or within app tests labels Oct 20, 2020
@github-project-automation github-project-automation bot moved this to To Do (long-term or to review) in cma-open-training Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmascience cmascience related rep documentation Improvements or additions to documentation pipelines/workflows Automated pipelines / workflows / actions via GitHub question Further information is requested S.Slow (> 2 days) sprint ready Issue is ready to work on testing Testing code - automated pipeline or within app tests
Projects
Status: To Do (long-term or to review)
Development

No branches or pull requests

1 participant