-
-
Notifications
You must be signed in to change notification settings - Fork 182
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] gh package snapshots... #5596
Conversation
from CI (hopefully)
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 existing repo should remain, you can add the additional one beside it.
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.
Great work. Much less changes than anticipated. Is the snapshot already downloadable somewhere?
Quality Gate passedIssues Measures |
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.
This needs a bit more work as it breaks some things and has some unnecessary things too.
@@ -1228,13 +1239,24 @@ | |||
<enabled>true</enabled> | |||
</snapshots> | |||
</pluginRepository> | |||
<pluginRepository> |
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.
This is not needed as there are no plugins that we publish.
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.
@duncdrum was this needed for snapshots of the sub-projects to be published to the registry?
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.
Cool!
@@ -1228,13 +1239,24 @@ | |||
<enabled>true</enabled> | |||
</snapshots> | |||
</pluginRepository> | |||
<pluginRepository> |
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.
@duncdrum was this needed for snapshots of the sub-projects to be published to the registry?
from CI (hopefully)
The previous SNAPSHOT repo hasn't seen any traffic for over a year. This automates release snapshots to GitHub on push events on develop.
We could make the step, run only after tests have passed (as they should always be green on develop anyway) but that would mean that every time the OWASP dependency check times out, we won't publish artefacts. So I decided against it. What do others think?
This will also not publish artefacts from PRs by design, but this could be adjusted.
close #5592