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 releases #28

Open
azukaar opened this issue Jun 20, 2019 · 8 comments
Open

Automate releases #28

azukaar opened this issue Jun 20, 2019 · 8 comments
Labels
Enhancement New feature or request New Plugin This is a new plugin that should be worked on Next
Milestone

Comments

@azukaar
Copy link
Owner

azukaar commented Jun 20, 2019

Needs #9, and a github-release provider

@azukaar azukaar added Enhancement New feature or request New Plugin This is a new plugin that should be worked on Next labels Jun 20, 2019
@filips123
Copy link

I would like a slightly different solution for automatic releases.

It would be better to release a new version on every GitHub release. This would be better for developers because they would only need to create GitHub release and the package will be automatically released to correct package managers.

@azukaar
Copy link
Owner Author

azukaar commented Jul 14, 2019

@filips123 do you mean like a hook on github releases to publish to other sources?

@filips123
Copy link

Yes, something like this. Or Travis CI build that runs on GitHub releases.

@azukaar
Copy link
Owner Author

azukaar commented Jul 14, 2019

Not sure if that's possible, but it's definitely a good idea in case you want to support multiple source easily.
Alternatively you could set your CI to run multiple "publish" every commit on master :

g publish
g publish -p github-release
g publish -p npm

@filips123
Copy link

filips123 commented Jul 14, 2019

GitHub hooks would be harder to do because it would require external API service. But it would be easier for developers.
with

Publishing with CI on GitHub releases is possible with Travis CI on: tags: true:

deploy:
  provider: script
  script: g publish
  on:
    tags: true

@azukaar Also, what does g publish do? Does it publish to all providers? If it doesn't, there should be support for that.

@azukaar
Copy link
Owner Author

azukaar commented Jul 14, 2019

g publish only publish using the default provider.

You can change that by adding to your gupm.json :

cli: {
 defaultProviders: {
   publish: yourProvider
 }
}

That is said you can't set an array or "all" in here.

It would be a good idea to support arrays in there now that you mention it! thanks for that. Publishing to all providers tho seems a bit counter-productive since you probably don't use all your installed providers in all projets

@filips123
Copy link

since you probably don't use all your installed providers in all projets

What about publishing to all used providers?

@azukaar
Copy link
Owner Author

azukaar commented Jul 14, 2019

What about publishing to all used providers?

Need to think about it. Some Providers won't even support publishing so I'm not quite sure

@azukaar azukaar added this to the 1.3.0 milestone Jul 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request New Plugin This is a new plugin that should be worked on Next
Projects
None yet
Development

No branches or pull requests

2 participants