Skip to content

Restore the build cache prior to running bin/pre_compile#321

Closed
edmorley wants to merge 1 commit into
heroku:masterfrom
edmorley:restore-cache-earlier
Closed

Restore the build cache prior to running bin/pre_compile#321
edmorley wants to merge 1 commit into
heroku:masterfrom
edmorley:restore-cache-earlier

Conversation

@edmorley
Copy link
Copy Markdown
Member

@edmorley edmorley commented Aug 5, 2016

So that any changes made to .heroku/ within pre_compile (such as installing additional libraries required for the later pip install) are not clobbered by the cache being copied on top of it afterwards.

Fixes #320.

edmorley pushed a commit to mozilla/treeherder that referenced this pull request Aug 10, 2016
The Heroku pre_compile script is currently run prior to the cache being
restored (heroku/heroku-buildpack-python#321),
which means we have to tweak PATH so vendor-libmysqlclient.sh can find
the binaries from the cache instead of the app directory.

However the workaround added in #1770 only added one of the two extra
required PATHs, this adds the other.

Prior to this the buildpack compile would output:
> ./bin/vendor-libmysqlclient.sh: line 65: pip: command not found

...and so wouldn't purge the old mysqlclient package, which is needed to
force recompilation against the newer libmysqlclient.

Once the PR against heroku-buildpack-python is merged, these workarounds
can be removed.
@edmorley
Copy link
Copy Markdown
Member Author

Rebased against latest master.

@kennethreitz any idea when you might be able to take a look at this? :-)

@edmorley
Copy link
Copy Markdown
Member Author

edmorley commented Nov 7, 2016

Rebased against master.

@kennethreitz
Copy link
Copy Markdown
Contributor

rebase!

@edmorley
Copy link
Copy Markdown
Member Author

Done :-)

So that any changes made to `.heroku/` within pre_compile (such as
installing additional libraries required for the later pip install) are
not clobbered by the cache being copied over afterwards.

Fixes #320.
@kennethreitz
Copy link
Copy Markdown
Contributor

rebase :)

@edmorley
Copy link
Copy Markdown
Member Author

edmorley commented Mar 14, 2017

Rebased again, please could you reopen? :-)

@edmorley
Copy link
Copy Markdown
Member Author

Re-rebased after the re-landing of the bp-watch removal.

@kennethreitz could you reopen? :-)

@kennethreitz
Copy link
Copy Markdown
Contributor

Strangely, GitHub won't let me re-open this PR.

I'm very weary of making any changes to the caching logic, FWIW.

@kennethreitz
Copy link
Copy Markdown
Contributor

Can you open another PR? Sorry for the headache.

@kennethreitz
Copy link
Copy Markdown
Contributor

And for the untimeliness.

@edmorley
Copy link
Copy Markdown
Member Author

edmorley commented Apr 4, 2017

Strangely, GitHub won't let me re-open this PR.
Can you open another PR? Sorry for the headache.

Ah I think GitHub gets confused if the PR is rebased whilst being closed. I've reopened as #372.

@edmorley edmorley self-assigned this Nov 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants