Nothing in the logs? Maybe you developed it against an newer version than where you deploy? Le 8 juin 2016 5:17 PM, "Daniel Mueller" <[email protected]> a écrit :
> Hi, > > > > I developed a plugin and was able to test it with hpi:run but when I > install it on our test Jenkins server, create a new Job and want to add a > build step, the plugin is not listed in the list of selectable build steps. > However, it seems to install just fine, because when I look into the log, I > can see that the plugin was installed successful, I am also able to see it > in the list of installed Plugins. > > > > Any idea what this could be? > > > > > > Mit freundlichen Grüßen / Kind Regards > > Daniel Mueller > ________________________________________________ > *OSTHUS GmbH* > Eisenbahnweg 9 - 11 > Eingang TH 6 > 52068 Aachen > > T +49 241-94314-232 > F +49 241-94314-19 > [email protected] > www.osthus.com > > LinkedIn <https://www.linkedin.com/company/osthus> Twitter > <https://twitter.com/OSTHUS> Youtube > <https://www.youtube.com/user/OsthusCompany> > > > > Handelsniederlassung: 52068 Aachen > Register: Amtsgericht Aachen, HRB 6398 > Geschäftsführer: Dr. Torsten Osthus, Wolfgang Colsman, Andreas Mohr > ________________________________________________ > Der Inhalt dieser E-Mail ist ausschließlich für den bezeichneten > Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail > oder dessen Vertreter sein sollten, so beachten Sie bitte, dass jede Form > der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder Weitergabe des > Inhalts dieser E-Mail unzulässig ist. Wir bitten Sie, sich in diesem Fall > mit dem Absender der E-Mail in Verbindung zu setzen. > ________________________________________________ > The information contained in this email is intended solely for the > addressee. Access to this email by anyone else is unauthorized. If you are > not the intended recipient, any form of disclosure, reproduction, > distribution or any action taken or refrained from in reliance on it, is > prohibited and may be unlawful. Please notify the sender immediately. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Robert Sandell > *Sent:* Mittwoch, 8. Juni 2016 17:09 > *To:* [email protected] > *Subject:* Re: Jenkins Variables > > > > No, the environment variables are passed along to each step's perform > method, and set as environment to each build's spawned sub-process to the > agent. > > > > On Wed, Jun 8, 2016 at 2:37 PM, Gilad Baruchian <[email protected]> > wrote: > > As I understand, the way to define variables in a jenkins job is to user > environment variables injection (variables I define in the job and when i > execute a build jenkins set them as windows environment variables). > > Can it be a problem if i run 2 jobs at the same time that have the same > variable names? wouldn't they override each other? > > -- > 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/37385289-f860-4fa3-aa71-3e0e1aaf3a80%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/37385289-f860-4fa3-aa71-3e0e1aaf3a80%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > > > -- > > Robert Sandell > > *Software Engineer* > > *CloudBees Inc.* > > -- > 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/CALzHZS3ZoUR2tE5OVgK2jaECZibHM2bnpOOFNcVzsbR4ctmnrQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3ZoUR2tE5OVgK2jaECZibHM2bnpOOFNcVzsbR4ctmnrQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- > 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/4DD3B9ED217122499DEC2BCA4FAD36A5BC0DDE40%40win10004.member.osthus.de > <https://groups.google.com/d/msgid/jenkinsci-dev/4DD3B9ED217122499DEC2BCA4FAD36A5BC0DDE40%40win10004.member.osthus.de?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CANWgJS49SHN5rrmyFNQo3%3DxQ1dzWQfYLNFgA7%2BhbjETreSQwAA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
