Re: [ovirt-users] [ovirt-devel] Lowering the bar for wiki contribution?
by Roy Golan
Adding infra which I forgot to add from the beginning
On 7 January 2017 at 02:44, Jakub Niedermertl <jniederm(a)redhat.com> wrote:
> On Wed, Jan 4, 2017 at 11:41 AM, Roy Golan <rgolan(a)redhat.com> wrote:
> >
> >
> > On 4 January 2017 at 12:17, Maor Lipchuk <mlipchuk(a)redhat.com> wrote:
> >>
> >>
> >>
> >> On Wed, Jan 4, 2017 at 11:38 AM, Daniel Erez <derez(a)redhat.com> wrote:
> >>>
> >>>
> >>>
> >>> On Wed, Jan 4, 2017 at 9:57 AM, Roy Golan <rgolan(a)redhat.com> wrote:
> >>>>
> >>>> I'm getting the feeling I'm not alone in this, authoring and
> publishing
> >>>> a wiki page isn't as used to be for long time.
> >>>>
> >>>> I want to suggest a bit lighter workflow:
> >>>>
> >>>> 1. Everyone can merge their page - (it's a wiki)
> >>>> Same as with (public and open) code, no one has the motivation to
> >>>> publish a badly written
> >>>> wiki page under their name. True, it can have an impact, but not as
> >>>> with broken code
> >>>>
> >>>
> >>> +1.
> >>> Moreover, I think we shouldn't block any merging. Instead, wiki
> >>> maintainers could act afterwards and revert when needed (Wikipedia
> style).
> >>> Another issue is that (sadly) unlike mediawiki, we need to wait for
> wiki
> >>> publish after a change. So I'd suggest to build and publish the wiki at
> >>> least once a day. Any way, I think we should make the workflow much
> more
> >>> intuitive and pleasant like the previous wiki - i.e. much less
> restrictive
> >>> than manipulating a code base.
> >>>
> >>>
> >>>>
> >>>> 2. Use Page-Status marker
> >>>> The author first merges the draft. Its now out there and should be
> >>>> updated as time goes and its
> >>>> status is DRAFT. Maintainers will come later and after review would
> >>>> change the status to
> >>>> PUBLISH. That could be a header in on the page:
> >>>> ---
> >>>> page status: DRAFT/PUBLISH
> >>>> ---
> >>>>
> >>>> Simple I think, and should work.
> >>>>
> >>
> >> +1
> >> The effort of maintaining the wiki today compare to how it used to be
> >> before is much more cumbersome and problematic.
> >> I think we can learn a lot from wikipedia workflow,
> >> It is a much more inviting process where anyone can change the content
> >> easily.
> >> I'm not saying we should let any anonymous user change the wiki but even
> >> if we make it easier in house we can achieve much more informative
> reliable
> >> and updated wiki.
> >>
> >
> >
> >
> > I really think Github Pages is a perfect fit and an alternative to my
> first
> > suggestion. see
> > https://github.com/oVirt/ovirt-site/wiki/Why-aren't-we-using-this%3F
>
> +1
> Github wiki would allow us instant publishing, review after after
> publishing, it works purely in browser (no need for running local ruby
> server) and it's a service that doesn't require any maintenance form
> our side.
>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Devel mailing list
> >>>> Devel(a)ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/devel
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users(a)ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>>
> >>
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
>
6 years, 10 months
[oVirt Jenkins] ovirt_master_hc-system-tests - Build # 52 - Still Failing!
by jenkins＠jenkins.phx.ovirt.org
------=_Part_68_1645509185.1490843485029
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/
Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/52/
Build Number: 52
Build Status: Still Failing
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #51
[Pavel Zhukov] Revert "ost: added repo closure test"
Changes for Build #52
[Pavel Zhukov] Revert "ost: added repo closure test"
[Daniel Belenky] system_tests_template: added 'email-ext' to hc-system-tests template
[Eyal Edri] removing jobs from master publisher - phase III
[Daniel Belenky] jenkins: added a 'standard' support to export junit reports
-----------------
Failed Tests:
-----------------
1 tests failed.
FAILED: nosetests-002_bootstrap.py.xml.[empty]
Error Message:
Stack Trace:
Test report file /home/jenkins/workspace/ovirt_master_hc-system-tests/exported-artifacts/nosetests-002_bootstrap.py.xml was length 0
------=_Part_68_1645509185.1490843485029--
7 years
Build failed in Jenkins: system-sync_mirrors-centos-base-el6-x86_64 #224
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el6-x86_64/2...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el6-x86_64/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from http://gerrit.ovirt.org/jenkins.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:799)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1055)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1086)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128:
stdout:
stderr: fatal: unable to access 'http://gerrit.ovirt.org/jenkins.git/': The requested URL returned error: 502
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1784)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1513)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at ......remote call to mirrors.phx.ovirt.org(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor473.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy72.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:797)
... 11 more
ERROR: null
7 years
oVirt infra daily report - unstable production jobs - 277
by jenkins＠jenkins.phx.ovirt.org
------=_Part_96_519744804.1491001225155
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also here:
- http://jenkins.ovirt.org/job/system_jenkins-report/277//artifact/exported...
Cheers,
Jenkins
------=_Part_96_519744804.1491001225155
Content-Type: text/html; charset=us-ascii; name=upstream_report.html
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=upstream_report.html
Content-ID: <upstream_report.html>
<!DOCTYPE html><head><style type="text/css">
table.gridtable {
border-collapse: collapse;
table-layout:fixed;
width:1600px;
font-family: monospace;
font-size:13px;
}
.head {
font-size:20px;
font-family: arial;
}
.sub {
font-size:18px;
background-color:#e5e5e5;
font-family: arial;
}
pre {
font-family: monospace;
display: inline;
white-space: pre-wrap;
white-space: -moz-pre-wrap !important;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;
}
</style>
</head>
<body>
<table class="gridtable" border=2>
<tr><th colspan=2 class=head>
RHEVM CI Jenkins Daily Report - 31/03/2017
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master-ansible-system-tests/">ovirt_master-ansible-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/">ovirt_master_hc-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_master_image-ng-system-tests/">ovirt_master_image-ng-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/system-sync_mirrors-centos-base-el6-x86_64/">system-sync_mirrors-centos-base-el6-x86_64</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_96_519744804.1491001225155--
7 years
Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #203
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/203/disp...>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 727a57d2a9af0c8ea223841d036ae5a42c6a9d04 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 727a57d2a9af0c8ea223841d036ae5a42c6a9d04
> git rev-list 727a57d2a9af0c8ea223841d036ae5a42c6a9d04 # timeout=10
[system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/hudson868693034221102614.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 687, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 727, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1451, in _commonLoadRepoXML
if self._latestRepoXML(local):
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1420, in _latestRepoXML
oxml = self._saveOldRepoXML(local)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1278, in _saveOldRepoXML
shutil.copy2(local, old_local)
File "/usr/lib64/python2.7/shutil.py", line 131, in copy2
copystat(src, dst)
File "/usr/lib64/python2.7/shutil.py", line 98, in copystat
os.utime(dst, (st.st_atime, st.st_mtime))
OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/epel-el7/repomd.xml.old.tmp'
Build step 'Execute shell' marked build as failure
7 years
[JIRA] (OVIRT-1290) Re-factor OST jobs YAML to reduce duplication
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1290?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1290:
--------------------------------
Summary: Re-factor OST jobs YAML to reduce duplication (was: Re-factor OST jobs YAML the reduce duplication)
> Re-factor OST jobs YAML to reduce duplication
> ---------------------------------------------
>
> Key: OVIRT-1290
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1290
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
> Labels: ost, yaml
>
> Besides the experimental flow jobs, and the manual OST job, we also have a few more jobs that run specific OST suits on a scheduled basis.
> Historically theses suits were written by different people and different job templates in YAML were also written for each suit.
> At some point we have normalized all the suit names in OST to be of the following structure:
> {code}
> <suit_type>-suit-<ovirt version>
> {code}
> This was initially done to allow the mirror injection process to find the '{{reposync-config.repo}}' file but also facilitated the creation of the generic manual OST job.
> Since all suites now follow the same naming convention there is no more reason to have separate YAML job templates per suit. This separation may even cause subtle issues.
> All the YAML OST job templates should be unified so that we'll have just one job template that is parametrized by the suite type and oVirt version. Furthermore we can probably have just one YAML project entry to create all scheduled OST jobs.
--
This message was sent by Atlassian JIRA
(v1000.870.1#100039)
7 years
