-
Notifications
You must be signed in to change notification settings - Fork 0
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
feature: use configuration as dependency #23
Conversation
Not sure, if we should stick to GitHub Packages. Maybe there is a more simpler approach. |
name = "inspectit-gepard-config" | ||
url = uri("https://maven.pkg.github.com/inspectIT/inspectit-gepard-config") | ||
credentials { | ||
username = project.findProperty("gpr.inspectit.gepard.user") ?: System.getenv("GITHUB_ACTOR") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the config-repo you only implemented the getenv() approach.
Should you also include the project.findProperty() case there?
credentials {
username = System.getenv("GITHUB_ACTOR")
password = System.getenv("GITHUB_TOKEN")
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The project.findProperty() is missing in the config-repo, since we only use the maven-publish task with the TechnicalUser there. The TechnicalUser is configured via env-properties.
Quality Gate passedIssues Measures |
No description provided.