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
Updated mesos package to use cmake. #7190
Conversation
This repo has @mesosphere-mergebot integration. You can perform the following commands by submitting a comment. Submit a comment with content "@mesosphere-mergebot help" to view more detailed help text and examples. Be sure the have a look at the mergebot documentation, too.
|
@mesosphere-mergebot bump-ee |
Enterprise Bump PR: mesosphere/dcos-enterprise/pull/7733 |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
f70ea6d
to
5aec4be
Compare
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
@mesosphere-mergebot bump-ee |
@mesosphere-mergebot label Ready For Review |
@akornatskyy note that the build the EE bump fails (the mergebot/enterprise/build-status/aggregate check below, also see the EE bump PR), because dcos-ee-mesos-modules still use the automake build. Please incorporate your changes from This is the case when we have to change OSS and EE together. |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akornatskyy Thanks for all this work!
If the remaining integration tests pass (I think now it is reasonable to hope that they will), the only thing that prevents us from merging this patch will be the Mesos bump that brings in the libprocess configuration fix that will resolve the failing memory profiler test.
After that bump gets into DCOS and if nothing else comes up, we (I/Greg/someone lese) will be able to land this PR pair.
@mesosphere-mergebot bump-ee |
Your pull request's branch is not based on the most recent version of |
@mesosphere-mergebot bump-ee |
Enterprise Bump mesosphere/dcos-enterprise/pull/7733 updated. |
@mesosphere-mergebot changelog-not-required No user-facing change. |
CHANGES.MD check override issued with the provided reason: No user-facing change. |
"git": "https://github.com/apache/mesos", | ||
"ref": "3d68993c8743231b6067738050786e750edda9b1", | ||
"ref_origin": "master" | ||
"sources": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @akornatskyy @asekretenko ,
Do you happen to remember what was the reason to change this from single_source
to sources
? I'm asking because unfortunatelly it broke our 'Bump Mesos CI' script: https://jenkins.mesosphere.com/service/jenkins/view/Mesos/job/mesos/job/BumpDCOS/job/Bump_DCOS_Mesos_And_Modules/645/console
Does it make sense to change it back to single_source
? Any concerns?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see much sense for this change... but generally speaking using single_source
should work as well. no concerns.
…ages. This patch reverts back changes made in PR dcos#7190.
…ages. This patch reverts back some changes made in PR dcos#7190.
High-level description
Build dcos linux mesos package with cmake.
Corresponding DC/OS tickets (required)