bitrise-io / bitrise-steplib Goto Github PK
View Code? Open in Web Editor NEWNew Bitrise StepLib
License: MIT License
New Bitrise StepLib
License: MIT License
Hi 👋🏻,
after upgrading from Xcode 12.4 stack, sonarqube-scanner
step stops working. The exact same config for the step is used. Please find step output below:
+------------------------------------------------------------------------------+
| (3) SonarQube Scanner - PR |
+------------------------------------------------------------------------------+
| id: sonarqube-scanner |
| version: 1.0.7 |
| collection: https://github.com/bitrise-io/bitrise-steplib.git |
| toolkit: bash |
| time: 2021-09-07T10:48:39Z |
+------------------------------------------------------------------------------+
| |
INFO[10:48:39] * [OK] Step dependency (unzip) installed, available.
INFO[10:48:39] * [OK] Step dependency (wget) installed, available.
/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/bitrise606852322/step_src/step.sh: line 18: [: 0 2021-04-20: integer expression expected
/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/tmp.tpvwk2AM ~/git
--2021-09-07 10:48:41-- https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-4.3.0.2102.zip
Resolving binaries.sonarsource.com (binaries.sonarsource.com)... 91.134.125.245
Connecting to binaries.sonarsource.com (binaries.sonarsource.com)|91.134.125.245|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 588561 (575K) [application/zip]
Saving to: ‘sonar-scanner-cli-4.3.0.2102.zip’
0K .......... .......... .......... .......... .......... 8% 158K 3s
50K .......... .......... .......... .......... .......... 17% 310K 2s
100K .......... .......... .......... .......... .......... 26% 2.73M 1s
150K .......... .......... .......... .......... .......... 34% 368K 1s
200K .......... .......... .......... .......... .......... 43% 1.93M 1s
250K .......... .......... .......... .......... .......... 52% 5.85M 1s
300K .......... .......... .......... .......... .......... 60% 18.8M 0s
350K .......... .......... .......... .......... .......... 69% 23.4M 0s
400K .......... .......... .......... .......... .......... 78% 399K 0s
450K .......... .......... .......... .......... .......... 86% 3.44M 0s
500K .......... .......... .......... .......... .......... 95% 4.84M 0s
550K .......... .......... .... 100% 24.4M=0.8s
2021-09-07 10:48:43 (700 KB/s) - ‘sonar-scanner-cli-4.3.0.2102.zip’ saved [588561/588561]
Archive: sonar-scanner-cli-4.3.0.2102.zip
creating: sonar-scanner-4.3.0.2102/
creating: sonar-scanner-4.3.0.2102/bin/
creating: sonar-scanner-4.3.0.2102/conf/
creating: sonar-scanner-4.3.0.2102/lib/
inflating: sonar-scanner-4.3.0.2102/bin/sonar-scanner.bat
inflating: sonar-scanner-4.3.0.2102/bin/sonar-scanner-debug
inflating: sonar-scanner-4.3.0.2102/conf/sonar-scanner.properties
inflating: sonar-scanner-4.3.0.2102/lib/sonar-scanner-cli-4.3.0.2102.jar
inflating: sonar-scanner-4.3.0.2102/bin/sonar-scanner-debug.bat
inflating: sonar-scanner-4.3.0.2102/bin/sonar-scanner
~/git
It never goes after that and just hangs there until build timeout. I am happy to provide any additional information that might be needed to fix this issue :)
When using JDK 11, android-sdk-update step failed with this stacktrace:
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/bind/annotation/XmlSchema
at com.android.repository.api.SchemaModule$SchemaModuleVersion.(SchemaModule.java:156)
at com.android.repository.api.SchemaModule.(SchemaModule.java:75)
at com.android.sdklib.repository.AndroidSdkHandler.(AndroidSdkHandler.java:81)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:73)
at com.android.sdklib.tool.sdkmanager.SdkManagerCli.main(SdkManagerCli.java:48)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.annotation.XmlSchema
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
Do you have plan to fix this error on this step ? thank you in advance
When we upload android builds to deploygate, the link to download the apk is expired after a week. This is happening because of the expiration time mentioned in the URL. Where we can change this time?
Example download link: https://d2fjxyapcfdbwq.cloudfront.net/binaries/Global/60170/3553_36f6f68e67fd951c20520fbbf0fb31/app-name-production-release-bitrise-signed.apk?Expires=1606306514&Signature=XXX&Key-Pair-Id=XXX
If i.e BITRISE_IPA_PATH
is defined then this line produces:
app_path: /path/to/ipa||
and then next step that uses the app_path
fails, because it contains two column characters at the end. Previous version 0.8.0
had one one column character at the end and somehow it did not bother other steps.
/cc @guness
I tried fixing it in steplib but could not find a way to inject some sort of script to resolve it as it was intended. Probably the best way is to do three separate variables and resolve in the step source.
For our dev builds, we are trying to expose the exact commit that triggered the build within the app so that they can reference it quickly or have it available. Unfortunately, on PRs the GIT_CLONE_COMMIT_HASH
is the outcome of the merge from staging versus the commit as cloned.
Example Values:
=> GIT_CLONE_COMMIT_HASH
value: ee8ca46253400cfdc3c63c6facd2dfbf47863a28
=> GIT_CLONE_COMMIT_MESSAGE_SUBJECT
value: Merge commit '6a066ad5f4bb236dce7f677373951430bd9807b5' into staging
On PR Builds, would Like GIT_CLONE_TRIGGERED_COMMIT_HASH to be the value embedded within the GIT_CLONE_COMMIT_MESSAGE_SUBJECT. As of now, I'm going to write a REGEX to pull that information out so that I can set as an environment variable for my app to read and report. Yes, I know that technically the compiled/merged version is what is ultimately used to produce the app, but since that commit never makes it back to my GitHub repo, it's not helpful from a search/audit trail perspecxtive.
In React Native 0.61, we're seeing issues with running pod install
vs pod update
, but the step doesn't appear to have a flag to switch between the two. We're going to move towards the more generic script step in the meantime, but it would be great if we could toggle between the two.
The distinction is noted here https://guides.cocoapods.org/using/pod-install-vs-update.html.
Hi, since upgrading to 2.8.X from 2.7.X I can no longer build/archive my tvOS target.
2.8.X
xcodebuild “-workspace” “/Users/vagrant/git/Kowalski.xcworkspace” “-scheme” “Kowalski TV” “-configuration” “Release” “COMPILER_INDEX_STORE_ENABLE=NO” “clean” “archive” “-archivePath” “/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/__archive__058960730/Kowalski TV.xcarchive” “-destination” “generic/platform=iOS” | xcpretty
2.7.X
xcodebuild “-workspace” “/Users/vagrant/git/Kowalski.xcworkspace” “-scheme” “Kowalski TV” “-configuration” “Release” “COMPILER_INDEX_STORE_ENABLE=NO” “clean” “archive” “-archivePath” “/var/folders/6q/wgy6jtp12w5gzgm9lzcglpqw0000gn/T/__archive__245322915/Kowalski TV.xcarchive” | xcpretty
As you can see there is the new destination parameter (iOS) which I can't seem to be able to edit in the step configuration.
Here is the error we get
xcodebuild: error: Unable to find a destination matching the provided destination specifier:
{ generic:1, platform:iOS }
Regards
Hello
I have a step failing with the following log :
+------------------------------------------------------------------------------+
| (5) Create QR code |
+------------------------------------------------------------------------------+
| id: create-install-page-qr-code |
| version: 0.1.0 |
| collection: https://github.com/bitrise-io/bitrise-steplib.git |
| time: 2016-05-27T12:15:35Z |
+------------------------------------------------------------------------------+
| |
INFO[12:15:35] Start installing (php5) with apt-get
INFO[12:15:35] (php5) isn't installed, installing...
| |
+----+--------------------------------------------------------------+----------+
| ⚠️ | Create QR code (exit code: 1) | 6.1 sec |
+----+--------------------------------------------------------------+----------+
| Issue tracker: .../github.com/dag-io/create-install-page-qr-code-step/issues |
| Source: https://github.com/dag-io/create-install-page-qr-code-step.git |
+----+--------------------------------------------------------------+----------+
▼
ERRO[12:15:41] sudo apt-get -y install php5 failed -- out: (Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
apache2 apache2-bin apache2-data libapache2-mod-php5 libapr1 libaprutil1
libaprutil1-dbd-sqlite3 libaprutil1-ldap lsof php5-cli php5-common php5-json
php5-readline ssl-cert
Suggested packages:
www-browser apache2-doc apache2-suexec-pristine apache2-suexec-custom ufw
apache2-utils php-pear php5-user-cache openssl-blacklist
The following NEW packages will be installed:
apache2 apache2-bin apache2-data libapache2-mod-php5 libapr1 libaprutil1
libaprutil1-dbd-sqlite3 libaprutil1-ldap lsof php5 php5-cli php5-common
php5-json php5-readline ssl-cert
0 upgraded, 15 newly installed, 0 to remove and 6 not upgraded.
Need to get 6,403 kB of archives.
After this operation, 26.3 MB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty/main libapr1 amd64 1.5.0-1 [85.1 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ trusty/main libaprutil1 amd64 1.5.3-1 [76.4 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ trusty/main lsof amd64 4.86+dfsg-1ubuntu2 [257 kB]
Get:4 http://archive.ubuntu.com/ubuntu/ trusty/main php5-json amd64 1.3.2-2build1 [34.4 kB]
Get:5 http://archive.ubuntu.com/ubuntu/ trusty/main libaprutil1-dbd-sqlite3 amd64 1.5.3-1 [10.5 kB]
Get:6 http://archive.ubuntu.com/ubuntu/ trusty/main libaprutil1-ldap amd64 1.5.3-1 [8,634 B]
Get:7 http://archive.ubuntu.com/ubuntu/ trusty-updates/main apache2-bin amd64 2.4.7-1ubuntu4.9 [839 kB]
Get:8 http://archive.ubuntu.com/ubuntu/ trusty-updates/main apache2-data all 2.4.7-1ubuntu4.9 [160 kB]
Get:9 http://archive.ubuntu.com/ubuntu/ trusty-updates/main apache2 amd64 2.4.7-1ubuntu4.9 [87.5 kB]
Get:10 http://archive.ubuntu.com/ubuntu/ trusty/main ssl-cert all 1.0.33 [16.6 kB]
Err http://archive.ubuntu.com/ubuntu/ trusty-security/main php5-common amd64 5.5.9+dfsg-1ubuntu4.16
404 Not Found [IP: 91.189.88.161 80]
Err http://archive.ubuntu.com/ubuntu/ trusty-security/main php5-cli amd64 5.5.9+dfsg-1ubuntu4.16
404 Not Found [IP: 91.189.88.161 80]
Err http://archive.ubuntu.com/ubuntu/ trusty-security/main php5-readline amd64 5.5.9+dfsg-1ubuntu4.16
404 Not Found [IP: 91.189.88.161 80]
Err http://archive.ubuntu.com/ubuntu/ trusty-security/main libapache2-mod-php5 amd64 5.5.9+dfsg-1ubuntu4.16
404 Not Found [IP: 91.189.88.161 80]
Err http://archive.ubuntu.com/ubuntu/ trusty-security/main php5 all 5.5.9+dfsg-1ubuntu4.16
404 Not Found [IP: 91.189.88.161 80]
Fetched 1,574 kB in 2s (650 kB/s)
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/php5/php5-common_5.5.9+dfsg-1ubuntu4.16_amd64.deb 404 Not Found [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/php5/php5-cli_5.5.9+dfsg-1ubuntu4.16_amd64.deb 404 Not Found [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/php5/php5-readline_5.5.9+dfsg-1ubuntu4.16_amd64.deb 404 Not Found [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/php5/libapache2-mod-php5_5.5.9+dfsg-1ubuntu4.16_amd64.deb 404 Not Found [IP: 91.189.88.161 80]
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/php5/php5_5.5.9+dfsg-1ubuntu4.16_all.deb 404 Not Found [IP: 91.189.88.161 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?) err: (exit status 100)
INFO[12:15:41] Failed to install (php5) with apt-get
WARN[12:15:41] Step (Create QR code) failed, but was marked as skippable
I suspect the step dependency resolver to now execute an apt-get update
before install dependencies
We're using legacy code signing. We have not gotten around to switching to automatic yet.
We had a situation where a developer set the development team value to a different team and xcode-archive code signing started failing
I tried using the force_team_id and team_id options but I got error code 65 and in one case error code 64.
I switched to using this xcodebuild_options: -DEVELOPMENT_TEAM= and everything works fine.
INFO[19:16:41] Start installing (curl) with apt-get
+------------------------------------------------------------------------------+
| (6) telegram-notify@1 |
+------------------------------------------------------------------------------+
| id: telegram-notify |
| version: 1.0.5 |
| collection: https://github.com/bitrise-io/bitrise-steplib.git |
| toolkit: bash |
| time: 2022-01-11T19:16:41Z |
+------------------------------------------------------------------------------+
| |
INFO[19:16:41] * [OK] Step dependency (curl) installed, available.
MESSAGE='🛑 profession-c-plus-plus: build 37 failed 😕 \nURL: https://app.bitrise.io/app/3a3204a3b62de311\nCommit: Adding correct coverage.txt
\n\n Branch: adding_coverage
Commit hash: def7dd01d655d6698bc6bba3ec1824d4561f0e5b
Commit subject: Adding correct coverage.txt
Commit message: '
'[' 0 -eq 0 ']'
MESSAGE='✅ profession-c-plus-plus: build 37 passed! 🎉\nCommit: Adding correct coverage.txt
\n Download URL ⬇️: https://app.bitrise.io/build/204b4841-c214-4160-ac10-bb814ac80702\n\n Branch: adding_coverage
Commit hash: def7dd01d655d6698bc6bba3ec1824d4561f0e5b
Commit subject: Adding correct coverage.txt
Commit message: '
curl -X POST -H 'Content-Type: application/json' -d '{ "chat_id": "[REDACTED]", "text":"✅ profession-c-plus-plus: build 37 passed! 🎉\nCommit: Adding correct coverage.txt
\n Download URL ⬇️: https://app.bitrise.io/build/204b4841-c214-4160-ac10-bb814ac80702\n\n Branch: adding_coverage
Commit hash: def7dd01d655d6698bc6bba3ec1824d4561f0e5b
Commit subject: Adding correct coverage.txt
Commit message: ", "parse_mode": "markdown" }' https://api.telegram.org/bot[REDACTED]/sendMessage
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 522 100 137 100 385 424 1191 --:--:-- --:--:-- --:--:-- 1611
{"ok":false,"error_code":400,"description":"Bad Request: can't parse entities: Can't find end of the entity starting at byte offset 193"}|
We contacted the Step maintainer multiple times, and we did not receive a response for more than a month.
I'm seeing this issue:
+------------------------------------------------------------------------------+
| (13) generate-changelog@0 |
+------------------------------------------------------------------------------+
| id: generate-changelog |
| version: 0.10.0 |
| collection: https://github.com/bitrise-io/bitrise-steplib.git |
| toolkit: go |
| time: 2022-08-30T20:41:40Z |
+------------------------------------------------------------------------------+
| |
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/syscall_darwin.1_13.go:29:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.1_13.go:27:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.1_13.go:40:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:28:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:43:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:59:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:75:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:90:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:105:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:121:3: //go:linkname must refer to declared function or variable
src/github.com/bitrise-steplib/steps-generate-changelog/vendor/golang.org/x/sys/unix/zsyscall_darwin_amd64.go:121:3: too many errors
ERRO[20:41:41] Step (generate-changelog@0) failed: Failed to prepare the step for execution through the required toolkit (go), error: Failed to install package, error: command /usr/local/bin/go "build" "-o" "/Users/vagrant/.bitrise/toolkits/go/cache/https___github.com_bitrise-io_bitrise-steplib.git-generate-changelog-0" "github.com/bitrise-steplib/steps-generate-changelog"
failed: exit status 2
| |
+---+---------------------------------------------------------------+----------+
| x | generate-changelog@0 (exit code: 1) | 3.82 sec |
+---+---------------------------------------------------------------+----------+
| Issue tracker: ...github.com/bitrise-steplib/steps-generate-changelog/issues |
| Source: https://github.com/bitrise-steplib/steps-generate-changelog |
+---+---------------------------------------------------------------+----------+
I've created a sample project, miniature-succotash-0.0.1.zip, to demonstrate Bitrise's build step doesn't recognize build.gradle.kts
. See failing build/logs here.
This example shows a simple packaging. Like the Groovy DSL, projects may include Kotlin files in project/buildSrc/com/kotlin/build.gradle.kts
.
cc @viktorbenei
I am running the bitrise share start -c
command with a fork of this repository as input and I keep getting the following error
"FATA[19:52:45] Failed to save step spec, error: Failed to walk through path, error: not supported key found in options: is_sensitive "
A lot of steps in this repository use the is_sensitive
option, but I am not sure what I should do about it. I just want to publish my step 😅
I am using bitrise cli version 1.42.0
My fork can be found at https://github.com/realappie/bitrise-steplib
The step at https://github.com/bitrise-io/bitrise-steplib/tree/d3581bdf1de00ddbbe0f0c7113f75d855312e8b1/steps/install-dotnetcore/1.0.0 links to a repo that does not exist.
Hello, until some days ago the step was working correctly, but now he fails and give this error : googleapi: Error 403: Release artifacts require permissions that are missing from permission declaration
I uploaded the APK to play store manually and it worked, but in bitrise still giving error, we didn't change the Google API key since the last time it worked
In my step, I need to include the yq package, which is the YAML parser equivalent to what jq is for JSON.
It provides a brew
package for macOS, but requires snap
for Linux. Alternatively, we can use the go get
method (per https://github.com/mikefarah/yq#install).
In order to execute the same code on both systems, I've decided to use the got get
method, but it is not working. I got this error:
+ GO111MODULE=on
+ go get -v github.com/mikefarah/yq/v2
github.com/mikefarah/yq (download)
created GOPATH=/bitrise/go; see 'go help gopath'
package github.com/mikefarah/yq/v2: cannot find package "github.com/mikefarah/yq/v2" in any of:
/usr/local/go/src/github.com/mikefarah/yq/v2 (from $GOROOT)
/bitrise/go/src/github.com/mikefarah/yq/v2 (from $GOPATH)
I am not a GO dev, so I have no idea what's going on there, specially because this same go get
command works on the macOS stack.
I can imagine these possible solutions, and would like an opinion in which seems a better route:
Figure out and fix the go get
issue on Ubuntu;
Install the yq
dependency for macOS, and the snap
for Ubuntu, and then, in my step.sh
I would check if we are running linux (using BITRISEIO_STACK_ID
?) and then run the snap install yq
;
Ditch yq
completely and look for another solution.
We're transferring ownership of community written https://github.com/bitrise-io/bitrise-steplib/tree/master/steps/bitrise-step-nowsecure-auto-analysis to be maintained by the vendor themselves. Any special magic necessary in order to make that transfer as we submit a new version of the step?
Hi,
I had a gemfile.lock in my root of my project, this caused the cocoapods install to fail, i assume its because you look for any .lock file in the step.
After i removed the gemfile.lock then it worked fine.
My apologies if this is in the docs somewhere, but how does a step contributor add an icon to their steps?
I've got a workflow where I added a Brew install Step
to install Python
, which works well.
The next Step that runs after this is a Script Step
that I use to run pip (one of the Python tools), in order to install a public plugin.
It contains something like this (I've added a generic name for the plugin, myPlugin):
python3 -m pip --version
python3 -m ensurepip --default-pip
alias pip='pip3'
pip install myPlugin
The problem is that it always fails saying that it doesn't know what pip
is (in the 4th line).
Surprisingly, if I run the workflow with Remote Access
and I use the terminal to run the same
commands
it works. So I'm not sure what the issue is that is causing the pip command not being recognised.
Is this an issue known when it comes to work with Python
and the package manager pip
?
When adding a password for code signing certificate, it is impossible to edit password field before clicking on the eye icon to show the password.
Clicking on the icon second time disables the password field.
Password field is enabled all the time. Click on the eye icon shows/hides the password.
We are using ios-auto-provision-appstoreconnect with automatically using the latest version for our ios builds to provision certificates and it was working fine with version 0.1.4.
However, on 9th of Dec the step got upgraded to 0.1.5 and it started to fail in our builds:
failed to check if profile is valid: project uses containers that are missing from the provisioning profile: [iCloud.$(CFBundleIdentifier)]
When we changed back to 0.1.4 the build got fixed.
Would it be possible to look into this issue? Thanks in advance.
I created a new Bitrise API token and used it as secret input variable for the trigger-bitrise-workflow
step.
This is the YAML config:
- trigger-bitrise-workflow:
inputs:
- workflow_id: ui-tests-test-launch
- api_token: "$BITRISE_API_KEY"
The workflow with that ID exists.
I get the following error:
Build Trigger API HTTP response status: 400 Bad Request
Build Trigger status: Invalid API token for Bitrise hook
Update Android SDK Step: https://github.com/bitrise-io/bitrise-steplib/tree/master/steps/android-sdk-update seems to be abandoned. There are unanswered issues created in 2017: https://github.com/guitcastro/steps-update-sdk/issues
I'm currently using the GitHub status step to set the commit status of my PRs on our Github Enterprise repos when the builds finish. Could we get a second step for running at the beginning of these builds which simply does the same thing but sets the status to pending?
What's the proper way to let the user choose to run a step or not in PR mode ? A regular step input ?
this step seems to be abandoned
I have created two issues and a PR that fixes both however got no response for 6 days. Maybe an official attempt would help.
https://github.com/marcelkalveram/bitrise-step-browserstack-upload.git
hi, i have followed the instructions to share my custom step using the following command:
bitrise run share-this-step
Here's the output:
Checking StepLib changes...
No git changes, it seems you already called this command
The only remaining thing is to create a Pull Request in the original StepLib repository. And you are done!
On GitHub you can find a Compare & pull request button, in the section called Your recently pushed branches:,
which will bring you to the page to Open a pull request, where you can review and create your Pull Request.
However, i can't seem to find the option to compare and pull in bitrise-steplib
Here's my custom step repo:
https://github.com/jeremy-chua/bitrise-step-fortify-on-demand-mobile-assessment
Here's the forked bitrise steplib repo
https://github.com/jeremy-chua/bitrise-steplib
What am in missing?
Even though the step says its successful I'm getting this error in the step.
Query to be executed in Jira: {
"jql": "project = OP AND status = 'Dev Done (Not in Build)'",
"startAt": 0,
"maxResults": 20,
"fields": [
"id"
],
"fieldsByKeys": false
}
parse error: Invalid numeric literal at line 1, column 6
These are the values I'm putting in the step
Jira project name: OP
Jira project URL: https://companyname.atlassian.net
Jira API token: {CorrectAPIToken}
Initial status: Dev Done (Not in Build)
Initial status: IN REVIEW
Custom field to update version number: {Empty }
App version: {Empty}
FATA[01:51:42] Failed to update StepLib (https://github.com/bitrise-io/bitrise-steplib.git), error: failed to generate spec for library (https://github.com/bitrise-io/bitrise-steplib.git), error: Failed to walk through path, error: Invalid environment (appetize_token), err: is_sensitive option is true but is_expand option is not. For sensitive inputs direct value is not allowed
Indeed there is no is_expand
: https://github.com/bitrise-io/bitrise-steplib/pull/1697/files#diff-55bf19228fc3e7fec1fce50898ceafe6R42
Not really
This fields should contain a short summary about this feature, to be more clear for the users who are not fully familiar with HipChat yet. In case of HipChat V1 api, please include a short description of what is 0>false
and 1>true
ps.: Wrong repository.
We have a convention that branch name should start with JIRA ticket number
so if Jira ticket is : https://xyz.atlassian.net/browse/PP-4045
so branch name will start with PP-4045
Jira issue key is a required input for this step. How can I enter this value dynamically in my case?
In order to extend test coverage to multiple real devices it would be nice if you could add a step for integrating with AWS Device Farms, the step wouldn't need to wait until the device farm has finished all tests (as the process for waiting for devices can be very slow), but knowing that it can trigger a device farm deployment would provide development team with very valuable test information.
Here's the link for AWS Device Farms:
https://aws.amazon.com/device-farm/
As the title mentions, it would be nice to have .gitignore file in the repo to exclude certain macOS files like .DS_Store
.
Something like Github macOS gitignore
Happy to create a PR.
Hello, we recently updated gradle and we get this error while building android. Nothing changed in the configuration of this step and the error seems too generic to understand what the problem is:
Run: failed to fetch variants: Downloading https://services.gradle.org/distributions/gradle-7.2-all.zip
Also, it would be nice to have an option to enable Debugging for this step.
Here is the full output of this step:
ProjectLocation: /Users/vagrant/git/packages/mobile/android
- AppPathPattern: */build/outputs/apk/*.apk
*/build/outputs/bundle/*.aab
- Variant: productionRelease
- Module: app
- BuildType: aab
- Arguments: -sourcemap-output android/tmp/index.bundle.map
- CacheLevel: none
- DeployDir: /Users/vagrant/deploy
Run: failed to fetch variants: Downloading https://services.gradle.org/distributions/gradle-7.2-all.zip
.....................................................................................................................................................
Welcome to Gradle 7.2!
Here are the highlights of this release:
- Toolchain support for Scala
- More cache hits when Java source files have platform-specific line endings
- More resilient remote HTTP build cache behavior
For more details see https://docs.gradle.org/7.2/release-notes.html
No argument was provided for command-line option '-c'.
USAGE: gradlew [option...] [task...]
-?, -h, --help Shows this help message.
-a, --no-rebuild Do not rebuild project dependencies.
-b, --build-file Specify the build file. (deprecated)
--build-cache Enables the Gradle build cache. Gradle will try to reuse outputs from previous builds.
-c, --settings-file Specify the settings file. (deprecated)
--configuration-cache Enables the configuration cache. Gradle will try to reuse the build configuration from previous builds. [incubating]
--configuration-cache-problems Configures how the configuration cache handles problems (fail or warn). Defaults to fail. [incubating]
--configure-on-demand Configure necessary projects only. Gradle will attempt to reduce configuration time for large multi-project builds. [incubating]
--console Specifies which type of console output to generate. Values are 'plain', 'auto' (default), 'rich' or 'verbose'.
--continue Continue task execution after a task failure.
-D, --system-prop Set system property of the JVM (e.g. -Dmyprop=myvalue).
-d, --debug Log in debug mode (includes normal stacktrace).
--daemon Uses the Gradle Daemon to run the build. Starts the Daemon if not running.
--export-keys Exports the public keys used for dependency verification.
-F, --dependency-verification Configures the dependency verification mode (strict, lenient or off)
--foreground Starts the Gradle Daemon in the foreground.
-g, --gradle-user-home Specifies the gradle user home directory.
-I, --init-script Specify an initialization script.
-i, --info Set log level to info.
--include-build Include the specified build in the composite.
-M, --write-verification-metadata Generates checksums for dependencies used in the project (comma-separated list)
-m, --dry-run Run the builds with all task actions disabled.
--max-workers Configure the number of concurrent workers Gradle is allowed to use.
--no-build-cache Disables the Gradle build cache.
--no-configuration-cache Disables the configuration cache. [incubating]
--no-configure-on-demand Disables the use of configuration on demand. [incubating]
--no-daemon Do not use the Gradle daemon to run the build. Useful occasionally if you have configured Gradle to always run with the daemon by default.
--no-parallel Disables parallel execution to build projects.
--no-scan Disables the creation of a build scan. For more information about build scans, please visit https://gradle.com/build-scans.
--no-watch-fs Disables watching the file system.
--offline Execute the build without accessing network resources.
-P, --project-prop Set project property for the build script (e.g. -Pmyprop=myvalue).
-p, --project-dir Specifies the start directory for Gradle. Defaults to current directory.
--parallel Build projects in parallel. Gradle will attempt to determine the optimal number of executor threads to use.
--priority Specifies the scheduling priority for the Gradle daemon and all processes launched by it. Values are 'normal' (default) or 'low'
--profile Profile build execution time and generates a report in the <build_dir>/reports/profile directory.
--project-cache-dir Specify the project-specific cache directory. Defaults to .gradle in the root project directory.
-q, --quiet Log errors only.
--refresh-dependencies Refresh the state of dependencies.
--refresh-keys Refresh the public keys used for dependency verification.
--rerun-tasks Ignore previously cached task results.
-S, --full-stacktrace Print out the full (very verbose) stacktrace for all exceptions.
-s, --stacktrace Print out the stacktrace for all exceptions.
--scan Creates a build scan. Gradle will emit a warning if the build scan plugin has not been applied. (https://gradle.com/build-scans)
--status Shows status of running and recently stopped Gradle Daemon(s).
--stop Stops the Gradle Daemon if it is running.
-t, --continuous Enables continuous build. Gradle does not exit and will re-execute tasks when task file inputs change.
--update-locks Perform a partial update of the dependency lock, letting passed in module notations change version. [incubating]
-v, --version Print version info.
-w, --warn Set log level to warn.
--warning-mode Specifies which mode of warnings to generate. Values are 'all', 'fail', 'summary'(default) or 'none'
--watch-fs Enables watching the file system for changes, allowing data about the file system to be re-used for the next build.
--write-locks Persists dependency resolution for locked configurations, ignoring existing locking information if it exists
-x, --exclude-task Specify a task to be excluded from execution., exit status 1
| |
+---+---------------------------------------------------------------+----------+
| x | [email protected] (exit code: 1) | 10.03 sec|
+---+---------------------------------------------------------------+----------+
| Issue tracker: ...thub.com/bitrise-steplib/bitrise-step-android-build/issues |
| Source: https://github.com/bitrise-steplib/bitrise-step-android-build |
+---+---------------------------------------------------------------+----------+
Hi guys!
Not sure if this is the right place to post this issue... My apologies if it's not :(
At @bamlab, we use Bitrise for our React Native projects, and we like to build both Android and iOS versions of the project on the same stack.
For now, we made a custom step installing Android SDK with Brew via a script, and adding the required tools.
Do you think it would be a good idea to include the Android SDK on the OSX stacks? If so, should we make a PR on https://github.com/bitrise-io/osx-box-bootstrap?
Or do you think it'd be best to submit an Android SDK step for the OS stacks?
Thanks! :)
There's been an issue in this step with parsing application names for a couple years at heyjobs/bitrise-android-application-attributes-step#1 that I created a PR for at heyjobs/bitrise-android-application-attributes-step#2 that hasn't received any attention in that timespan.
Somewhere in the last 10 days, there must have been a change that causes our builds to fail.
INFO[06:46:17] Step uses latest version -- Updating StepLib ...
INFO[06:46:17] Update StepLib (https://github.com/bitrise-io/bitrise-steplib.git)...
Already up-to-date.
FATA[06:46:17] Failed to update StepLib (https://github.com/bitrise-io/bitrise-steplib.git), error: failed to generate spec for library (https://github.com/bitrise-io/bitrise-steplib.git), error: Failed to walk through path, error: not supported key found in options: is_sensitive
WARN[06:46:17] Step uses latest version, but failed to update StepLib, err: exit status 1
INFO[06:46:17] Step info not found in StepLib (https://github.com/bitrise-io/bitrise-steplib.git) -- Updating ...
INFO[06:46:17] Update StepLib (https://github.com/bitrise-io/bitrise-steplib.git)...
Already up-to-date.
FATA[06:46:18] Failed to update StepLib (https://github.com/bitrise-io/bitrise-steplib.git), error: failed to generate spec for library (https://github.com/bitrise-io/bitrise-steplib.git), error: Failed to walk through path, error: not supported key found in options: is_sensitive
Is there a flag to enable in configuration of the step to enable logging?
all we got was a rather unhelpful
Waiting for test results
- Validating
- (1/1) running
- (0/1) running
=> Test finished
Test results:
Model API Level Locale Orientation Outcome
Pixel2 29 it portrait failure
would be nice to have at least which test failed, even better the full log
I wanted to use the official danger step in my workflow to work with an on premise BitBucket Server instance. Unfortunately the step only offers input fields for GitHub or Gitlab. But Danger itself can work with BitBucket Server instances as it can be read here: https://danger.systems/js/usage/bitbucket_server.html
As a workaround I set the env vars in my workflow config and use the Script
step to invoke danger. I know that this is a not a big issue, but it would be nice if the official Danger step could support input fields for all SCM systems that are supported by the Danger CLI.
I'm trying to update my step.
However, it fails with the following error.
remote: Invalid username or password.
How can I be successful?
$ bitrise run share-this-step
...
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/kanari3/bitrise-steplib.git/'
I've also tried the following, although it may be an older method
$ bitrise share create --tag [step-version-tag] --git [step-git-uri].git --stepid [step-id]
Almost done! You should review your Step's step.yml file (the one added to the local StepLib),
and once you're happy with it call $ bitrise share finish
$ bitrise share finish
Submitting the changes...
pushing to your fork: https://github.com/kanari3/bitrise-steplib.git
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/kanari3/bitrise-steplib.git/'
2020/05/14 16:48:21 Bitrise share finish failed, error: exit status 1
ssh -T [email protected]
-> successfullygit config --list
Is there anything else I should be doing?
This step can be removed because we separated it into 3 steps (#2865 #2866 #2867) to keep steps as clear as possible because we plan to add some other steps to monitor the quality of the mobile applications.
Moreover, the setup should be easier and people will be able to add a step only if it's useful in their case (or requested by the client eg.)
Step
deploy-to-bitrise-io
Enviroment
id: deploy-to-bitrise-io
version: 1.13.2
collection: https://github.com/bitrise-io/bitrise-steplib.git
toolkit: go
Steps to reproduce
Use deploy-to-bitrise-io
as usual to deploy Android *.aab
files to Bitrise.
Error from build log
Uploading aab file: /bitrise/deploy/****
- analyzing aab
- fetching info
Could not download file from: unable to download file from: https://github.com/google/bundletool/releases/download/0.13.4/bundletool-all-0.13.4.jar. Status code: 404
this step seems to be abandoned, everyone has own fork fixing some problems.
I have created an issue and got no response for 12 days. Maybe an official attempt would help.
https://github.com/justice3120/bitrise-step-open-vpn
I am happy to take over maintenance of the step or support it if Bitrise converts it to official step, unless owner disagrees.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.