Hello Again, In the project meta of a maintenance incident, we usually have **something like**: <releasetarget project="SUSE:Updates:<PRODUCT>:x86_64" repository="update" trigger="maintenance"/> If I change trigger="maintenance" to trigger="manual", will I be able to release the maintenance update by running the following command? $ osc api -X POST '/source/Maintenance:XX/patchinfo?cmd=release&target_project=SUSE:Updates:<PRODUCT>:x86_64&repository=<repository-from-incident>&target_repository=update' Why I'm asking this specifically is whether this would trigger the workflow of updating package tracking information and copying the binaries, etc.? Regards, Srinidhi.
On Wednesday, 10 July, 2019 at 03:40 PM, Srinidhi B <Srinidhi.BS@microfocus.com> wrote: Hello Marcus,
Thank you for responding!
On Wednesday, 10 July, 2019 at 03:27 PM, Marcus Meissner <meissner@suse.de> wrote: Hi Srinidhi,
On Wed, Jul 10, 2019 at 03:37:37AM -0600, Srinidhi B wrote:
Hello Everyone,
I've a question regarding OBS Maintenance Process: What is the best way to
re-release a maintenance update into a different codestream? What I mean to ask is - a maintenance update released for codestream X needs to be released
into codestream Y with following conditions:
A different product from the same built binaries?
Yes. Same built binaries to a different product line. (e.g., between base product and add-on product)
<snip/>
What we do:
osc unlock $INCIDENT the previous released incident. This will keep the package still locked.
add the new product channels (via osc addchannels or osc branch -M ... $OLDINCIDENT)
Edit the project meta:
osc meta prj -e $INCIDENT
remove trigger="maintenance" XML attributes from the repos that should NOT be rereleased.
Thank you for sharing these steps! I was aware of some of these steps, but this trigger="maintenance" is new to me. Will add this to my notes!
But unfortunately, I don't have access to the old incident because the re-release will happen across Build Service instances. This is why, we can't use this approach and we need to import these updates into our instance of Build Service.
Regards, Srinidhi.
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org