Oh. That wouldn't be ideal.
Thank You for sharing!
Regards,
-Tanay
On Sun, Jul 21, 2019 at 2:20 AM Valentyn Tymofieiev
wrote:
> The GitHub pull request builder plugin, which we currently use, allow only
> one trigger phrase per Jenkins job [1].
>
> We could have another job that runs all 4
Thank You! Looking forward to this :)
On Sun, Jul 21, 2019 at 2:35 AM Pablo Estrada wrote:
> Hello all,
>
> This will be streamed on youtube on this link:
> https://www.youtube.com/watch?v=xpIpEO4PUDo
>
> I think there will be a live chat, so I will hopefully be available to
> answer questions.
Hello all,
This will be streamed on youtube on this link:
https://www.youtube.com/watch?v=xpIpEO4PUDo
I think there will be a live chat, so I will hopefully be available to
answer questions. To be honest, my workflow is not super efficient, but...
oh well, hopefully it will be at least somewhat
The GitHub pull request builder plugin, which we currently use, allow only
one trigger phrase per Jenkins job [1].
We could have another job that runs all 4 postcommits, but it would appear
on a PR as a different job, separate from per-minor-version jobs.
[1]
Never seems to time out or finish for me:
$ ./gradlew :sdks:java:io:amazon-web-services:test
Starting a Gradle Daemon, 1 busy Daemon could not be reused, use
--status for details
Configuration on demand is an incubating feature.
<=<-> 98% EXECUTING [22m 21s]
> IDLE
> IDLE
> IDLE
>
Hi Anton,
It should not be a machine issue, since you have the container got started.
I would say give it around 5 - 10 minutes, it would throw out connection
time out error log. This usually happens when the integration tests can't
connect to the container. As you may notice, in the tests we
I've seen this myself trying to run tests in Linux (Goobuntu).
On Fri, Jul 19, 2019 at 1:15 PM Anton Kedin wrote:
>
> Hi dev@,
>
> Does anyone know if there's anything extra needed to run `DynamoDBIOTest`? If
> I do `./graldew :sdks:java:io:amazon-web-services:build --debug` it passes
> few
