 | Lars Fosdal on Security alarm provider Woonve… |
 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2025/01/16
For me, saving bitbucket.org passwords fails consistently (when using app passwords, it keeps popping up the git credentials dialog on Windows each time I try to push to origin), so I need to dig deeper into [Wayback/Archive] Updating Git for Windows credentials for Bitbucket app password – Stack Overflow.
Query: [Wayback/Archive] windows store bitbucket app password in git – Google Suche
--jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2024/04/04
Bitbucket nuked all Mercurial repositories in 2020 in the midst of my cancer treatment so back then I wrote Sunsetting Mercurial support in Bitbucket – Bitbucket
So I am glad there is [Wayback/Archive] Mercurial Bitbucket Archive | Index
This is the archive of all public Mercurial projects that were hosted on Bitbucket before they [Wayback/Archive] removed Mercurial support on July 1, 2020. Some projects might be unavailable or incomplete because they were deleted or made private before we had a chance to archive them.
Posted in BitBucket, Development, DVCS - Distributed Version Control, Mercurial/Hg, Source Code Management | Leave a Comment »
Posted by jpluimers on 2022/05/24
For my link archive: [Wayback] version control – Migrate from bitbucket to GitLab – Stack Overflow
Documentation: [Wayback] Import your project from Bitbucket Cloud to GitLab | GitLab
–jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitLab, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2020/08/27
Example URL to diff Spring.pas over two commits in a git repository (reminder to self: see if I can find similar information for a Mercurial repository):
This diffs the file https://bitbucket.org/sglienke/spring4d/src/master/Source/Base/Spring.pas over these commits
master branch release of version 1.2.1)–jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
Posted by jpluimers on 2020/01/30
February 1st, the start commences of Sunsetting Mercurial support in Bitbucket – Bitbucket [WayBack]. Starting June 1st, only git is supported by Bitbucket, despite them having started with and focused mainly Mercurial at first.
Here are the major dates of the sunset:
- February 1, 2020: users will no longer be able to create new Mercurial repositories
- June 1, 2020: users will not be able to use Mercurial features in Bitbucket or via its API and all Mercurial repositories will be removed.
All current Mercurial functionality in Bitbucket will be available through May 31, 2020.
So by now you should have started migrating from Mercurial to git, probably away from BitBucket.
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2019/01/10
When you search for git push "The requested URL returned error: 403", then the usual answer is “use ssh over https”, for instance at [WayBack] github – Pushing to Git returning Error Code 403 fatal: HTTP request failed – Stack Overflow.
However, lots of places (especially larger corporations and financials) limit outgoing traffic to http and https based for (often perceived) security reasons.
In this case, I needed a solution for Windows, which – after a long search – found two solutions that are below.
I use the https://gitlab.com/wiert.me/examples/sql-examples.git repository as an example, but it isn’t limited to GitLab: the same symptoms happen with other hosters as well (for instance on GitHub and BitBucket):
First what doesn’t work: they all give the same 403 message.
git version 2.13.3.windows.1)git config --local credential.helper cachegit config --local credential.https://gitlab.com.username wiertPushing to https://gitlab.com/wiert.me/examples/sql-examples.git
git: 'credential-cache' is not a git command. See 'git --help'.
remote: HTTP Basic: Access denied
fatal: Authentication failed for 'https://gitlab.com/wiert.me/examples/sql-examples.git/'The first thing that works is to include the actual password in the repository URL like this:
When you enter the correct password, everything is fine. Except that the password is stored as plain text on disk.
The real solution on Windows is to use the Windows Credential Manager. I found this because of the 5th failure above.
To see which username/password combinations have been stored or add your own, you can start the Credential Manager on the command-line like this (each Windows version seems to have a different path to the UI from the control panel; the console trick just works on all Windows versions I tested):
%windir%\explorer.exe shell:::{1206F5F1-0569-412C-8FEC-3204630DFB70}Note the above was the reason for writing List of Shell GUIDs for various Windows versions for use in shortcuts and batch files.
I have the impression that the “cached” credential manager will work on non-Windows systems, but need to find some time testing that on multiple platforms. Stay tuned (:
For that I need to look into at least these:
–jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitHub, GitLab, Source Code Management | Leave a Comment »
Posted by jpluimers on 2018/12/18
One of the BitBucket features I like a lot is that in the commit history, you see the branches involved in a nice diagram on the left side of the commits: https://bitbucket.org/pypy/pypy/commits
BitBucket used to be popular to host public repositories, but from a public perspective, they are on the decline for that (they even removed the [once popular] bitbucket.org/explore page and [WayBack] will not re-introduce it).
Right now, only major git based hosters still have explore pages:
So it makes sense to see where they provide diagrams of branches, so here are some examples to go from a project to the graph:
–jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, GitHub, GitLab, Mercurial/Hg, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2018/07/25
If you are using bitbucket from behind a firewall, these might be important to you:
What are we doing? We’ll start a gradual rollout of changing our A records in DNS starting at 22:00 UTC on Sunday, July 29 2018 to point to new IP addresses. The rollout is expected to be completed for all our customers two weeks later, i.e by the 15th of August.
…
How will this affect you?
Most users will not have to do anything special for this migration. Your DNS servers should pick up the new IPs within a few minutes of the migration, and your systems should start using the new IPs right away. We’ll keep the old IPs running for a few weeks afterwards just in case, though.
Firewall considerations
If you control inbound or outbound access with a firewall, then you may need to update your configuration. Please whitelist these new IPs now; you should be able to remove the old IPs after the migration is complete. New destination IP addresses for
bitbucket.org,bitbucket.com,api.bitbucket.org,bitbucket.io,bytebucket.org,altssh.bitbucket.orgwill be: IPv4:18.205.93.0/25and13.52.5.0/25IPv6:2406:da00:ff00::0/96
- Note: this IPv6 range includes subnets that are not necessary owned by Atlassian, but is the longest subnet that matches *all* Bitbucket IPv6 Atlassian IPs. We will post a list of the exact IPv6 addresses at https://confluence.atlassian.com/bitbucket/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall-343343385.html soon. Webhooks IPs will remain unchanged as per https://confluence.atlassian.com/bitbucket/manage-webhooks-735643732.html
SSH considerations
Our server’s SSH key is not changing, so most SSH clients will continue to work without interruption. However, a small number of users may see a warning similar to this when they push or pull over SSH: Warning: the RSA host key for ‘bitbucket.org’ differs from the key for the IP address ‘18.205.93.1’ The warning message will also tell you which lines in your ~/.ssh/known_hosts need to change. Open that file in your favorite editor, remove or comment out those lines, then retry your push or pull.
Additional resources Atlassian Public IP ranges JSON: https://ip-ranges.atlassian.com/ (will be updated with the new addresses as part of the new IPs rollout) https://confluence.atlassian.com/bitbucket/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall-343343385.html (will be updated with the new addresses as part of the new IPs rollout)
From:
–jeroen
Posted in BitBucket, Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2017/07/26
Seems I need to say good bye to Bitbucket: while creating a new repository without changing any user aspects, I got this nice message at https://bitbucket.org/repo/create which does not explain which limit I reached:
You’ve exceeded your user limit, restricting all your repositories to read-only access. Change your plan to restore write access. Learn more
Later I found that https://bitbucket.org/account/user/jeroenp/plans-and-billing/ lists I’m within the free plan:
–jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Source Code Management | Leave a Comment »
Posted by jpluimers on 2017/05/16
When logging in using the Web UI with a username
As of a few days, I was getting this error in my SourceTree output when pushing to git :
remote: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile.
I think this is at least related to a change Bitbucket made 2 years ago for their site logon:
You can no longer log in with a username. Use your Atlassian account email address instead.
Source: Bitbucket
Pushing to bitbucket with cached credentials from SourceTree has worked for months. One thing that was different now (and should have given me a clue) the broken [WayBack] broken Git Credentials Manager popup showed but should not have.
When you get this credential manager you have to escape it as otherwise you will get an “Empty password” error.
Broken Git Credential Manager for Windows
Initially I blamed the error on the SourceTree 2.x upgrade I did last week. Unlike previous upgrades, this one had kept the old version (in my case 1.9.13.7) around and after a few clicks (skipping the “go to download page” prompt forever) and closing SourceTree 2.0, I fas able to start SourceTree 1.9 again.
SourceTree 1.9 had the same problem which meant it was either git itself, or the Bitbucket back-end.
To prove it was the Bitbucket back-end, I did everything An example of this is in the output below.
What helped were these steps:
https://jeroenp@bitbucket.org/jeroenp/fastmm.git to
https://bitbucket.org/jeroenp/fastmm.git
Now SourceTree happily cached my credentials.
I’ve used this to scan the git config files for ones starting with a username:
grep -inSwl jeroenp@bitbucket config
Notes:
Reproduction of the issue:
C:\Users\jeroenp\Versioned\FastMM>git --version git version 2.12.2.windows.1 C:\Users\jeroenp\Versioned\FastMM>git -c diff.mnemonicprefix=false -c core.quotepath=false push -v --tags --set-upstream bitbucket develop:develop Pushing to https://jeroenp@bitbucket.org/jeroenp/fastmm.git Logon failed, use ctrl+c to cancel basic credential prompt. Password for 'https://jeroenp@bitbucket.org/': remote: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile. fatal: Authentication failed for 'https://jeroenp@bitbucket.org/jeroenp/fastmm.git/'
This has worked for months (after [WayBack] canceling the Git Credentials Manager popup as that has been broken for a very long time and gives you a remote: Empty password).
What helped was this:
C:\Users\jeroenp\Versioned\FastMM>git -c diff.mnemonicprefix=false -c core.quotepath=false push -v --tags --set-upstream bitbucket develop:develop Pushing to https://bitbucket.org/jeroenp/fastmm.git Logon failed, use ctrl+c to cancel basic credential prompt. Username for 'https://bitbucket.org/': jeroen...@....com Password for 'https://jeroen...@....comcom@bitbucket.org/': Total 0 (delta 0), reused 0 (delta 0) POST git-receive-pack (196 bytes) remote: remote: Create pull request for develop: remote: https://bitbucket.org/jeroenp/fastmm/pull-requests/new?source=develop&t=1 remote: To https://bitbucket.org/jeroenp/fastmm.git xxxxxxxx..xxxxxxxx develop -> develop updating local tracking ref 'refs/remotes/bitbucket/develop' Branch develop set up to track remote branch develop from bitbucket.
–jeroen
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 