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

[Agent] Investigate Jenkins CI for PRs targetting Fleet branch. #16290

Closed
ph opened this issue Feb 12, 2020 · 5 comments
Closed

[Agent] Investigate Jenkins CI for PRs targetting Fleet branch. #16290

ph opened this issue Feb 12, 2020 · 5 comments
Assignees
Labels
in progress Pull request is currently in progress. [zube]: In Progress

Comments

@ph
Copy link
Contributor

ph commented Feb 12, 2020

We use to have the Jenkins Ci run on our PRs but for a few days this doesn't appear to be the case we only have Travis-ci running. I am going to take a look, creating the issue so it's doesn't fall into a crack.

Did you saw the same behavior @michalpristas ?

@ph ph added in progress Pull request is currently in progress. [zube]: In Progress Project:fleet labels Feb 12, 2020
@ph ph self-assigned this Feb 12, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ingest (Project:fleet)

@michalpristas
Copy link
Contributor

i havent noticed as i mostly check Travis (i like UI better) but this is indeed weird

@ph
Copy link
Contributor Author

ph commented Feb 13, 2020

Yeah, after discussing over slack its because or feature branch doesn't follow the appropriate scheme for having them included we need to add `feature-* in front of our branch.

@ph
Copy link
Contributor Author

ph commented Feb 13, 2020

So I've renamed the fleet branch to feature-ingest, the same name as Kibaban this indeed fix the problems with the beats-ci job. I am almost certain that it did work at some point.

@ph ph closed this as completed Feb 13, 2020
@ph
Copy link
Contributor Author

ph commented Feb 13, 2020

Note, that renaming the branch did auto-close all the PRs that was targeting that branch.

If you want to see that beats-ci is running you can also take a look at #16314

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in progress Pull request is currently in progress. [zube]: In Progress
Projects
None yet
Development

No branches or pull requests

3 participants