> 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 ( https://www.jenkins.io/doc/book/pipeline/) as it's a pretty core concept of Jenkins these days. If in this specific case \o/ is there anything that could be done to improve this discoverability for you? On Mon, Sep 12, 2022 at 12:02 PM Karl Henselin <[email protected]> wrote: > > 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 UTC-5 [email protected] > wrote: > >> 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 new plugin via archetype, and then >> comparing pom and other files. >> >> On Fri, Sep 9, 2022 at 11:21 AM 'Jesse Glick' via Jenkins Developers < >> [email protected]> wrote: >> >>> On Fri, Sep 9, 2022 at 1:13 PM Karl Henselin <[email protected]> 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, but I can't >>>> understand the logs to know what might be wrong. >>>> >>> >>> `verify-ci-status` fails, because there is no CI status—you have no >>> `Jenkinsfile`. >>> >>> -- >>> 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/CANfRfr0dJb684HVsg1ak%3DAmEkpQxnbvs%2B%3DTtkuqdqWapz1Jxxw%40mail.gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0dJb684HVsg1ak%3DAmEkpQxnbvs%2B%3DTtkuqdqWapz1Jxxw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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/31d08e6c-d804-491b-9201-ff3566abb552n%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/31d08e6c-d804-491b-9201-ff3566abb552n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CAG%3D_DuuZX9BcNvDNkK9zL%3DkRaJ6VA6AHAXfjhhX0Cd-TGhvLGA%40mail.gmail.com.
