File: control

package info (click to toggle)
libjira-client-automated-perl 1.90-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, sid
  • size: 208 kB
  • sloc: perl: 1,428; makefile: 2
file content (45 lines) | stat: -rw-r--r-- 2,096 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Source: libjira-client-automated-perl
Maintainer: Debian Perl Group <pkg-perl-maintainers@lists.alioth.debian.org>
Uploaders: Dominique Dumont <dod@debian.org>
Section: perl
Testsuite: autopkgtest-pkg-perl
Priority: optional
Build-Depends: debhelper-compat (= 12)
Build-Depends-Indep: libdata-dump-perl <!nocheck>,
                     libhttp-message-perl <!nocheck>,
                     libjson-perl <!nocheck>,
                     libjson-xs-perl <!nocheck>,
                     liblwp-protocol-https-perl <!nocheck>,
                     libtest-exception-perl <!nocheck>,
                     libtest-mockmodule-perl <!nocheck>,
                     libtest-most-perl <!nocheck>,
                     libwww-perl <!nocheck>,
                     perl
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libjira-client-automated-perl
Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libjira-client-automated-perl.git
Homepage: https://metacpan.org/release/JIRA-Client-Automated

Package: libjira-client-automated-perl
Architecture: all
Depends: ${misc:Depends},
         ${perl:Depends},
         libdata-dump-perl,
         libjson-perl,
         libjson-xs-perl,
         liblwp-protocol-https-perl,
         libwww-perl
Description: JIRA REST Client for automated scripts
 JIRA::Client::Automated is an adapter between any automated system and JIRA's
 REST API. JIRA::Client::Automated is explicitly designed to easily create and
 close issues within a JIRA instance via automated scripts.
 .
 For example, if you run nightly batch jobs, you can use
 JIRA::Client::Automated to have those jobs automatically create issues in
 JIRA for you when the script runs into errors. You can attach error log files
 to the issues and then they'll be waiting in someone's open issues list when
 they arrive at work the next day.
 .
 If you want to avoid creating the same issue more than once you can search
 JIRA for it first, only creating it if it doesn't exist. If it does already
 exist you can add a comment or a new error log to that issue.