Visual Studio Team Services Build with label not found - azure-devops

I have a label in my project
When I queue a build, and put the label in the "Source Version" field, prefixed with a L, it always comes up the following error:
500: TF14064: Could not find label mylabel#$/.
Anyone been able to get this functionality to work?

Most likely the problem is that your label is not collection-scoped and therefore you need to provide a scope with your label. If you created your label in Visual Studio, the scope is probably project-scoped. So for example if your label is 'mylabel' and your project name is 'myproject' then in the Source Version field you should enter this:
Lmylabel#$/myproject
Here are a couple links that help explain labels and scopes if you are interested.
https://msdn.microsoft.com/en-us/library/9ew32kd1(v=vs.100).aspx
http://teamfoundation.blogspot.com/2008/03/label-scope-revealed.html
I'll update the Microsoft Connect Page with this information too.

I can reproduce this issue and have help you submit a feedback on Microsoft Connect Page, you can track the status here: https://connect.microsoft.com/VisualStudio/feedback/details/2345698/500-tf14064-could-not-find-label-error-occurs-when-queue-a-build-with-specified-label

I was facing the same issue for TFS build and the error says like: “Cannot find the current label tfs build”.
How to resolve the issue:
Go to Configuration of your TFS build
Make the Label sources as true
Build the solution now and it's building fine.
Please reach out if any issues.

Related

Trouble with POD installation: "`ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES"

I have issues with POD installation.
In "ProjectName"[Demo] and "ProjectName"[Release] I get the error:
"...target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in `Pods/Target Support Files/Pods-ProjectName-Demo/Pods-ProjectName-Demo.debug.xcconfig'. This can lead to problems with the CocoaPods installation"
I have set "Always Embed Swift Standard Library" to NO
Edit: I have done the suggested steps in the suggested duplicate post thread, but still got error
I was able to fix this problem by doing the following:
1.Go into Build Settings
2.At the top select All and Combined
3.Under Build Options you should see Always Embed Swift Standard Libraries and it is bold.
4.Click on it and click delete. It should now be unbolded.
5.Pod install and the error/errors should go away!
For more details please refer this link.https://github.com/CocoaPods/CocoaPods/issues/5981

Error occurred while starting the build in Openshift 3

I have been trying to deploy a war file as an OpenShift project. The server used is jboss-webserver30-tomcat8. I have followed the below steps -
Put ROOT.war file under 'deployments' directory in local system.
Upload the changes in github.
Create a new JAVA project in OpenShift 3 and provide the github repository details.
No automatic build or deployment starts. On manually clicking on Start Build button, the below error is displayed:
An error occurred while starting the build. Reason: Error resolving
ImageStreamTag jboss-webserver30-tomcat8-openshift:1.2 in namespace
openshift: unable to find latest tagged image
Please suggest how can I resolve the error.
This is an issue with how the jboss-webserver30-tomcat8-openshift imagestream is defined in the cluster. We are working to correct this, it is not currently importing the correct set of tags and as a result the 1.2 tag was stopped being a valid tag, when it should be.
However the short term solution is change your buildconfig to reference one of the tags that has a valid image reference associated (e.g. 1.3) instead of the 1.2 tag it is currently referencing. Your build should then be able to run.
A (temporarily) unavailable builder image may be related to this platform upgrade that correlates with the time of posting your question.
Generally, the best place to check for any incident reports or scheduled maintenance is the Status Page (Starter | Pro clusters; it's linked in the web console too, in the upper right corner of the interface).
If this does not seem to be related (e.g. you're not on the starter-us-west-2 cluster where the platform upgrade is taking place) or persists after the maintenance is over, I would encourage you to check the open issues, and log a new bug report, if it's not in the list.
Thank you.

Mule ESB, Launching project encountered an issue after the project was renamed

I have a flow running within a project named 'dm' that was created by someone else.
This flow works well.
I Right click and hit "Copy", and then I hit "Paste", and chose the project name 'dm_1'. All looks well
So I try to run the new project, I right click on the flow and hit "Run As - Mule Application"
Immediately I get the following error:
Launching dm_1 has encountered a problem.
Studio has encountered a problem. In order to get assistance with this issue, either contact MuleSoft or post a message in the MuleSoft Community Forums (http:/forum.mulesoft.org) with a detailed description of how you encountered the problem
DETAILS:
Studio has encountered a problem. In order to get assistance with this issue, either contact MuleSoft Support or post a message on the MuleSoft community forums (http://forum.mulesoft.org) with a detailed description of how you encountered the problem.
Project referenced by launch does not exist.
So how do I fix this problem.
I do not see anything within the xml that would suggest there is a project name that needs to be changed as well, with the possible exception of the following line:
<mulexml:schema-validation-filter schemaLocations="C:\Users\xxx\AnypointStudio\workspace\dm\src\main\resources\p.xsd" returnResult="false" doc:name="Schema Validation"/>
Where do I look to change the project name
try adding a new flow to the same project. Then right click on the new flow and run it. This will cause the entire project to run.

microsoft chart controls the resource cannot be found

Microsoft Chart Controls on shared hosting with .net framework 4.0 installed. "The resource cannot be found."
Locally it works just fine. I confirmed that the dlls are on the server.
I have tried changing all settings in the web.config and ImageLocation parameters. No luck.
Any suggestions?
To troubleshoot the issue first make sure that the chart assemblies are installed in the GAC.
Then try to hit the server with server/yoursite/chartimg.axd?i=0.png&g=0 from the browser (use these exact parameters). If you get "The resource cannot be found" then the handler is not installed properly: look for the issue in your web.config and try again until you get "System.ArgumentException: The image is not found". This means the handler is installed properly and works as expected.
Then render the page which contains a chart control where Chart.ImageStorageMode = UseHttpHandler. If you get an exception please post the exception stack here as well as your major controls layout like: "the chart is placed in update panel, which is placed in a user control, which is placed in update panel in the page".

How can I fix this Android SDK build problem in Eclipse?

I am using Eclipse for Android dev and everything was going fine until I tried to incorporate the facebook SDK. Now when I tried to back it out, there appears to be an artifact left behind that Eclipse tries to link the FB library?!?
[2010-11-17 18:50:22 - Library Project] Unable to set linked path var '_android_com.facebook.android' for library /Users/mobibob/Projects/workspace/facebook-android-sdk/facebook: Path variable name cannot contain character: ..
Any clue where this command / reference is in the build configuration? I have scoured it as best that I can, but I still get the same error.
Problem solved ... as it turns out, it was not so much the Facebook SDK but something that I did in the process of configuring the library reference. I am not entirely certain of how I misconfigured, but I was tweaking the various "path" settings such that, once when the automatic build tried to build my project, an import for android.R was added to my source module. This superseded com.myproject.R and would not resolve the values for resource references.
There were other problems with path order and setting that I modified during the troubleshooting that made it worse. Recreating the project without Facebook was the first step to discovery and fixing.
Either way, the lesson I learned is that the build error messages can misdirect one to the configuration when the problem is in the source code.