Closed ruspl-afed closed 4 years ago
CI is ok, isn't it?
Yes, it works now. May be we can retire Travis.
You mean to remove the .yml file?
Yes. I would say "and change repository settings" but I suppose there is nothing to change there as it was never working.
@ilg-ul please have a look on README in my fork - build status works good https://github.com/ruspl-afed/eclipse-plugins/
The Jenkins job is not CI, I trigger it only when I want the result published in the builds folder, so I guess the badge should not point to it, but to the GitHub Actions.
I would say "and change repository settings" but I suppose there is nothing to change there as it was never working.
It worked before the migration.
There is still a web hook pointing to Travis, should I remove it?
The Jenkins job is not CI, I trigger it only when I want the result published in the builds folder, so I guess the badge should not point to it, but to the GitHub Actions.
Done
I would say "and change repository settings" but I suppose there is nothing to change there as it was never working.
It worked before the migration.
There is still a web hook pointing to Travis, should I remove it?
Yes, I would stick to GitHub actions - at the moment it is the best choice for GitHub
Great, thank you!
If we find a solution to enable stats for the p2 repo, I think we can consider to release 5.1.2.
.travis.yml removed, and the webhook deleted.
Update fork