...
| Section | ||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Access to Bitbucket web interface
Access to Stash Bitbucket requires that you can login to the main ECMWF page: http://www.ecmwf.int/. This is normally the case if you have an account on ECMWF systems. Use your normal userid and secureid password.
...
To clone the OpenIFS git repository at your local site requires setting a further password to correctly authenticate with the Stash Bitbucket server.
Make sure you can successfully log in to the main ECMWF website before following the procedure below.
...
- Log out from www.ecmwf.int
- Go to https://software.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 Stash Bitbucket in some minutes. You can test it in StashBitbucket's web interface https://software.ecmwf.int/stash/login as long as you are still logged out from www.ecmwf.int
...
| Info | ||
|---|---|---|
| ||
Please ensure you checkout the release branch from the repositories for use. These The release branches mirror the versions available on the ftp site and will be fully tested. To checkout a published release use the release tags. All new code should be placed in a 'feature' branched from 'develop'. Don't create a new feature from a release branch. Only hotfixes should branch from releases (see branching model below). |
...
For example, branches from SMHI would all live under 'smih.se', such as, develop/smhi.se/long-run-changes'; from Barcelona Supercomputer Centre, 'develop/bsc.es/xios' and so on.
If necessary, these user-contributed branches can have their own 'develop' and 'release' branches before any merge takes place on the OpenIFS mainline develop branch. These are the responsibility of the site to manage.
It's desirable to follow the gitflow model under the user contributed branches to maintain consistency with the branch model.
...