sbt-ci-release | sbt plugin to automate Sonatype releases | Continous Integration library

by olafurpg Scala Version: v1.5.7 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | sbt-ci-release Summary

sbt-ci-release is a Scala library typically used in Devops, Continous Integration applications. sbt-ci-release has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This is an sbt plugin to help automate releases to Sonatype and Maven Central from GitHub Actions. Beware that publishing from GitHub Actions requires you to expose Sonatype credentials as secret environment variables in GitHub Actions jobs. However, secret environment variables are not accessible during pull requests.

Support

Quality

Security

License

Reuse

Support

sbt-ci-release has a low active ecosystem.

It has 199 star(s) with 46 fork(s). There are 10 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 50 have been closed. On average issues are closed in 64 days. There are 7 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of sbt-ci-release is v1.5.7

Quality

sbt-ci-release has 0 bugs and 0 code smells.

Security

sbt-ci-release has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sbt-ci-release code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

sbt-ci-release is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sbt-ci-release releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

It has 166 lines of code, 17 functions and 1 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sbt-ci-release

Get all kandi verified functions for this library.

sbt-ci-release Key Features

No Key Features are available at this moment for sbt-ci-release.

sbt-ci-release Examples and Code Snippets

No Code Snippets are available at this moment for sbt-ci-release.

Community Discussions

Trending Discussions on sbt-ci-release

Issue with "No Staging repository found" in sonatype publish

Allow travis.ci to push github

QUESTION

Issue with "No Staging repository found" in sonatype publish

Asked 2019-Jun-18 at 16:28

I am using the amazing plugin sbt-ci-release but I think I am doing something wrong. I posted the whole details of all my experimentation and steps and attempt as an issue in their repo which can be find here.

To do it short, when travis is calling +publishSigned it is yelling about

...

ANSWER

Answered 2019-Jun-18 at 16:28

The issue was that my branch tag was 0.1 instead of v0.1 , adding the heading v solve the problem.

See https://github.com/olafurpg/sbt-ci-release/issues/44#issuecomment-503087541

Source https://stackoverflow.com/questions/56587653

QUESTION

Allow travis.ci to push github

Asked 2018-Sep-06 at 14:30

I was hoping I could just add travis.ci as a collaborator, but didn't find anything in that direction. Maybe it's a security measure because they don't want to leak their credentials in the virtual environment.

Other (unsatisfying) ideas:

share my github credentials with travis via encrypted vars
create a separate github account for travis
create separate ssh keys, share with travis (encrypted), add to my github

Does anyone have a better idea?

Context: I'm publishing my project from travis.ci and it automatically assigns a new version number that's tracked as a git tag, e.g. v1.0.5

Without anything setup, it obviously fails due to missing permissions: pushing to remote, using `git push origin v0.1.41` remote: Invalid username or password. fatal: Authentication failed for 'https://github.com/mpollmeier/sbt-ci-release-early-usage.git/'

...

ANSWER

Answered 2018-Sep-06 at 14:02

I ended up using a github access token a of https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/, but I'm still keen to hear better alternatives...

Source https://stackoverflow.com/questions/52205609

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sbt-ci-release

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: