You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "stack (Created) (JIRA)" <ji...@apache.org> on 2012/02/23 20:20:54 UTC
[jira] [Created] (INFRA-4482) Why is my upload to mvn spread across
multiple repositories?
Why is my upload to mvn spread across multiple repositories?
------------------------------------------------------------
Key: INFRA-4482
URL: https://issues.apache.org/jira/browse/INFRA-4482
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Reporter: stack
I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
{code}
<servers>
<!-- To publish a snapshot of some part of Maven -->
<server>
<id>apache.snapshots.https</id>
<username>stack
</username>
<password>XXXX
</password>
</server>
<!-- To publish a website using Maven -->
<!-- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
<username>stack
</username>
<password>XXXX
</password>
</server>
</servers>
<profiles>
<profile>
<id>apache-release</id>
<properties>
<gpg.keyname>00A5F21E</gpg.keyname>
<gpg.passphrase>XXXX
</gpg.passphrase>
</properties>
</profile>
</profiles>
</settings>
{code}
My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4482) Why is my upload to mvn spread
across multiple repositories?
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214952#comment-13214952 ]
stack commented on INFRA-4482:
------------------------------
I cannot pubish my staging repos even if I select all because each complains of missing elements. For example:
{code}
Staging ruleset evaluation on repository 'org.apache.hbase-049 (u:stack, a:38.99.102.224)' has failed.
Staging Checksum Validation
-Missing MD5: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.md5.'
Staging Signature Validation
-Missing Signature: '/org/apache/hbase/hbase/0.92.0/hbase-0.92.0.jar.asc' does not exist for 'hbase-0.92.0.jar'.
{code}
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Reporter: stack
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-4482) Why is my upload to mvn spread across
multiple repositories?
Posted by "Sebb (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebb updated INFRA-4482:
------------------------
Component/s: Nexus
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: stack
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-4482) Why is my upload to mvn spread across
multiple repositories?
Posted by "stack (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated INFRA-4482:
-------------------------
Attachment: Screen Shot 2012-02-23 at 9.50.58 AM.png
Picture of multiple repos for one artifact upload
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Reporter: stack
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4482) Why is my upload to mvn spread
across multiple repositories?
Posted by "Brian Demers (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219408#comment-13219408 ]
Brian Demers commented on INFRA-4482:
-------------------------------------
It looks like your outbound connection keeps getting a different IP. Can you verify this is how your network is setup?
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: stack
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4482) Why is my upload to mvn spread across
multiple repositories?
Posted by "Brian Fox (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed INFRA-4482.
----------------------------
Resolution: Unresolved
Assignee: Brian Fox
For now Nexus needs to have a stable ip for inbound deploys, it uses a combination of user agent, ip and user to divine a single stream of artifacts from a build.
We are rewriting staging, planned for 2.1 in a month or so that will allow a different mode of staging where this won't be an issue.
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: stack
> Assignee: Brian Fox
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4482) Why is my upload to mvn spread
across multiple repositories?
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219518#comment-13219518 ]
stack commented on INFRA-4482:
------------------------------
I talked to our ops lads:
"Yep. That's exactly the case. We have a NAT pool where we use 32 IP addresses for network address translation. Stability of the outgoing IP address is only guaranteed per destination IP address."
It would seem that I have to find a build server that is inside a network that doesn't NAT pool.... I'll have to go scrounging if so.
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: stack
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4482) Why is my upload to mvn spread
across multiple repositories?
Posted by "stack (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238717#comment-13238717 ]
stack commented on INFRA-4482:
------------------------------
Workaround was to do upload from home rather than from work.
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: stack
> Assignee: Brian Fox
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4482) Why is my upload to mvn spread
across multiple repositories?
Posted by "Sebb (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219439#comment-13219439 ]
Sebb commented on INFRA-4482:
-----------------------------
Surely the Nexus login should be sufficient to identify the client?
Why does Nexus take any notice of the IP address?
If I upload some files to a staging repo one day, but don't close the repo, I would expect to be able to upload to the same staging repo at a later stage even if my ISP gives me a new IP address; and I would expect to be able to upload a different host too.
Also, a single IP address may be shared between multiple users (e.g. if uploading from a corporate intranet).
> Why is my upload to mvn spread across multiple repositories?
> ------------------------------------------------------------
>
> Key: INFRA-4482
> URL: https://issues.apache.org/jira/browse/INFRA-4482
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: Nexus
> Reporter: stack
> Attachments: Screen Shot 2012-02-23 at 9.50.58 AM.png
>
>
> I'm been struggling publishing a release to repository.apache.org. Its worked for me in the past. If you look at https://repository.apache.org/index.html#stagingRepositories (you need to be logged in), you will see that I somehow made twelve repositories when I did my mvn release:perform, each artifact element to its own repo. Any idea how that happens? (I'll attach a png that shows similar). How do I prevent it?
> I have another issue where the upload to apache will fail with a 400 Bad Request very frequently uploading one of my artifact items -- usually maven-metadata.xml -- but then, just now, it went through fine. Pointers appreciated on this little nugget too.
> I'm using mvn 3.0.4 and 2.2.2 of the maven:release plugin. Otherwise, my settings.xml is one that has worked for me in the past:
> {code}
> <servers>
> <!-- To publish a snapshot of some part of Maven -->
> <server>
> <id>apache.snapshots.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> <!-- To publish a website using Maven -->
> <!-- To stage a release of some part of Maven -->
> <server>
> <id>apache.releases.https</id>
> <username>stack
> </username>
> <password>XXXX
> </password>
> </server>
> </servers>
> <profiles>
> <profile>
> <id>apache-release</id>
> <properties>
> <gpg.keyname>00A5F21E</gpg.keyname>
> <gpg.passphrase>XXXX
> </gpg.passphrase>
> </properties>
> </profile>
> </profiles>
> </settings>
> {code}
> My pom is here: http://svn.apache.org/viewvc/hbase/tags/0.92.0mvn/pom.xml?view=markup
> Thanks for any pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira