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

Workflow #99

Merged
merged 4 commits into from
Aug 12, 2021
Merged

Workflow #99

merged 4 commits into from
Aug 12, 2021

Conversation

ABHAY0O7
Copy link
Contributor

Implemented Gradle build to Github actions.

Now the Github Actions will check for correct gradle build on ubuntu-latest before merging a PR
From now github will look for malicious PR on gradle module
@sonarcloud
Copy link

sonarcloud bot commented Jul 28, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@ABHAY0O7
Copy link
Contributor Author

Hii @tdurieux
When you will merge this PR, the plugin will be ready for community use.
So, I want you to publish this plugin to the maven repository.
I am not doing this because this is more precisely a community action 😅 , which requires some experience, also while publishing the plugin, maven will ask for the credentials of the repository owner, which I don't have, so better any community member performs this action.
Also before publishing the plugin to the maven repository you need to build the Gradle module, in a specified format so that the test doesn't get failed. Follow these steps :

  • First, run mvn clean install in the project's root directory of the project to install the required dependencies of the Gradle module.
  • Then run gradle clean build -x test to exclude the test in the first build because test resources require the plugin that they will found neither in the maven repository nor in the local repository.
  • Then run gradle publishToMavenLocal to install the plugin in the local repository.
  • Then again run gradle clean build to ensure that the tests are running without any errors.
  • Then the plugin will be ready to be published on the maven repository.

When you are done with this, ping me, and I will update the README for the depclean Gradle plugin usage as required.
Until then, I will be continuing my next task. 😄

Best,
Abhay

@tdurieux
Copy link
Contributor

I, unfortunately, don't have the permissions to push to maven repository. We will need to wait @cesarsotovalero.

@ABHAY0O7
Copy link
Contributor Author

I, unfortunately, don't have the permissions to push to maven repository. We will need to wait @cesarsotovalero.

No problem we can do it later. 😄
Until then you can merge these PRS and I will update the README soon.

@ABHAY0O7 ABHAY0O7 changed the title Workflow Workflow (2) Aug 6, 2021
@tdurieux tdurieux merged commit c7556f0 into ASSERT-KTH:master Aug 12, 2021
@ABHAY0O7 ABHAY0O7 deleted the workflow branch August 12, 2021 18:51
@ABHAY0O7 ABHAY0O7 changed the title Workflow (2) Workflow Aug 12, 2021
@ABHAY0O7 ABHAY0O7 mentioned this pull request Aug 13, 2021
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

2 participants