I pushed an empty commit not long ago and it took a few minutes for
tests to be started
On 11/2/18 11:13 AM, Kirk Lund wrote:
I just push an empty commit 15 minutes ago to my PR branch and it did not
trigger a precheckin. Should I just keep pushing empty commits until
something happens? Is the
That should be enough. Let me see what I can do.
On Fri, Nov 2, 2018 at 11:13 AM Kirk Lund wrote:
> I just push an empty commit 15 minutes ago to my PR branch and it did not
> trigger a precheckin. Should I just keep pushing empty commits until
> something happens? Is there another way to trigge
I just push an empty commit 15 minutes ago to my PR branch and it did not
trigger a precheckin. Should I just keep pushing empty commits until
something happens? Is there another way to trigger a precheckin? Sorry for
all the questions but I seem to be blocked.
https://github.com/apache/geode/pull
That's unfortunate, half of the precheckin jobs for my PR started correctly
and half of them failed with:
/usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/response/raise_error.rb:16:in
`on_complete': GET https://api.github.com/repos/apache/geode/pulls/2768:
404 - Not Found // See:
https://d
You can’t restart PR jobs even with access. Concourse will only restart the
latest PR, which may not be yours. To restart a PR check you push and empty
commit to your branch.
-Jake
> On Nov 2, 2018, at 10:38 AM, Kirk Lund wrote:
>
> I want to be able to restart my precheckin jobs. Specifical
I want to be able to restart my precheckin jobs. Specifically, I'd like to
restart the UnitTest job on my latest PR precheckin:
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-pr/jobs/UnitTest/builds/347
It seems to have hit a snag that's unrelated to my PR:
/usr/lib/ru
