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

OFFI-56: Adding Elasticsearch setup workflow #376

Merged
merged 23 commits into from
Jul 24, 2024
Merged

OFFI-56: Adding Elasticsearch setup workflow #376

merged 23 commits into from
Jul 24, 2024

Conversation

porgabi
Copy link
Member

@porgabi porgabi commented Jul 20, 2024

@wAsnk wAsnk added this pull request to the merge queue Jul 24, 2024
Merged via the queue into dev with commit 1922d7f Jul 24, 2024
6 checks passed
@Piedone
Copy link
Member

Piedone commented Jul 24, 2024

There's a container build step running before anything else, even if Elasticsearch setup is not enabled:

image

See https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/actions/runs/10082467596/job/27876788040.

Can this be avoided?

@porgabi
Copy link
Member Author

porgabi commented Jul 26, 2024

There's a container build step running before anything else, even if Elasticsearch setup is not enabled:

image

See https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/actions/runs/10082467596/job/27876788040.

Can this be avoided?

I can't quite tell why referencing the third-party action without actually running it does this.

@Piedone
Copy link
Member

Piedone commented Jul 26, 2024

Then you can look up if this is normal behavior for such an action using Docker and/or ask under the project.

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 this pull request may close these issues.

3 participants