git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 1/3] Add Travis CI support

From
Lars Schneider <larsxschneider@gmail.com>
Date
Oct 12, 2015, 19:43 UTC
Message-ID
<61B448FB-DB61-42B6-ACDF-181F76169061@gmail.com>
In-Reply-To
<CAHGBnuOqVPHAhfN6qtt=VDODW9h+A1xMEnzaZfD61DCNyj_YOg@mail.gmail.com>
On 12 Oct 2015, at 12:37, Sebastian Schuberth <sschuberth@gmail.com> wrote:
Show 19 quoted lines
> On Mon, Oct 12, 2015 at 7:12 PM, Lars Schneider
> <larsxschneider@gmail.com> wrote:
> 
>>>> +install: make configure && ./configure
>>>> +
>>>> +before_script: make
>>>> +
>>>> +script: make --quiet test
>>> 
>>> Semantically, it does not seem correct to me that configuarion goes to the install step. As "make test" will build git anyway, I'd instead propose to get rid of "install" and just say:
>>> 
>>> before_script: make configure && ./configure
>>> 
>>> script: make --quiet test
>> 
>> I understand your point. I did this to make the "make" logs easily accessible (no option "--quite"). By default Travis CI automatically collapses the logs from all stages prior to the "script" stage. You can uncollapse these logs by clicking on the little triangle on the left border of the log. Therefore the "make" logs are available without noise.
> 
> To make this more clear, I guess what you're referring to is the
> visual difference between [1] and [2], correct?
correct!
Show 16 quoted lines
> 
>> Do you see value in "make" logs?
>> 
>> If yes then we could also do:
>> before_script: make configure && ./configure && make
> 
> Reading through Travis' docs [3] again, "before_script" is documented
> to "return a non-zero exit code, the build is errored and stops
> immediately", while "script" is documented as "returns a non-zero exit
> code, the build is failed, but continues to run before being marked as
> failed". As it does not make much sense to continue the build or even
> start testing if the build failed, maybe it's indeed best to do:
> 
> before_script: make configure && ./configure && make
> 
> script: make --quiet test
Ok, then I will make it so :-)

Thanks, Lars

Previous: Sebastian SchuberthNext: Sebastian Schuberth
Message 13 of 29 in “Add Travis CI support”
  1. 0/3 Add Travis CI supportlarsxschneider@gmail.com, Oct 11, 2015
  2. 1/3 Add Travis CI supportlarsxschneider@gmail.com, Oct 11, 2015
  3. Eric SunshineOct 11, 2015
  4. Lars SchneiderOct 12, 2015
  5. Sebastian SchuberthOct 12, 2015
  6. Junio C HamanoOct 12, 2015
  7. Sebastian SchuberthOct 12, 2015
  8. Lars SchneiderOct 12, 2015
  9. Sebastian SchuberthOct 12, 2015
  10. Matthieu MoyOct 12, 2015
  11. Lars SchneiderOct 12, 2015
  12. Sebastian SchuberthOct 12, 2015
  13. Lars SchneiderOct 12, 2015
  14. Sebastian SchuberthOct 12, 2015
  15. Matthieu MoyOct 12, 2015
  16. Lars SchneiderOct 14, 2015
  17. Matthieu MoyOct 15, 2015
  18. Jean-Noël AvilaOct 15, 2015
  19. Jean-Noël AvilaOct 13, 2015
  20. Lars SchneiderOct 15, 2015
  21. Matthieu MoyOct 15, 2015
  22. Lars SchneiderOct 15, 2015
  23. Johannes SchindelinOct 15, 2015
  24. Matthieu MoyOct 15, 2015
  25. 2/3 git-p4: Improve test case portability for t9815 git-p4-submit-faillarsxschneider@gmail.com, Oct 11, 2015
  26. 3/3 git-p4: Skip t9819 test case on case insensitive file systemslarsxschneider@gmail.com, Oct 11, 2015
  27. Luke DiamandOct 12, 2015
  28. Junio C HamanoOct 12, 2015
  29. Junio C HamanoOct 12, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.