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

Remove/replace Shipkit #410

Closed
nipafx opened this issue Jan 18, 2021 · 9 comments · Fixed by #419
Closed

Remove/replace Shipkit #410

nipafx opened this issue Jan 18, 2021 · 9 comments · Fixed by #419

Comments

@nipafx
Copy link
Member

nipafx commented Jan 18, 2021

Shipkit is deprecated and the GitHub project is archived. They write:

"One Shipkit Gradle plugin to rule them all" approach has proven hard to maintain for the team. We are converted Shipkit into a narrow set of small libraries (design note). Several customers, inclusing Mockito project have already migrated.

We need to investigate whether there is already a replacement ("We are converted" is an unfortunate mistake because it could be "have converted" or "are converting") and then possibly migrate to it. This may also fix #246.

On a side note: Our version of Shipkit uses a deprecated GitHub API that stops working in May. It was fixed, though, so this could be solved by updating Shipkit.

@Michael1993
Copy link
Member

I guess it's 'have converted' because 'Several customers inclusing Mockito project have already migrated'.

Maybe we should just copy Mockito? 🤷

@aepfli
Copy link
Member

aepfli commented Jan 18, 2021

Oh cool, I will take a look tomorrow evening

@Michael1993
Copy link
Member

Updating Shipkit is already 'in-progress' because dependabot opened #400.

@slawekjaranowski
Copy link
Contributor

Now Shipkit is split to new separate projects:
https://github.com/shipkit/shipkit-auto-version
https://github.com/shipkit/shipkit-changelog
Those project should be used

@slawekjaranowski
Copy link
Contributor

If nobody is working on it, I can try do it in a few days.
Please assign me.

@slawekjaranowski
Copy link
Contributor

and PR #419

@nipafx
Copy link
Member Author

nipafx commented Feb 1, 2021

I've just got a mail from GitHub (full text below) that they revoked my read-only OAuth token that we used for ShipKit. I was a bit surprised at first - after all, what's the harm in sharing a read-only token? Only thing I could come up with was that other people could use it to circumvent rate-limiting. Either way, we need a new way to implement this because I assume future tokens would share the same fate (sooner or later).

@aepfli Was there a reason why this token was not also passed in as an environment variable?

@slawekjaranowski First of all, hi! 👋🏾 Thanks for taking up this task - it may take a few days before I get to look at your PR, but that doesn't change that it is highly appreciated. Don't forget to add yourself to the README as described here. If you haven't already, can you take this opportunity to replace the token with a System environment variable called GH_READ_TOKEN and let me know what permissions it needs, so I can create the token and put it into the variable?

[GitHub] OAuth access token found in commit

Hello nipafx,

We noticed that a valid OAuth, GitHub App or Personal Access Token of yours was committed to a GitHub repository. Disclosing a valid access token would allow other people to interact with GitHub on your behalf, potentially altering data, your contact information, and billing data.

As a precautionary measure, we have revoked the token. You will need to generate a new token for the app to authenticate to GitHub.

Here are a couple of steps you can do to ensure your account security has not been compromised:

The commit in question is at https://github.com/sullis/junit-pioneer/blob/52b010f1de1e03ec6326dd859e9655b15699f854/gradle/shipkit.gradle

Please feel free to contact us at https://github.com/contact if you have any questions or concerns.

Thanks,
GitHub.com

@aepfli
Copy link
Member

aepfli commented Feb 1, 2021

I never ever touched this token :D - would have been a good idea - it is from long time ago, even before our migration to Github actions.

@slawekjaranowski
Copy link
Contributor

mentioned token will be remove in my PR

slawekjaranowski added a commit to slawekjaranowski/junit-pioneer that referenced this issue Feb 4, 2021
slawekjaranowski added a commit to slawekjaranowski/junit-pioneer that referenced this issue Feb 4, 2021
slawekjaranowski added a commit to slawekjaranowski/junit-pioneer that referenced this issue Feb 4, 2021
slawekjaranowski added a commit to slawekjaranowski/junit-pioneer that referenced this issue Feb 9, 2021
@Michael1993 Michael1993 moved this from Next up to In progress in Exploring Io Feb 23, 2021
@nipafx nipafx linked a pull request Feb 28, 2021 that will close this issue
14 tasks
Exploring Io automation moved this from In progress to Done Feb 28, 2021
nipafx pushed a commit that referenced this issue Feb 28, 2021
Migrate to new Shipkit plugins (#410 / #419)

Shipkit is deprecated and the GitHub project[1] is archived. They
write:

> "One Shipkit Gradle plugin to rule them all" approach has proven
> hard to maintain for the team. We [have] converted Shipkit into a
> narrow set of small libraries (design note[2]). Several customers,
> inclu[d]ing Mockito project have already migrated.

More preecisely, Shipkit was split into these projects:

* shipkit-auto-version[3]
* shipkit-changelog[4]
* shipkit-github-release (no source on GitHub?)

This change updates the build accordingly.

Closes: #410
Maybe solves: #256 (can't be determined without a release build)
PR: #419

[1]: https://github.com/mockito/shipkit
[2]: https://github.com/mockito/shipkit/blob/master/docs/design-specs/future-shipkit.md
[3]: https://github.com/shipkit/shipkit-auto-version
[4]: https://github.com/shipkit/shipkit-changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

4 participants