Difference between revisions of "Updates builder"
(First version) |
(Added templates) |
||
| Line 1: | Line 1: | ||
| − | Updates-builder is a tool to automatically check for package updates and build them in ABF. | + | {{Prog|Updates-builder}} is a tool to automatically check for package updates and build them in ABF. |
== Example == | == Example == | ||
| − | Let's take | + | Let's take {{Pkg|alleyoop}} package as an example - we have version 0.9.7 and want to look for updates: |
$ updates_builder.py --run-one alleyoop | $ updates_builder.py --run-one alleyoop | ||
| Line 12: | Line 12: | ||
done | done | ||
| − | Wow, update is available! updates_builder has downloaded the new tarball, pushed it to ABF file store, updated .abf.yml and spec files and initiated a new build. | + | Wow, update is available! {{Prog|updates_builder}} has downloaded the new tarball, pushed it to ABF file store, updated .abf.yml and spec files and initiated a new build. |
| − | All changes are applied in a | + | All changes are applied in a separate branch called '''auto_update'''. The build is initiated for '''rosa2012.1''' platform, but the result is pushed to '''import_personal''' repository. Moreover, currently resulting packages are not published |
- you should go to container to download them. | - you should go to container to download them. | ||
| − | The next step is to check if the package has been built successfully (if you subscribed to ABF notifications, you will receive a mail about build results). If the built succeeded then you can download the resulting package and check if it works properly. If yes, then merge it to the repository | + | The next step is to check if the package has been built successfully (if you subscribed to ABF notifications, you will receive a mail about build results). If the built succeeded then you can download the resulting package and check if it works properly. If yes, then merge it to the repository. |
| − | First, let's checkout the alleyoop project itself using abf-console-client: | + | First, let's checkout the {{Pkg|alleyoop}} project itself using {{Prog|abf-console-client}}: |
$ abf get alleyoop; cd alleyoop | $ abf get alleyoop; cd alleyoop | ||
$ git checkout auto_update | $ git checkout auto_update | ||
| − | Take a look at the updated .abf.yml and spec file and add/commit | + | Take a look at the updated .abf.yml and spec file and add/commit changes if necessary. |
| − | And now let's switch to rosa2012.1 branch and merge the changes there: | + | And now let's switch to '''rosa2012.1''' branch and merge the changes there: |
$ git checkout rosa2012.1 | $ git checkout rosa2012.1 | ||
| Line 31: | Line 31: | ||
$ abf put -m "LOG Updated to 0.9.8" | $ abf put -m "LOG Updated to 0.9.8" | ||
| − | That's all! Now you can initiate a build for rosa2012.1 platform from the rosa2012.1 branch, The package is updated! | + | That's all! Now you can initiate a build for '''rosa2012.1''' platform from the '''rosa2012.1''' branch, The package is updated! |
== Technical Details == | == Technical Details == | ||
| − | To get information about new software releases, updates_builder uses http://upstream-tracker.org service. If you want updates_builder to monitor some package for which the upstream URL is missing - feel free to contact upstream-tracker.org authors. | + | To get information about new software releases, updates_builder uses http://upstream-tracker.org service. If you want {{Prog|updates_builder}} to monitor some package for which the upstream URL is missing - feel free to contact upstream-tracker.org authors. |
| − | To work with ABF, updates_builder uses [[ABF Console Client]]. | + | To work with ABF, {{Prog|updates_builder}} uses [[ABF Console Client]]. |
[[Category:Package Management]] | [[Category:Package Management]] | ||
Revision as of 17:19, 4 December 2012
Updates-builder is a tool to automatically check for package updates and build them in ABF.
Example
Let's take alleyoop package as an example - we have version 0.9.7 and want to look for updates:
$ updates_builder.py --run-one alleyoop <...> alleyoop-0.9.8 https://sourceforge.net/projects/alleyoop/files/alleyoop/alleyoop-0.9.8/alleyoop-0.9.8.tar.gz <...> Creating a new spec file Downloading file https://sourceforge.net/projects/alleyoop/files/alleyoop/alleyoop-0.9.8/alleyoop-0.9.8.tar.gz done
Wow, update is available! updates_builder has downloaded the new tarball, pushed it to ABF file store, updated .abf.yml and spec files and initiated a new build.
All changes are applied in a separate branch called auto_update. The build is initiated for rosa2012.1 platform, but the result is pushed to import_personal repository. Moreover, currently resulting packages are not published - you should go to container to download them.
The next step is to check if the package has been built successfully (if you subscribed to ABF notifications, you will receive a mail about build results). If the built succeeded then you can download the resulting package and check if it works properly. If yes, then merge it to the repository.
First, let's checkout the alleyoop project itself using abf-console-client:
$ abf get alleyoop; cd alleyoop $ git checkout auto_update
Take a look at the updated .abf.yml and spec file and add/commit changes if necessary.
And now let's switch to rosa2012.1 branch and merge the changes there:
$ git checkout rosa2012.1 $ git merge auto_update $ abf put -m "LOG Updated to 0.9.8"
That's all! Now you can initiate a build for rosa2012.1 platform from the rosa2012.1 branch, The package is updated!
Technical Details
To get information about new software releases, updates_builder uses http://upstream-tracker.org service. If you want updates_builder to monitor some package for which the upstream URL is missing - feel free to contact upstream-tracker.org authors.
To work with ABF, updates_builder uses ABF Console Client.
