Bug 436862 - Ability to release multiple things using at once
Summary: Ability to release multiple things using at once
Status: RESOLVED FIXED
Alias: None
Product: releaseme
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-10 09:08 UTC by Bhushan Shah
Modified: 2021-05-10 11:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bhushan Shah 2021-05-10 09:08:22 UTC
SUMMARY

When doing release for PlaMo gear, I created some wrapper scripts to wrap around tarme/tagme/branchme etc

Similary there exists some scripts for Plasma in repo.

But this is not practical

STEPS TO REPRODUCE
1. Want to release > 1 thigns

OBSERVED RESULT

You will need multiple wrapper scripts for this

EXPECTED RESULT

You can do something like,

./tarme.rb --origin trunk --version 21.05 plasma-phonebook,plasma-dialer,spacebar....xyz

and it would create a tars without needing explicit loop/wrapper script

similar goes for tagme and branchme.
Comment 1 Harald Sitter 2021-05-10 09:13:56 UTC
don't you then still need a script to remember which $foo is part of $productset? That is to say that I agree with the use case, but the suggested solution seems a bit lackluster.

https://invent.kde.org/sysadmin/repo-metadata/-/issues/3 might be what we want?

The way I see it you aren't releasing a bunch of stuff, you are releasing a $thing that is comprised of a bunch of stuff and the trouble is that we have no way to define $thing in any of the metadata we have.
Comment 2 Bhushan Shah 2021-05-10 09:33:24 UTC
(In reply to Harald Sitter from comment #1)
> don't you then still need a script to remember which $foo is part of
> $productset?

Well sure, but then this can be as simple as the simple yml file or text file with list of repositories I want releaseme to act on for starter. 

> https://invent.kde.org/sysadmin/repo-metadata/-/issues/3 might be what we
> want?

I agree with need for this though.
Comment 3 Harald Sitter 2021-05-10 09:56:50 UTC
The problem is that we, KDE, have been putting bandaids on this problem forever so I'd rather see that metadata issue moved forward to have a proper solution outside proprietary metadata for a specific tool (in this case releaseme - as indeed right now releaseme doesn't sport proprietary metadata by design because this was a huge problem in kdelibs4 times).

I guess somewhat separate from that we can still have the argument list, then it's at least not my proprietary metadata but yours :P
Comment 4 Bug Janitor Service 2021-05-10 10:30:21 UTC
A possibly relevant merge request was started @ https://invent.kde.org/sdk/releaseme/-/merge_requests/10
Comment 5 Harald Sitter 2021-05-10 11:39:29 UTC
Git commit 3238ae1a724b9f3cc9eb44ba1a74fbca91875e89 by Harald Sitter.
Committed on 10/05/2021 at 10:26.
Pushed by sitter into branch 'master'.

accept multiple project names as input

this allows mass releasing software by passing multiple project names to
tarme. this effectively recycles the already existing tech of releasing
an entire project category. everything should work just fine as-is since
the internal metadata between tarme and tagme are designed around
multiple projects

M  +6    -7    tarme.rb

https://invent.kde.org/sdk/releaseme/commit/3238ae1a724b9f3cc9eb44ba1a74fbca91875e89