Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
update_repo
#432update_repo
#432Changes from all commits
d43dd41
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Note that we are using an unstable development snapshot of ODK here - I am cool with this, indeed, I have been testing this very same pipeline locally (with the updates in this PR), but we need to remember that it is.
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.
Sorry, I actually forgot you'd already told me to do this.
Questions / issues
This will be tricky for me to remember the next time I do it months from now. Is there any way to automate this so that I don't have to remember it?
Is there a specific reason why we're you're asking for
ODK_TAG=v1.4.3
instead oflatest
?If I don't specify an
ODK_TAG
, why isn't it defaulting tolatest
?I would figure that's what would happen, since in
run.sh
it has:ODK_TAG=${ODK_TAG:-latest}
I'm getting the same results if I run
ODK_TAG=v1.4.3 sh run.sh make update_repo
orsh run.sh make ODK_TAG=v1.4.3 update_repo
as when I runsh run.sh make update_repo
. Why?The changes are exactly the same; there is no diff. I started on a fresh branch and compared the results. Even the
Makefile
still says# ODK Version: v1.5-dev
.Also, I recollect you saying something a few months ago about how now "dev would run by default". Do you remember that? Is this simply a result of some configuration you did regarding that? Given (3), I would expect
-latest
to run, but it appears that is not so.Log
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.
No, using
latest
andv1.4.3
would be the same. I need to usev1.4.3
because I also built the ODK locally on my machine, so mylatest
is not the officiallatest
.see file
src/ontology/run.sh.conf
which specifies the default environment variables. We needdev
for everything other thanupdate_repo
.I dont know. I run
ODK_TAG=v1.4.3 ./run.sh make update_repo
but I cant imagine that makes a difference.run.sh.conf
should determine your defaults.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 haven't looked at
run.sh.conf
before, I'll take a look. If I'm still confounded after that, maybe I can show you on Monday.