Downloads:

3,268

Downloads of v 1.3.0-alpha0338:

16

Last Update:

28 Jan 2021

Package Maintainer(s):

Software Author(s):

  • catenalogic

Tags:

jira command line interface cli

JiraCli

This is a prerelease version of JiraCli.

1.3.0-alpha0338 | Updated: 28 Jan 2021

Downloads:

3,268

Downloads of v 1.3.0-alpha0338:

16

Maintainer(s):

Software Author(s):

  • catenalogic

JiraCli 1.3.0-alpha0338

This is a prerelease version of JiraCli.

Some Checks Have Failed or Are Not Yet Complete

1 Test Failing and 1 Passing Test


Validation Testing Failed


Verification Testing Passed

Details

To install JiraCli, run the following command from the command line or from PowerShell:

>

To upgrade JiraCli, run the following command from the command line or from PowerShell:

>

To uninstall JiraCli, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade jiracli -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade jiracli -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure jiracli installed
  win_chocolatey:
    name: jiracli
    state: present
    version: 1.3.0-alpha0338
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'jiracli' do
  action    :install
  version  '1.3.0-alpha0338'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: jiracli,
    Version: 1.3.0-alpha0338,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller jiracli
{
   Name     = 'jiracli'
   Ensure   = 'Present'
   Version  = '1.3.0-alpha0338'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'jiracli':
  provider => 'chocolatey',
  ensure   => '1.3.0-alpha0338',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install jiracli version="1.3.0-alpha0338" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.
Description

JIRA command line interface.


runtimes\win7-x86\lib\net47\JiraCli.exe
md5: 31B61C4AB517448D467555517265D404 | sha1: 04500C6A8E63A41F813408E8827E022681A4717B | sha256: 0745BF175C803E9630B48BB4C69D9D886FADA4FBABF1F0272576B090333D702F | sha512: 82914CAE5994709FB54347162988475012BE76A933DD8B3C9AA1E9F194D719500FD0CA100F972273882C9188703797EFF842BAEB58633C7D591E53475AB38444
runtimes\win7-x86\lib\net47\JiraCli.exe.config
<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.6.10.0" newVersion="2.6.10.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Threading.Tasks" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.6.10.0" newVersion="2.6.10.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="RestSharp" publicKeyToken="598062e77f915f75" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-106.11.7.0" newVersion="106.11.7.0" />
      </dependentAssembly>
    </assemblyBinding>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.Serialization.Primitives" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.1.2.0" newVersion="4.1.2.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7" />
  </startup>
</configuration>
runtimes\win7-x86\lib\net47\JiraCli.pdb
 
runtimes\win7-x86\lib\net47\JiraCli.xml
<?xml version="1.0"?>
<doc>
    <assembly>
        <name>JiraCli</name>
    </assembly>
    <members>
        <member name="T:MethodTimeLogger">
            <summary>
            Note: do not rename this class or put it inside a namespace.
            </summary>
        </member>
        <member name="M:JiraCli.ArgumentParser.SplitCommandLine(System.String)">
            <summary>
            Shamelessly taken from stackoverflow: http://stackoverflow.com/questions/298830/split-string-containing-command-line-parameters-into-string-in-c-sharp/298990#298990
            </summary>
            <param name="commandLine"></param>
            <returns></returns>
        </member>
        <member name="T:JiraCli.Models.IssueKey">
            <summary>
            A class representing a JIRA issue key [PROJECT KEY]-[ISSUE ID]
            </summary>
        </member>
        <member name="M:JiraCli.Services.VersionService.#ctor(JiraCli.Services.IMergeVersionService,JiraCli.Services.IVersionInfoService)">
            <summary>
            Initializes a new instance of the <see cref="T:JiraCli.Services.VersionService" /> class.
            </summary>
            <param name="mergeVersionService">The merge version service.</param>
            <param name="versionInfoService">The version information service.</param>
        </member>
        <member name="T:ModuleInitializer">
            <summary>
            Used by the ModuleInit. All code inside the Initialize method is ran as soon as the assembly is loaded.
            </summary>
        </member>
        <member name="M:ModuleInitializer.Initialize">
            <summary>
            Initializes the module.
            </summary>
        </member>
    </members>
</doc>

No results available for this package. We are building up results for older packages over time so expect to see results. If this is a new package, it should have results within a day or two.

Version Downloads Last Updated Status
JiraCli 1.3.0-alpha0338 16 Thursday, January 28, 2021 Exempted
JIRA CLI 1.2.0-unstable0019 382 Monday, July 17, 2017 Exempted
JIRA CLI 1.2.0-unstable0012 320 Monday, June 27, 2016 Exempted
JiraCli 1.2.0-beta0002 89 Friday, June 28, 2019 Exempted
JiraCli 1.2.0-beta0001 73 Friday, June 28, 2019 Exempted
JiraCli 1.2.0-beta0000 61 Friday, June 28, 2019 Exempted
JiraCli 1.2.0-alpha0043 90 Friday, June 28, 2019 Exempted
JIRA CLI 1.1.0-unstable0015 358 Wednesday, August 26, 2015 Exempted
JIRA CLI 1.1.0-unstable0003 383 Monday, December 1, 2014 Exempted

This package has no dependencies.

Discussion for the JiraCli Package

Ground Rules:

  • This discussion is only about JiraCli and the JiraCli package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or JiraCli, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus