-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Actions NullPointer #23
Comments
I think you want |
sorry that's a bit confusing.. our actual file doesn't include them I was just obfuscating the name. We used either secrets.GITHUB_TOKEN or whatever our personal access token was named. |
If you look in the GitHub Actions log, expand the exact step which runs sbt, and then expand the top-most expandable thingy within that step. This should be a print out of all of the environment variables which are in-scope for the run. Double check to make sure that Also it occurs to me that we check
Let's try to get the smallest possible build in the most controlled possible environment which reproduces the problem. |
@djspiewak I deleted the package from the registry as an earlier broken pipe exception seemingly left it in a partially published state... I ran the action again and it published successfully! Weird... Now when I try to push updates I get the error you mentioned requiring me to use personal access tokens with read-package scope enabled for private packages.
When using the personal access tokens, would I want to set the GITHUB_ACTOR env var along with using the personal access token from secrets? |
Still getting the 422 response from github packages... The only way I can seem to get it to publish successfully is if the artifact version is bumped (e.g. 2.3.1-SNAPSHOT -> 2.3.2-SNAPSHOT) which is strange considering SNAPSHOTs should be allowed to be updated/overwritten with changes. If I try to make changes to a SNAPSHOT version and publish I always run into the following error.
|
Ah! This is very interesting. I haven't experimented with this (I simply don't use Not that this is a bad thing, IMO. :-) Unstable snapshots (i.e. versions that you overwrite) are really bad practice and result in unstable and unreproducible downstream builds. You're usually better off using something like hash snapshots. Also sorry for losing track of this issue. It fell off my notifications for some reason. Is the |
Receiving this consistently using the plugin version 0.5.2 for an internal/private, org-based repository.
Actions yaml file...
In build.sbt...
Error (as much as I could copy from github actions log in the web UI)
The text was updated successfully, but these errors were encountered: