Tutorials
Git
- Annotate source view and diff view with Jest/ESLint information
- Hands-on GitOps with OneDev and Kubernetes
- Get notification when files under folder src/core are changed on master branch
- Set up Repository Mirror with GitHub
- Code review with OneDev
Pull Request
- Run CI job against merged commit when pull request changed files under src folder
- Require at least two members from expert group to approve if a pull request changed files under src/core folder
- Fine-grained notification control
- Set up application live Preview in pull request
Issue
- Fix issues via commit message to link issues, commits, builds and pull requests
- Add custom field Platform and Kernel Version. Kernel Version should be displayed only when Platform is specified as Linux
- Continue with above scenario. For all open Windows issues assigned to tommy or jerry, reassign to robin
- Create an issue board to show open issue assignment between different users
- Assign newly created issues to project owners by default
- Add custom field Module and assign issue of particular module to module leader automatically
- Auto-transit issue to custom state Deployed when build fixing it is deployed
- Auto-transit issue to custom state In Review when relevant pull request is opened
- Auto-transit open issues to state Idle when there is no activity on them for some time
- Add custom state Verified. Only Tester role can transit issues to this state. Further, the transition is applicable for all issue types except Task
- Fine-grained notification control
- Create/discuss issues via email
- Working with Issue Links
- Set up Issue Labels
Build
- Build docker image and push to docker hub
- Working with CI/CD cache
- Build promotion explained
- Interact with insecure docker registry
- Set up CI/CD farm with agents
- Execute CI/CD jobs outside container with OneDev shell executors
- Specify build version when manually trigger a build and create a corresponding tag if build is successful
- Use POM project version as build version in Java maven project
- Prompt for Platform and Kernel Version when manually trigger a build. Kernel Version should be displayed only when Platform is specified as Linux
- Test against any combination of Oracle/MySQL and Linux/Windows upon master branch committing
- Auto-create an issue and assign to committer for investigation upon build failure on master branch; Auto-close the issue when subsequent build succeeds again
- Generate artifacts in one job, and use them in another job
- Generate files in one job, process each file concurrently in the second job, and collect processed results in the third job
- Retry jobs upon Kubernetes worker node error
- Use MySQL service while running the job
- Meet build farm in Kubernetes cluster
- Run build on windows node in Kubernetes cluster
- Clone submodules in build job via SSH
- Retrieve all project tags while running a job
- Commit code in build job and push to OneDev
- Build spec reuse and customization
- Understanding pipeline
Security
- How to clone via SSH
- Single sign on with GitHub
- Single sign on with Okta and authorize users based on Okta group membership information
- LetsEncrypt setup in Kubernetes
- Use secret value in build spec
- Anonymous user can only access release builds of certain projects
- Release builds can only be generated from master branch
- Only release builds from master branch of certain projects can be deployed into production cluster, all other builds should use the test cluster