How to use "koji call host.*" api ?

[Eric Zhong]

How to use host.* API ???
How to specify the "host" ???

[zhongwenjia@localhost ~]$ koji call host.getHost
AuthError: No host specified

[Mike McLean]

On 03/31/2011 11:32 PM, Eric Zhong wrote:
>  How to use host.* API ???
>  How to specify the "host" ??? 
Step 1) be a build host

These calls are designed to /only/ be called by running build hosts. It 
does not make sense for regular users to call them. Not even admins.

Let us know what you are trying to accomplish. Most likely there is a 
way to do it without using any host.* calls.

>  [zhongwenjia@localhost ~]$ koji call host.getHost
>  AuthError: No host specified

[Eric Zhong]

Thanks ,
I want to move a scratch build to a regular build.
Because programmers do not follow the specification of changelog and
increase release number, and if them build, it will occupy a NVR.
So, i just let them to scratch build , and check changelog and release
number; if it's OK , then i will move it to the regular build state.
If I just import the SRPM&RPMS, it will lost build logs and some other info;
i just want it looks like a regular build .
Or do you have some better ways ,  thank you very much!!!



2011/4/2 Mike McLean <mikem(a)redhat.com&gt;

>  On 03/31/2011 11:32 PM, Eric Zhong wrote:
>  > How to use host.* API ???
>  > How to specify the "host" ???
>
>  Step 1) be a build host
>
>  These calls are designed to /only/ be called by running build hosts. It
>  does not make sense for regular users to call them. Not even admins.
>
>  Let us know what you are trying to accomplish. Most likely there is a
>  way to do it without using any host.* calls.
>
>  > [zhongwenjia@localhost ~]$ koji call host.getHost
>  > AuthError: No host specified
>  --
>  buildsys mailing list
>  buildsys(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/buildsys
>

[Mike McLean]

On 04/01/2011 09:37 PM, Eric Zhong wrote:
>  Thanks ,
>  I want to move a scratch build to a regular build.
>  Because programmers do not follow the specification of changelog and
>  increase release number, and if them build, it will occupy a NVR.
>  So, i just let them to scratch build , and check changelog and release
>  number; if it's OK , then i will move it to the regular build state.
>  If I just import the SRPM&RPMS, it will lost build logs and some other info;
>  i just want it looks like a regular build .
>  Or do you have some better ways ,  thank you very much!!! 
Unfortunately, scratch builds are intended to be what exactly that.

Ideally, your developers would increase the release number for their 
production builds. It is not uncommon for developers to use a series of 
scratch builds as tests, then bump the release and run a normal build 
once things are working. Stop covering for their mistakes and they will 
quickly learn how to bump a release after a few build failures. At least 
the NVR uniqueness check is early in the process.

If you absolutely must create regular builds from scratch build content, 
the least bad way is to simply import them, and perhaps copy the build 
logs somewhere. I realize this is losing information, most notably the 
buildroot data. However, trying to forge a regular build after the fact 
is asking for trouble.

A future version of Koji may be able to do what you want, but for now 
scratch builds are just scratch builds.

[Eric Zhong]

"Stop covering for their mistakes and they will
quickly learn how to bump a release after a few build failures."

Thanks!

2011/4/4 Mike McLean <mikem(a)redhat.com&gt;

>  On 04/01/2011 09:37 PM, Eric Zhong wrote:
>  > Thanks ,
>  > I want to move a scratch build to a regular build.
>  > Because programmers do not follow the specification of changelog and
>  > increase release number, and if them build, it will occupy a NVR.
>  > So, i just let them to scratch build , and check changelog and release
>  > number; if it's OK , then i will move it to the regular build state.
>  > If I just import the SRPM&RPMS, it will lost build logs and some other
>  info;
>  > i just want it looks like a regular build .
>  > Or do you have some better ways ,  thank you very much!!!
>
>  Unfortunately, scratch builds are intended to be what exactly that.
>
>  Ideally, your developers would increase the release number for their
>  production builds. It is not uncommon for developers to use a series of
>  scratch builds as tests, then bump the release and run a normal build
>  once things are working. Stop covering for their mistakes and they will
>  quickly learn how to bump a release after a few build failures. At least
>  the NVR uniqueness check is early in the process.
>
>  If you absolutely must create regular builds from scratch build content,
>  the least bad way is to simply import them, and perhaps copy the build
>  logs somewhere. I realize this is losing information, most notably the
>  buildroot data. However, trying to forge a regular build after the fact
>  is asking for trouble.
>
>  A future version of Koji may be able to do what you want, but for now
>  scratch builds are just scratch builds.
>  --
>  buildsys mailing list
>  buildsys(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/buildsys
>