You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Stian Soiland-Reyes <st...@apache.org> on 2019/01/09 15:37:11 UTC
Taverna git repos moved to GitBox/GitHub
Thanks to Ian, we have now migrated the Taverna Git repositories
We can now write to either gitbox.apache.org or the github.com
repositories.
For committers this should mean easier handling of pull requests as the
GitHub UI would also have write access.
Note that the previous "git-wip-us" repositories are now removed, see
below on how to update your checkout.
Committers/PPMC folks - if you find yourself not in this list:
https://github.com/orgs/apache/teams/taverna-committers/members
.. then you will need to link your GitHub account with your ASF account
here: https://gitbox.apache.org/setup/
Alternatively you can still commit with your ASF account - but now to
the repository at https://gitbox.apache.org instead of the old
git-wip-us.apache.org server. This should also work in read-only for
anonymous users.
I've updated https://taverna.incubator.apache.org/download/code/
with the new info and GitBox in the dropdown list, you may find this
useful to update your checkouts.
I've added "GitHub SSH" in the list which should work
as well for those using SSH keys with GitHub.
New secret feature on page:
If you switch dropdown to "Apache GitBox" then the Browse button will
also go there instead of GitHub.
To update an existing checkout, use "git remote set-url" with your
new favourite:
stain@biggie:~/src/incubator-taverna-maven-parent$ git remote set-url origin git@github.com:apache/incubator-taverna-maven-parent.git
stain@biggie:~/src/incubator-taverna-maven-parent$ git pull
Already up-to-date.
Committers - to test authorization (https works anonymously) you can do a small
change in README.md before you git push.
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
RE: Taverna git repos moved to GitBox/GitHub
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
Woohoo. It’s sorted. All those little computer agents talking to each other. It’s so 21st century.
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 27 March 2019 14:59
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub
Hello,
So I went GitHub.com/apache and found that there was an old invite (sure I clicked that years ago but anyway....). However I get a 404 on https://github.com/orgs/apache/teams/taverna-committers/members. Do I just have to wait for apache/gitbox/GitHub to talk to each other or is there something else I need to click.
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 27 March 2019 14:42
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub
Hello,
Just realised that I wasn’t a member of the ASF GitHub org. I tried setting up via gitbox but I get stuck at the “MFA Status” part where it tells me to add GitHub id to my id.apache.org page and wait for an email. I thought I did that years ago. Is this something that we have to do again?
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 18 January 2019 11:53
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub
Hello,
Sounds a good option to me Stian 😊. I tend to use ssh for all my GitHub repos.
Cheers,
Ian
Sent from Mail for Windows 10
From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub
On Mon, 14 Jan 2019 11:06:00 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Which git server should be the default <developerConnection> ?
> This is used by "mvn release:prepare" in the release procedure.
>
>
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh
Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories;
editing straight in GitHub!
Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!
I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
RE: Taverna git repos moved to GitBox/GitHub
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
So I went GitHub.com/apache and found that there was an old invite (sure I clicked that years ago but anyway....). However I get a 404 on https://github.com/orgs/apache/teams/taverna-committers/members. Do I just have to wait for apache/gitbox/GitHub to talk to each other or is there something else I need to click.
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 27 March 2019 14:42
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub
Hello,
Just realised that I wasn’t a member of the ASF GitHub org. I tried setting up via gitbox but I get stuck at the “MFA Status” part where it tells me to add GitHub id to my id.apache.org page and wait for an email. I thought I did that years ago. Is this something that we have to do again?
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 18 January 2019 11:53
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub
Hello,
Sounds a good option to me Stian 😊. I tend to use ssh for all my GitHub repos.
Cheers,
Ian
Sent from Mail for Windows 10
From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub
On Mon, 14 Jan 2019 11:06:00 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Which git server should be the default <developerConnection> ?
> This is used by "mvn release:prepare" in the release procedure.
>
>
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh
Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories;
editing straight in GitHub!
Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!
I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
RE: Taverna git repos moved to GitBox/GitHub
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
Just realised that I wasn’t a member of the ASF GitHub org. I tried setting up via gitbox but I get stuck at the “MFA Status” part where it tells me to add GitHub id to my id.apache.org page and wait for an email. I thought I did that years ago. Is this something that we have to do again?
Cheers,
Ian
Sent from Mail for Windows 10
From: Ian Dunlop
Sent: 18 January 2019 11:53
To: dev@taverna.incubator.apache.org
Subject: RE: Taverna git repos moved to GitBox/GitHub
Hello,
Sounds a good option to me Stian 😊. I tend to use ssh for all my GitHub repos.
Cheers,
Ian
Sent from Mail for Windows 10
From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub
On Mon, 14 Jan 2019 11:06:00 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Which git server should be the default <developerConnection> ?
> This is used by "mvn release:prepare" in the release procedure.
>
>
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh
Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories;
editing straight in GitHub!
Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!
I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
RE: Taverna git repos moved to GitBox/GitHub
Posted by Ian Dunlop <ia...@gmail.com>.
Hello,
Sounds a good option to me Stian 😊. I tend to use ssh for all my GitHub repos.
Cheers,
Ian
Sent from Mail for Windows 10
From: Stian Soiland-Reyes
Sent: 17 January 2019 23:27
To: dev@taverna.incubator.apache.org
Subject: Re: Taverna git repos moved to GitBox/GitHub
On Mon, 14 Jan 2019 11:06:00 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Which git server should be the default <developerConnection> ?
> This is used by "mvn release:prepare" in the release procedure.
>
>
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh
Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories;
editing straight in GitHub!
Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!
I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
Re: Taverna git repos moved to GitBox/GitHub
Posted by Stian Soiland-Reyes <st...@apache.org>.
On Mon, 14 Jan 2019 11:06:00 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Which git server should be the default <developerConnection> ?
> This is used by "mvn release:prepare" in the release procedure.
>
>
> [ ] gitbox.apache.org https
> [ ] GitHub https
> [x] GitHub ssh
Not hearing much (I guess it's not a thing to have strong opinions on!)
I went for the above option and updated the remaining repositories;
editing straight in GitHub!
Also updated build jobs in https://builds.apache.org/view/taverna/
to check from gitbox, so apologies for all the automated emails
that then came all at once!
I think only thing remaining now is to see when we get a pull request if
the email notifications work as before.
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718
Re: Taverna git repos moved to GitBox/GitHub
Posted by Stian Soiland-Reyes <st...@apache.org>.
On Wed, 9 Jan 2019 15:37:11 +0000, Stian Soiland-Reyes <st...@apache.org> wrote:
> Thanks to Ian, we have now migrated the Taverna Git repositories
> We can now write to either gitbox.apache.org or the github.com
> repositories.
To make "mvn release:" still work I have updated
scm/developerConnection in pom.xml as
https://github.com/apache/incubator-taverna-maven-parent/blob/master/pom.xml#L438
Which git server should be the default <developerConnection> ?
This is used by "mvn release:prepare" in the release procedure.
Reload https://taverna.incubator.apache.org/download/code/ and see
dropdown box for the various options:
gitbox https://gitbox.apache.org/repos/asf/incubator-taverna-maven-parent.git
https https://github.com/apache/incubator-taverna-maven-parent.git
ssh git@github.com:apache/incubator-taverna-maven-parent.git
(git:// is read-only)
To avoid repeated password entry during Maven release, then for https
(either server) you will need to configure git to remember the
credentials:
https://reference.apache.org/committer/git#committersgettingstarted
(same as before, just different server name)
The GitHub ssh option can alternatively work with ssh client keys
for password-less acccess:
https://help.github.com/articles/connecting-to-github-with-ssh/
In this case you will need to configure your GitHub account
with each ssh key per machine you need commit access from.
If you have set a passphrase to encrypt the local key you will need to
run "ssh-agent bash" and then "ssh-add" first to unlock.
My suggestion is to use the GitHub ssh option as it is my favourite
over fiddling with stored passwords, but there are arguments against:
* https password can be stored securely in OSX keychain
* We should not rely on third-party github.com during release prep, but
use AFS's server
* ssh-keys can be tricky to generate and (if they have empty
pass-phrase) insecure if stored on an unencrypted file system
Which option can we go for? Note a vote, just give your opinion if any:
[ ] gitbox.apache.org https
[ ] GitHub https
[ ] GitHub ssh
--
Stian Soiland-Reyes
https://orcid.org/0000-0001-9842-9718