Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use https instead of git #63

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

programbeginnerTW
Copy link
Contributor

use https protocol instead of git protocol because Github is deprecating git protocol

Submitter checklist

use https protocol instead of git protocol because Github is deprecating git protocol
@damianszczepanik
Copy link
Member

Share the announcement about it

@programbeginnerTW
Copy link
Contributor Author

programbeginnerTW commented Jul 24, 2023

@damianszczepanik I've created a new post here !

Greetings!

Copy link

@MarkEWaite MarkEWaite left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the proposed change, but as far as I can tell, the change is unnecessary.

The transition from git protocol to https protocol is needed when the protocol is declared as git://. That transition is needed because GitHub no longer supports the unauthenticated git:// protocol. Read the GitHub blog post for more details.

This is proposing to change the protocol from ssh:// to https://. While that change is not harmful, it is not consistent with the title of the pull request and does not provide significant benefit in functionality.

An example of the cases where a transition from git:// to https:// is included in the Jenkins tutorial

@damianszczepanik
Copy link
Member

Recently I had problems because of invalid protocol https://github.com/jenkinsci/sidebar-link-plugin/pull/63/files - the problem occurs only during release goal but not at the compile/test/verification stage

@MarkEWaite
Copy link

Recently I had problems because of invalid protocol https://github.com/jenkinsci/sidebar-link-plugin/pull/63/files - the problem occurs only during release goal but not at the compile/test/verification stage

Thanks for the clarification. The plugin archetype uses https, so no objections from me that this plugin uses https. When I generated an empty plugin from the archetype, the scm section looked like this:

    <connection>scm:git:https://github.com/${gitHubRepo}</connection>
    <developerConnection>scm:git:https://github.com/${gitHubRepo}</developerConnection>
    <tag>${scmTag}</tag>
    <url>https://github.com/${gitHubRepo}</url>

Anything that brings plugins closer to the syntax used by the plugin archetype is great for me.

pom.xml Outdated
@@ -97,7 +97,7 @@
</description>

<scm>
<connection>scm:git:ssh://git@github.com/${gitHubRepo}.git</connection>
<connection>scm:git:https://git@github.com/${gitHubRepo}.git</connection>
Copy link

@MarkEWaite MarkEWaite Jul 24, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The username portion of the URL is not included in the plugin archetype. The .git suffix is not included in the connection either. Optionally may want to remove those two differences so that the differences between the plugin and the archetype are reduced.

Suggested change
<connection>scm:git:https://git@github.com/${gitHubRepo}.git</connection>
<connection>scm:git:https://github.com/${gitHubRepo}</connection>

@damianszczepanik
Copy link
Member

Since this can be tested only during the release process I will accept only configuration that was proven during the release, eg https://github.com/damianszczepanik/maven-cucumber-reporting/blob/master/pom.xml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants