| Age | Commit message (Collapse) | Author |
|
run.sh is added, which is a shorthand for running
`docker-compose -f devtools/docker/compose.yaml`.
The dockercompose function from devtools/docker.sh is also now used
where applicable.
Change-Id: I424157c25b4ad7f96d23ba37c3dc2cb4caa34c8c
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/339392
Trust: Julie Qiu <julie@golang.org>
Run-TryBot: Julie Qiu <julie@golang.org>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
|
|
To prevent bloat on host machines adding the remove
option to docker-compose run commands for the nodejs
service.
Change-Id: I4e1db7edaf127848dadeb34f3d1aa69512cb2501
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/334257
Trust: Jamal Carvalho <jamal@golang.org>
Run-TryBot: Jamal Carvalho <jamal@golang.org>
Reviewed-by: Julie Qiu <julie@golang.org>
|
|
The "docker-" is removed from docker-compose.yaml to remove unnecessary
repetition.
Change-Id: I9a4bfcb7dcb52281f49d2c67361454d900ce38c5
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/334449
Trust: Julie Qiu <julie@golang.org>
Run-TryBot: Julie Qiu <julie@golang.org>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Jonathan Amsterdam <jba@google.com>
|
|
Now that we can use the nodejs in the docker-compose file for running
e2e tests against different environments, switch back to using the
nodejs set up using docker-compose.
This reverts commit bd83a0e9ec81216a0dd3c749ce7a98fc7a18ffb7.
Change-Id: Ia19e3415b85cd4ff726e80913bc9e0a4cdb095e4
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/329916
Trust: Julie Qiu <julie@golang.org>
Reviewed-by: Jonathan Amsterdam <jba@google.com>
|
|
Revert the change to devtools/nodejs.sh in CL 328890 for the deployment
script to work.
Shared logic between the two scripts will be updated in a future CL.
Change-Id: I5e14d080f0d2a0d769391ab1e056e9a23288cd44
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/329909
Trust: Julie Qiu <julie@golang.org>
Run-TryBot: Julie Qiu <julie@golang.org>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
|
|
The docker command in devtools/nodejs.sh is moved to docker-compose.
Change-Id: I0ee98fcbe6007729cb4e4dd57381d2d674d58347
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/328890
Trust: Julie Qiu <julie@golang.org>
Run-TryBot: Julie Qiu <julie@golang.org>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Jamal Carvalho <jamal@golang.org>
Reviewed-by: Jonathan Amsterdam <jba@google.com>
|
|
Adds CI to clean up logs and run tools in continuous integration mode.
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD will skip chromium downloads during
npm installs.
Change-Id: I85ceca9d5b95b70b07feed5085d86cba571aff7d
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/328634
Trust: Jamal Carvalho <jamal@golang.org>
Run-TryBot: Jamal Carvalho <jamal@golang.org>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Jonathan Amsterdam <jba@google.com>
|
|
The internal kokoro build.sh currently runs the following:
devtools/ci/ci.sh
devtools/ci/nodejs.sh npm install --quiet
devtools/ci/nodejs.sh npm run lint
devtools/ci/nodejs.sh npm run test
devtools/ci/e2e.sh
Rather than having multiple files referenced in the internal kokoro
file, moving these tests to ci.sh. That way it is more opaque what we
are running in CI, and easier to add/remove files and comment out lines
for testing.
devtools/ci/nodejs.sh will be deleted in a future CL once it has been
removed from the internal build.sh.
Change-Id: I397a5d5cd2efb59da7a771617330f70b980911b0
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/326970
Trust: Julie Qiu <julie@golang.org>
Run-TryBot: Julie Qiu <julie@golang.org>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Jonathan Amsterdam <jba@google.com>
|
|
A copy of devtools/ci/nodejs.sh is made to devtools/nodejs.sh, and the
latter is now referenced where devtools/ci/nodejs.sh was previously used.
This makes it easier to comment out tests when testing configuration
changes to kokoro.
Also, since the contents of ./devtools/nodejs.sh are used in non-ci
parts of the repo, so it makes sense to have that script outside the ci/
folder.
In a future CL, rather than having these 3 lines in the kokoro config:
devtools/ci/nodejs.sh npm install --quiet
devtools/ci/nodejs.sh npm run lint
devtools/ci/nodejs.sh npm run test
They will be moved to devtools/ci/nodejs.sh, which will use
devtools/nodejs.sh.
Change-Id: I156324a625666ead31be18ae19e5608d38e0faf1
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/326989
Trust: Julie Qiu <julie@golang.org>
Run-TryBot: Julie Qiu <julie@golang.org>
Reviewed-by: Jonathan Amsterdam <jba@google.com>
|