[yast-devel] jenkins autosubmit to factory
Hi, today I plan to modify jenkins to do this stuff. It was done only partial, because when my script run, maintenance update of jenkins start ( I get no info that it is planned, Daniel and Bernhard added to CC ). So some job have it and few doesn't. I plan to run script again on Monday, so all jobs will have it. To not loose the script add it to devtools[1], so next time it will be faster ( now it took me with writting script and reading API documentation around half of hour ) and everyone can reuse it. Josef [1] https://github.com/yast/yast-devtools/pull/39 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Fri, 8 Nov 2013 18:45:29 +0100 Josef Reidinger <jreidinger@suse.cz> wrote:
Hi, today I plan to modify jenkins to do this stuff. It was done only partial, because when my script run, maintenance update of jenkins start ( I get no info that it is planned, Daniel and Bernhard added to CC ). So some job have it and few doesn't.
I plan to run script again on Monday, so all jobs will have it. To not loose the script add it to devtools[1], so next time it will be faster ( now it took me with writting script and reading API documentation around half of hour ) and everyone can reuse it.
Josef
JFYI - now script run successfully and now all modules in jenkins can do autosubmit to factory and send email if failed author of commit and to yast-commit. One thing to emails - I disable sending emails for each failed build, so it send only once if it failed and then send another when it is fixed, but no emails between when it is still broken. If you want old behavior, we can discuss it and it is easy to change it. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Update related to autosubmit to factory. Today I found that there is bug in logic that check version, so I am fixing it, but do not have time to test it properly, so plan is that I test it and deploy on jenkins on friday when it should start working. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 8.11.2013 18:45, Josef Reidinger napsal(a):
Hi, today I plan to modify jenkins to do this stuff. It was done only partial, because when my script run, maintenance update of jenkins start ( I get no info that it is planned, Daniel and Bernhard added to CC ). So some job have it and few doesn't.
I plan to run script again on Monday, so all jobs will have it. To not loose the script add it to devtools[1], so next time it will be faster ( now it took me with writting script and reading API documentation around half of hour ) and everyone can reuse it.
It would be nice to document the autosubmit at http://en.opensuse.org/openSUSE:YaST:_Development_Workflow so that we don't end up with undocumented black magic. As an external developer, I would probably primarily like to know: * what code exactly goes where * how is the submit triggered * how the whole thing works (what things happen in what order and how can I inspect them) -- David Majda SUSE developer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Mon, Nov 11, 2013 at 09:58:24AM +0100, David Majda wrote:
It would be nice to document the autosubmit at
http://en.opensuse.org/openSUSE:YaST:_Development_Workflow
so that we don't end up with undocumented black magic.
As an external developer, I would probably primarily like to know:
* what code exactly goes where * how is the submit triggered * how the whole thing works (what things happen in what order and how can I inspect them)
Right. Done. Please review that page, as the paste below is missing the hyperlinks. master / Factory submit code via pull requests in the repositories on GitHub the continuous integration server simply calls rake osc:sr from the packaging_tasks gem, which makes a local build using fresh OBS dependencies (osc:build) commits to the OBS development project obs://YaST:Head* (osc:commit) if the version has changed, submits to obs://openSUSE:Factory* (osc:sr) (* the target projects are configured in the yast-rake gem, required from each package's Rakefile) -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
Dne 18.11.2013 16:48, Martin Vidner napsal(a):
On Mon, Nov 11, 2013 at 09:58:24AM +0100, David Majda wrote:
It would be nice to document the autosubmit at
http://en.opensuse.org/openSUSE:YaST:_Development_Workflow
so that we don't end up with undocumented black magic.
As an external developer, I would probably primarily like to know:
* what code exactly goes where * how is the submit triggered * how the whole thing works (what things happen in what order and how can I inspect them)
Right. Done. Please review that page, as the paste below is missing the hyperlinks.
LGTM content-wise. It could use some formatting/styling love, but I don't have time to help with that now. -- David Majda SUSE developer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
David Majda -
Josef Reidinger -
Martin Vidner