Problem with Pipeline Snippet Generation about violation-comments-to-stash-plugin HOT 20 CLOSED

Looking at the auto-generated documentation, I think the issue might be with this parameter:

violationConfigs Array/List: org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class org.jenkinsci.plugins.jvctb.config.ViolationConfig

from violation-comments-to-stash-plugin.

Where do you find the auto generated documentation? :)

Den 9 aug. 2016 07:41 skrev "Daniel Capo Sobral" [email protected]:

Looking at the auto-generated documentation, I think the issue might be
with this parameter:

violationConfigs
Array/List:
org.kohsuke.stapler.NoStaplerConstructorException: There's no
@DataBoundConstructor on any constructor of class
org.jenkinsci.plugins.jvctb.config.ViolationConfig

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#13 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAa1E0cQWZurJXx8FKLVJWnyAe1eFTbfks5qeBMFgaJpZM4Jfu1m
.

from violation-comments-to-stash-plugin.

https://jenkins.url/pipeline-syntax/html

Where jenkins.url is the base URL of your Jenkins server.

Oh, and then you have to scroll down to step, and, on step, scroll down to this plugin, though I suppose you just want to know where that documentation is. :)

from violation-comments-to-stash-plugin.

Does not work for me.

from violation-comments-to-stash-plugin.

The job-dsl-plugin also mentions such an api viewer. But that one also gives me 404.

http://localhost:8080/jenkins/plugin/job-dsl/api-viewer

But you are probably right, I'll add the annotation.

from violation-comments-to-stash-plugin.

Ok, that's strange. I can get to that link (well, a similar link prefixed by the job) by going to a pipeline job, entering its configuration, clicking the "Pipeline Syntax" link below the Script/Script Path box, which opens something like [this]https://www.dropbox.com/s/2dma0fa0dfjbrgl/Screenshot%202016-08-08%2023.59.49.png?dl=0) to me, and then I click on the Step Reference link.

Or, in other words, you can find it from the Snippet Generator page.

from violation-comments-to-stash-plugin.

I tried just adding the annotation. Then the configuration cannot be saved using the configuration GUI... so its not a quick fix. But I'll have a look later today.

from violation-comments-to-stash-plugin.

I was using to old Jenkins version for the job-dsl-plugin to work. Now I see the docs being generated.

I made a release with the annotation now, hopefully it will solve your issue.

from violation-comments-to-stash-plugin.

Did 1.19 get pulled down? I saw it earlier today, but now that I can bring Jenkins down for upgrade, it isn't there anymore.

from violation-comments-to-stash-plugin.

No it should still be there.

Den 10 aug. 2016 06:15 skrev "Daniel Capo Sobral" <[email protected]

:

Did 1.19 get pulled down? I saw it earlier today, but now that I can bring
Jenkins down for upgrade, it isn't there anymore.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#13 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAa1EyefSqW5A6sJqCpkbvT6b4DXk5Glks5qeVBVgaJpZM4Jfu1m
.

from violation-comments-to-stash-plugin.

Ok, I updated, and the auto-generated doc looks fine, but the snippet generator still just gives me step <object of type org.jenkinsci.plugins.jvctb.ViolationsToBitbucketServerRecorder>.

from violation-comments-to-stash-plugin.

I made a new release now. And this time I actually tested it myself =) So 1.20 should hopefully do it!

from violation-comments-to-stash-plugin.

See the README for examples.

from violation-comments-to-stash-plugin.

That worked, though now I get Jenkins has not been started, or was already shut down and nothing happens, but that also happened on a Maven style build, so it's not pipeline-related.

from violation-comments-to-stash-plugin.

Do you think that is related to this plugin?

from violation-comments-to-stash-plugin.

Yes, it always appear right after "Found 0 violations from ViolationConfig
[reporter=ANDROIDLINT, pattern=]", and there's no output (or action) from
the notifier about creating the comment on Bitbucket.

On 11 August 2016 at 06:28, Tomas Bjerre [email protected] wrote:

Do you think that is related to this plugin?

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#13 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAInF45UYlbDWRaX6kHt24eNX6dDNdPOks5qexV6gaJpZM4Jfu1m
.

Daniel C. Sobral

I travel to the future all the time.

from violation-comments-to-stash-plugin.

What version of Jenkins do you use? I use 2.7.

from violation-comments-to-stash-plugin.

I may have found whats wrong here. I released 1.21. It may fix you problem.

I also added the exact JenkinsFile I use for testi g to the readme.

from violation-comments-to-stash-plugin.

Jenkins 2.17. Curiously, it looked like I had gotten a NPE when I omitted the unused reporters, but I didn't look into that as it was simple to just specify everything (which the snippet generator does by default). I'll try 1.21 tonight, and if it doesn't work, I'll get a ticket for that.

I've changed my pipeline to make sure the message was related to this plugin, and it is.

from violation-comments-to-stash-plugin.

Ok, I traced the other issue. And I can confirm that the plugin is working
with Pipeline fine now, thanks.

On 11 August 2016 at 13:41, Tomas Bjerre [email protected] wrote:

I may have found whats wrong here. I released 1.21. It may fix you problem.

I also added the exact JenkinsFile I use for testi g to the readme.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#13 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAInF4NTQTMXS2DyBVmMw0xlgSvqP5Mxks5qe3rbgaJpZM4Jfu1m
.

Daniel C. Sobral

I travel to the future all the time.

from violation-comments-to-stash-plugin.