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

Adjust CI configuration #16216

Merged
merged 2 commits into from
Feb 12, 2020
Merged

Adjust CI configuration #16216

merged 2 commits into from
Feb 12, 2020

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Feb 10, 2020

What does this PR do?

This PR adjust the path of the generators as these have been moved.

Why is it important?

It has to be adjusted, otherwise the CI jobs cannot start.

Checklist

- [ ] My code follows the style guidelines of this project
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] I have made corresponding change to the default configuration files
- [ ] I have added tests that prove my fix is effective or that my feature works

Requies #16127

@kvch kvch mentioned this pull request Feb 10, 2020
18 tasks
@ycombinator ycombinator self-assigned this Feb 10, 2020
@ycombinator ycombinator self-requested a review February 10, 2020 17:20
@@ -32,7 +32,7 @@ $env:TEST_COVERAGE = "true"
$env:RACE_DETECTOR = "true"

# Install mage from vendor.
exec { go install github.com/elastic/beats/vendor/github.com/magefile/mage } "mage install FAILURE"
exec { go install -mod=vendor github.com/magefile/mage } "mage install FAILURE"
Copy link
Contributor

@ycombinator ycombinator Feb 10, 2020

Choose a reason for hiding this comment

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

Just for my understanding, this change is not really related to the _templates path change, right? It's just another change needed when moving to go modules?

Copy link
Contributor

@ycombinator ycombinator left a comment

Choose a reason for hiding this comment

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

Template path changes LGTM, as a follow up to the changes made in #15688.

@kvch
Copy link
Contributor Author

kvch commented Feb 11, 2020

jenkins test this

@kvch kvch merged commit 4c53445 into elastic:go-modules Feb 12, 2020
kvch added a commit that referenced this pull request Feb 26, 2020
## What does this PR do?

This PR adjust the path of the generators as these have been moved.

## Why is it important?

It has to be adjusted, otherwise the CI jobs cannot start.
kvch added a commit that referenced this pull request Feb 27, 2020
## What does this PR do?

This PR adjust the path of the generators as these have been moved.

## Why is it important?

It has to be adjusted, otherwise the CI jobs cannot start.
kvch added a commit that referenced this pull request Feb 28, 2020
## What does this PR do?

This PR adjust the path of the generators as these have been moved.

## Why is it important?

It has to be adjusted, otherwise the CI jobs cannot start.
kvch added a commit that referenced this pull request Mar 2, 2020
## What does this PR do?

This PR adjust the path of the generators as these have been moved.

## Why is it important?

It has to be adjusted, otherwise the CI jobs cannot start.
kvch added a commit that referenced this pull request Mar 3, 2020
## What does this PR do?

This PR adjust the path of the generators as these have been moved.

## Why is it important?

It has to be adjusted, otherwise the CI jobs cannot start.
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
## What does this PR do?

This PR adjust the path of the generators as these have been moved.

## Why is it important?

It has to be adjusted, otherwise the CI jobs cannot start.
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.

2 participants