bikebilly

4 ms·

1. 1.▲
   by bikebilly 9y ago

   It's a good point, I just opened an issue about that, feel free to add more context on it: https://gitlab.com/gitlab-org/gitlab-ce/issues/35022
2. 2.▲
   by bikebilly 9y ago

   Thanks for the feedback, there is actually an issue regarding this topic: https://gitlab.com/gitlab-org/gitlab-ce/issues/28996 . Feel free to contribute to it!
3. 3.▲
   by bikebilly 9y ago

   Thanks for your feedback, we're seriously considering all the input from the community, wherever it is coming from. Talking about artifacts retention policy, we actually support defining an expiration date and we're also consideri
4. 4.▲
   by bikebilly 9y ago

   If you could extract branch information from fabric tasks, and then merge the branch with associated deployment handled by GitLab CI, the workflow would be the simplest one. For that reason maybe you could investigate more on your idea of p
5. 5.▲
   by bikebilly 9y ago

   Features scheduled to be EE only are intended to be useful mainly for big organizations, you can find more information here: https://about.gitlab.com/about/#what-features-are-ee-only . The decision could be reverted, it
6. 6.▲
   by bikebilly 9y ago

   Thank you for sharing your thoughts: you're totally right, this feature has much interest by the community and is an high priority. By the way, this is also a very complex topic, as you need to provide great flexibility but at the same