Update YouTrack state on issue from checkin comment in SVN - teamcity

I've been trying to set issues to status "fixed" from my SVN commits, but it keeps on failing. This is what I've been trying as SVN comment:
#TCSE-20 fixed
and
TCSE-20 fixed
Where TCSE-20 of course is my issue id. I then run my build in TeamCity, which is linked to the YouTrack project.
The comment gets recognized in YouTrack as it's added to the Comments tab. But the state remains as Submitted. What am I doing wrong?

The solution was what I was hinting in my comment. I am the administrator of our YouTrack server, and I used my email address for the "root" account, as well as having my own user, based on my username, with the same email address. When I changed the "root" accounts email address to one of my colleagues, the commands executed correctly.
Now I would like to know how to solve this better, like disabling "root" from the user lookup function, but that will be another issue. :-)

Related

Sourcetree: Invalid password for Github despite having a valid OAUTH token on Windows

I use Github and Sourcetree on my Windows machine.
I have been into Tools - Options - Authentication and added my Github account. I am 120% sure that my settings are correct.
However, when I try to push anything, I keep getting:
git -c diff.mnemonicprefix=false -c core.quotepath=false push -v --tags origin develop:develop
fatal: HttpRequestException encountered.
An error occurred while sending the request.
remote: Invalid username or password.
fatal: Authentication failed for 'REPOLINK'
Pushing to REPOLINK
Completed with errors, see above.
Now, I also tried to remove the account in my settings, and then entering e-mail / password manually. Usually it will say OK and ask for my 2FA code on my phone, but for now it just fails and responds with invalid username/password.
Any ideas?
EDIT:
Still a problem. I also tried to decrease my commit size from 15k files to just 1. Doesn't work.
I managed to commit through the console (but I have to fill credentials each time).
So unfortunately this is still unsolved.
http://www.omniweb.com/wordpress/?p=1291 this person solved it, it works for me.
navigating to C:\Users\USERNAME\AppData\Local\Atlassian\SourceTree and removing (or renaming) the passwd file.
Once this file is removed, restart SourceTree and execute a fetch or something else that requires access to the repo in question. SourceTree will then prompt you for your password, rewriting the cached credentials.
This is not a very good answer, but I still wanted to show my solution now 1.5 months have gone by.
On 3 computers I've failed to get Sourcetree to work. I'm using Windows on all machines, and above problem keeps happening no matter what I do. I've tried preferences/settings, filling it on prompt...
I doubt it's my account - I use Github OAUTH in many other programs.
The day after this post, I switched to SmartGit. Works much better and no problems, and will not go back.
This is a very bad answer - but if you're ending up here from Google - this is one possible solution.

User has does not have permission to be mentioned

We have a TFS user who appears to have the same permissions as a colleague in their team. However this user can't be #mentioned despite having the ability to open and close and otherwise edit the bug that they can't be mentioned in.
The following error is emailed to me following attempting to #mention this user.
#Joe Bloggs cannot be mentioned in the Bug 41729. The user does not have
sufficient permissions.
We can't see any differences between a user that can be tagged and one that can't.
We were getting this same error.
Went into the project settings -> security.
Clicked "remove" on that user
at which point the "remove" changed into an "undo".
Clicked the "undo".
Now we are no longer seeing this error. Seems like something internally just needed to be recombobulated :-)
If you are sure that the user exists and can be mentioned with "Joe Bloggs" then they do not have read permission on the bug you are referring to. You should go back and check what group membership they have in the project.

How to solve Unexpected HTTP status code: 404(-1)

Although I set up my xcode swift file to create a repository when I click SourceControl -> Make a Working Copy I receive the error window "All projects are already under source control. Then when I to Window -> Welcome to Xcode -> "Check out an existing project" I get the error "Unexpected HTTP status code: 404(-1).
Does anyone have an idea on how to solve this please? Thank you
When you use Welcome to XCode > Check out an existing project you need to enter the github repository url as provided on the <> Code tab in github. It will look something like
https://github.com/username/MyRepository.git
In my case I got -401 with the following premises:
The URL was OK
The user credentials were OK
However, the user was not approved for downloading from that repository
Using the correct user solved the issue.
I got this issue when using xcode with bitbucket service.
Not entirely sure if I changed something or bitbucket changed something but I noticed that my domain in the URI for the remote had changed in bitbucket and xcode was no longer attempting to push to the correct path.
eg.
domain/repo.git
for some reason now was:
domaincom/repo.git
again, I do not remember changing anything but perhaps something changed in bitbucket to alter how the usernames are formed?
I think my team ( username ) was domain.com and they always worked with the first part up until the first . but perhaps changes have allowed for their service to remove all dots and use the full team name ( username )
I removed and re added the remote using the correct URI and it worked.
In my case, the issue was with my bitbucket plan which had exceeded the free plan tier and was restricted to read-only. Fixed my plan in bitbucket, and the issue was solved after a while.

Xcode setting up for git repository hung

I was trying to set up my Xcode 5 connecting to my github repository. The procedure stopped like this
It could never get through it. What else can I do to get it done? Thanks!
I ran into the same issue, and it turned out to be because I was using a lowercase username in the URL when my actual GitHub username is mixed-case (!). It seems that missing or invalid credentials sometimes simply cause it to hang on the "Verifying" step.
This is a long shot, but go to your GitHub profile and double-check the actual case of your username. Also try copying the clone URL from GitHub's web page for the repository, then adding the (username)# portion, to make sure there are no typos in your URL.

Team Explorer Everywhere - Domain user could not be validated

I am using Team Explorer Everywhere command line tool on a mac. I've setup a connection to the TFS and i got my files. Checked them out for editing and i see on another machine they are indeed checked out. Now when i try to check them back in i run
sudo tf checkin MiniOrka.iOS -recursive -comment:Testing -login:myUsernam#myDomain,myPW
But all i get is:
Exception in thread "main" com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: >RebuildCallersViews: Connecting Domain User could not be validated. ---> >RebuildCallersViews: Connecting Domain User could not be validated. ---> >RebuildCallersViews: Connecting Domain User could not be validated.
at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:127)
at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:826)
at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:454)
at ms.tfs.workitemtracking.clientservices._03._ClientService2Soap12Service.getMetadataEx2(_ClientService2Soap12Service.java:745)
at com.microsoft.tfs.core.clients.workitem.internal.metadata.Metadata.update(Metadata.java:515)
at com.microsoft.tfs.core.clients.workitem.internal.metadata.Metadata.update(Metadata.java:482)
at com.microsoft.tfs.core.clients.workitem.internal.WITContext.(WITContext.java:97)
at com.microsoft.tfs.core.clients.workitem.WorkItemClient.getContext(WorkItemClient.java:359)
at com.microsoft.tfs.core.clients.workitem.WorkItemClient.query(WorkItemClient.java:521)
at com.microsoft.tfs.client.clc.vc.commands.CommandCheckin.checkWorkItems(CommandCheckin.java:354)
at com.microsoft.tfs.client.clc.vc.commands.CommandCheckin.run(CommandCheckin.java:181)
at com.microsoft.tfs.client.clc.Application.run(Application.java:294)
at com.microsoft.tfs.client.clc.Application.run(Application.java:144)
at com.microsoft.tfs.client.clc.vc.Main.main(Main.java:33)
And my files remain checked out. I am a member of the Contributor group (they can add, modify and delete items within the team project).
Anyone know how to fix this?
Try using -login:myUsernam#myDomain and entering the password at the prompt that follows.

Resources