...
Section | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
- Log out from www.ecmwf.int
- Go to https://softwaregit.ecmwf.int/issues/login.jsp. Choose "Can't access your account"
- Write your user id.
- Now you should get an email from JIRA offering you a link to reset your JIRA password. Follow this link and type in the new password (it doesn't matter if you don't already have one).
- This password should be available in Bitbucket in some minutes. You can test it in Bitbucket's web interface https://softwaregit.ecmwf.int/stash/login as long as you are still logged out from www.ecmwf.int
...
Code Block | ||
---|---|---|
| ||
% mkdir openifs % cd openifs % git clone ssh://git@softwaregit@git.ecmwf.int:7999/oifs/oifs40r1.git # use: git clone https://nagc@softwarenagc@git.ecmwf.int/stash/scm/oifs/oifs40r1.git external to ECMWF Cloning into 'oifs40r1'... remote: Counting objects: 4680, done. remote: Compressing objects: 100% (3654/3654), done. remote: Total 4680 (delta 1206), reused 4175 (delta 871) Receiving objects: 100% (4680/4680), 21.45 MiB | 20.71 MiB/s, done. Resolving deltas: 100% (1206/1206), done. Checking connectivity... done % cd oifs40r1 % git checkout develop # or whichever release version is required (the most recent is recommended) Branch develop set up to track remote branch develop from origin. Switched to a new branch 'develop' % git checkout -b feature/new_idea # create new branch. ALWAYS branch from the develop branch, never the master branch. Switched to a new branch 'feature/new_idea' |
...
Code Block |
---|
% git clone ssh://git@softwaregit@git.ecmwf.int:7999/oifs/oifs40r1.git oifs40r1v1.1 ...... % cd oifs40r1v1.1 % git checkout v1.1 Note: checking out 'v1.1'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. |
...
Code Block |
---|
% git pull fatal: remote error: CAPTCHA required Your Stash account has been marked as requiring a CAPTCHA to be solved before you may login again. This is typically caused by too many attempts to login with an incorrect password. The required CAPTCHA prevents your SCM client from accessing Stash until it is solved, even if you enter your password correctly. If you are currently logged in to Stash via a browser you may need to logout and then log back in in order to clear the CAPTCHA. Visit Stash at https://softwaregit.ecmwf.int/stash for more details. |
...
- Log off the ECMWF Single Sign On system www.ecmwf.int
- Log in manually into Stash, filling the CAPTCHA field (you will be asked for it after you try a first time). https://softwaregit.ecmwf.int/stash/login
- The password is the same password you use with git, that you can change or recover in JIRA (but do allow some minutes for synchronization from JIRA to Stash
...