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

[Stable14] Drone: do not check stable* but only stable14 #11505

Merged
merged 1 commit into from
Oct 1, 2018

Conversation

rullzer
Copy link
Member

@rullzer rullzer commented Oct 1, 2018

I'm not sure if regexes like this are supported else I'll hard code it on the stable branches.

@rullzer rullzer force-pushed the drone/14/no_branch_wildcard branch 2 times, most recently from 6a04b10 to e4e92c9 Compare October 1, 2018 10:22
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
@rullzer rullzer force-pushed the drone/14/no_branch_wildcard branch from e4e92c9 to 6a9d244 Compare October 1, 2018 10:24
@rullzer
Copy link
Member Author

rullzer commented Oct 1, 2018

Ok so no real regex in drone.yml yet it seems. Now hardcoded it to stable14 so no multiple drone jobs get injected when a branch is called stable14-foo-bar etc :)

@MorrisJobke MorrisJobke added the 3. to review Waiting for reviews label Oct 1, 2018
@MorrisJobke MorrisJobke added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Oct 1, 2018
@rullzer rullzer changed the title [Stable14] Drone: do not check stable* but only stable[0-9]+ [Stable14] Drone: do not check stable* but only stable14 Oct 1, 2018
@rullzer rullzer merged commit c3a72ba into stable14 Oct 1, 2018
@rullzer rullzer deleted the drone/14/no_branch_wildcard branch October 1, 2018 14:44
@MorrisJobke MorrisJobke mentioned this pull request Oct 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants