The Jenkins extension doesn't seem to work in conjunction with the Folder's add-on for Jenkins. This allows nesting Jobs within a folder.
In the Jenkins URL it ends up in something like \job\folder\job\jobname

Would there be a way for me to enter the Job name to work with this from the BuildMaster side?
I understand it's an add-on for Jenkins but this is historical for us and to change it would be a big task at this point.

Product: BuildMaster
Version: 5.6.6

I have a test setup where I have several release template variables for Deployment that have initial values and are not required. Then I've set the Build stage to Auto Deploy the next stage.
When I try to run this I get a warning in the Create Package dialog saying I cannot deploy because Deployment Variables must be entered and then it does not auto deploy the next stage.
Is this expected? I would have thought if none of the Variables are required that it would just run the next stage.
I even went in and created the same variables in the Pipeline and it still will not auto deploy.

Here is the excerpt from the Pipeline:

{
  "Name": "TestWorkFlow",
  "Color": null,
  "Description": "",
  "EnforceStageSequence": true,
  "Stages": [
    {
      "Name": "Build",
      "Description": null,
      "TargetExecutionMode": "Sequential",
      "Targets": [
        {
          "PlanName": "TestImport",
          "EnvironmentName": "Build",
          "BuildImporterTemplate": null,
          "ServerNames": [
            "BUILD2"
          ],
          "ServerRoleNames": [],
          "DefaultServerContext": 1
        }
      ],
      "Gate": {
        "UserApprovals": [],
        "GroupApprovals": [],
        "AutomaticApprovals": []
      },
      "PostDeploymentPlan": null,
      "PostDeploymentEventListeners": [],
      "AutoPromote": true,
      "Variables": {}
    },
    {
      "Name": "Development",
      "Description": null,
      "TargetExecutionMode": "Parallel",
      "Targets": [
        {
          "PlanName": "TestApp Test Plan",
          "EnvironmentName": "Development",
          "BuildImporterTemplate": null,
          "ServerNames": [],
          "ServerRoleNames": [],
          "DefaultServerContext": 0
        }
      ],
      "Gate": {
        "UserApprovals": [],
        "GroupApprovals": [],
        "AutomaticApprovals": []
      },
      "PostDeploymentPlan": null,
      "PostDeploymentEventListeners": [],
      "AutoPromote": false,
      "Variables": {
        "ClientId": "TestCustomerId",
        "AppPoolName": "blah_pipeline",
        "test1": "blah_pipeline_blah",
        "ManualDeployment": "False"
      }
    },

And the Release Template used:

{
  "Name": "testtemplate",
  "Pipeline": "TestWorkFlow",
  "ReleaseVariables": [
    {
      "Name": "JenkinsProject",
      "Description": "",
      "InitialValue": "MainBuild",
      "Required": false,
      "Sensitive": false,
      "Type": "Text",
      "PipelineStageName": "",
      "ListValues": [],
      "ListMultiple": false,
      "ListRestrict": false,
      "ListSourceDescription": null,
      "ListSourceXml": null,
      "ListVariableSource": null
    }
  ],
  "PackageVariables": [
    {
      "Name": "JenkinsBuildNumber",
      "Description": "",
      "InitialValue": "",
      "Required": true,
      "Sensitive": false,
      "Type": "DynamicList",
      "PipelineStageName": "",
      "ListValues": [],
      "ListMultiple": false,
      "ListRestrict": true,
      "ListSourceDescription": "Jenkins (<span class=\"hilite\">OF_BuildTasker</span>)  builds for <span class=\"hilite\"><span class=\"variable\">$JenkinsProject</span></span>.",
      "ListSourceXml": "<Inedo.Extensions.Jenkins.ListVariableSources.JenkinsBuildNumberVariableSource Assembly=\"Jenkins\"><Properties CredentialName=\"Tasker\" JobName=\"$JenkinsProject\" /></Inedo.Extensions.Jenkins.ListVariableSources.JenkinsBuildNumberVariableSource>",
      "ListVariableSource": {
        "CredentialName": "Tasker",
        "JobName": "$JenkinsProject"
      }
    },
    {
      "Name": "ServerList",
      "Description": "",
      "InitialValue": "build2",
      "Required": true,
      "Sensitive": false,
      "Type": "DynamicList",
      "PipelineStageName": "",
      "ListValues": [],
      "ListMultiple": false,
      "ListRestrict": true,
      "ListSourceDescription": "Servers in Development environments.",
      "ListSourceXml": "<Inedo.BuildMaster.Extensibility.ListVariableSources.ServerListVariableSource Assembly=\"BuildMasterExtensions\"><Properties EnvironmentsFilter=\"Development\" /></Inedo.BuildMaster.Extensibility.ListVariableSources.ServerListVariableSource>",
      "ListVariableSource": {
        "EnvironmentsFilter": "Development"
      }
    }
  ],
  "DeploymentVariables": [
    {
      "Name": "AppPoolName",
      "Description": "",
      "InitialValue": "blah",
      "Required": false,
      "Sensitive": false,
      "Type": "Text",
      "PipelineStageName": "",
      "ListValues": [],
      "ListMultiple": false,
      "ListRestrict": false,
      "ListSourceDescription": null,
      "ListSourceXml": null,
      "ListVariableSource": null
    },
    {
      "Name": "test1",
      "Description": "",
      "InitialValue": "blahblah",
      "Required": false,
      "Sensitive": false,
      "Type": "Text",
      "PipelineStageName": "",
      "ListValues": [],
      "ListMultiple": false,
      "ListRestrict": false,
      "ListSourceDescription": null,
      "ListSourceXml": null,
      "ListVariableSource": null
    },
    {
      "Name": "ManualDeployment",
      "Description": "Do not change this value. Used internally for scripts.",
      "InitialValue": "true",
      "Required": false,
      "Sensitive": false,
      "Type": "Checkbox",
      "PipelineStageName": "",
      "ListValues": [],
      "ListMultiple": false,
      "ListRestrict": false,
      "ListSourceDescription": null,
      "ListSourceXml": null,
      "ListVariableSource": null
    }
  ],
  "DefaultDeployableOption": "PreviousRelease",
  "Deployables": [
    {
      "Name": "TestDeploy"
    }
  ]
}

Thanks.

Product: BuildMaster
Version: 5.6.6

Is there a way to tell if a Stage is being auto deployed by a previous stage or manually executed?
I'm trying to handle a situation where the script will act a bit differently based on if it is auto deployed or not.

Product: BuildMaster
Version: 5.6.6

I am trying to use the Ensure or Get Proget Package, feed is correct, credentials correct, but when it runs i'm getting an odd error:
The server returned an error (404): OData method is not implemented.

This is for a Nuget feed so is that supposed to work via these functions?

Product: BuildMaster
Version: 5.6.4

Is there a way for me to use BuildMasters resource credentials when calling a Powershell script stored in BuildMaster?

Thanks.

Product: BuildMaster
Version: 5.6.4

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.

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

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.

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)

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

Thanks for clarifying that about the Nuget feeds. Awhile back I understood the behavior had been changed so new Nuget feeds did not function the same way.
It was a discussion related to Jenkins so I may have misunderstood where the change was.

that's a good suggestion I might be able to use that with some other adjustments.

Is there someway to make a copy of my previous Deployment feeds? The configuration of those feeds fit my needs perfectly.

Another question, sort of related, there is the concept of Groups when I'm uploading to Proget but I can find no use for it on the Proget server, is there someway within the Web UI to sort or show the groupings?
I see Tags in the feeds which seems to correlate but I cannot filter to only see the packages for a particular tag either.

I'm going to submit a bug on this as there is also an issue with Deleting a package from a Universal feed when there are multiple versions of the package.

I found a possible solution, looks like the Jenkins add-on for BuildMaster is now handling the metatdata in the version string. However, when I upload a package to the universal feed as 1.0.0+29 and then upload another as 1.0.0+30 the feed shows 1.0.0+29 as the current package and I have to go into the Full Versions list to see the newer packages, but even then I cannot select any of the other versions listed like I can in other feeds.

Is this a bug?

We have a couple of products that are 10+ year established code base and a very large code base on top of that. So changing the versioning of these products is not going to happen anytime soon.
Just prior to 5.x you had introduced the Deployment feeds which allowed, still widely used, 4 placed versioning like 1.0.0.4. This allows me to store multiple versions of packages in the feed.
I still have two of these Deployment feeds but I cannot create anymore, so my question is how can I handle the need to keep multiple build packages around in a ProGet feed, say a Universal one? So if I upload today 1.0.0.4 and tomorrow need to upload 1.0.0.5 and keep both around for a few weeks how can I do that without creating entriely separate packages? Right now if I upload a package using our versioning but following your feed requirements I cannot do this since they get pushed as 1.0.0 in both cases.

Why make a Universal feed so restrictive? It's supposed to be Universal isn't it?

Product: ProGet
Version: 4.6.3

Not sure if this is a Buildmaster HTTP Post issue or a ProGet API issue.
I've tried several iterations of the HTTP Post to try and promote a package on ProGet.
I've followed everything I can find on both subjects but have been unable to get it to work.

What I'm not sure about is how to enter JSON in the BuildMaster HTTP post function. I've tried TextData and FormData.

The issue I'm having is that I keep getting a 401 unauthorized however I am putting in an API Key that is configured for Promotion API on ProGet.

Here is what I have been trying:

    Post-Http http://progetserver/api/promotions/promote
    (
        ContentType: application/json,
        TextData: key: "API Key entered here", 
            packageName: "Package Name",
            user: "Admin username",
            version: "54.0.0",
            fromFeed: "src feed",
            toFeed: "dest feed",
            comments: "This package promoted by BuildMaster",
        LogRequestData: true,
        LogResponseBody: true
    );

I've also tried it with FormData but that didn't work, which I would expect in this case.

Product: BuildMaster
Version: 5.5.3

I would like to use some of the functions under the Windows SDK that pre-5 BuildMaster did have. I know BM doesn't have these actions directly being used but I was wondering if there is someway to call them?
For example I need to use the Install to GAC function but now in 5.x I cannot seem to call it.

Thanks,
Jon

Product: BuildMaster
Version: 5.4.2

Oh ok, I thought it was done by you. I'll pester him about that then.
Sorry about that.

Thanks,
Jon

I realize the API can do it but since there is a plugin for Jenkins and this seems like a very useful option could we add a feature request for that?

What is the eta on the API update?

Thanks,
Jon

Using the Jenkins BuildMaster plugin I know I can launch a BuildMaster job but what it doesn't seem to be capable of is specifying which stage of the pipeline you want to execute.
If I have a Jenkins job builds the app, then I want it to have BuildMaster import the files, then setup an Integration test area, then go back to Jenkins to run the integration tests, then assuming success have BuildMaster execute the next step by calling it again, will that work? It seems that the BuildMaster plugin only supports just doing the "Create Package" call so if I call it again will just re-import the files again rather than do the next stage?
I know I can put the Execute Next Stage flag on in BuildMaster but I don't want it to do that in place of calling it the second time.

Thanks.

Product: BuildMaster
Version: 5.3.7