![]() ![]() 23:34 ` travis-ci: introduce a $jobname variable for 'ci/*' scripts SZEDER Gábor 23:34 ` travis-ci: clean up setting environment variables SZEDER 23:34 ` SZEDER Gábor * travis-ci: use 'set -x' in 'ci/*' scripts for extra tracing output Travis-ci: set GIT_TEST_HTTPD in 'ci/lib-travisci.sh' Travis-ci: move setting environment variables to 'ci/lib-travisci.sh' Travis-ci: introduce a $jobname variable for 'ci/*' scripts Travis-ci: use 'set -x' in 'ci/*' scripts for extra tracing output If we enable further knobs in the future. "GETTEXT_POISON-SPLIT_INDEX" is just too long to exist and won't scale Like "misc-knobs" or whatever, because the combination #Install git lfs travis PatchThis patch series conflicts with the last patch in Thomas' split indexįix conflict is not overly difficult, but to resolve it we should firstĬome up with a reasonable job name for that build job, e.g. Have now more freedom to set a specific variable only for specific build This patch series deals with this by adding means that 'ci/*' scriptsĬan use to identify which build job they are taking part in (patch 3),Īnd then setting environment variables in 'ci/lib-travisci.sh', where we Setting GIT_TEST_HTTPD to 'ci/lib-travisci.sh', like the quoted patchĭid with paths to P4 and Git LFS, because then it would be set for the 32īit Linux build job which runs everything as root, thus can't run https +++ -12,20 +12,18 case "$" inĪstute readers ) might have been wondering what's the deal with thisĮnvironment variable in the patch context, since this won't have anyĮffect outside of this script, either. Other 'ci/' scripts, so all those scripts will see the updated $PATHĬi/install-dependencies.sh | 10 ++++-Ģ files changed, 12 insertions(+), 6 deletions(-)ĭiff -git a/ci/install-dependencies.sh b/ci/install-dependencies.sh Move adjusting $PATH to 'ci/lib-travisci.sh', which is sourced in all Modifies $PATH, but to no effect, because 'ci/run-tests.sh' only sees This case, 'ci/install-dependencies.sh' downloads P4 and Git LFS and Only visible in that single script but not in any of the others. Separate shell processes, any variable set in one of those scripts is However, after theseĮmbedded scriptlets were moved into dedicated scripts executed in Was visible during the rest of the build job. Set in a scriptlet embedded in our '.travis.yml', thus its new value This worked just fine before said commit, because $PATH was ![]() The reason is that P4 and Git LFS binaries are not installed to aĭirectory in the default $PATH, but their directories are prepended to Scripts, ), claiming there are no P4 or Git LFS installed. #Install git lfs travis codeLinux build jobs on Travis CI skip the P4 and Git LFS tests sinceĬommit 657343a60 (travis-ci: move Travis CI code into dedicated To: Lars Schneider, Junio C Hamano +Cc: git, SZEDER Gábor 23:34 ` travis-ci: clean up setting environment variables SZEDER GáborĠ siblings, 1 reply 44+ messages in thread #Install git lfs travis archiveTravis-ci: fix running P4 and Git LFS tests in Linux build jobs archive mirror help / color / mirror / Atom feed * travis-ci: fix running P4 and Git LFS tests in Linux build jobs 11:55 SZEDER Gábor ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |