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

Setting to autobuild all tags #3039

Closed
jakirkham opened this issue Aug 7, 2017 · 5 comments
Closed

Setting to autobuild all tags #3039

jakirkham opened this issue Aug 7, 2017 · 5 comments
Labels
Improvement Minor improvement to code Needed: design decision A core team decision is required

Comments

@jakirkham
Copy link
Contributor

Would be nice to have a setting for simply autobuilding all tags. Currently one needs to go into the settings and enable these one at a time. By having all tags autobuilt, this would smooth out the release process quite a bit.

@humitos humitos added Improvement Minor improvement to code Needed: design decision A core team decision is required labels Dec 26, 2017
@humitos
Copy link
Member

humitos commented Dec 26, 2017

Hi @jakirkham! Thanks for the report.

I mean, I understand that you want to create a new tag and make RTD automatically active it and build it. I assume that this would only works for tags since branches make no too much sense to me, right? I like the idea.

Maybe we can add something to the YAML file like

autobuild: tags

or

autobuild: true

or similar.

@jouvin
Copy link

jouvin commented Apr 25, 2018

+1, it would be a very nice new feature. And it would be good if we could also define a maximum number of versions to automatically built, if this is not a version explicitely selected. This would allow to prune old versions automatically.

@humitos humitos added this to the New build features milestone Apr 25, 2018
@humitos
Copy link
Member

humitos commented Apr 25, 2018

@stsewd this is something that could be considered in #3878

@stsewd
Copy link
Member

stsewd commented Apr 26, 2018

@humitos I don't understand this very clear :/. This seems like a global setting, those aren't going to be handled on the YAML file. Maybe #4001 is better for this use case (If I believe is this)?

@humitos
Copy link
Member

humitos commented Nov 15, 2018

Closing this in favor of #4001 which is closer to start being implemented.

@humitos humitos closed this as completed Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Minor improvement to code Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

4 participants