Closed smarnach closed 8 years ago
Thanks for the pull request, @smarnach! It looks like you're a member of a company that does contract work for edX. If you're doing this work as part of a paid contract with edX, you should talk to edX about who will review this pull request. If this work is not part of a paid contract with edX, then you should ensure that there is an OSPR issue to track this work in JIRA, so that we don't lose track of your pull request.
To automatically create an OSPR issue for this pull request, just visit this link: https://openedx-webhooks.herokuapp.com/github/process_pr?repo=edx%2Fedx-analytics-configuration&number=27
After small comment, :+1:
:+1:
@e0d @mulby Thanks! I'll wait for @feanil to comment before merging.
@e0d @mulby I just noticed I don't have write permission for this repo, so one of you will have to merge this.
@feanil Thanks for confirming. I've changed the version to the edx fork of 1.9.3 now, since I'm not sure this would work with 2.x, and it probably makes sense to use the same version as in the configuration repo anyway.
@e0d @mulby Could one of you please merge the PR?
How critical is this change? It will require us to update all of our jenkins jobs I think...
I encountered 2 major issues:
@mulby That's unfortunate. We've been using the updated version for a while and didn't run into any problems. The reason for this upgrade were problem with the old verison @mtyaka experienced, see https://github.com/edx/edx-analytics-pipeline/pull/209#issuecomment-191629410. Matjaz, do you have any additional comments?
It would make sense to revisit this after we get jenkins setup automated.
JIRA ticket: OLIVE-18
This is a replacement for #19, which got closed and can't be re-opened. See also edx/edx-analytics-pipeline#209
@mulby Can you please take a look?