sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Radu Cotescu (Jira)" <j...@apache.org>
Subject [jira] [Comment Edited] (SLING-8864) Creating a new JIRA version fails
Date Wed, 27 Nov 2019 13:32:00 GMT

    [ https://issues.apache.org/jira/browse/SLING-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983508#comment-16983508
] 

Radu Cotescu edited comment on SLING-8864 at 11/27/19 1:31 PM:
---------------------------------------------------------------

I've just realised that this is part PEBKAC, part a not so helpful error message. I was still
using my old Jira username and password, from before the migration to LDAP. Is there a way
to detect an authentication failure and report it like that? We do have a 401 error code in
the response, so I guess it shouldn't be that difficult.


was (Author: radu.cotescu):
I've just realised that this is part PEBKAC, part a not so helpful error message. I was still
using my old Jira username and password, from before the migration to LDAP. Is there a way
to detect an authentication failure and report it like that?

> Creating a new JIRA version fails
> ---------------------------------
>
>                 Key: SLING-8864
>                 URL: https://issues.apache.org/jira/browse/SLING-8864
>             Project: Sling
>          Issue Type: Bug
>          Components: Tooling
>            Reporter: Radu Cotescu
>            Assignee: Robert Munteanu
>            Priority: Major
>             Fix For: Committer CLI 1.0.0
>
>
> {noformat}
> docker run -it --env-file=./docker-env apache/sling-cli release create-new-jira-version
-r 2160 -x INTERACTIVE
> Found Version: Resource Resolver 1.6.16 (id=12346273, fixed issues=3).
> Should version Resource Resolver 1.6.18 be created?
> Yes (y)/No (n)? [Yes (y)]:
> Failed executing command
> java.io.IOException: Status line : HTTP/1.1 401 401. Failed parsing response as JSON
( java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 11 column
1 path $ )
> 	at org.apache.sling.cli.impl.jira.VersionClient.newException(VersionClient.java:235)
> 	at org.apache.sling.cli.impl.jira.VersionClient.create(VersionClient.java:156)
> 	at org.apache.sling.cli.impl.release.CreateJiraVersionCommand.run(CreateJiraVersionCommand.java:90)
> 	at picocli.CommandLine.executeUserObject(CommandLine.java:1687)
> 	at picocli.CommandLine.access$900(CommandLine.java:146)
> 	at picocli.CommandLine$RunLast.handle(CommandLine.java:2059)
> 	at picocli.CommandLine$RunLast.handle(CommandLine.java:2026)
> 	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:1893)
> 	at picocli.CommandLine.execute(CommandLine.java:1822)
> 	at org.apache.sling.cli.impl.CommandProcessor.runCommand(CommandProcessor.java:110)
> 	at org.apache.sling.cli.impl.ExecutionTrigger.lambda$activate$0(ExecutionTrigger.java:33)
> 	at java.base/java.lang.Thread.run(Unknown Source)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message