In BuildMaster 4.2.0, we are making variables usable across almost all of BuildMaster, including notifiers. If you can wait for the next version, you'll just be able to use a variable in an execution completed notifier. We will likely be shipping a 4.2 beta this week. If you need this functionality before then, you'll have to implement a custom notifier.

Hello JP, have you seen the Sleep Action? I think that would solve what you're looking for...

Are you still experiencing this problem? The ProGet service is very lightweight and should startup almost instantly, though it's possible that the database connection is what's taking the time. Could you try running the ProGet service interactively? (Make sure to stop the service and run the ProGet.Service.exe executable) This will give instant logging feedback and detail any errors or connection slowness as it happens.

Thanks for the report - we have reproduced the issue and have implemented a fix for this in v4.1.7 due out later today.

we fixed our problem. after many tests we found out that we must use the absolute name of the package "CompanyName.Project.Common.Application" and not only application.

Thanks Tod! Works like a charm. Perhaps a better approach would be to clear the handlers and add only the ones used by the application? In any case that pretty much solves it for us (until the next problematic suffix...) Thank you.

Wanted to follow up on this issue and thank you for the response. We upgraded from 4.1.5 to 4.1.6 and I reran a script that should have failed and it did indeed throw an error. SQL Server Extension was upgraded to 4.1.3.0 and the expected error is thrown. Thanks again. Source and Target directory same; splitting. AgentBasedAction Initialization Complete: Temp Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\TMP Source Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\SRC Target Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\WRK Server: XXXXXXXXXXXXX (Id: 2) Initializing action... Initialization complete. Executing... DB Version: 1 Current Version: 1 Total Scripts in BuildMaster: 8 Scripts Reported Run by Target DB: 10 Determining scripts that need to be run... Scripts to run: 1 Executing FailFailFail The script "FailFailFail" execution failed. SQL Error: Cannot find the object "dbo.KSJHFKSHFKJSSKFLSJKDF" because it does not exist or you do not have permissions. Execution Complete. Execution complete. Finalizing... Target directory unused; joining with source. Finalization complete.

It is... but in this case it seems the error is that an empty value is attempted to be added; it's hard to know exactly where that value is coming from by just seeing the error message unfortunately... In BuildMaster 4.1 and earlier, empty variable values are not allowed. This will change in 4.2, along with some other improvements.

See: http://stackoverflow.com/questions/22767440/using-teamcity-build-number-in-buildmaster

This is not a very common scenario, so I would suggest altering your workflow to not always update the packages if they don't change. Alternatively you'll need to add some custom steps such as deleting the package before pushing it, or using a custom package store.

It sounds like there are some encoding issues; i would make sure your assemblyinfo file in source control is saved as UTF-8.

Yes Spaces were in all of my feed names. Removing the spaces resolved my issue. Removing the spaces also resolved the issue where the Download button was not working which I had reported in another thread. Thanks.

It looks like that particular package has a .nuspec file that does not match the name of the package ID. If you change the name of the nuspec file inside the package to match the package ID it should be able to be indexed. We will add a better error message for this in the next version.

We don't have one.... for now we're planning on featuring our deploy features in v3. Any suggestions or things you think we should do?

We had considered this feature when designing ProGet, but ultimately didn't implement it. One very popular workflow is to have BuildMaster push the packages to different feeds based on environment. Have you considered using that?

I believe this is a bug in NuGet; https://nuget.codeplex.com/workitem/4050 If not, I would suggest to do a fiddler trace to see specifically which url is failing,.

I get the same error with nuget.exe 2.7,2.6 and 2.5. We hope you can fix it in future version

This can sometimes happen if you import a plan from an application that only has a single deployable. It is possible that a deployment plan could be created without being assigned to a deployable, and since applications with a single deployable are designed to hide deployables from the UI, it's difficult to determine what would have caused this. From the UI, the easiest way to ensure that the correct deployables are assigned to an action group is to add a 2nd "dummy" deployable that will re-enable the ability to see assigned deployables from the UI perspective. This will then display the deployable name on the action group as it did before v4.0.

That seems odd - it's possible Gallio changed the output format of the tests and they are no longer registering correctly as failures in BuildMaster. Can you post the issue on GitHub? https://github.com/Inedo/bmx-gallio/issues