Comments

• 

  over 9 years ago by zzhou | Reply

  Wikipedia of Continuous_integration

  Concept - All developers merge their code in the shared mainline several times a day. - To combine CI with test automated to prevent "integration hell". - In addition to running the unit and integration tests, CI could contribute to additional static and dynamic tests, measure and profile performance, extract and format documentation from the source code, etc.

  Best Practices - Maintain a code repository ==> github/osc - Automate the build ==> OBS/IBS Keep the build fast - Test in a clone of the production environment ==> TBD easy to get the latest deliverables - Automate deployment ==> TBD - Everyone can see the results of the latest build ==> TBD - Fix Broken Builds Immediately

  CI :: Tools

  • SCM: github - Webhooks

    • "Obs Service Hooks" is called upon a "push" event.

  • BS: obs - "_service" file and TOKEN

    • Let github.com trigger your source update and build your RPM http://openbuildservice.org/2013/11/22/Source-Update-Via_Token

  • CI: jenkins - "URLTrigger Plug-in"

    • poll URL changes and trigger a job execution upon a new RPM.
    • track upstream changes and rebase downstream repo.

  • Automate deployment(Testbed Orchestration)

    • [yes] autoyast
    • [yes] openQA - "Asset Creation" golden master image
    • [?] "chef vs puppet"
    • [no] openstack

  • Run Testsuites, Teamwork, more, ...

×
Edit Comment 1306
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
#### Wikipedia of Continuous_integration Concept - All developers merge their code in the shared mainline several times a day. - To combine CI with test automated to prevent "integration hell". - In addition to running the unit and integration tests, CI could contribute to additional static and dynamic tests, measure and profile performance, extract and format documentation from the source code, etc. Best Practices - Maintain a code repository ==> github/osc - Automate the build ==> OBS/IBS Keep the build fast - Test in a clone of the production environment ==> TBD easy to get the latest deliverables - Automate deployment ==> TBD - Everyone can see the results of the latest build ==> TBD - Fix Broken Builds Immediately #### CI :: Tools * SCM: github - Webhooks - "Obs Service Hooks" is called upon a "push" event. * BS: obs - "_service" file and TOKEN - Let github.com trigger your source update and build your RPM http://openbuildservice.org/2013/11/22/Source-Update-Via_Token * CI: jenkins - "URLTrigger Plug-in" - poll URL changes and trigger a job execution upon a new RPM. - track upstream changes and rebase downstream repo. * Automate deployment(Testbed Orchestration) - [yes] autoyast - [yes] openQA - "Asset Creation" golden master image - [?] "chef vs puppet" - [no] openstack * Run Testsuites, Teamwork, more, ...
 
×
Reply to zzhou
Wikipedia of Continuous_integration
Concept - All developers merge their code in the shared mainline several times a day. - To combine CI with test automated to prevent "integration hell". - In addition to running the unit and integration tests, CI could contribute to additional static and dynamic tests, measure and profile performance, extract and format documentation from the source code, etc.
Best Practices - Maintain a code repository ==> github/osc - Automate the build ==> OBS/IBS Keep the build fast - Test in a clone of the production environment ==> TBD easy to get the latest deliverables - Automate deployment ==> TBD - Everyone can see the results of the latest build ==> TBD - Fix Broken Builds Immediately
CI :: Tools
• SCM: github - Webhooks

  • "Obs Service Hooks" is called upon a "push" event.

• BS: obs - "_service" file and TOKEN

  • Let github.com trigger your source update and build your RPM http://openbuildservice.org/2013/11/22/Source-Update-Via_Token

• CI: jenkins - "URLTrigger Plug-in"

  • poll URL changes and trigger a job execution upon a new RPM.
  • track upstream changes and rebase downstream repo.

• Automate deployment(Testbed Orchestration)

  • [yes] autoyast
  • [yes] openQA - "Asset Creation" golden master image
  • [?] "chef vs puppet"
  • [no] openstack

• Run Testsuites, Teamwork, more, ...
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview