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

fix(ci): ephemeral env build #26852

Merged
merged 5 commits into from
Jan 31, 2024
Merged

Conversation

dpgaspar
Copy link
Member

@dpgaspar dpgaspar commented Jan 29, 2024

SUMMARY

fixes ephemeral envs, broken by: #26473

I'm taking the ephemeral build out of the docker/pull_request workflow trigger and placing it on issue_comment.
issue_comment triggers at the issue level and uses the default branch latest SHA, this makes it hard to properly test CI workflow changes but on the other hand makes this path resilient to any possible issues caused by PRs.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

}
core.info(`Getting PR #${request.pull_number} from ${request.owner}/${request.repo}`)
const pr = await github.pulls.get(request);
Copy link
Member Author

Choose a reason for hiding this comment

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

To fetch the last SHA from the PR where the comment was made, more details here: actions/checkout#331

@rusackas
Copy link
Member

This seems stuck on the docker-build process... should we close/reopen the PR to kick-start it, or is it an actual problem with the PR?

@dpgaspar
Copy link
Member Author

dpgaspar commented Jan 31, 2024

This seems stuck on the docker-build process... should we close/reopen the PR to kick-start it, or is it an actual problem with the PR?

it's because of a defined required workflow that I'm removing here
fixed here: #26917

@dpgaspar dpgaspar merged commit 807c57c into apache:master Jan 31, 2024
28 checks passed
@dpgaspar dpgaspar deleted the fix/ephemeral-ci branch January 31, 2024 12:06
sfirke pushed a commit to sfirke/superset that referenced this pull request Mar 22, 2024
@mistercrunch mistercrunch added 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 4.0.0 labels Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/L 🚢 4.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants