On Thu, Sep 15, 2022 at 7:52 AM Karl Henselin wrote:
> I didn't know that github had a jenkins action, which apparently it does,
> or something causes it to find a jenkinsfile and know that means to run
> some github actions.
>
No, these things are decoupled. ci.jenkins.io notices the
I don't use Jenkins, github, or github actions at my job, so I hadn't heard
of a jenkinsfile before this discussion.
I don't see it mentioned in the documentation about how to set up ci/cd.
I would maybe note that jenkinsfile is used on
https://www.jenkins.io/doc/developer/publishing/releasing-cd/
> I didn't know I needed a Jenkinsfile, or what it was for :)
Just for my curiosity, as a plugin maintainer, do you not know what a
jenkinsfile is for in general? or specifically in this context for your
plugin?
If in general, I would recommend reviewing the pipeline docs (
Thanks so much all of you for your help!
I didn't know I needed a Jenkinsfile, or what it was for :)
I see that step running now when I make pull requests, and I think that CD
will work too.
I wouldn't have gotten it without your help!
Thanks,
Karl
On Friday, September 9, 2022 at 3:09:01 PM
Looks like your plugin is pretty old. You may want to look through the
archetypes repo to see what other files you should bring in (like
incrementals)
https://github.com/jenkinsci/archetypes/blob/master/common-files/Jenkinsfile
is the standard jenkinsfile though
I would recommend generating a
On Fri, Sep 9, 2022 at 1:13 PM Karl Henselin wrote:
> I followed the CD automation guide for Jenkins plugins, and I think that I
> was successful with all the steps.
> However, when I make a pull request, it never releases a new version.
> I tried running the CD job with debug logging turned on,
I followed the CD automation guide for Jenkins plugins, and I think that I
was successful with all the steps.
However, when I make a pull request, it never releases a new version.
I tried running the CD job with debug logging turned on, but I can't
understand the logs to know what might be
