-
Notifications
You must be signed in to change notification settings - Fork 7
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
TEST BUMP EE #368
base: master
Are you sure you want to change the base?
TEST BUMP EE #368
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/mergebot-test-dcos-enterprise/pull/243 |
@mesosphere-mergebot restart mergebot/test-imitation |
Expected Format: |
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
5 similar comments
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
Encountered the following error interfacing with JIRA while attempting to restart: <class 'TypeError'>: replace() takes no keyword arguments |
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
Encountered the following error interfacing with JIRA while attempting to restart: <class 'TypeError'>: the JSON object must be str, not 'Response' |
@mesosphere-mergebot restart mergebot/test-imitation D2IQ-67157 |
@mesosphere-mergebot restart mergebot/jenkins-test-imitation D2IQ-67157 |
No such status as mergebot/jenkins-test-imitation |
@mesosphere-mergebot restart mergebot/jenkins-test-imitation D2IQ-67157 |
Encountered the following error interfacing with JIRA while attempting to restart: <class 'NameError'>: name 'url' is not defined |
@mesosphere-mergebot restart mergebot/jenkins-test-imitation D2IQ-67157 |
Encountered the following error interfacing with JIRA while attempting to restart: <class 'NameError'>: name 'teamcity_logs_url' is not defined |
@mesosphere-mergebot restart mergebot/jenkins-test-imitation D2IQ-67157 |
Encountered the following error interfacing with JIRA while attempting to restart: <class 'NameError'>: name 'teamcity_logs_url' is not defined |
@mesosphere-mergebot restart mergebot/jenkins-test-imitation D2IQ-67157 |
Encountered the following error interfacing with JIRA while attempting to restart: <class 'NameError'>: name 'teamcity_logs_url' is not defined |
@mesosphere-mergebot restart mergebot/jenkins-test-imitation D2IQ-67157 |
Encountered the following error interfacing with JIRA while attempting to restart: <class 'NameError'>: name 'teamcity_logs_url' is not defined |
@mesosphere-mergebot restart mergebot/jenkins-test-imitation D2IQ-67157 |
@mesosphere-mergebot test all |
29 similar comments
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
@mesosphere-mergebot test all |
High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:
Related tickets (optional)
Other tickets related to this change:
Checklist for all PRs
CHANGES.md
or explain why this is not a user-facing change:Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath
packages
), then in addition to the above please also include:PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:
It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.