A local rpm build can be achieved using ''mock''. You can do it by issuing the following command:
+
A local rpm build can be achieved using ''mock''. You can do it by issuing the following command:<syntaxhighlight lang="shell">
−
make mockbuild
make mockbuild
−
+
</syntaxhighlight>While positioned in the cloned directory. mock will read the data in the directory (NOT from git) and create a src and binary rpm. This can then be copied to the test VM and tried.
−
While positioned in the cloned directory. mock will read the data in the directory (NOT from git) and create a src and binary rpm. This can then be copied to the test VM and tried.
=Saving the Source code to Gitea=
=Saving the Source code to Gitea=
Line 111:
Line 109:
''git push'' WILL ACTUALLY do the update to the remote repo.
''git push'' WILL ACTUALLY do the update to the remote repo.
+
+
Once I have saved a set of changes to gitea/git I then paste a link to the set of changes (taken from the Rocket Gitea channel typically) into the corresponding bugzilla entry for the change.
=Tagging and starting a build=
=Tagging and starting a build=
+
When you want to do a koji build, then you need to generate a release tag in the gitea/git repo and then submit the current source to koji for the build. This is best done after you have saved any changes etc by a sequence of ''git add'', ''git commit'' and ''git push''.
+
+
The command to tag and build is:<syntaxhighlight>
+
make tag build
+
</syntaxhighlight>Once the build starts, the command returns a link to the build log, this can then be posted to the corresponding bugzilla record.