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

Replace Travis CI process with GitHub Actions #264

Closed
Sancretor opened this issue Jun 21, 2021 · 0 comments · Fixed by #263 or #279
Closed

Replace Travis CI process with GitHub Actions #264

Sancretor opened this issue Jun 21, 2021 · 0 comments · Fixed by #263 or #279
Labels
done This issue was solved but not merged in master enhancement New feature or request
Milestone

Comments

@Sancretor
Copy link
Contributor

Is your feature request related to a problem? Please describe.

As of now, the project uses Travis CI to implement its CI process.
But Travis CI workers are limited in free plan, and we are limited in some functionalities.
In order to improve our processes, we would like to use GitHub Actions instead.

Describe the solution you'd like

The CI/CD process should consists in these steps :

  • Checkout code, build, tests, and analyze quality with SonarCloud

  • If it's a push on master branch :

    • Check if a milestone is completed (nb issues > 0, nb closed issues > 0, nb open issues = 0)
    • If any, close it
    • Then create a tag and a GitHub Release with issues from this milestone, depending on labels
    • Add the generated JAR file in the Release
@Sancretor Sancretor added the enhancement New feature or request label Jun 21, 2021
@Sancretor Sancretor added this to the 4.0.0 milestone Jun 21, 2021
@Sancretor Sancretor linked a pull request Jun 21, 2021 that will close this issue
11 tasks
@Sancretor Sancretor added the done This issue was solved but not merged in master label Jun 23, 2021
@Sancretor Sancretor mentioned this issue Aug 27, 2021
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
done This issue was solved but not merged in master enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant