[releaseme] [Bug 458728] New: tarme fails because it wants to communicate with Jenkins

[Tobias Leupold]

https://bugs.kde.org/show_bug.cgi?id=458728

            Bug ID: 458728
           Summary: tarme fails because it wants to communicate with
                    Jenkins
           Product: releaseme
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: tl at stonemx.de
                CC: sitter at kde.org
  Target Milestone: ---

tarme.rb currently fails when taring a release, with something like

Traceback (most recent call last):
        8: from ./tarme.rb:74:in `<main>'
        7: from ./tarme.rb:74:in `collect'
        6: from ./tarme.rb:81:in `block in <main>'
        5: from
/hd/home/tobias/tmp/git/releaseme/lib/releaseme/release.rb:66:in `get'
        4: from
/hd/home/tobias/tmp/git/releaseme/lib/releaseme/release.rb:154:in `check_ci!'
        3: from
/hd/home/tobias/tmp/git/releaseme/lib/releaseme/jenkins.rb:60:in
`from_name_and_branch'
        2: from
/hd/home/tobias/tmp/git/releaseme/lib/releaseme/jenkins.rb:23:in `get'
        1: from /usr/lib64/ruby/2.7.0/net/http/response.rb:133:in `value'
/usr/lib64/ruby/2.7.0/net/http/response.rb:124:in `error!': 302 "Found"
(Net::HTTPRetriableError)

This seems to be due to releaseme wanting to check the Jenkins CI state of the
project to be released, and build.kde.org meanwhile being redirected to
metrics.kde.org/login (or, more essentially, Jenkins being retired).

After commenting out the "check_ci!" call in "lib/releaseme/release.rb",
creating a release tarball works again.

-- 
You are receiving this mail because:
You are the assignee for the bug.