Comments

• 

  almost 8 years ago by locilka | Reply

  Hi. You be interested in Roman's https://github.com/roman-neuhauser/bs-update

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

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

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

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Hi. You be interested in Roman's https://github.com/roman-neuhauser/bs-update
 
×
Reply to locilka
Hi. You be interested in Roman's https://github.com/roman-neuhauser/bs-update
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

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

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

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

  almost 8 years ago by locilka | Reply

  Another idea is what the Yast team does with all packages: https://ci.opensuse.org/view/Yast/job/yast-autoinstallation-master/lastStableBuild/consoleFull

  We have Jenkins jobs that periodically check for changes in Git. If some are found, we checkout the Git repo, create a package, build it, run tests, and if everything is OK, we also submit it to our devel project and create a subtmit request to openSUSE and SLE.

  Of course, we run more tests than just unit tests. We also, for instance, run RuboCop to check the code quality.

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

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

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

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
Another idea is what the Yast team does with all packages: https://ci.opensuse.org/view/Yast/job/yast-autoinstallation-master/lastStableBuild/consoleFull We have Jenkins jobs that periodically check for changes in Git. If some are found, we checkout the Git repo, create a package, build it, run tests, and if everything is OK, we also submit it to our devel project and create a subtmit request to openSUSE and SLE. Of course, we run more tests than just unit tests. We also, for instance, run RuboCop to check the code quality.
 
×
Reply to locilka
Another idea is what the Yast team does with all packages: https://ci.opensuse.org/view/Yast/job/yast-autoinstallation-master/lastStableBuild/consoleFull
We have Jenkins jobs that periodically check for changes in Git. If some are found, we checkout the Git repo, create a package, build it, run tests, and if everything is OK, we also submit it to our devel project and create a subtmit request to openSUSE and SLE.
Of course, we run more tests than just unit tests. We also, for instance, run RuboCop to check the code quality.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

* Use asterisks
* for lists

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

This is an ![example image](http://paste.opensuse.org/view/raw/68957446)

This is a user link @hans

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