Can someone educate me how to re-trigger a single test suite in CI?
On Thu, Feb 13, 2020 at 5:10 AM Lausen, Leonard
wrote:
> Hi Denis,
>
> pipeline may be the wrong word, job may be the correct one. For example,
> commiters can currently access a job page like
>
>
Hi Marco,
I've taken up the task to fix the CD pipeline [1] and it's pending CI checks
and merge. I also made the adjustments to the namespace layout of the mxnet s3
bucket and updated the static page which is now accessible from
https://repo.mxnet.io/dist/index.html.
Meanwhile, the access
Hi Denis,
pipeline may be the wrong word, job may be the correct one. For example,
commiters can currently access a job page like
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-17521/5/
, press "Login" and then the restart button to only
This might or might not work given that GH PR is failed or not given overall CI
run status, not just few builds from it. But it is a good suggestion to try
out, we will evaluate whether it could be accomplished. Thanks!
On 2/12/20, 11:05 AM, "Lausen, Leonard" wrote:
Thank you Denis for
We intend this bot to be very simplistic initially. But your idea is very
interesting and we will consider if we can roll this out as phase 2.
On 2/12/20, 10:57 AM, "PrzemysÅ≠aw TrÄ˙dak" wrote:
Hi Denis,
Could this bot be smart enough to first do the sanity pipeline (to catch
Thank you Denis for taking up this initiative. With respect to "Introduce
per-PR
CI bot" and the "[mxnet-ci] run" command. Would it make sense to add
"retriggering only failed pipelines" to the scope? For example users could be
asked to specify the name of the pipeline, or have "[mxnet-ci] run
Hi Denis,
Could this bot be smart enough to first do the sanity pipeline (to catch stuff
like lint errors etc.) before launching the full thing?
Thanks
Przemek
On 2020/02/12 18:12:07, "Davydenko, Denis"
wrote:
> Hello, MXNet dev community,
> As you all know, the experience with CI
Hello, MXNet dev community,
As you all know, the experience with CI infrastructure isn’t ideal in spite of
its high cost. For this reason, we’re proposing the following changes to
improve stability, reduce cost, and grant more control to contributors. As we
work in a refresh of CI, we believe
