From 0 to 1, from invitation-type internal test to charging launch, Flow. CI has experienced more than ten months of precipitation and polishing. During this period, flow.ci engineers worked hard to implement a series of major feature updates, Bug fixes, and feature optimizations.
This article documents major feature updates and related hands-on tutorials during the internal beta of Flow. ci, as well as new features that will be iterated over for the foreseeable future.
Officially closed
At the beginning of April, Flow. ci Beta was launched, officially entering the vision of developers. The Beta version of Flow. ci supports the most mainstream foreign code warehouse construction, as well as basic plug-ins and triggers, supports the mainstream development language to create automatic workflow, and provides basic practice tutorials related to each development language. The idea was that Flow. CI would liberate engineers from repetitive tasks.
Go online with documents
The official document of flow.ci supports both Chinese and English versions. By the way, the official documentation for continuous deployment and automatic updates using flow.ci is also available here.
More suitable for domestic developers – code repository support Coding
Flow. Ci quickly supported Coding repository after investigating the usage habits of domestic developers. In addition to existing code sources (GitHub/GitLab/Bitbucket), Coding can now be selected for continuous integration when creating projects 🙂
Code quality inspection plug-in online
Better code quality checks that help us detect errors in code, reduce codereView time, and improve code maintainability.
Based on this principle, we have launched several code quality checking plug-ins, covering the main code quality checking plug-ins in every development language. It’s also very easy to add plug-ins: search for relevant keywords and click “Add” to add them to an existing workflow.
Support continuous integration of iOS projects
At the request of most iOS developers, Flow. ci began to support continuous integration of iOS projects. Check out this iOS quick start to help you quickly compile, test, package and upload to fir. Im, all in one go:
You can also refer to the flow. Ci iOS construction experience shared by @Amamoy in internal test >> Initial experience of Flow. Remember a heartwarming iOS continuous integration.
Flow. Ci open beta
Register Remove the restriction of invitation code, users can directly register to use flow.ci. We are trying to make Flow. ci accessible to more developers and open to more voices.
.yml configuration files are supported
In addition to page configuration workflow, flow.ci currently supports the more geeky way of setting workflow –. Yml configuration file, refer to the document: YML configuration file for details. Choose the way you like and be happy 🙂
So far, the above are the major functional updates of Flow. CI from internal testing to charging launch. What will the future flow. CI look like? We have planned the following major functions online, see if there are any of the functions you expect.
More flexible custom Docker images
If you are not satisfied with the official Flow. Ci docker image, then be sure to try custom Docker image! You can install any runtime components, dependency packages and so on in the custom Docker image, which is more flexible and convenient.
Support plug-in customization, open the plug-in market
Many developers like to use custom plug-in scripts. In the future, Flow. ci will unify the script standards for plug-ins, and developers can submit their plug-ins to the Flow. ci plug-in market as an open source, so that developers can avoid repeating the wheel.
Build status monitoring capabilities
One of the principles of continuous integration is that everyone can see the build status of the current project. Flow. ci will monitor the build status of the project from the two dimensions of “project” and “time”, so as to easily track the failure of the project to the relevant responsible personnel.
Project construction data analysis presentation
Data analysis of project construction can be screened according to “time” to check the success rate of project construction, construction times, construction duration and other data indicators, so as to more conveniently understand and analyze the construction status of team projects.
Support continuous deployment
Continuous deployment is more of a focus than continuous integration. Use flow.ci to automatically deploy the tested code to various cloud platforms such as AWS, Ali Cloud, IBM Bluemix (plug-in form) or your own server, and automate the entire workflow from build-test-deploy
Support for product storage
In the future, Flow. ci will save logs generated during the construction process, installation packages of the construction results and other related products, so that the products can be traced and searched, and the codes and products correspond one by one.
Long-Run
Make sure the environment is clean/fresh so that the results are the same every time. Long-run provides a sustainable test environment for deployable releases after the build is completed, so that projects and different code versions are isolated from each other.
The seven new features above will be available in the next three months, so if you need anything else, please comeFlow. The ci communityLet us know 🙂
I hope flow. CI will bring you more surprises in the future!