Ask A Question

View Question

Hello,
I've got Jira integration setup but it keeps failing with a 503 error.
The credentials used are the same I use with another program and it works fine with Jira so I know that part is correct.
Here is the error I'm getting:

Code

System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Inedo.BuildMasterExtensions.Jira.JiraApi.JiraSoapServiceService.login(String in0, String in1)
at System.Lazy1.CreateValue() at System.Lazy1.LazyInitValue()
at Inedo.BuildMasterExtensions.Jira.Clients.JiraSoapClient.EnumerateIssues(JiraContext context)
at Inedo.BuildMaster.IssueTracking.LegacyIssueTrackerIssueSynchronizer.SyncIssuesInRelease(Applications_Extended application, Releases_Slim release, String[] categoryFilter)

Code

Thanks.

Product: BuildMaster
Version: 5.6.4

Well I found a way to get farther. I had to go into the Configure External Source after I configured it and use the Manually Refresh button. Once I did that it would work if I didn't use a JQL statement.
Now if I put in a JQL statement it partially works. I get one issue from one release but it errors trying to get others.

Here is the JQL I am using:
project = "Schedule Maximizer" and fixVersion = $ReleaseNumberPart(major).0$ReleaseNumberPart(minor) and Component = API and Sub-Components = "Scheduling Module"

If I use the $ReleaseNumberPart(major).0$ReleaseNumberPart(minor) by itself in your Fix Version field I get everything from all the releases. However I'm trying to limit to certain components/subcomponents. The one that works does have them set it just doesn't seem to want to pick up any other versions.

And the error info:

Message - 
 An error occurred in the web application: Value cannot be null. Parameter name: attribute
 
Details -
URL: http://servername/0x44/BuildMaster.Web.WebApplication/Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar/GetNotifications
Referrer: http://servername/reference
User: username
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Stack trace: at System.Xml.Linq.XAttribute.op_Explicit(XAttribute attribute)
at Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar.<>c.<GetNotificationAsync>b__6_5(XElement e)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar.<GetNotificationAsync>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.BuildMaster.Web.WebApplication.Controls.NotificationBar.<GetNotifications>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar)
at System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

In the first case, you were using a "Legacy Issue Tracker". But it looks like you set up a "Issue Source" now, which is the new recommended way.

To debug Issue Sources, you can run a sync manually, and then check out the execution log. This should give some more details as to what the cause of the error might be.

What I sent you above is the only error info I get. The Execution log just says it Completes successfully yet I get no data back that I know is there.
I can take the exact same JQL into Jira, fill in the numbers correctly, and it works.
It also works for one Release version in BuildMaster it's just not working for another.

Is there a way to make BuildMaster log the JQL statement it is trying to use?

Sorry for so many quick posts. I just ran it again using the Manual Refresh and I get the First error I sent. You said this is the Legacy Issue stuff but I'm doing it all from that one spot so how do I get it to NOT use the Legacy?
There is only 1 Source setup for it.

Please disregard now. It's all working fine.
Someone changed the issues I was seeing in Jira yesterday and moved them to another release, incorrectly, at about the same time I was viewing them.

I got the legacy aspect figured out as well so all of future configs should be non-legacy.

Thanks.

Answer Question