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

Integrate w/ GitHub Releases API #47

Closed
mikeal opened this issue Feb 16, 2015 · 11 comments
Closed

Integrate w/ GitHub Releases API #47

mikeal opened this issue Feb 16, 2015 · 11 comments

Comments

@mikeal
Copy link
Contributor

mikeal commented Feb 16, 2015

So, GitHub has this "releases" feature. Every tag automatically becomes a "release" but there is also an API to add other resources to that release like our binary builds and even the Changelog.

This came up recently when people started asking for more features from the website's release section like an RSS feed, nodejs/iojs.org#79, which we would actually get for free if we were using the GitHub Releases API.

Also, because these tags/releases already exist it would be great if people found all the relevant resources there if that's the place they decide to look for releases.

@kenperkins
Copy link

+1

2 similar comments
@therebelrobot
Copy link

+1

@retrohacker
Copy link

👍

@kenperkins
Copy link

I wonder if we can use https://developer.github.com/v3/repos/releases/#upload-a-release-asset to upload our actual .dmg, .dpkg, .msi, etc binaries to GH.

@jbergstroem
Copy link
Member

@kenperkins I think that's what we want to do. I'll have a look at integrating this with jenkins build steps.

@rmg
Copy link

rmg commented Feb 23, 2015

@jbergstroem +1 on integrating it into the build steps

@fixe
Copy link

fixe commented Feb 25, 2015

+1

@jbergstroem
Copy link
Member

I built a prototype ages ago but I'm starting to feel that this is better hosted off nodejs.org regardless. I wish github gave us slightly more control in that regard. I'd +1 a WONTFIX here.

@rvagg
Copy link
Member

rvagg commented Nov 30, 2015

/cc @ralphtheninja I think you did some work on this for level* stuff right? perhaps you can lend an opinion here for us. I'm not qualified, I don't use the feature (either as a publisher and I manage to mostly avoid it as a user).

@jbergstroem
Copy link
Member

So, if we're going to proceed with something here (I'm still -1, we lose download info) we probably want to separate the job from Jenkins seeing how indirect access through PR in jobs can bleed credentials.

@jbergstroem
Copy link
Member

Closing this. Don't see this happening or even why at this point (read: why replace nodejs.org/dist/). Feel free to reopen though.

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

8 participants