CI/CD Broken?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- ci-cd
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.
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:
"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..
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NativeScript/android
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
NativeScript/android#2039 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
NativeScript/android#2024 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
NativeScript/android#2020 ·
-
Difficulty 5/5 Over a week Newbie friendliness 42/100
NativeScript/android#2019 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
NativeScript/android#1986 ·
All issues in NativeScript/android
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·