Skip_cleanup: true is now deprecated. How to go for gradle publish?

Deployment
,
1

What would be the correct replacement for deploy.skip_cleanup: true to avoid this error:

Not currently on any branch.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)
	modified:   gradlew
no changes added to commit (use "git add" and/or "git commit -a")
Dropped refs/stash@{0} (9fcc757e1adcea11837cf468b569c3fd8d28b9a4)
Script failed with status 127
failed to deploy

That’s the project that is erroring: https://travis-ci.org/lamba92/firebase-multiplatform/builds/630005806

2

In dpl v2, skipping cleanup is the default behavior and there’s instead cleanup: to do the opposite.

3

I tried to just leave it. It still errors the same!
Have a look here: https://travis-ci.org/lamba92/firebase-multiplatform/jobs/630004282/config

4

You are not using dpl v2 (see the above link for details). So if you need build artifacts for deployment, either leave skip_cleanup: true in, or move to dpl v2.

5

I’ll opt in and retry then! Anyway the build is having the same error even with skip_cleanup: true which is strange since it always worked :roll_eyes:
https://travis-ci.org/lamba92/firebase-multiplatform/jobs/630005807/config

6

the build is having the same error even with skip_cleanup: true
Travis CI - Test and Deploy with Confidence

As per Uploading Files and skip_cleanup - Deployment - Travis CI, skip_cleanup: should be directly inside deploy::

deploy:
  skip_cleanup: true
1 Like