Taking this discussion, what about including *optional* JCasC dependency to
Jenkins Test Harness
Jenkins Performance Test Framework supports JCasC rules, and we want to
make it accessible to users.
Her is the ongoing pull
request:
https://github.com/jenkinsci/jenkins-test-harness/pull/135/files#r290641674
I see two possible options:
- Keep the JCasC code in the PR as is
- Move the JCasC code to the Configuration-as-Code plugin codebase
- Taking ongoing activities like
https://github.com/jenkinsci/configuration-as-code-plugin/pull/908 ,
and it might make sense to introduce a new module for JCasC test tools
WDYT?
On Wednesday, June 5, 2019 at 3:51:31 PM UTC+2, Jesse Glick wrote:
>
> On Wed, Jun 5, 2019 at 3:33 AM Oleg Nenashev <[email protected]
> <javascript:>> wrote:
> > we would need to integrate PCT directly into Jenkins Core pipeline.
> > I had a pull request for that (
> https://github.com/jenkinsci/jenkins/pull/3438), but it was stalled.
> Maybe we could revisit it.
>
> +1, this would benefit core stability broadly.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/f663aab5-dbc5-4a7e-af41-0063053f070a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
