Skip to content
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

Issues with release script #767

Closed
justin808 opened this issue Mar 21, 2017 · 10 comments
Closed

Issues with release script #767

justin808 opened this issue Mar 21, 2017 · 10 comments

Comments

@justin808
Copy link
Member

justin808 commented Mar 21, 2017

I documented the problem here.

Essentially, the release script works, but there's an error.

@justin808
Copy link
Member Author

Recommendation is to switch to using the bundler rake tasks:

Any volunteers to help me with this one?

@isolo
Copy link
Contributor

isolo commented Mar 28, 2017

I'll do it

@isolo
Copy link
Contributor

isolo commented Mar 28, 2017

@justin808 I've debugged gem-release a little. I think I found the reason why it tries to release a version twice. gem-release goes through every gemspec file and applies a command to each of them. For example, for react_on_rails that method returns something like that:
[".", "spec/dummy/client/node_modules/react-on-rails/gen-examples/examples/basic/client/node_modules/react-on-rails", "spec/dummy/client/node_modules/react-on-rails/gen-examples/examples/basic-server-rendering/client/node_modules/react-on-rails", ...]
As you can see, that gem tries to apply a command to all of this gemspecs. Consequently, when it release a version for current directory, it goes to the next and fails with Repushing of gem versions is not allowed.
I'll create a pull request tomorrow.

@justin808
Copy link
Member Author

@isolo can you maybe submit a PR to the gem-release, or maybe at least copy this comment there: svenfuchs/gem-release#63

@dwradcliffe
Copy link

Great debugging @isolo!

@isolo
Copy link
Contributor

isolo commented Mar 29, 2017

Fixed that with #778

@justin808
Copy link
Member Author

Great work @isolo! Moving the discuss to the PR!

@isolo
Copy link
Contributor

isolo commented Mar 29, 2017

Yeah, If we delete ./spec/dummy/client/node_modules/react-on-rails/react_on_rails.gemspec I think it solves the problem (the other occurrences are deleted by Rake::Task["examples:clobber"].invoke), but it sounds a little bit shaky. gem-release does not look like a maintainable project, so we can assume (or freeze the version) that its behaviour wouldn't change and anyway we have a dependency on it (bumping version).
I think any of these variants are acceptable. What do you think @justin808 ? It's not hard to make any of these variants workable.

@justin808
Copy link
Member Author

Longer term, we should follow the schneems article. I'd feel more comfortable keeping the script as-is with the addition of deleting the extra gemspecs, maybe via a find command that excludes the top level one.

@justin808
Copy link
Member Author

@isolo Bonus points for following Richards article now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants