Skip to content

Refactor CI pipeline action #18359

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

Merged
merged 3 commits into from
Jul 27, 2023
Merged

Refactor CI pipeline action #18359

merged 3 commits into from
Jul 27, 2023

Conversation

aledbf
Copy link
Member

@aledbf aledbf commented Jul 26, 2023

Description

Summary generated by Copilot

🤖 Generated by Copilot at 4fcd49a

Refactor GitHub workflows to use generic actions for self-hosted runners on GCP. Delete unused workflow files and merge related workflows into build.yml.

Related Issue(s)

Fixes #

How to test

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

Build Options

Build
  • /werft with-werft
    Run the build with werft instead of GHA
  • leeway-no-cache
  • /werft no-test
    Run Leeway with --dont-test
Publish
  • /werft publish-to-npm
  • /werft publish-to-jb-marketplace
Installer
  • analytics=segment
  • with-dedicated-emulation
  • workspace-feature-flags
    Add desired feature flags to the end of the line above, space separated
Preview Environment
  • /werft with-local-preview
    If enabled this will build install/preview
  • /werft with-preview
  • /werft with-large-vm
  • /werft with-gce-vm
    If enabled this will create the environment on GCE infra
  • with-integration-tests=workspace
    Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh
  • with-monitoring

/hold

@@ -13,8 +13,10 @@ on:

jobs:
create-runner:
uses: ./.github/workflows/create_runner.yml
secrets: inherit
uses: gitpod-io/gce-github-runner/.github/workflows/create-vm.yml@secrets
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we update @secrets to @main before merging (which I guess means merge the PR for the secrets branch?). Think otherwise this will break once the secrets branch gets removed due to the PR merging

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to that in a different PR. I am using the same thing for dedicated.

Think otherwise this will break once the secrets branch gets removed due to the PR merging

Good point. That said, that feature is disabled in the gce-github-runner repository.

@roboquat roboquat merged commit 62ec096 into main Jul 27, 2023
@roboquat roboquat deleted the aledbf/pipeline-1 branch July 27, 2023 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants