You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the behaviour for mock image building has changed now with tim present. Pre-tim, a mock image build was practically a no-op however now with tim in place, the template actually builds a image when I request a mock build.
sloranz mentioned there are two type of mock builds for imagefactory and in order to get a fake build (like we did pre-tim), we would need to edit the templates os name (to FedoraMock or RHELMock) which I assume we would want to do on the fly as we pass the user's template to imagefactory.
The text was updated successfully, but these errors were encountered:
Basically I am thinking we want mock builds to continue being a no op (like pre-tim conductor behaviour). In order for that to happen, the template os name needs to use FedoraMock or RHELMock. When originally discovering this and discussing with Dev, the line of thought was have tim update the os template name on the fly when mock target is requested otherwise mock builds actually build a full blown image which mock does not need or use.
I noticed that the behaviour for mock image building has changed now with tim present. Pre-tim, a mock image build was practically a no-op however now with tim in place, the template actually builds a image when I request a mock build.
sloranz mentioned there are two type of mock builds for imagefactory and in order to get a fake build (like we did pre-tim), we would need to edit the templates os name (to FedoraMock or RHELMock) which I assume we would want to do on the fly as we pass the user's template to imagefactory.
The text was updated successfully, but these errors were encountered: