search

tweenjs / es6-tween

ES6 version of tween.js
MIT License
186 stars 34 forks source link

The Travis CI access fail due of permission #24

Closed dalisoft closed 7 years ago

dalisoft commented 7 years ago

@sole I can't access to settings. Or i should leave the app? If yes, i will leave :(

dalisoft commented 7 years ago

Sorry @sole. It's maybe mistake of npmjs or [travis], i not sure

sole commented 7 years ago

Sorry @dalisoft it is my fault! I revoked a token and forgot to update it on this repository. I will do it and update you here

sole commented 7 years ago

Is it working now? it looks like it should be?

dalisoft commented 7 years ago

@sole My tokens will been not a one, i am curius because nobody can't access to my profile and can't revoke my token without my permission, right? There it's not your fault. My tokens was used for 2 repos, not a one. Anyway i am already released release with my fork. I test it later

dalisoft commented 7 years ago

@sole I am still can't access to Travis CI repo (@tweenjs/es6-tween), but can access to fork (@dalisoft/es6-tween). Currently i am commit to my fork, anyway it releases to (@tweenjs/es6-tween)

sole commented 7 years ago

I don't understand what you're trying to do - can you explain exactly what you're trying to do and where?

dalisoft commented 7 years ago

I cant set my token for es6 tween on travis to release new version

sole commented 7 years ago

Right, I don't really know what is actually happening. Looking at the travis output I can only see

> es6-tween@1.11.3 semantic-release /home/travis/build/tweenjs/es6-tween
> semantic-release pre && npm publish && semantic-release post --owner=sole --user=dalisoft
[Travis Deploy Once]: Success at attempt 1. All 1 jobs passed.
semantic-release ERR! pre Failed to determine new version.
semantic-release ERR! pre ENOCHANGE There are no relevant changes, so no new version is released.

and I don't know why is it failing to determine a new version.

I'll tell you what I've looked at, and let's see if together we can figure out what's wrong:

My first suspect is here: the NPM token belongs to the user tweenjsadmin that I created so that publishes will not be done by me, but by that account.

But your semantic release configuration tries to publish as owner = sole using a token for tweenjsadmin, so that's not going to work. Maybe if you change the config to use the tweenjsadmin it will work?

sole commented 7 years ago

We also had a similar issue a while ago with semantic-release which couldn't determine the current version

dalisoft commented 7 years ago

Yes, only one account can be publish with Travis + semantic-release

dalisoft commented 7 years ago 
semantic-release ERR! pre Failed to determine new version.
semantic-release ERR! pre ENOCHANGE There are no relevant changes, so no new version is released.

Try trigger the version by comment on the commit

fix(travis): trigger travis, may fix the issue
dalisoft commented 7 years ago

@sole semantic-release fixes in v2.2.1, i did some config changes and improvements for performance and repo. I think you like it