NativeScript / NativeScript/android

CI/CD Broken?

Open
#1,623 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
563
Forks
144
Avg merge
10h 46m
Merged PRs (30d)
14

Description

Hello,

Wondering about the CI/CD process, seems like theres only running builds on PRs and not on master anymore?

https://travis-ci.org/github/NativeScript/android-runtime/builds

Also in README.md its stated that build is failing for android-runtime:

https://camo.githubusercontent.com/8b408336680e41143426654e4075f401e287e07f/68747470733a2f2f7472617669732d63692e6f72672f4e61746976655363726970742f616e64726f69642d72756e74696d652e7376673f6272616e63683d6d6173746572

"next" is pointing to something very old and PRs are not reachable by next-$DATE-$TRAVIS_BUILD_NUMBER
https://github.com/NativeScript/android-runtime/blob/master/.travis.yml#L6

Can we somehow support to get this smooth again?
Having a feeling that theres a lot of things not going in the right direction..

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the Travis CI builds linked in the issue, then compare the CI configuration in .travis.yml with the build status shown in README.md. Confirm whether master builds and next-$DATE-$TRAVIS_BUILD_NUMBER artifacts are still supported; the issue is done when the CI status and build references are current and working.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.