[Bugs] [Bug 1727727] Build+Packaging Automation

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1727727



--- Comment #7 from hari gowtham <hgowtham at redhat.com> ---
@Misc, I see debian machines have 20GB disks each and Ubuntu has 30GB disk in
the current machines. And we did come across debian machine not having enough
space to build lately.
So a bit more for the new machines in jenkins would be better.

About signing, is it fine if we get the password to the machines as a parameter
from the person who triggers the jenkins' job and proceed with it to sign in?
This way we can make use of the same machine for building and signing the
package. But I'm not sure if the parameters are logged somewhere. Which will
let others know the password.
If that's the case, do we have a work around for this? If manual intervention
is necessary for signing, it sort of defeats a portion of this effort. 

@Kaleb, I wanted to ask about the steps for the initial environment setup.
Thanks for informing about it, will look into it once the machines are
available.
I want to know if the package that are already built on these lab machines have
to be moved to these new jenkins' machine as a part of keeping track of
packages. 
And will there be any other work to be done as a part of this movement.

Thanks,
Hari.

-- 
You are receiving this mail because:
You are on the CC list for the bug.