Skip to content

update manifest url to production server#9985

Merged
thomasneirynck merged 1 commit intoelastic:5.xfrom
thomasneirynck:update_manifest_url_prod
Jan 23, 2017
Merged

update manifest url to production server#9985
thomasneirynck merged 1 commit intoelastic:5.xfrom
thomasneirynck:update_manifest_url_prod

Conversation

@thomasneirynck
Copy link
Copy Markdown
Contributor

@thomasneirynck thomasneirynck commented Jan 20, 2017

Closes #9970

Use the production server on the feature branches

@thomasneirynck
Copy link
Copy Markdown
Contributor Author

jenkins, test this

@thomasneirynck
Copy link
Copy Markdown
Contributor Author

failing test is due to lucene issue

@thomasneirynck
Copy link
Copy Markdown
Contributor Author

@drewr @spalger @ppisljar could you add an LGTM to this? this updates the Kibana feature branches (5.2 and up) to the new production URL.

@drewr
Copy link
Copy Markdown

drewr commented Jan 23, 2017

LGTM 🎉

@thomasneirynck thomasneirynck merged commit deb399a into elastic:5.x Jan 23, 2017
elastic-jasper added a commit that referenced this pull request Jan 23, 2017
Backports PR #9985

**Commit 1:**
update manifest url to production server

* Original sha: bf6d130
* Authored by Thomas Neirynck <thomas@elastic.co> on 2017-01-20T20:52:43Z
thomasneirynck pushed a commit that referenced this pull request Jan 23, 2017
Backports PR #9985

**Commit 1:**
update manifest url to production server

* Original sha: bf6d130
* Authored by Thomas Neirynck <thomas@elastic.co> on 2017-01-20T20:52:43Z
@epixa
Copy link
Copy Markdown
Contributor

epixa commented Feb 14, 2017

@thomasneirynck Why wasn't this done in master?

@thomasneirynck
Copy link
Copy Markdown
Contributor Author

@epixa master uses the staging service (tiles-staging.elastic.co). release branches use production (tiles.elastic.co).

#10007 is a follow up to do this automatically, but these services weren't available until very close to 5.2, so we decided to do it manually first.

@epixa
Copy link
Copy Markdown
Contributor

epixa commented Feb 14, 2017

Thanks for the clarification

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants