Github Release Deployment
Hello guys,
I've got GitHub Release Deployment setup in my project, and thus
far, it's working great.
I use it so that for every commit, I create a new build, and a new
release on github.
For the github release a new tag and release is automatically
created.
My question is:
Is there any way I can change the name for that tag and
release?
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 18 Dec, 2014 05:39 PM
What would you like to put there?
2 Posted by Daniel Häfele on 18 Dec, 2014 05:41 PM
Something more interesting than just "0.0.123".
In my case, I would like to have the format "v0.0.123" or even "Build v0.0.123".
Support Staff 3 Posted by Feodor Fitsner on 18 Dec, 2014 05:45 PM
I see, make sense. Basically, it would be great to have some format string for that, kind of
Build v$(appveyor_build_version), right?4 Posted by Daniel Häfele on 18 Dec, 2014 05:46 PM
Now we're on the same table! =)
This is exactly what I thought about.
Support Staff 5 Posted by Feodor Fitsner on 18 Dec, 2014 05:49 PM
OK, that's an easy improvement - will deploy this week :)
6 Posted by Daniel Häfele on 18 Dec, 2014 05:53 PM
Amazing =)
Let me tell you, I just recently started fiddling around with AppVeyor, and everytime I have a question, you're around and help me within a second, that's amazing!
Love that customer service.
Support Staff 7 Posted by Feodor Fitsner on 20 Dec, 2014 04:42 AM
It's been deployed: http://www.appveyor.com/docs/deployment/github#provider-settings - there is a new
releasesetting.8 Posted by haefele on 20 Dec, 2014 12:25 PM
Just had a little bit of trouble with it, because you can't have spaces
in it (GitHub doesn't allow it), so I just got the following error
message in my log:
Error creating GitHub release: Response status code does not indicate
success: 422 (Unprocessable Entity).
Just replacing the space in my release string with a dash, made it work.
Thanks!
Support Staff 9 Posted by Feodor Fitsner on 20 Dec, 2014 11:04 PM
Yeah, will add that into documentation.
10 Posted by martin.costello... on 23 Dec, 2014 07:13 PM
It would be worth adding to the documentation that the lack of support for spaces is a GitHub constraint, rather than an AppVeyor one. Then I wouldn't have gone searching for why with the aim to ask you for support to do so :)
As I'll be creating a draft release anyway so I can edit the release notes before I publish the release, I'll just edit then name at that point.
11 Posted by martin.costello... on 23 Dec, 2014 07:15 PM
And a second point I just realised, before I white space restriction in the documentation, I'd put my draft yml through the new validator and I wasn't warned that spaces were present in the release name.
It would be nice for the yml validator to check this and warn the user.
Support Staff 12 Posted by Feodor Fitsner on 23 Dec, 2014 07:23 PM
But there is a warning in docs: http://www.appveyor.com/docs/deployment/github#provider-settings ?
Pushing validator that far is hard - right now it's just syntax/schema validation, values is another thing (though it's doable of course) :)
13 Posted by martin.costello... on 23 Dec, 2014 07:28 PM
I meant more that if you clarified that it's a GitHub requirement, people wouldn't then be tempted to ask you to make a change to support it. Had I not found this thread, that's what I would have done as all my existing manually-created releases have spaces in the names.
That's fair regarding the validator though, just a suggestion :)
Support Staff 14 Posted by Feodor Fitsner on 23 Dec, 2014 07:29 PM
I got it. Will add a note.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:52 AM.