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

Automate release process #4

Open
3 tasks
netbe opened this issue Jan 11, 2018 · 5 comments
Open
3 tasks

Automate release process #4

netbe opened this issue Jan 11, 2018 · 5 comments

Comments

@netbe
Copy link
Collaborator

netbe commented Jan 11, 2018

  • define what to do exactly on that issue
  • add CI checks / tests (if needed)
  • add CI build on release tag (is it the right way🤷‍♂️)
@tmspzz
Copy link
Member

tmspzz commented Jan 11, 2018

Can you elaborate more on define what to do exactly on that issue ? What do you mean?

Thanks for moving the repo here btw ❤️

@netbe
Copy link
Collaborator Author

netbe commented Jan 11, 2018

@blender yeah of course.

I thought it was better to move it here instead of adding you as collaborator on that repo.

My first thoughts:

Scenario:

  • one makes a change with a PR
  • tests are run on PR
  • once reviewed and tests passed, one can merge the PR
  • To release, one can go to release https://github.com/OpenShelter/fastlane-plugin-rome/releases, draft the release. This will tag the version (this means the version will be changed beforehand in code, or is there another way to do it?)
  • The CI sees the tag and proceeds with release doing a rake release to rubygems.

@tmspzz
Copy link
Member

tmspzz commented Jan 11, 2018

So basically we only need to setup travis, I'm I right?

Afaik you have to change the version for the release manually prior to running rake release

@netbe
Copy link
Collaborator Author

netbe commented Jan 11, 2018

yes that's right. That's the setup I have on my other repo, maybe this will suffice:
https://github.com/netbe/Babelish/blob/master/.travis.yml

@tmspzz
Copy link
Member

tmspzz commented Jan 11, 2018

I think it will.

As for the automated release I don't think that's possible. I did some googling but didn't find much.

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

No branches or pull requests

2 participants