Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upRun automated tests on PRs before merging #2725
Comments
andrewdavidwong
added
C: website
enhancement
labels
Mar 24, 2017
andrewdavidwong
added this to the
Documentation/website milestone
Mar 24, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Will look into it, shouldn't be that hard. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Apr 19, 2017
Contributor
I have some WIP initial testing in here and here. General idea is to always checkout qubesos.github.io, have a _utils/travis.sh script there which properly checks out upstream version of all submodules, substituting specific repo under test. Then run tests on that.
WIP version is broken because it uses master rather than the PR. Fix should be simple but I won't have time to work on this (or really anything qubes-related) for the next few weeks, so just sharing WIP version in case anyone wants to pick it up in the mean time.
Once that works, I've also implemented incremental spell checking. Will merge after.
|
I have some WIP initial testing in here and here. General idea is to always checkout qubesos.github.io, have a _utils/travis.sh script there which properly checks out upstream version of all submodules, substituting specific repo under test. Then run tests on that. WIP version is broken because it uses master rather than the PR. Fix should be simple but I won't have time to work on this (or really anything qubes-related) for the next few weeks, so just sharing WIP version in case anyone wants to pick it up in the mean time. Once that works, I've also implemented incremental spell checking. Will merge after. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Apr 19, 2017
Member
The easiest way to make it working on the right sources (PR instead of master) is rely on Travis and use whatever it downloaded. Like here:
https://github.com/QubesOS/qubes-builder/blob/master/scripts/travis-build#L63-L67
|
The easiest way to make it working on the right sources (PR instead of master) is rely on Travis and use whatever it downloaded. Like here: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
May 6, 2017
Contributor
@marmarek I see you've started merging this. A few notes:
- The reason I had a separate old_site and new_site dirs checked out in separate locations simultaneously is because I found some checks (for example reporting words introduced by the PR not found in the dictionary nor in existing documentation text) seem to make the most sense to implement by building both new and old
_sites and diffing results of scripts run each. - I intentionally used all repos of the owner of the "base" of the PR rather than hard-coding QubesOS, which means it's possible to test net effect of changes in multiple repos before sending any PR to QubesOS/*. IMO that behavior is worth retaining.
I'm in final exams right now, otherwise I'd have sent PRs already :)
|
@marmarek I see you've started merging this. A few notes:
I'm in final exams right now, otherwise I'd have sent PRs already :) |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 6, 2017
Member
|
On Fri, May 05, 2017 at 06:03:04PM -0700, Jean-Philippe Ouellet wrote:
@marmarek I see you've started merging this. A few notes:
1. The reason I had a separate old_site and new_site dirs checked out in separate locations simultaneously is because I found some checks (for example reporting words introduced by the PR not found in the dictionary *nor in existing documentation text*) seem to make the most sense to implement by building both new and old `_site`s and diffing results of scripts run each.
I see, I've retained this behaviour - simply use ./_site instead of
"~/new_site".
2. I intentionally used all repos of the owner of the "base" of the PR rather than hard-coding QubesOS, which means it's possible to test net effect of changes in multiple repos before sending any PR to QubesOS/*. IMO that behavior is worth retaining.
+1
I'm in final exams right now, otherwise I'd have sent PRs already :)
Good luck :)
…--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
added a commit
to QubesOS/qubesos.github.io
that referenced
this issue
May 6, 2017
marmarek
closed this
in
QubesOS/qubes-doc@3ae2b4f
May 6, 2017
added a commit
to QubesOS/qubes-posts
that referenced
this issue
May 6, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
May 6, 2017
Member
Merged work by @jpouellet . For now I've enabled it for qubes-doc and qubes-posts repos. Unfortunately it will work only for new PRs (made from just updated master) - there is no no easy way to add this to all those existing PRs...
But there is a trick: you can merge a bunch of PRs into some test branch, push it (without signed tag yet) and wait for Travis to check it. If ok, sign and push to master.
|
Merged work by @jpouellet . For now I've enabled it for qubes-doc and qubes-posts repos. Unfortunately it will work only for new PRs (made from just updated master) - there is no no easy way to add this to all those existing PRs... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Thanks, @jpouellet and @marmarek! |
jpouellet
referenced this issue
in QubesOS/qubes-doc
May 25, 2017
Merged
Various minor spelling and grammar fixes #421
added a commit
to jpouellet/qubesos.github.io
that referenced
this issue
Jul 4, 2017
added a commit
to jpouellet/qubesos.github.io
that referenced
this issue
Jul 4, 2017
jpouellet
referenced this issue
in QubesOS/qubesos.github.io
Jul 4, 2017
Closed
Differential spell checking #110
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@marmarek, can you please enable this on the HCL subrepo? |
andrewdavidwong
reopened this
Jul 8, 2017
andrewdavidwong
assigned
marmarek
Jul 8, 2017
added a commit
to QubesOS/qubes-hcl
that referenced
this issue
Jul 11, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Done. |
marmarek
closed this
Jul 11, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Thanks, @marmarek! |
pushed a commit
to qubesos-bot-jpo/qubesos.github.io
that referenced
this issue
Jul 22, 2017
added a commit
to jpouellet/qubesos.github.io
that referenced
this issue
Jul 22, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Jul 22, 2017
Contributor
xref #2935 (qubesos.github.io: travis builds ~/old_site using merge head instead of base)
|
xref #2935 (qubesos.github.io: travis builds ~/old_site using merge head instead of base) |
andrewdavidwong commentedMar 24, 2017
@marmarek: Is there a way we can run automated Travis CI test on qubes-doc and website PRs before merging them? I often find that I merge a qubes-doc PR only to have it report a broken link after your automated script updates the submodule. It would be great for PR contributors to be able to see that their PR is going to break a link and fix it before I merge.